Hi Troels,
I would now like to talk about the concept drawn in
http://wiki.nmr-relax.com/File:Git_development.png. I may have missed
the point of this figure at first - the use of Github.
I would like to start by saying that Github is an interesting concept,
but that is not where relax development belongs. Open source projects
require far more infrastructure - the repository is only one small
part of the project. What is required is a full software hosting
facility. This is provided by Sourceforge, GNU Savannah, Gna!, etc.
Such open source infrastructure is not provided by Github. And they
have never pretended that they are a replacement for such
infrastructure. Github is a different concept. Due to over a decade
of emails, bug reports, support requests, news stories, and the
management of tasks, it will not be easy to shift away from the Gna!
infrastructure. There are a huge number of links in the mailing list
archives and elsewhere that break. It could nevertheless be done.
But shifting to Github is not a solution - there are no mailing lists,
tasks, new reporting, etc. That is why git is supported by
Sourceforge and Savannah (and likely Gna! at some point in the
future).
I have no problem if you find a way of using Github to work with
relax. Github does have some nice features. If you can use this to
push commits back to the subversion repository, once you have full
commit access, that would be great. But to ask the relax developers
to set up Github accounts and shift development to Github, just to be
able to work in a familiar environment, that is a bit much. A
different solution is needed, one where you push back to svn. As
relax is a relatively small project, in terms of developers, then
there will be no need for pull requests. For relax, the shared
repository model would be best. All developers will be able push
their code, whether in svn or git.
Regards,
Edward
On 24 July 2013 01:54, Troels Emtekær Linnet <tlinnet@xxxxxxxxx> wrote:
Hi relax developers.
I would like to suggest yet another development possibility by using Git.
Motivation:
Subversion needs an online repository, to store each commits.
Subsequent calls to svn diff > patch will generate the difference
according to the last revision.
Therefore the development at the moment require to:
* make some lines of code
* make a path file and a commit message
* use the support tracker to upload patch and commit message
wait for acceptance
wait for commit to official repository
then do an svn update
then return to point 1
This takes time, and require that repository maintainer is online.
If the above scheme is not followed, the patch files will come out of sync.
I suggest to introduce yet another development possibility by using Git.
I do not suggest to shift away from the GNA! infrasctructure,
I merely suggest to use the powers of Git, to collaborate on a feature
development, before
releasing a patch for review and commit to SVN repository.
This is maintained by a server, who tracks the relax-commit messages at
http://www.mail-archive.com/relax-commits@xxxxxxx/
That server translates the history, and commits to github.
Here a range of developers can pull the latest changes.
Make feature branches. Share those branches.
Make edits online. Use android/iphone apps.
Work on trains/planes etc. Allowing offline commits.
When the feature is ready, easily make a patch file, and upload
to the GNA trackers.
The patch file contains all the commit messages, and
changes between each commit.
That should make it easy to review, and comment on.
Git also allow to squash commits and rewrite commits.
A feature highly appreciated, based on the review comments.
I have made a wiki page, from where we can start discussing.
Here I tried to make an image of my idea.
I am very skilled in MS paint. :-)
http://wiki.nmr-relax.com/Git_development
Best
Troels Emtekær Linnet
_______________________________________________
relax (http://www.nmr-relax.com)
This is the relax-devel mailing list
relax-devel@xxxxxxx
To unsubscribe from this list, get a password
reminder, or change your subscription options,
visit the list information page at
https://mail.gna.org/listinfo/relax-devel
Re: Suggested faster development with Git, keeping GNA infrastructure