On 28.10.2007, at 18:21, Roland Weber wrote:

...
I'm not so sure about the 4th parapgraph: the first part is implicit
anyway (adoption), the second part is fine but sounds a bit strange -
dunno, I guess the board will have questions here, but it probably isn't a show-stopper, so best is to leave it as it is and wait on feedback...

What it means is: we won't start writing our own applications, but we'll adopt applications from elsewhere, even if it is beyond the scope of the "low level components" that are our core business. The second part means
"we're not going to compete with Tomcat, Jetspeed or the likes".

Yep, understood - 1st part would be covered by the 1st paragraph already and 2nd part isn't really necessary though I can understand the reasoning (in light of the previous discussions).

I believe the reference to applications in the first paragraph is very
general, this one is meant to limit the scope. But the phrasing is rather coming from the other way, as if there was no mentioning of applications
in the first paragraph, and the scope is extended in the fourth.

Yep, it seems to be contradictory (it isn't really); though what I wanted to express is that this is common practice with ASF TLPs without explicit mentioning in the original proposal (e.g. compare to other TLPs which also adopt projects, either developed at the ASF or coming in from the Incubator).

Suggestions for improvements are welcome. Maybe we can drop it altogether,
but I feel the scope should have some kind of restriction somewhere.

Anyway, as said, feel free to leave as is, or simply drop - it's pretty clear but useless IMHO :-)

...
10th paragraph should mention both artifacts of the two prior
paragrahps

I wrote it as a reference to the subproject, which at Jakarta is
responsible for both artifacts. It is now changed to reference
both artifacts instead of the subproject.

Ok, I think it's more clear now.

Also, most of the previous proposals (not all!) had the following
paragraph:

"RESOLVED, that the initial Apache HttpComponents Project be and hereby
is tasked with the creation of a set of bylaws intended to encourage
open development and increased participation in the
Apache HttpComponents Project; and be it further"

Creating bylaws... sounds scary :-) I'll leave it to you to find the
appropriate place for putting in that paragraph.

Hehe, yes, required for a TLP, e.g. just something like:

http://jakarta.apache.org/site/management.html
http://ant.apache.org/bylaws.html
http://httpd.apache.org/dev/guidelines.html
...

But to be honest I think we can leave out that paragraph; as said only a subset of the previous proposals had it and it also isn't in the Incubator template.

Cheers,
Erik


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to