And where is the public discussion? Is there any public discussion at all? This is the first public message I've seen so far, and my email on the libposix-development mailing list (the very first message there!) has been ignored so far.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
While you don't accept that the project is still in the planning stage, I'll keep answering the same thing to you. ;-)
We have 2 forums for general public and 1 mailing list for developers. All of those are public. SF SMTP server seems to be delaying mail delivery for many hours, however.
I have your code here, thanks for the help. I need you to relicense _each file_ under the BSD license (which is equivalent to the MIT license). The directory structure will be different, to accomodate the needs of platform independence, modularity and others. Here's a preliminary INDEX file, for appreciation (from now on, such discussion must go on libposix-development):
README - the main file explaining what libposix is
mandatory/ - Consists of all the mandatory parts of POSIX that are able to
be implemented in standard ISO C and don't need to be
optimized.
optional/ - Consists of all the optional parts of POSIX that are able to
be implemented in standard ISO C and don't need to be
optimized (empty for now).
system/ - Consists of all the mandatory and optional parts of POSIX
that need to be implemented in assembly and don't need to be
optimized. Only the kernel interfaces are expected to be here.
There should be a subdirectory for every operating system
suported here.
compiler/ - Consists of all the mandatory and optional parts of POSIX
that require compiler support to be written (so that this code
is "compiler specific").
optimized/ - Consists of all the mandatory and optional parts of POSIX that
could potentially be optimized whenever possible or be handled
by custom operations in the compiler. This is the only place
that may be a mess of C, assembly, compiler specific
extensions, ifdefs, etc. Note that most optimizations are
actually responsibility of the compiler. This directory
must only contain code that requires custom anotations,
or the compiler will be unable to optimize it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> While you don't accept that the project is still in the planning stage, I'll keep answering the same thing to you. ;-)
It's not like I don't accept anything, it's just that I have to keep nagging you over and over again in order to get _any_ information. A behind-the-doors initial planning phase isn't something that creates a lot of initial trust. Also, I think that in the beginning, not too much time should be spent on planning, because in the "end", everything is going to be different, anyway. First designs usually don't work out as intended.
> SF SMTP server seems to be delaying mail delivery for many hours, however.
Greylisting, probably?
> I need you to relicense _each file_ under the BSD license (which is equivalent to the MIT license).
If it's equivalent, then why should I relicense it? Which of the BSD licenses? 2, 3 or 4 clause? Please bear in mind that the MIT/X Consortium license is "link-compatible" with all variations of the BSD license, so I don't see any problem that would make a relicense necessary.
> The directory structure will be different, [...]
Of course. This was merely a very simple example to "provoke" at least some reaction. ;-)
> from now on, such discussion must go on libposix-development
I fully agree.
Regards,
Andreas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has any actual work been done on this?
We're still in the planning stage. There are still a couple of things to deal with before writing code, but I hope to upload "Hello world" soon. :-)
Who is "we"? And why is this discussion not public?
By "we" I mean anyone who is part of the project. The current member list is in the "Summary" page. This is a public list.
And where is the public discussion? Is there any public discussion at all? This is the first public message I've seen so far, and my email on the libposix-development mailing list (the very first message there!) has been ignored so far.
While you don't accept that the project is still in the planning stage, I'll keep answering the same thing to you. ;-)
We have 2 forums for general public and 1 mailing list for developers. All of those are public. SF SMTP server seems to be delaying mail delivery for many hours, however.
I have your code here, thanks for the help. I need you to relicense _each file_ under the BSD license (which is equivalent to the MIT license). The directory structure will be different, to accomodate the needs of platform independence, modularity and others. Here's a preliminary INDEX file, for appreciation (from now on, such discussion must go on libposix-development):
README - the main file explaining what libposix is
mandatory/ - Consists of all the mandatory parts of POSIX that are able to
be implemented in standard ISO C and don't need to be
optimized.
optional/ - Consists of all the optional parts of POSIX that are able to
be implemented in standard ISO C and don't need to be
optimized (empty for now).
system/ - Consists of all the mandatory and optional parts of POSIX
that need to be implemented in assembly and don't need to be
optimized. Only the kernel interfaces are expected to be here.
There should be a subdirectory for every operating system
suported here.
compiler/ - Consists of all the mandatory and optional parts of POSIX
that require compiler support to be written (so that this code
is "compiler specific").
optimized/ - Consists of all the mandatory and optional parts of POSIX that
could potentially be optimized whenever possible or be handled
by custom operations in the compiler. This is the only place
that may be a mess of C, assembly, compiler specific
extensions, ifdefs, etc. Note that most optimizations are
actually responsibility of the compiler. This directory
must only contain code that requires custom anotations,
or the compiler will be unable to optimize it.
> While you don't accept that the project is still in the planning stage, I'll keep answering the same thing to you. ;-)
It's not like I don't accept anything, it's just that I have to keep nagging you over and over again in order to get _any_ information. A behind-the-doors initial planning phase isn't something that creates a lot of initial trust. Also, I think that in the beginning, not too much time should be spent on planning, because in the "end", everything is going to be different, anyway. First designs usually don't work out as intended.
> SF SMTP server seems to be delaying mail delivery for many hours, however.
Greylisting, probably?
> I need you to relicense _each file_ under the BSD license (which is equivalent to the MIT license).
If it's equivalent, then why should I relicense it? Which of the BSD licenses? 2, 3 or 4 clause? Please bear in mind that the MIT/X Consortium license is "link-compatible" with all variations of the BSD license, so I don't see any problem that would make a relicense necessary.
> The directory structure will be different, [...]
Of course. This was merely a very simple example to "provoke" at least some reaction. ;-)
> from now on, such discussion must go on libposix-development
I fully agree.
Regards,
Andreas