On pondělí 14. srpna 2017 17:31:00 CEST Greg Sutcliffe wrote: > Hi all, > > This went fairly quiet, but we all seem largely in agreement. I'll > draft something up for the website and send a PR tomorrow. I had a few > side questions though: > > On Wed, 2017-07-19 at 10:13 +0200, Marek Hulán wrote: > > In general +1. I'm not sure if official policy changes anything, > > probably does not do any harm either > > Indeed, and helps us to remember to add maintainers when bringing a > plugin into the GitHub org. > > > It would be great if someone went over all plugins under theforeman > > org on github, found projects with single owner and ask the owner to > > extend the list. Or someone scritped a simple check so we would > > avoid this situation in future. I think what Dmitri described > > is fair and should become a common practice for new repos/gems in our > > org. > > Is there a way to view that info on Rubygems? I can't see it on the gem > pages themselves, is there an API I've missed?
I can see it on gem page, e.g. at https://rubygems.org/gems/foreman_chef search for OWNERS. There's just me. This is how to get this info through curl curl https://rubygems.org/api/v1/gems/foreman_chef/owners.json see http://guides.rubygems.org/rubygems-org-api/#owner-methods for more details. -- Marek > > On Tue, 2017-07-18 at 16:28 +0200, Daniel Lobato Garcia wrote: > > +1 to this, I am stuck with foreman-docker where I want to give > > publish > > What's blocking you? Who owns the gem? > > Regards > Greg -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
