The interest around the BPEL implementation in Agila has mostly moved to Ode
and the workflow part isn't evolving so declaring the project as dormant
sounds fair enough. As for the policy, wouldn't it be possible to do a two
step thing? Like:
1. Make svn read-only and the mailing-list subscriber only.
2. If nobody shows up after something like a couple of month, just shut down
everything.
Sending a warning on the mailing-lists could be appropriate too. I can take
care of whatever is necessary for Agila if needed, I'm still hanging around
here :)
Thanks,
Matthieu.
On 7/17/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Garrett Rooney wrote:
> FWIW, It's merely the lack of a clue as to what needs to be changed
> that's kept me from closing down lucene4c.
That, and Agila and a couple of others, prompted my e-mail.
> > I'd suggest that the PMC declare a project as dormant, with the effect
being
> > that we set the SVN ACL to read-only. If people want to wake the
project
> > up, we can change the ACL.
So no debate on this?
> > I'm not sure what would be best for the mailing list.
> > ... Or do we just turn them off, with a bounce notice
> > that people interested in resurrecting the project
> > contact us on [EMAIL PROTECTED]
> Personally, I'd be in favor of closing the lists down
So along the lines of above?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
