This is the first I've heard of this most recent change. Thanks Snowcrash :)<div><br></div><div>Cheers</div><div>James/Hiro</div><div><br><br><div class="gmail_quote">On Sun, Oct 25, 2009 at 2:33 PM, Dahlia Trimble <span dir="ltr"><<a href="mailto:dahliatrimble@gmail.com">dahliatrimble@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Patches are *usually* accepted if submitted according to the contribution guidelines. Additionally, patches are evaluated based on the benefits they provide and whether they are considered supportable, and whether they fit into the architectural philosophy for the core code base. Often a core developer would need to take some form of ownership for the patch so the community has some assurance that it can be supported. If the patch submitter works with a core developer to help with these issues and is actively supporting the community via IRC, the mailing list, or the wiki, it improves the likelihood that the patch will be accepted.<div>
<br></div><div>I suspect your best bet would be to develop working relationships with those core developers who are familiar with those parts of the code base which your patch(es) affect(s), and/or core developers who have accepted your past patches.</div>
<div><br></div><div>-d</div><div><br></div><div><br><br><div class="gmail_quote"><div class="im">On Sun, Oct 25, 2009 at 12:20 PM, Snowcrash Short <span dir="ltr"><<a href="mailto:snowcrash.short@gmail.com" target="_blank">snowcrash.short@gmail.com</a>></span> wrote:<br>
</div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I can see that I - or at least my license - has been the topic of<br>
discussion on the -core mailing list.<br>
<br>
I would like to point out, that I have submitted all my patches, advise<br>
and comments, both in mantis, the mailing list, the wiki and on the IRC<br>
channel, in the spirit of the contribution guidelines.<br>
<br>
Consequently my patches in mantis is released to the public under BSD<br>
Any comments on the wiki are under creative-commons Attribution-Share<br>
Alike 2.5, and any advise given on IRC is considered by me to be in the<br>
public domain.<br>
<br>
Whether or not, core will accept patches from me, would be of interest<br>
to me, since preparing the patches takes time, which I could spend more<br>
productively otherwise.<br>
<br>
Best regards<br>
ps. I don't want to start any drama, just provide cool facts<br>
pps. there is no sarcasm intended in this email.<br>
<br>
On Tue, 2009-10-20 at 12:27 -0400, Frisby, Adam wrote:<br>
> OK, since I have a nagging feeling no-one read Teravus's original post in this long thread (and with a hope of putting this to rest).<br>
><br>
> There are guidelines for the -core list, which are the following:<br>
> If the topic can be discussed on dev, it should be. Core's scope is limited to issues related to commit access, licensing, money, server administrator and other 'meta' issues relating to running the project. No-one on dev is missing out on any development or code related discussion. Membership is limited to active committers (min. one commit in last 6 mo to maintain commit access & ML access). 'Votes' are done on consensus with any committer having full veto power.<br>
><br>
> That said, DSVC is not a panacea to programming. Git is better than SVN at merging files; but it's still not excellent - Melanie puts in a ton of work each week in managing our various branches and bringing them together, conflicts and all.<br>
><br>
> Until someone realises that DSVC needs to include language specific patterns (such as refactorings), there is still going to need to be a core project at the middle making sure the base works, and still a bunch more people who can update branches & forks accordingly. Otherwise maintaining distributions becomes an effort in trying to hit moving targets.<br>
><br>
> Since it'll probably satisfy some of the people who are curious about what is discussed on core, here's the last 10 threads. (this represents probably 3-5 months of traffic, as I said before, it's low volume.) - as you can see, they all do fall into the guidelines listed above.<br>
><br>
> Last 10 threads on opensim-core:<br>
> 1. Snowcrash's contributions - whether his eclectic license on SCEngine affects contributions to opensim master and specifically whether to accept patches relating to it. (Licensing.)<br>
> 2. Mantis stopped sending emails, can someone look?<br>
> 3. Where is the CS2JK license?<br>
> 4. Forwarded a request for a spokesperson to speak to someone studying OSS communities.<br>
> 5. Stefan announcing his resignation (cc:'d to dev)<br>
> 6. JHurliman commit access [redux]?<br>
> 7. Sean changing projects at IBM, resignation.<br>
> 8. JHurliman commit access?<br>
> 9. Request for moderator access on the wiki.<br>
> 10. Vote on go/no-go on git after trial.<br>
><br>
> Regards,<br>
><br>
> Adam<br>
><br>
> > -----Original Message-----<br>
> > From: <a href="mailto:opensim-dev-bounces@lists.berlios.de" target="_blank">opensim-dev-bounces@lists.berlios.de</a> [mailto:<a href="mailto:opensim-dev-" target="_blank">opensim-dev-</a><br>
> > <a href="mailto:bounces@lists.berlios.de" target="_blank">bounces@lists.berlios.de</a>] On Behalf Of Dr Scofield<br>
> > Sent: Tuesday, 20 October 2009 6:50 AM<br>
> > To: <a href="mailto:opensim-dev@lists.berlios.de" target="_blank">opensim-dev@lists.berlios.de</a><br>
> > Subject: Re: [Opensim-dev] The notion of "core"<br>
> ><br>
> ><br>
> > Edward Middleton wrote:<br>
> > > Teravus Ovares wrote:<br>
> > >> ... Your argument was that the advent of the distributed source<br>
> > control<br>
> > >> system made the 'commit right vote' obsolite, ...<br>
> > ><br>
> > > My point was that, with a DVCS, "commit rights" are really just the<br>
> > > right to release manage the official repository.<br>
> ><br>
> > right. opensim-core is just a bunch of dudes and dudettes that manage<br>
> > the<br>
> > official repository.<br>
> ><br>
> > DrS<br>
> ><br>
> > --<br>
> > dr dirk husemann ---- virtual worlds research ---- ibm zurich research<br>
> > lab<br>
> > SL: dr scofield ---- <a href="mailto:drscofield@xyzzyxyzzy.net" target="_blank">drscofield@xyzzyxyzzy.net</a> ----<br>
> > <a href="http://xyzzyxyzzy.net/" target="_blank">http://xyzzyxyzzy.net/</a><br>
> > RL: <a href="mailto:hud@zurich.ibm.com" target="_blank">hud@zurich.ibm.com</a> - +41 44 724 8573 -<br>
> > <a href="http://www.zurich.ibm.com/~hud/" target="_blank">http://www.zurich.ibm.com/~hud/</a><br>
> > _______________________________________________<br>
> > Opensim-dev mailing list<br>
> > <a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
> > <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>===================================<br><a href="http://osgrid.org">http://osgrid.org</a><br><a href="http://del.icio.us/SPQR">http://del.icio.us/SPQR</a><br><a href="http://twitter.com/jstallings2">http://twitter.com/jstallings2</a><br>
<a href="http://www.linkedin.com/pub/5/770/a49">http://www.linkedin.com/pub/5/770/a49</a><br>
</div>