This is the first I've heard of this most recent change. Thanks Snowcrash :)
Cheers James/Hiro On Sun, Oct 25, 2009 at 2:33 PM, Dahlia Trimble <dahliatrim...@gmail.com>wrote: > 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. > > 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. > > -d > > > > On Sun, Oct 25, 2009 at 12:20 PM, Snowcrash Short < > snowcrash.sh...@gmail.com> wrote: > >> I can see that I - or at least my license - has been the topic of >> discussion on the -core mailing list. >> >> I would like to point out, that I have submitted all my patches, advise >> and comments, both in mantis, the mailing list, the wiki and on the IRC >> channel, in the spirit of the contribution guidelines. >> >> Consequently my patches in mantis is released to the public under BSD >> Any comments on the wiki are under creative-commons Attribution-Share >> Alike 2.5, and any advise given on IRC is considered by me to be in the >> public domain. >> >> Whether or not, core will accept patches from me, would be of interest >> to me, since preparing the patches takes time, which I could spend more >> productively otherwise. >> >> Best regards >> ps. I don't want to start any drama, just provide cool facts >> pps. there is no sarcasm intended in this email. >> >> On Tue, 2009-10-20 at 12:27 -0400, Frisby, Adam wrote: >> > 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). >> > >> > There are guidelines for the -core list, which are the following: >> > 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. >> > >> > 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. >> > >> > 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. >> > >> > 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. >> > >> > Last 10 threads on opensim-core: >> > 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.) >> > 2. Mantis stopped sending emails, can someone look? >> > 3. Where is the CS2JK license? >> > 4. Forwarded a request for a spokesperson to speak to someone studying >> OSS communities. >> > 5. Stefan announcing his resignation (cc:'d to dev) >> > 6. JHurliman commit access [redux]? >> > 7. Sean changing projects at IBM, resignation. >> > 8. JHurliman commit access? >> > 9. Request for moderator access on the wiki. >> > 10. Vote on go/no-go on git after trial. >> > >> > Regards, >> > >> > Adam >> > >> > > -----Original Message----- >> > > From: opensim-dev-boun...@lists.berlios.de [mailto:opensim-dev- >> > > boun...@lists.berlios.de] On Behalf Of Dr Scofield >> > > Sent: Tuesday, 20 October 2009 6:50 AM >> > > To: opensim-dev@lists.berlios.de >> > > Subject: Re: [Opensim-dev] The notion of "core" >> > > >> > > >> > > Edward Middleton wrote: >> > > > Teravus Ovares wrote: >> > > >> ... Your argument was that the advent of the distributed source >> > > control >> > > >> system made the 'commit right vote' obsolite, ... >> > > > >> > > > My point was that, with a DVCS, "commit rights" are really just the >> > > > right to release manage the official repository. >> > > >> > > right. opensim-core is just a bunch of dudes and dudettes that manage >> > > the >> > > official repository. >> > > >> > > DrS >> > > >> > > -- >> > > dr dirk husemann ---- virtual worlds research ---- ibm zurich research >> > > lab >> > > SL: dr scofield ---- drscofi...@xyzzyxyzzy.net ---- >> > > http://xyzzyxyzzy.net/ >> > > RL: h...@zurich.ibm.com - +41 44 724 8573 - >> > > http://www.zurich.ibm.com/~hud/ >> > > _______________________________________________ >> > > Opensim-dev mailing list >> > > Opensim-dev@lists.berlios.de >> > > https://lists.berlios.de/mailman/listinfo/opensim-dev >> > _______________________________________________ >> > Opensim-dev mailing list >> > Opensim-dev@lists.berlios.de >> > https://lists.berlios.de/mailman/listinfo/opensim-dev >> >> _______________________________________________ >> Opensim-dev mailing list >> Opensim-dev@lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/opensim-dev >> > > > _______________________________________________ > Opensim-dev mailing list > Opensim-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/opensim-dev > > -- =================================== http://osgrid.org http://del.icio.us/SPQR http://twitter.com/jstallings2 http://www.linkedin.com/pub/5/770/a49
_______________________________________________ Opensim-dev mailing list Opensim-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/opensim-dev
