Ioannis,
Also see this thread in the Sympy mailing list about how they did the
migration:
https://groups.google.com/forum/#!msg/sympy/3fblubiXUyU/pHTOL3uwKY0J
El 02/10/14 a las #4, Carlos Córdoba escribió:
Hi to everyone,
Thanks for the kind words Steven, and sorry for not saying something
about this before. We discussed about this last week with Sylvain in
person, and agreed this is the best for the project. Spyder is getting
more and more traction lately, so it'd be better to do this now rather
than later, when it could be a lot more painful and disrupting.
However, I don't have time to make this a reality (as you probably
guess). Before migrating the code, I'd like to migrate our issues, so
that we preserve the same numbers referenced in commit messages (which
I use a lot).
I took a look at the test done by Ioannis, and the main problem I saw
is that GoogleCode milestones are not translated as Github ones, just
as labels.That should be fixed :-)
Ioannis, we trust you with this task (unless someone else wants to do
it :-). I think you should use this fork of the project you mentioned
to do the transition:
https://github.com/skirpichev/google-code-issues-migrator/tree/my2
That was the code used by the Sympy guys to do theirs. Try to
translate at least 700 issues to see if it's working correctly or not.
Cheers,
Carlos
El 02/10/14 a las #4, Steven Silvester escribió:
I have to stick up for Carlos on this one. He is essential the only
core dev at this point, and is taking on a pretty heroic task of
curating this project *while* contributing substantial features to
the base. If the the shift to Github were to happen, someone else
should step up and do the bulk of that work and then hand the keys
over to Carlos.
On Saturday, September 20, 2014 11:40:36 PM UTC-5, Ioannis Filippidis
wrote:
Hello all,
I would like to ask about thoughts and opinions regarding moving
the development of Spyder to github, using git.
Potential advantages are:
- git offers more control than mercurial. The point of this email
is not to start an argumentation of git vs hg, some comments can
be found in this issue:
https://code.google.com/p/spyderlib/issues/detail?id=1911
<https://code.google.com/p/spyderlib/issues/detail?id=1911>
and these older discussions linked from it:
https://groups.google.com/forum/#!searchin/spyderlib/github/spyderlib/F0N3MdUNEtA/cP1DmEmibssJ
<https://groups.google.com/forum/#%21searchin/spyderlib/github/spyderlib/F0N3MdUNEtA/cP1DmEmibssJ>
https://groups.google.com/forum/#!searchin/spyderlib/github/spyderlib/z4JrnmAE3rA/oPUp8_Y8hI0J
<https://groups.google.com/forum/#%21searchin/spyderlib/github/spyderlib/z4JrnmAE3rA/oPUp8_Y8hI0J>
Examples of github's flexibility:
- branching
- history editing (amending, rebasing, cherry-picking,
squashing, etc.)
- staging: a handy mechanism for filtering changes into
smaller commits
- it is likely that several developers that use github regularly
would be interested in submitting patches or reporting and
discussing issues for Spyder. Forking and pull requests have
benefited a lot the growth of other projects, e.g., networkx:
http://networkx.github.io/
- the core of the python scientific stack is on github. Some of
these projects were previously hosted elsewhere (e.g., SourceForge).
It cannot be overlooked that they all chose to switch to github,
and have been quite active after the switch.
https://github.com/numpy
https://github.com/scipy
https://github.com/matplotlib
https://github.com/ipython
https://github.com/sympy
https://github.com/pydata
https://github.com/nose-devs/nose/
<https://github.com/nose-devs/nose/>
https://github.com/enthought
https://github.com/cython
https://github.com/search?utf8=%E2%9C%93&q=scikit
<https://github.com/search?utf8=%E2%9C%93&q=scikit>
- github is rising in popularity, and considering its function,
the main reason appears to be that people find it more practical
as an interface for managing their projects.
- issue tracking:
- (github-flavored) markdown
- linking to messages by commit hash
- linking to specific lines in code in specific changesets
- and several other features.
For tools that can help with migration, please take a look at
issue #1911
(https://code.google.com/p/spyderlib/issues/detail?id=1911
<https://code.google.com/p/spyderlib/issues/detail?id=1911>).
For completeness, it is worth mentioning that python development
uses hg, but the reasons are here:
http://legacy.python.org/dev/peps/pep-0374/#why-mercurial-over-other-dvcss
<http://legacy.python.org/dev/peps/pep-0374/#why-mercurial-over-other-dvcss>
and are either subjective, or time-specific:
1. windows interface for git: has improved much since 2009,
see, e.g., Github for Windows
2. developer opinions: this is personal preference of a set
of people
3. promoting a tool written in python - is not really
relevant to the function of a vcs.
Thanks,
ioannis
--
You received this message because you are subscribed to the Google
Groups "spyder" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/spyderlib.
For more options, visit https://groups.google.com/d/optout.
