Hi developers,
I wanted to canvas opinion about moving wxHaskell development from darcs on
code.haskell.org to (git, obviously) on GitHub.
Potential advantages:
- Easier for new committers to commit code
- GitHub provides some pretty decent tools (integrated issue tracker,
particularly)
- Easier handling of the wxWidgets 2.8/2.9 branches. I'm pretty
impressed at the way git does this (and was not impressed by merging Dave
Tapley's darcsden branch back into the code.haskell.org mainline using
darcs - this turned out to be a completely manual operation which was no
fun at all).
Downsides:
- I personally find darcs easier than git, and as Haskellers we should
promote darcs if possible
- Possibly a new tool for old hands to learn
I would say that a move is probably only worthwhile if we think that it
would help to attract new developer to the project.
I have put up an experimental project at
https://github.com/jodonoghue/wxHaskell which gives an idea how the two
branches would look.
One option might be to use wxHaskell as a test case for darcs-bridge, in
which case we could allow commits to darcs or Github, but I'll leave it to
Eric to decide whether darcs bridge is ready for such a use case.
Regards
Jeremy
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
