On 06/29/2013 05:15 PM, Charles Steinkuehler wrote: > Tier 3) Everyone else. It is currently difficult to "elegantly" share > any updates with others. I can very easily clone git.linuxcnc.org to > my box and make some changes, but then what? Do I post a patch to the > mailing list (ignored and/or easily lost)? Do I open my local git > repository to use by others (hard to setup, has security implications, > and assumes that in addition to crafting a fix/update for LinuxCNC I'm > also a network admin capable of safely running a public service on the > internet)? Do I push a clone of the LinuxCNC git repository to > somewhere like github, bitbucket, etc. and point folks to my changes > there (seems a bit presumptuous at the least)? > > Basically, I don't care what happens as long as it is clear (ie: > listed plainly wherever folks are pointed to git.linuxcnc.org to grab > the code) what someone should do if they wish to modify the source and > share their changes with others. This could be as simple as a > statement that it is OK to clone the git repo to github or bitbucket > or where-ever, a separate git area with open push access > (chaos.linuxcnc.org, or perhaps "here_be_dragons"!), or some other > option I haven't thought of.
I think you're describing the same problem that Peter Jensen described at the Hackfest. I think you're both saying that it's unclear how to contribute to the LinuxCNC project. (Well, i think Peter doesn't think it's unclear any more, but maybe other people do that I don't know about.) I pointed Peter at the Wiki page describing exactly this: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Git I think it was Jeff Epler who wrote that, back in... I don't remember when. But the earliest revision that our Wiki remembers is rev 34, from March 2011. So it's been around for a while. We could probably talk about whether that page is as clear as it could be, or as easy to find as it could be, or as detailed as it could be.... But it's there, and i think it describes fairly clearly how to communicate contributions back to the LinuxCNC project. I think the system we describe on that Wiki page is very much the standard way things are generally done in the open source world: Anonymously clone our public git repo, then send us commits in the form of email or a pull request from your public repo (which may be hosted on one of the free git-hosting sites, or on your private server, it doesn't matter). For example, this is how the GM6 driver was contributed back (via github), and i think that process worked very smoothly. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
