On IRC I have recently been talking about how I think it would be
beneficial for our project to move towards github.  In particular, I
think that accepting pull requests via the github web interface may help
bring more first-time contributors to the project, and it would stop
contributions from being overlooked.

As a pilot project, I will begin reviewing pull requests to
https://github.com/jepler/linuxcnc-mirror for at least an hour a week
starting now, and continuing for at least 8 weeks.  Chris Radek has also
volunteered to do review for a similar amount of time.  Pull requests
are public, so anyone can view and comment on them at
https://github.com/jepler/linuxcnc-mirror/pulls and any developer can
merge them via the normal git merge process.

Once we see how the pilot project goes, we can further consider whether
it makes sense to create an official linuxcnc presence on github, to
continue accepting pull requests via linuxcnc-mirror, or to go back to
the old status quo.

Jeff


Sidebar: How does the github workflow work if the official repository
is on git.linuxcnc.org?

To *accept* a pull request, a developer with push access to
git.linuxcnc.org has to 'git remote add' the github repository of the
contributor, 'git pull' the branch, build and test, and 'git push' the
pull request to git.linuxcnc.org.  

Any other operation, such as commenting on a pull request, is done via
the github website (including by their public API)

Using the "merge pull request" button in the github user interface would
appear to work, but the merge would be reverted the next time the
repository is mirrored from git.linuxcnc.org.

Even if this were not the case, relying on the github web interface to
determine that a branch can be automatically merged doesn't mean it will
build and work, so the pull-build-test is a sound idea anyway.

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to