On 07/10/16 15:16, Ryan Schmidt wrote:
On Oct 7, 2016, at 9:04 AM, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote:
Hi,
There will always be problems with the transition to GitHub that can be
discussed on the mailing list to find a common solution. Then it can be
documented to point people to that if they have the same problem.
Yes. But I want to at least know how to perform the tasks that I currently
perform with Trac and Subversion once we move to GitHub. I currently do not
feel that I understand how to do that, and worry that I and other contributors
who do not know Git very well will no longer be able to contribute effectively
once we switch.
My experience with moving from subversion to git is you can read about it as
much as you want, but there is no substitute for just starting to try and use
it. It takes a little time to get used to, but once you do you will not go back
to svn.
So whilst I understand you want to try and work everything out up front, before
hand, in practice I think you have to expect a bit of a learning curve for
everyone at first, and basically just dive in and make the change.
I have used Git and GitHub for years; I joined GitHub in 2010. Doesn't mean I
know how to do anything more than clone and commit.
My point still stands though, you have to actively try the things you
need to do, to get used to them.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
