This is quite a long thread now so its not that clear what the actual
proposal is now, could you maybe state what the current proposal is?

I think its something like "If a podling is over a year old and not
done a release then retire it". As i've said i don't think thats a
very good rule and doesn't seem like its really been thought through
properly. For example, its kept saying that the podling would go to
the ASF Attic but the Attic is only for TLPs so retired podlings don't
go there.

How about before adding a new rule to the policy page we just try it
with a few of the old podlings first to see what happens and from that
find what sort of rule might work?

   ...ant

On Wed, Jul 9, 2014 at 8:23 AM, Roman Shaposhnik <r...@apache.org> wrote:
> On Tue, Jul 1, 2014 at 11:01 PM, ant elder <ant.el...@gmail.com> wrote:
>> Right, and thats why i don't think a rule like that would be useful.
>
> I still don't quite follow. Are you saying that the rule wouldn't
> be useful, or that incubator -> attic migration wouldn't be?
>
>> If Droids was made to retire the code would be frozen in the attic or
>> forced out to github,
>
> That would be true. But what's the harm in that? The code
> still exists and can be checked out. What we're essentially
> signaling to the outside world is that ASF can no longer
> vouch for the viability of the community around it. Isn't it
> the truth of the matter?
>
>> forced to change its package name
>
> I don't really see any reason to do that for code
> that got moved to that attic. Am I missing something?
>
>> in the code and so probably lose existing users,
>
> Again, why would code lose users? Remember we're talking
> about a situation of no releases here. Presumably those
> users who are comfortable building from the repo would
> just keep doing so. And since there was no release,
> what else is out there for us to worry about?
>
>> and remove all references to apache in  the
>> project and doc and website etc etc. All tons of work which being a small
>> project they'd probably never get done so it would likely be the death of
>> the project.
>
> I see no reason to do any of that for the project that's
> in the attic.
>
>> And for what purpose? To quote one of them from their dev list a couple of
>> months ago: "Going to the attic would suck. It's a solid code base, it's
>> just one of those things that doesn't necessarily need to change much.".
>> The main people in Droids we know and trust, they are ASF members and PMC
>> chairs. We in the Incubator should be helping them graduate not looking for
>> ways to retire the project.
>
> The quote feels a little bit misinformed about the attic/ASF
> policies.
>
> Thanks,
> Roman.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to