You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Christopher <ct...@apache.org> on 2017/11/02 20:56:08 UTC
Update README for retired podlings?
Should the Apache Incubator update the README on all retired podlings, to
more clearly indicate their retired status?
For example, from the README at https://github.com/apache/incubator-pirk ,
it's not obvious that the podling is retired.
I know there's a RETIRED.txt file, but that's easily overlooked. I suggest
the Incubator PMC updating the retired projects' README's with an
indication that the podling is retired, perhaps with a link to an
explanation of what that means:
https://incubator.apache.org/guides/retirement.html#what_is_retirement
For example, simply inserting the following line at the top of retired
podlings README's may suffice:
This project is [retired](
https://incubator.apache.org/guides/retirement.html#what_is_retirement)
I don't think this is a big deal, but might be something nice to do.
Another option is to stop mirroring retired podlings to GitHub, but that
just seems mean.
Re: Update README for retired podlings?
Posted by Christopher <ct...@apache.org>.
I just meant "mean" in that it makes it harder for the project to be picked
back up if there's renewed interest. I understand deleting SVN... because
it's still in the history, but I think it's strange if ASF deleted GIT...
because that deletes history. Perhaps just delete the GIT mirror on GitHub?
On Thu, Nov 2, 2017 at 5:07 PM Dave Fisher <da...@comcast.net> wrote:
> Actually when the podling is retired the SVN and or GIT must be deleted.
> It’s mean, but if people cared they could have contributed and kept it
> going.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Nov 2, 2017, at 1:56 PM, Christopher <ct...@apache.org> wrote:
> >
> > Should the Apache Incubator update the README on all retired podlings, to
> > more clearly indicate their retired status?
> >
> > For example, from the README at https://github.com/apache/incubator-pirk
> ,
> > it's not obvious that the podling is retired.
> >
> > I know there's a RETIRED.txt file, but that's easily overlooked. I
> suggest
> > the Incubator PMC updating the retired projects' README's with an
> > indication that the podling is retired, perhaps with a link to an
> > explanation of what that means:
> > https://incubator.apache.org/guides/retirement.html#what_is_retirement
> >
> > For example, simply inserting the following line at the top of retired
> > podlings README's may suffice:
> >
> > This project is [retired](
> > https://incubator.apache.org/guides/retirement.html#what_is_retirement)
> >
> > I don't think this is a big deal, but might be something nice to do.
> > Another option is to stop mirroring retired podlings to GitHub, but that
> > just seems mean.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: Update README for retired podlings?
Posted by Hen <ba...@apache.org>.
On Fri, Nov 3, 2017 at 4:29 AM, Shane Curcuru <as...@shanecurcuru.org> wrote:
> Dave Fisher wrote on 11/2/17 11:13 PM:
> >> On Nov 2, 2017, at 7:06 PM, John D. Ament <jo...@apache.org>
> wrote:
> >>> On Thu, Nov 2, 2017 at 6:17 PM Dave Fisher <da...@comcast.net>
> wrote:
> >>>>> On Nov 2, 2017, at 3:08 PM, sebb <se...@gmail.com> wrote:
>
> >>>>> On 2 November 2017 at 21:07, Dave Fisher <da...@comcast.net>
> wrote:
> ...snip...
> >> I'm not even sure I agree with deleting the websites. It was a project.
> >> Now it's not. That doesn't mean the information should no longer be
> >> available. But not sure the resources need to be covered.
> >
> > Either the IPMC should review the policy or we should ask the board to
> set/confirm the policy for “retired” podlings.
>
> Podlings in incubation are not Apache projects - by definition. They
> are podlings effectively managed within the incubator. So it would be
> best for the IPMC to come up with a specific policy or plan for this,
> vote on it, and then just let the board know "Hey, here's how we're
> going to formally handle retiring podling assets".
>
> Personally, I think it depends on how long the podling was around (i.e.
> how many likely other people were attempting to use the project) and
> what the state of it's IP clearance is. In particular, if IP clearance
> weren't complete, I would vote for deleting the repos, just to ensure
> that we're not distributing (even via source control) IP that the ASF
> isn't assured of having under our license.
>
>
I'd argue that being under our license is not important.
If we have code in our source control that can't be distributed, it should
be deleted (regardless of project). If we have a retired Incubator podling
with code that didn't get sufficiently relicensed from another open source
license, no big deal (provided that's clear).
My vote (unsurprisingly) would be for treating a retired podling the same
way a retired project is treated.
Hen
Re: Update README for retired podlings?
Posted by Shane Curcuru <as...@shanecurcuru.org>.
Dave Fisher wrote on 11/2/17 11:13 PM:
>> On Nov 2, 2017, at 7:06 PM, John D. Ament <jo...@apache.org> wrote:
>>> On Thu, Nov 2, 2017 at 6:17 PM Dave Fisher <da...@comcast.net> wrote:
>>>>> On Nov 2, 2017, at 3:08 PM, sebb <se...@gmail.com> wrote:
>>>>> On 2 November 2017 at 21:07, Dave Fisher <da...@comcast.net> wrote:
...snip...
>> I'm not even sure I agree with deleting the websites. It was a project.
>> Now it's not. That doesn't mean the information should no longer be
>> available. But not sure the resources need to be covered.
>
> Either the IPMC should review the policy or we should ask the board to set/confirm the policy for “retired” podlings.
Podlings in incubation are not Apache projects - by definition. They
are podlings effectively managed within the incubator. So it would be
best for the IPMC to come up with a specific policy or plan for this,
vote on it, and then just let the board know "Hey, here's how we're
going to formally handle retiring podling assets".
Personally, I think it depends on how long the podling was around (i.e.
how many likely other people were attempting to use the project) and
what the state of it's IP clearance is. In particular, if IP clearance
weren't complete, I would vote for deleting the repos, just to ensure
that we're not distributing (even via source control) IP that the ASF
isn't assured of having under our license.
--
- Shane
https://www.apache.org/foundation/marks/resources
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Update README for retired podlings?
Posted by Dave Fisher <da...@comcast.net>.
Sent from my iPhone
> On Nov 2, 2017, at 7:06 PM, John D. Ament <jo...@apache.org> wrote:
>
>> On Thu, Nov 2, 2017 at 6:17 PM Dave Fisher <da...@comcast.net> wrote:
>>
>>
>>
>> Sent from my iPhone
>>
>>>> On Nov 2, 2017, at 3:08 PM, sebb <se...@gmail.com> wrote:
>>>>
>>>> On 2 November 2017 at 21:07, Dave Fisher <da...@comcast.net> wrote:
>>>> Actually when the podling is retired the SVN and or GIT must be
>> deleted. It’s mean, but if people cared they could have contributed and
>> kept it going.
>>>
>>> Huh?
>>>
>>> The website is deleted, but AFAIK SVN/Git is just made read-only.
>>
>> I guess I may be wrong and misremembering something Greg Stein wrote in
>> the past.
>>
>
> I'm not even sure I agree with deleting the websites. It was a project.
> Now it's not. That doesn't mean the information should no longer be
> available. But not sure the resources need to be covered.
Either the IPMC should review the policy or we should ask the board to set/confirm the policy for “retired” podlings.
Regards,
Dave
>
>
>>
>> Regards,
>> Dave
>>
>>>
>>>> Regards,
>>>> Dave
>>>>
>>>> Sent from my iPhone
>>>>
>>>>> On Nov 2, 2017, at 1:56 PM, Christopher <ct...@apache.org> wrote:
>>>>>
>>>>> Should the Apache Incubator update the README on all retired podlings,
>> to
>>>>> more clearly indicate their retired status?
>>>>>
>>>>> For example, from the README at
>> https://github.com/apache/incubator-pirk ,
>>>>> it's not obvious that the podling is retired.
>>>>>
>>>>> I know there's a RETIRED.txt file, but that's easily overlooked. I
>> suggest
>>>>> the Incubator PMC updating the retired projects' README's with an
>>>>> indication that the podling is retired, perhaps with a link to an
>>>>> explanation of what that means:
>>>>> https://incubator.apache.org/guides/retirement.html#what_is_retirement
>>>>>
>>>>> For example, simply inserting the following line at the top of retired
>>>>> podlings README's may suffice:
>>>>>
>>>>> This project is [retired](
>>>>> https://incubator.apache.org/guides/retirement.html#what_is_retirement
>> )
>>>>>
>>>>> I don't think this is a big deal, but might be something nice to do.
>>>>> Another option is to stop mirroring retired podlings to GitHub, but
>> that
>>>>> just seems mean.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Update README for retired podlings?
Posted by "John D. Ament" <jo...@apache.org>.
On Thu, Nov 2, 2017 at 6:17 PM Dave Fisher <da...@comcast.net> wrote:
>
>
> Sent from my iPhone
>
> > On Nov 2, 2017, at 3:08 PM, sebb <se...@gmail.com> wrote:
> >
> >> On 2 November 2017 at 21:07, Dave Fisher <da...@comcast.net> wrote:
> >> Actually when the podling is retired the SVN and or GIT must be
> deleted. It’s mean, but if people cared they could have contributed and
> kept it going.
> >
> > Huh?
> >
> > The website is deleted, but AFAIK SVN/Git is just made read-only.
>
> I guess I may be wrong and misremembering something Greg Stein wrote in
> the past.
>
I'm not even sure I agree with deleting the websites. It was a project.
Now it's not. That doesn't mean the information should no longer be
available. But not sure the resources need to be covered.
>
> Regards,
> Dave
>
> >
> >> Regards,
> >> Dave
> >>
> >> Sent from my iPhone
> >>
> >>> On Nov 2, 2017, at 1:56 PM, Christopher <ct...@apache.org> wrote:
> >>>
> >>> Should the Apache Incubator update the README on all retired podlings,
> to
> >>> more clearly indicate their retired status?
> >>>
> >>> For example, from the README at
> https://github.com/apache/incubator-pirk ,
> >>> it's not obvious that the podling is retired.
> >>>
> >>> I know there's a RETIRED.txt file, but that's easily overlooked. I
> suggest
> >>> the Incubator PMC updating the retired projects' README's with an
> >>> indication that the podling is retired, perhaps with a link to an
> >>> explanation of what that means:
> >>> https://incubator.apache.org/guides/retirement.html#what_is_retirement
> >>>
> >>> For example, simply inserting the following line at the top of retired
> >>> podlings README's may suffice:
> >>>
> >>> This project is [retired](
> >>> https://incubator.apache.org/guides/retirement.html#what_is_retirement
> )
> >>>
> >>> I don't think this is a big deal, but might be something nice to do.
> >>> Another option is to stop mirroring retired podlings to GitHub, but
> that
> >>> just seems mean.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: Update README for retired podlings?
Posted by Dave Fisher <da...@comcast.net>.
Sent from my iPhone
> On Nov 2, 2017, at 3:08 PM, sebb <se...@gmail.com> wrote:
>
>> On 2 November 2017 at 21:07, Dave Fisher <da...@comcast.net> wrote:
>> Actually when the podling is retired the SVN and or GIT must be deleted. It’s mean, but if people cared they could have contributed and kept it going.
>
> Huh?
>
> The website is deleted, but AFAIK SVN/Git is just made read-only.
I guess I may be wrong and misremembering something Greg Stein wrote in the past.
Regards,
Dave
>
>> Regards,
>> Dave
>>
>> Sent from my iPhone
>>
>>> On Nov 2, 2017, at 1:56 PM, Christopher <ct...@apache.org> wrote:
>>>
>>> Should the Apache Incubator update the README on all retired podlings, to
>>> more clearly indicate their retired status?
>>>
>>> For example, from the README at https://github.com/apache/incubator-pirk ,
>>> it's not obvious that the podling is retired.
>>>
>>> I know there's a RETIRED.txt file, but that's easily overlooked. I suggest
>>> the Incubator PMC updating the retired projects' README's with an
>>> indication that the podling is retired, perhaps with a link to an
>>> explanation of what that means:
>>> https://incubator.apache.org/guides/retirement.html#what_is_retirement
>>>
>>> For example, simply inserting the following line at the top of retired
>>> podlings README's may suffice:
>>>
>>> This project is [retired](
>>> https://incubator.apache.org/guides/retirement.html#what_is_retirement)
>>>
>>> I don't think this is a big deal, but might be something nice to do.
>>> Another option is to stop mirroring retired podlings to GitHub, but that
>>> just seems mean.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Update README for retired podlings?
Posted by sebb <se...@gmail.com>.
On 2 November 2017 at 21:07, Dave Fisher <da...@comcast.net> wrote:
> Actually when the podling is retired the SVN and or GIT must be deleted. It’s mean, but if people cared they could have contributed and kept it going.
Huh?
The website is deleted, but AFAIK SVN/Git is just made read-only.
> Regards,
> Dave
>
> Sent from my iPhone
>
>> On Nov 2, 2017, at 1:56 PM, Christopher <ct...@apache.org> wrote:
>>
>> Should the Apache Incubator update the README on all retired podlings, to
>> more clearly indicate their retired status?
>>
>> For example, from the README at https://github.com/apache/incubator-pirk ,
>> it's not obvious that the podling is retired.
>>
>> I know there's a RETIRED.txt file, but that's easily overlooked. I suggest
>> the Incubator PMC updating the retired projects' README's with an
>> indication that the podling is retired, perhaps with a link to an
>> explanation of what that means:
>> https://incubator.apache.org/guides/retirement.html#what_is_retirement
>>
>> For example, simply inserting the following line at the top of retired
>> podlings README's may suffice:
>>
>> This project is [retired](
>> https://incubator.apache.org/guides/retirement.html#what_is_retirement)
>>
>> I don't think this is a big deal, but might be something nice to do.
>> Another option is to stop mirroring retired podlings to GitHub, but that
>> just seems mean.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Update README for retired podlings?
Posted by Dave Fisher <da...@comcast.net>.
Actually when the podling is retired the SVN and or GIT must be deleted. It’s mean, but if people cared they could have contributed and kept it going.
Regards,
Dave
Sent from my iPhone
> On Nov 2, 2017, at 1:56 PM, Christopher <ct...@apache.org> wrote:
>
> Should the Apache Incubator update the README on all retired podlings, to
> more clearly indicate their retired status?
>
> For example, from the README at https://github.com/apache/incubator-pirk ,
> it's not obvious that the podling is retired.
>
> I know there's a RETIRED.txt file, but that's easily overlooked. I suggest
> the Incubator PMC updating the retired projects' README's with an
> indication that the podling is retired, perhaps with a link to an
> explanation of what that means:
> https://incubator.apache.org/guides/retirement.html#what_is_retirement
>
> For example, simply inserting the following line at the top of retired
> podlings README's may suffice:
>
> This project is [retired](
> https://incubator.apache.org/guides/retirement.html#what_is_retirement)
>
> I don't think this is a big deal, but might be something nice to do.
> Another option is to stop mirroring retired podlings to GitHub, but that
> just seems mean.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org