Re: [Radiant] Re: Re: Best event listing extension?
For reference, just as before the switch, not every pull request is accepted to the Radiant core. However, the overarching difference seems to me that anyone can take their own fork and run with it, without needing 'permission'. Sean On Wed, Aug 6, 2008 at 11:53 AM, Marty Haught <[EMAIL PROTECTED]> wrote: >> I'm not saying to not manage your extension's development. But in Git >> the culture of open source collaboration is mildly different. But then >> again, I see your point. I can't wait to see what page_event becomes >> though. Could easily be a core extension once it reaches maturity! > > I'm not offended in the least by all of this. I decided not to accept > Tim's pull request as it would make more work for me and would be > incompatible with how I want to develop my extension. I have zero > issue with his forking my extension and anyone can do the same. > However, to suggest that you should automatically except a pull > request is a bit much. I've no doubt that those that need multi-day > support should go with his fork as it may be a while before I get to > it. > > Cheers, > Marty > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: Best event listing extension?
> I'm not saying to not manage your extension's development. But in Git > the culture of open source collaboration is mildly different. But then > again, I see your point. I can't wait to see what page_event becomes > though. Could easily be a core extension once it reaches maturity! I'm not offended in the least by all of this. I decided not to accept Tim's pull request as it would make more work for me and would be incompatible with how I want to develop my extension. I have zero issue with his forking my extension and anyone can do the same. However, to suggest that you should automatically except a pull request is a bit much. I've no doubt that those that need multi-day support should go with his fork as it may be a while before I get to it. Cheers, Marty ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Re: Best event listing extension?
[EMAIL PROTECTED] wrote: > On Wed, 2008-08-06 at 18:03 +0200, Arik Jones wrote: >> There really is no reason to be a prude about it though. It's open >> source and we should expect no less. I say instead of complaining, >> re-factor the code and release it. That'd seem easier than trying to >> micro-manage each pull request. > > > Easy gents, we're all on the same side here. There is no reason why > Marty shouldn't be able to manage the extension he built. There's also > no reason to hate on Tim for forking it. That's the great thing about > open source, we build on the successes of others. > > I'll probably be using Tim's version of the extension (no offense Marty) > because it has some added functionality that I need. When Marty finds > the time to modify the original extension (time is always in short > supply) I'll probably switch back to his version. I didn't mean to stir > up any ill will that may, or may not, exist between Marty or Tim. Both > of you guys rock. > > > ~Nate I'm not saying to not manage your extension's development. But in Git the culture of open source collaboration is mildly different. But then again, I see your point. I can't wait to see what page_event becomes though. Could easily be a core extension once it reaches maturity! -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
