search

maestrodev / librarian-puppet

Since 0.9.11.6 this fork is no longer used
MIT License
16 stars 7 forks source link

Submit upstream? #4

Closed patcon closed 11 years ago

patcon commented 11 years ago

Hey! Not to get on your case or anything, but any reason why you guys aren't interested in submitting your patches upstream to @rodjek's repo? I'm just seeing that it's causing a bit of fragmentation as others are starting to use your gem/project too, so I was curious :)

brettporter commented 11 years ago

I believe we have pull requests open for all of the patches already. We're certainly open to any suggestions on how to make them easier to integrate upstream!

patcon commented 11 years ago

Thanks brett! Sorry, I tried searching with github's advanced search, but I guess still figuring it out.. :/

adamcstephens commented 11 years ago

Has anyone approached @rodjek about creating a shared project?

rodjek commented 11 years ago

So, many of the open pull requests were merged in for the 0.9.8 release a few weeks ago. I'm hoping to have a decent block of time in the next couple of weeks to spend getting librarian-puppet up to date with respect to issues & pull requests.

patcon commented 11 years ago

Hm. Good point. Anyone mind if I open an issue in his queues about having a co-maintainer? I'm not thinking myself as I'm mainly into Chef, not Puppet, so I thought I'd double-check that it's ok with y'all

cc: @zifik

zifik commented 11 years ago

We have plans to use it in the workplace and I've already made contributions to get it working behind a proxy. I'm game for helping out, but I'm still new to ruby.

As for the fragmentation, I'll gladly shut down my fork as soon as the features I really need are merged.

carlossg commented 11 years ago

I opened an full pull request at https://github.com/rodjek/librarian-puppet/pull/73