Abandoned plugins under theforeman github org

Development
#1

Hello there

thanks to Tomer and Timo, we were able to fix most of plugins after
FactoryGirl was renamed to FactoryBot, see [1] for current status. As part of
that, I found two plugins where we didn't get any response and they seem
abandoned. Would it make sense to remove them from the foreman org on github
and perhaps remove their jenkins jobs or even redmine projects? Do you know
about any other abandoned plugin?

The plugins:

rundeck [2] - last commit 12 Jul 2016
pipeline [3] - last commit 21 Sep 2016, author confirms it's no longer
maintained [4]

[1] https://pad-katello.rhcloud.com/p/factory_bot_update
[2] https://github.com/theforeman/foreman_host_rundeck/
[3] https://github.com/theforeman/foreman_pipeline
[4] https://github.com/theforeman/foreman_pipeline/pull/
74#issuecomment-341057533

Thanks

··· -- Marek
#2

Hi,
foreman_pipeline was already removed from packaging repo, I have no
objections against removing it from Redmine, Jenkins and Foreman org on
Github as it hasn't been updated in a year.

O.

··· On Tue, Nov 7, 2017 at 5:44 PM, Marek Hulán wrote:

Hello there

thanks to Tomer and Timo, we were able to fix most of plugins after
FactoryGirl was renamed to FactoryBot, see [1] for current status. As part
of
that, I found two plugins where we didn’t get any response and they seem
abandoned. Would it make sense to remove them from the foreman org on
github
and perhaps remove their jenkins jobs or even redmine projects? Do you know
about any other abandoned plugin?

The plugins:

rundeck [2] - last commit 12 Jul 2016
pipeline [3] - last commit 21 Sep 2016, author confirms it’s no longer
maintained [4]

[1] https://pad-katello.rhcloud.com/p/factory_bot_update
[2] https://github.com/theforeman/foreman_host_rundeck/
[3] https://github.com/theforeman/foreman_pipeline
[4] https://github.com/theforeman/foreman_pipeline/pull/
74#issuecomment-341057533

Thanks

–
Marek

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

#3

… i would not remove it from the github org. There are even more abandoned plugins there. I would not delete the code, maybe somebody wants to start work on them again.

I would mark them as unmaintained in the repo description, remove the jenkins jobs and remove them from packaging.

Timo

#4

+1 of marking as unmaintained, but keeping around

– Ivan

··· On Wed, Nov 8, 2017 at 12:04 PM, Timo Goebel wrote: > ... i would not remove it from the github org. There are even more abandoned plugins there. I would not delete the code, maybe somebody wants to start work on them again. > > I would mark them as unmaintained in the repo description, remove the jenkins jobs and remove them from packaging. > > Timo > > -- > You received this message because you are subscribed to the Google Groups "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.
#5

+1 on just marking it in README and in the github description.

··· On Wed, Nov 08, 2017 at 12:07:43PM +0100, Ivan Necas wrote: >+1 of marking as unmaintained, but keeping around > >-- Ivan > >On Wed, Nov 8, 2017 at 12:04 PM, Timo Goebel wrote: >> ... i would not remove it from the github org. There are even more abandoned plugins there. I would not delete the code, maybe somebody wants to start work on them again. >> >> I would mark them as unmaintained in the repo description, remove the jenkins jobs and remove them from packaging.
#6

+1 from me too. I can make those changes as an Org owner if need be.

Greg

··· On 08/11/17 11:12, Ewoud Kohl van Wijngaarden wrote: > +1 on just marking it in README and in the github description.