Andrew C. Oliver wrote:
>
> If you mean you saved over it, you can easily get the last version back.
no, i mean iw was working solely in preview, and hadn't saved it at all. :-(
i was waiting until it was further along.
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
A
de for new
projects. Incorporates the requirements of the
board, so that new projects can be sure they are
meeting the expectations of the board.
Cheers,
Berin
> From: Rodent of Unusual Size <[EMAIL PROTECTED]>
> Subject: Re: incubator, exit and publication
> Date: 29/09/
On 9/28/03 7:59 AM, "Rodent of Unusual Size" <[EMAIL PROTECTED]> wrote:
> Rodent of Unusual Size wrote:
>>
>> under a draft prototype set of pmc bylaws, probably. i'm
>> working on one now that i should be able to post in a couple
>> of hours.
>
> well, thanks to mozilla crashing, and the wiki
On Sunday, September 28, 2003, at 01:04 AM, Stephen McConnell wrote:
robert burrell donkin wrote:
(sorry stephen i should have probably been clearer.)
i was looking for an official(ish) statement from roy or one of the
other senior (board level) ASF folks.
(i'm happy to take active steps to en
Berin Lautenbach wrote:
>
> Hoping you are aware that we put a strawman together for this here :
>
> http://nagoya.apache.org/wiki/apachewiki.cgi?IncubatorCharterDraft
no, not for the incubator specifically; as a potential template
for any project.
--
#kenP-)}
Ken Coar, Sanagendamgagwedwei
Rodent of Unusual Size wrote:
>
> under a draft prototype set of pmc bylaws, probably. i'm
> working on one now that i should be able to post in a couple
> of hours.
well, thanks to mozilla crashing, and the wiki not treating
'preview' as meaning 'display but don't store even temporarily',
i los
robert burrell donkin wrote:
(sorry stephen i should have probably been clearer.)
i was looking for an official(ish) statement from roy or one of the
other senior (board level) ASF folks.
(i'm happy to take active steps to ensure that ASF policy is enforced
by the jakarta pmc - and any other
robert burrell donkin wrote:
(sorry stephen i should have probably been clearer.)
i was looking for an official(ish) statement from roy or one of the
other senior (board level) ASF folks.
(i'm happy to take active steps to ensure that ASF policy is enforced by
the jakarta pmc - and any other pr
(sorry stephen i should have probably been clearer.)
i was looking for an official(ish) statement from roy or one of the other
senior (board level) ASF folks.
(i'm happy to take active steps to ensure that ASF policy is enforced by
the jakarta pmc - and any other project's i'm involved with - b
robert burrell donkin wrote:
On Friday, September 26, 2003, at 08:13 AM, Roy T. Fielding wrote:
A release requires 3 +1 and a majority of those voting, wherein
the only people allowed to vote are the PMC responsible for that
code. In other words, the usual rules apply -- it is simply harder
to g
On Friday, September 26, 2003, at 08:13 AM, Roy T. Fielding wrote:
A release requires 3 +1 and a majority of those voting, wherein
the only people allowed to vote are the PMC responsible for that
code. In other words, the usual rules apply -- it is simply harder
to get the votes.
just to make sur
Rodent of Unusual Size wrote:
This has not been codified anywhere for the
Incubator. Should I add this into the draft
Charter for the PMC?
under a draft prototype set of pmc bylaws, probably. i'm
working on one now that i should be able to post in a couple
of hours.
Ken,
Hoping you are aware t
Berin Lautenbach wrote:
>
> Is the rule below universal accross the ASF? I
> thought it was up to the PMC of each project on
> how to handle releases of sub-projects.
>
> This has not been codified anywhere for the
> Incubator. Should I add this into the draft
> Charter for the PMC?
under a dr
Nicola Ken Barozzi wrote:
This means that, legally speaking, the Incubator can decide to do
releases and then remove a project, as also can be done with other
projects. Nothing is immutable, again legally speaking.
+1 - so releases are permitted (with caveats of course).
2 the incubator votes p
Roy,
Please do not take this the wrong way, I'm trying to be constructive :>.
One of the things that's been driving me up the wall is quite a few
people telling me "this is the way it must be done because the bylaws
say so". But when I go to the bylaws, I get something much more vague -
namel
Rodent of Unusual Size wrote:
Stephen McConnell wrote:
At the end of the day we need to address the issue of wht rights the
Incubator PMC has to endorce the publication of an artifact generated by
a project prior to the exit of said project from the incubator.
Publication by a Sponoring Entiry
Stephen McConnell wrote:
>
> At the end of the day we need to address the issue of wht rights the
> Incubator PMC has to endorce the publication of an artifact generated by
> a project prior to the exit of said project from the incubator.
> Publication by a Sponoring Entiry is a different subje
Stephhen,
"At the end of the day we need to address the issue of wht rights the
Incubator PMC has to endorce the publication of an artifact generated by
a project prior to the exit of said project from the incubator.
Publication by a Sponoring Entiry is a different subject - but
publication
Stephen,
While you say "Ok - going with Apache tradition - its not the PMC that
makes the
decision of a *release*. Its the committers in the incubator (who
basically represent a bunch of rather non-incubator interest groups). "
In fact while that represents the Jakarta tradition I think it
Roy T. Fielding wrote:
Ok - going with Apache tradition - its not the PMC that makes the
decision of a *release*.
BZZZT. According to the bylaws, the only people authorized to make
decisions
on behalf of the ASF (including the decision to release code to the
general
public) are officers or
HO) responsible for publication -
only because it can override the opinions of the Incuabtor PMC as to
readiness of a technical artifact - as distinct from the readiness of a
community baking a artifact.
Cheers, Steve.
Everything else could almost be case by case.
Cheers,
Berin
From:
Ok - going with Apache tradition - its not the PMC that makes the
decision of a *release*.
BZZZT. According to the bylaws, the only people authorized to make
decisions
on behalf of the ASF (including the decision to release code to the
general
public) are officers or the PMC responsible for the
Roy T. Fielding wrote:
A release requires 3 +1 and a majority of those voting, wherein
the only people allowed to vote are the PMC responsible for that
code. In other words, the usual rules apply -- it is simply harder
to get the votes.
I am kind of surprised that folks think it would be any di
"Roy T. Fielding" <[EMAIL PROTECTED]>
> Subject: Re: incubator, exit and publication
> Date: 26/09/2003 17:13:46
> To: [EMAIL PROTECTED]
>
> A release requires 3 +1 and a majority of those voting, wherein
> the only people allowed to vote are the PMC responsible for that
A release requires 3 +1 and a majority of those voting, wherein
the only people allowed to vote are the PMC responsible for that
code. In other words, the usual rules apply -- it is simply harder
to get the votes.
I am kind of surprised that folks think it would be any different.
Roy
---
be
undertaken until there is sign of that all legal
ownership issues have been covered off.
Everything else could almost be case by case.
Cheers,
Berin
>
> From: Stephen McConnell <[EMAIL PROTECTED]>
> Subject: incubator, exit and publication
> Date: 26/09/2003 16:54:29
&
I'm been following the messages concerning exit criteria and releases
and I see a conflict. If a project is under incubation, then it is not
accepted into Apache and therfore the content that is generating is
simply content under observation - not Apache content. As such, how can
a such a pro
27 matches
Mail list logo
