[IPMC] What to do with retired podling repositories

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[IPMC] What to do with retired podling repositories

Daniel Gruno-2
Hello IPMC and other folks,

We have a big bunch of retired podlings with git repositories on
git-wip-us. As we are working on retiring this service, we need to
address what happens with these old project repositories.

The retired podlings we need to address are:
blur, cmda, concerted, corinthia, cotton, gearpump, gossip, hdt, horn,
htrace, iota, mrql, openaz, pirk, provisionr, quickstep, ripple, s4,
slider, wave

Before February 7th, we at ASF Infra, would love if the incubator could
decide what happens to these repositories, either individually or as a
whole.

Some suggested options are:

1) delete the repositories
2) rename them to incubator-retired-$foo.git
3) Do nothing, but put a note on github etc that they retired.
4) punt it to the attic if possible (you'd have to coordinate with the
Attic PMC then)
5) Something else??

Please talk among yourselves and let Infra know :)

With regards,
Daniel on behalf of ASF Infra.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [IPMC] What to do with retired podling repositories

Myrle Krantz-2
If we can’t name a reason for keeping the data, I’d be inclined to just
delete.  We are not data squirrels.

: o),
Myrle

On Sun, Jan 13, 2019 at 10:15 AM Daniel Gruno <[hidden email]> wrote:

> Hello IPMC and other folks,
>
> We have a big bunch of retired podlings with git repositories on
> git-wip-us. As we are working on retiring this service, we need to
> address what happens with these old project repositories.
>
> The retired podlings we need to address are:
> blur, cmda, concerted, corinthia, cotton, gearpump, gossip, hdt, horn,
> htrace, iota, mrql, openaz, pirk, provisionr, quickstep, ripple, s4,
> slider, wave
>
> Before February 7th, we at ASF Infra, would love if the incubator could
> decide what happens to these repositories, either individually or as a
> whole.
>
> Some suggested options are:
>
> 1) delete the repositories
> 2) rename them to incubator-retired-$foo.git
> 3) Do nothing, but put a note on github etc that they retired.
> 4) punt it to the attic if possible (you'd have to coordinate with the
> Attic PMC then)
> 5) Something else??
>
> Please talk among yourselves and let Infra know :)
>
> With regards,
> Daniel on behalf of ASF Infra.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [IPMC] What to do with retired podling repositories

Sharan Foga
Hi

I am doing some research on incubator projects and the ones that didn't
make it to TLP could be interesting to analyse so I'd be in favour of the
rename rather than a delete for now.

Thanks
Sharan






On Mon, 14 Jan 2019, 07:12 Myrle Krantz <[hidden email] wrote:

> If we can’t name a reason for keeping the data, I’d be inclined to just
> delete.  We are not data squirrels.
>
> : o),
> Myrle
>
> On Sun, Jan 13, 2019 at 10:15 AM Daniel Gruno <[hidden email]>
> wrote:
>
> > Hello IPMC and other folks,
> >
> > We have a big bunch of retired podlings with git repositories on
> > git-wip-us. As we are working on retiring this service, we need to
> > address what happens with these old project repositories.
> >
> > The retired podlings we need to address are:
> > blur, cmda, concerted, corinthia, cotton, gearpump, gossip, hdt, horn,
> > htrace, iota, mrql, openaz, pirk, provisionr, quickstep, ripple, s4,
> > slider, wave
> >
> > Before February 7th, we at ASF Infra, would love if the incubator could
> > decide what happens to these repositories, either individually or as a
> > whole.
> >
> > Some suggested options are:
> >
> > 1) delete the repositories
> > 2) rename them to incubator-retired-$foo.git
> > 3) Do nothing, but put a note on github etc that they retired.
> > 4) punt it to the attic if possible (you'd have to coordinate with the
> > Attic PMC then)
> > 5) Something else??
> >
> > Please talk among yourselves and let Infra know :)
> >
> > With regards,
> > Daniel on behalf of ASF Infra.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [IPMC] What to do with retired podling repositories

Greg Stein-4
In reply to this post by Myrle Krantz-2
If they didn't graduate, then they aren't Apache projects. So as Myrle
says, "what are they doing on our servers?" For the retired podlings, our
copy of their code could be misleading, relative to where it came from, or
where the community may have newly forked it.

Not an Infra opinion,
-g


On Mon, Jan 14, 2019 at 12:12 AM Myrle Krantz <[hidden email]> wrote:

> If we can’t name a reason for keeping the data, I’d be inclined to just
> delete.  We are not data squirrels.
>
> : o),
> Myrle
>
> On Sun, Jan 13, 2019 at 10:15 AM Daniel Gruno <[hidden email]>
> wrote:
>
> > Hello IPMC and other folks,
> >
> > We have a big bunch of retired podlings with git repositories on
> > git-wip-us. As we are working on retiring this service, we need to
> > address what happens with these old project repositories.
> >
> > The retired podlings we need to address are:
> > blur, cmda, concerted, corinthia, cotton, gearpump, gossip, hdt, horn,
> > htrace, iota, mrql, openaz, pirk, provisionr, quickstep, ripple, s4,
> > slider, wave
> >
> > Before February 7th, we at ASF Infra, would love if the incubator could
> > decide what happens to these repositories, either individually or as a
> > whole.
> >
> > Some suggested options are:
> >
> > 1) delete the repositories
> > 2) rename them to incubator-retired-$foo.git
> > 3) Do nothing, but put a note on github etc that they retired.
> > 4) punt it to the attic if possible (you'd have to coordinate with the
> > Attic PMC then)
> > 5) Something else??
> >
> > Please talk among yourselves and let Infra know :)
> >
> > With regards,
> > Daniel on behalf of ASF Infra.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [IPMC] What to do with retired podling repositories

Sharan Foga
Hi Greg

You have a good point and my need is a more of a personal one (rather than
an IPMC one) so if delete is the consensus,  then go for it. I won't hold
it up.

Thanks
Sharan


On Mon, 14 Jan 2019, 11:25 Greg Stein <[hidden email] wrote:

> If they didn't graduate, then they aren't Apache projects. So as Myrle
> says, "what are they doing on our servers?" For the retired podlings, our
> copy of their code could be misleading, relative to where it came from, or
> where the community may have newly forked it.
>
> Not an Infra opinion,
> -g
>
>
> On Mon, Jan 14, 2019 at 12:12 AM Myrle Krantz <[hidden email]> wrote:
>
>> If we can’t name a reason for keeping the data, I’d be inclined to just
>> delete.  We are not data squirrels.
>>
>> : o),
>> Myrle
>>
>> On Sun, Jan 13, 2019 at 10:15 AM Daniel Gruno <[hidden email]>
>> wrote:
>>
>> > Hello IPMC and other folks,
>> >
>> > We have a big bunch of retired podlings with git repositories on
>> > git-wip-us. As we are working on retiring this service, we need to
>> > address what happens with these old project repositories.
>> >
>> > The retired podlings we need to address are:
>> > blur, cmda, concerted, corinthia, cotton, gearpump, gossip, hdt, horn,
>> > htrace, iota, mrql, openaz, pirk, provisionr, quickstep, ripple, s4,
>> > slider, wave
>> >
>> > Before February 7th, we at ASF Infra, would love if the incubator could
>> > decide what happens to these repositories, either individually or as a
>> > whole.
>> >
>> > Some suggested options are:
>> >
>> > 1) delete the repositories
>> > 2) rename them to incubator-retired-$foo.git
>> > 3) Do nothing, but put a note on github etc that they retired.
>> > 4) punt it to the attic if possible (you'd have to coordinate with the
>> > Attic PMC then)
>> > 5) Something else??
>> >
>> > Please talk among yourselves and let Infra know :)
>> >
>> > With regards,
>> > Daniel on behalf of ASF Infra.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
>> >
>> >
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: [IPMC] What to do with retired podling repositories

Daniel Gruno-2
On 1/14/19 12:12 PM, Sharan F wrote:
> Hi Greg
>
> You have a good point and my need is a more of a personal one (rather
> than an IPMC one) so if delete is the consensus,  then go for it. I
> won't hold it up.

If you are doing research on them, and you are (presumably) using Kibble
there, you could just make sure they are scraped before they are
deleted, and you should be fine.

>
> Thanks
> Sharan
>
>
> On Mon, 14 Jan 2019, 11:25 Greg Stein <[hidden email]
> <mailto:[hidden email]> wrote:
>
>     If they didn't graduate, then they aren't Apache projects. So as
>     Myrle says, "what are they doing on our servers?" For the retired
>     podlings, our copy of their code could be misleading, relative to
>     where it came from, or where the community may have newly forked it.
>
>     Not an Infra opinion,
>     -g
>
>
>     On Mon, Jan 14, 2019 at 12:12 AM Myrle Krantz <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         If we can’t name a reason for keeping the data, I’d be inclined
>         to just
>         delete.  We are not data squirrels.
>
>         : o),
>         Myrle
>
>         On Sun, Jan 13, 2019 at 10:15 AM Daniel Gruno
>         <[hidden email] <mailto:[hidden email]>> wrote:
>
>          > Hello IPMC and other folks,
>          >
>          > We have a big bunch of retired podlings with git repositories on
>          > git-wip-us. As we are working on retiring this service, we
>         need to
>          > address what happens with these old project repositories.
>          >
>          > The retired podlings we need to address are:
>          > blur, cmda, concerted, corinthia, cotton, gearpump, gossip,
>         hdt, horn,
>          > htrace, iota, mrql, openaz, pirk, provisionr, quickstep,
>         ripple, s4,
>          > slider, wave
>          >
>          > Before February 7th, we at ASF Infra, would love if the
>         incubator could
>          > decide what happens to these repositories, either
>         individually or as a
>          > whole.
>          >
>          > Some suggested options are:
>          >
>          > 1) delete the repositories
>          > 2) rename them to incubator-retired-$foo.git
>          > 3) Do nothing, but put a note on github etc that they retired.
>          > 4) punt it to the attic if possible (you'd have to coordinate
>         with the
>          > Attic PMC then)
>          > 5) Something else??
>          >
>          > Please talk among yourselves and let Infra know :)
>          >
>          > With regards,
>          > Daniel on behalf of ASF Infra.
>          >
>          >
>         ---------------------------------------------------------------------
>          > To unsubscribe, e-mail:
>         [hidden email]
>         <mailto:[hidden email]>
>          > For additional commands, e-mail:
>         [hidden email]
>         <mailto:[hidden email]>
>          >
>          >
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [IPMC] What to do with retired podling repositories

Sharan Foga
Hi Daniel

Yes I'll be using Kibble so a great suggestion! Sounds like a win-win situation to me :-)

Thanks
Sharan

On 2019/01/14 11:14:26, Daniel Gruno <[hidden email]> wrote:

> On 1/14/19 12:12 PM, Sharan F wrote:
> > Hi Greg
> >
> > You have a good point and my need is a more of a personal one (rather
> > than an IPMC one) so if delete is the consensus,  then go for it. I
> > won't hold it up.
>
> If you are doing research on them, and you are (presumably) using Kibble
> there, you could just make sure they are scraped before they are
> deleted, and you should be fine.
>
> >
> > Thanks
> > Sharan
> >
> >
> > On Mon, 14 Jan 2019, 11:25 Greg Stein <[hidden email]
> > <mailto:[hidden email]> wrote:
> >
> >     If they didn't graduate, then they aren't Apache projects. So as
> >     Myrle says, "what are they doing on our servers?" For the retired
> >     podlings, our copy of their code could be misleading, relative to
> >     where it came from, or where the community may have newly forked it.
> >
> >     Not an Infra opinion,
> >     -g
> >
> >
> >     On Mon, Jan 14, 2019 at 12:12 AM Myrle Krantz <[hidden email]
> >     <mailto:[hidden email]>> wrote:
> >
> >         If we can’t name a reason for keeping the data, I’d be inclined
> >         to just
> >         delete.  We are not data squirrels.
> >
> >         : o),
> >         Myrle
> >
> >         On Sun, Jan 13, 2019 at 10:15 AM Daniel Gruno
> >         <[hidden email] <mailto:[hidden email]>> wrote:
> >
> >          > Hello IPMC and other folks,
> >          >
> >          > We have a big bunch of retired podlings with git repositories on
> >          > git-wip-us. As we are working on retiring this service, we
> >         need to
> >          > address what happens with these old project repositories.
> >          >
> >          > The retired podlings we need to address are:
> >          > blur, cmda, concerted, corinthia, cotton, gearpump, gossip,
> >         hdt, horn,
> >          > htrace, iota, mrql, openaz, pirk, provisionr, quickstep,
> >         ripple, s4,
> >          > slider, wave
> >          >
> >          > Before February 7th, we at ASF Infra, would love if the
> >         incubator could
> >          > decide what happens to these repositories, either
> >         individually or as a
> >          > whole.
> >          >
> >          > Some suggested options are:
> >          >
> >          > 1) delete the repositories
> >          > 2) rename them to incubator-retired-$foo.git
> >          > 3) Do nothing, but put a note on github etc that they retired.
> >          > 4) punt it to the attic if possible (you'd have to coordinate
> >         with the
> >          > Attic PMC then)
> >          > 5) Something else??
> >          >
> >          > Please talk among yourselves and let Infra know :)
> >          >
> >          > With regards,
> >          > Daniel on behalf of ASF Infra.
> >          >
> >          >
> >         ---------------------------------------------------------------------
> >          > To unsubscribe, e-mail:
> >         [hidden email]
> >         <mailto:[hidden email]>
> >          > For additional commands, e-mail:
> >         [hidden email]
> >         <mailto:[hidden email]>
> >          >
> >          >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [IPMC] What to do with retired podling repositories

Daniel Gruno-2
In reply to this post by Daniel Gruno-2
Just a note from infra that we'll need a decision from the IPMC on this
matter no later than February 7th, preferably before :)

With regards,
Daniel.

On 1/13/19 10:14 AM, Daniel Gruno wrote:

> Hello IPMC and other folks,
>
> We have a big bunch of retired podlings with git repositories on
> git-wip-us. As we are working on retiring this service, we need to
> address what happens with these old project repositories.
>
> The retired podlings we need to address are:
> blur, cmda, concerted, corinthia, cotton, gearpump, gossip, hdt, horn,
> htrace, iota, mrql, openaz, pirk, provisionr, quickstep, ripple, s4,
> slider, wave
>
> Before February 7th, we at ASF Infra, would love if the incubator could
> decide what happens to these repositories, either individually or as a
> whole.
>
> Some suggested options are:
>
> 1) delete the repositories
> 2) rename them to incubator-retired-$foo.git
> 3) Do nothing, but put a note on github etc that they retired.
> 4) punt it to the attic if possible (you'd have to coordinate with the
> Attic PMC then)
> 5) Something else??
>
> Please talk among yourselves and let Infra know :)
>
> With regards,
> Daniel on behalf of ASF Infra.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [IPMC] What to do with retired podling repositories

sebb-2-2
In reply to this post by Greg Stein-4
In the past, SVN repos have just been made read-only.
(The intention was to move them to
http://svn.apache.org/viewvc/incubator/RETIRED/ but that never
happened)

I think it would be a mistake to drop the repos.
There's no guarantee that the code is available anywhere else, and it
seems wrong to throw away any effort spent on it at the ASF.

On Mon, 14 Jan 2019 at 10:25, Greg Stein <[hidden email]> wrote:

>
> If they didn't graduate, then they aren't Apache projects. So as Myrle says, "what are they doing on our servers?" For the retired podlings, our copy of their code could be misleading, relative to where it came from, or where the community may have newly forked it.
>
> Not an Infra opinion,
> -g
>
>
> On Mon, Jan 14, 2019 at 12:12 AM Myrle Krantz <[hidden email]> wrote:
>>
>> If we can’t name a reason for keeping the data, I’d be inclined to just
>> delete.  We are not data squirrels.
>>
>> : o),
>> Myrle
>>
>> On Sun, Jan 13, 2019 at 10:15 AM Daniel Gruno <[hidden email]> wrote:
>>
>> > Hello IPMC and other folks,
>> >
>> > We have a big bunch of retired podlings with git repositories on
>> > git-wip-us. As we are working on retiring this service, we need to
>> > address what happens with these old project repositories.
>> >
>> > The retired podlings we need to address are:
>> > blur, cmda, concerted, corinthia, cotton, gearpump, gossip, hdt, horn,
>> > htrace, iota, mrql, openaz, pirk, provisionr, quickstep, ripple, s4,
>> > slider, wave
>> >
>> > Before February 7th, we at ASF Infra, would love if the incubator could
>> > decide what happens to these repositories, either individually or as a
>> > whole.
>> >
>> > Some suggested options are:
>> >
>> > 1) delete the repositories
>> > 2) rename them to incubator-retired-$foo.git
>> > 3) Do nothing, but put a note on github etc that they retired.
>> > 4) punt it to the attic if possible (you'd have to coordinate with the
>> > Attic PMC then)
>> > 5) Something else??
>> >
>> > Please talk among yourselves and let Infra know :)
>> >
>> > With regards,
>> > Daniel on behalf of ASF Infra.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
>> >
>> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]