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

Reply via email to