epics
epics copied to clipboard
railslove
Give gem authors admin write access to the repository
It seems that @railslove removed the authors of this gem from the repository - probably by accident. Sadly nobody @railslove takes care of the maintenance of the gem and has abandoned it.
Please at least transfer ownership of this repository to one of the gem authors.
//cc @tmschndr @stephanpavlovic @bonflintstone
You are right, it should not be like this! I think this happened in some well meant cleanup of our Github organisation. Can you give me a list of people that should have access to this repository @bumi? If anyone feel up to the task of overtaking this project I am also more than happy to facilitate the transfer.
At Railslove we simply do not have the expertise to mainting this project anymore, so we are more than happy to pass this on! Thanks for bringing this up.
thanks @bonflintstone
that would be: @kangguru, @tobischo, me
shall we create a new epics github org for that?
Alright, you all god write access now. I think it's a good idea to create a new organization, though I think for now it should also be ok for this to stay here until someone wants to put in the effort to set it up. If other people need to be added or some other things changed, just ping me.
You might need to check your email @bumi 😉
It seems that clahub.com is simply down atm. For now, I simply made @bumi admin to this repository, so feel free to force-merge the prs you deem worthy.
It has not been reachable for at least the past 2 weeks though.
So not sure if they will come back up?
It seems like it. Are you aware of any decent alternatives? I would think that we still need a way to handle CLAs
I don't think so as you say you can not maintain the code right now. and a license is there: https://github.com/railslove/epics/blob/master/LICENSE.txt
Are there any updates on this?
I'd say if a CLA is required by railslove to be safe when it comes to accepting contributions, then someone from railslove should set it up. It would be much appreciated if that could happen sooner rather than later, as that appears to be blocking all current and potential future contributions.
Additionally it would allow us to more easily carry on with our gained collaborator permissions and deal with incoming issues.
Happy new year everyone!
Just so that this doesn't get lost here: any updates on this?
Hi and happy new year!
It's on our ToDos here at Railslove and we'll give an update soon. Awfully sorry that this takes so long!
Hi @bumi, @tobischo and @kangguru,
we removed clahub and replaced it with cla-assistant.io since handling CLAs is still required.
Again, sorry for taking so long!
Hi @zollillo Excellent, thanks I signed it already so my changes should be good to go
@zollillo @bumi @kangguru How are we going to deal with gem releases of new versions?
Also to raise it here: do we have to maintain the JRuby support? I am having issues getting that to work (lack of experience with JRuby really) and would rather remove it than being stuck maintaining that bit.
I'd be fine with removing JRuby. If somebody needs it maybe they can then contribute and work on those tests?
@kangguru are you ready to do a new release (now with #105 ) ?
Closing this issue now, as the original purpose was achieved. Waiting for a renewed invite to be rubygems maintainer, as I missed it previously (sorry about that)