Re: How do we handle deprecated modules?
On Tue, 2019-01-15 at 15:45 +0100, Bertrand Delacretaz wrote: > On Tue, Jan 15, 2019 at 3:31 PM Stefan Seifert < > sseif...@pro-vision.de> wrote: > > ...as starting point i've created a wiki page: > > https://cwiki.apache.org/confluence/x/VIUCBg ... > > Thank you! I have tweaked it to make it clearer that we will gladly > accept collaborations from other projects on this. > > Once we agree on the feature list we might advertise that page on > dev@community.a.o and/or Twitter to raise interest. As a first step I sent a query on users@infra asking if such features are on a roadmap. Thanks, Robert
Re: How do we handle deprecated modules?
On Tue, 2019-01-15 at 14:31 +, Stefan Seifert wrote: > > I know there are multiple Github-related items that we would to get > > more tooling on: > > > > - archiving repositories > > - github topics > > - disabling Jira integration > > > > It would be great is someone could create a wiki page which lists > > all > > our needs so we can take this to infra and see how we can make this > > happen. It's probably going to take us writing the code - which I > > think > > is entirely possible - but having the items is the first step in > > getting the ball rolling. > > as starting point i've created a wiki page: > https://cwiki.apache.org/confluence/x/VIUCBg > > maybe we can add a note to the "disabling JIRA integration" point, > was not sure about the details on this. Thanks! I added a note and also described the new item about Jenkins/GitHub hooks. Robert
Re: How do we handle deprecated modules?
On Tue, Jan 15, 2019 at 3:31 PM Stefan Seifert wrote: > > ...as starting point i've created a wiki page: > https://cwiki.apache.org/confluence/x/VIUCBg ... Thank you! I have tweaked it to make it clearer that we will gladly accept collaborations from other projects on this. Once we agree on the feature list we might advertise that page on dev@community.a.o and/or Twitter to raise interest. -Bertrand
RE: How do we handle deprecated modules?
>I know there are multiple Github-related items that we would to get >more tooling on: > >- archiving repositories >- github topics >- disabling Jira integration > >It would be great is someone could create a wiki page which lists all >our needs so we can take this to infra and see how we can make this >happen. It's probably going to take us writing the code - which I think >is entirely possible - but having the items is the first step in >getting the ball rolling. as starting point i've created a wiki page: https://cwiki.apache.org/confluence/x/VIUCBg maybe we can add a note to the "disabling JIRA integration" point, was not sure about the details on this. stefan
Re: How do we handle deprecated modules?
On Tue, 2019-01-15 at 14:00 +0100, Bertrand Delacretaz wrote: > On Tue, Jan 15, 2019 at 1:32 PM Carsten Ziegeler < > cziege...@apache.org> wrote: > > That (archiving) sounds like a good option to me... > > I like it as well, but... > > > Stefan Seifert wrote > > > additionally in github there is an option to "archive" a > > > repository [1]... > > > I suppose this can only be done by infra... > > Unless we can contribute code to https://selfserve.apache.org/ that > allows us to do it ourselves, I suppose infra would be reluctant to > have more work related to this. I know there are multiple Github-related items that we would to get more tooling on: - archiving repositories - github topics - disabling Jira integration It would be great is someone could create a wiki page which lists all our needs so we can take this to infra and see how we can make this happen. It's probably going to take us writing the code - which I think is entirely possible - but having the items is the first step in getting the ball rolling. Robert
Re: How do we handle deprecated modules?
On Tue, Jan 15, 2019 at 1:32 PM Carsten Ziegeler wrote: > That (archiving) sounds like a good option to me... I like it as well, but... > Stefan Seifert wrote > > additionally in github there is an option to "archive" a repository [1]... > > I suppose this can only be done by infra... Unless we can contribute code to https://selfserve.apache.org/ that allows us to do it ourselves, I suppose infra would be reluctant to have more work related to this. -Bertrand > > [1] https://help.github.com/articles/archiving-a-github-repository/
Re: How do we handle deprecated modules?
That (archiving) sounds like a good option to me Regards Carsten Stefan Seifert wrote i think as well we should not delete the git repository. adding a badge makes sense. additionally in github there is an option to "archive" a repository [1] - it's then set to readonly for everyone and github displays a label "Archived" in the repository list and a warning message if anything from the repo itself is displayed. if need arise it can be un-archived as well. i suppose this can only be done by infra. stefan [1] https://help.github.com/articles/archiving-a-github-repository/ -Original Message- From: Carsten Ziegeler [mailto:cziege...@apache.org] Sent: Tuesday, January 15, 2019 10:49 AM To: dev@sling.apache.org Subject: How to we handle deprecated modules? Hi with svn we moved deprecated/obsolete modules to the attic How do we handle this now with git? The thread at [1] seems to suggest batches. I personally don't like having git repositories around which should not be used. On the other hand, removing the git repo has some disadvantages as well. WDYT? [1] https://lists.apache.org/thread.html/63719253a3f3659e4e24009e2e8e212a1c9bb7 7fddc696b772d9@%3Cdev.sling.apache.org%3E Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
