Hi! we plan to move from Gitorious to GitHub. I already started by copying Git repository over, and will keep it in sync during the next days. Proposal is to have the next release on GitHub already, so we only need to find a nice revision for tagging v0.4.3. After the move I also propose to move from current Redmine to GitHub issues. This lowers the hesitation-threshold for actually filing bugs. This is because of the integration and because people just know how to file bugs at GitHub. RFC! th -- Tobias Hintze // KO GmbH http://kogmbh.com/legal/
On 20 September 2013 18:44, Tobias Hintze
Hi!
we plan to move from Gitorious to GitHub.
Sounds exciting!
I already started by copying Git repository over, and will keep it in sync during the next days.
Proposal is to have the next release on GitHub already, so we only need to find a nice revision for tagging v0.4.3.
After the move I also propose to move from current Redmine to GitHub issues. This lowers the hesitation-threshold for actually filing bugs. This is because of the integration and because people just know how to file bugs at GitHub.Sounds exciting!
What does this mean for the current MR queue? Do you want us to re-raise those on git-hub branches...? -- Philip Peitsch Mob: 0439 810 260
----- Original Message -----
After the move I also propose to move from current Redmine to GitHub issues. This lowers the hesitation-threshold for actually filing bugs. This is because of the integration and because people just know how to file bugs at GitHub.Sounds exciting!
What does this mean for the current MR queue? Do you want us to re-raise those on git-hub branches...?
I would say, let us: * start to file new issues at GitHub now already * keep current MR queue at gitorious and work on it there * only migrate issues over to GitHub if some MRs just wont close th -- Tobias Hintze // KO GmbH http://kogmbh.com/legal/
On 21/09/2013, at 6:32 AM, Tobias Hintze wrote:
After the move I also propose to move from current Redmine to GitHub issues. This lowers the hesitation-threshold for actually filing bugs. This is because of the integration and because people just know how to file bugs at GitHub.Sounds exciting!
What does this mean for the current MR queue? Do you want us to re-raise those on git-hub branches...?
I would say, let us: * start to file new issues at GitHub now already * keep current MR queue at gitorious and work on it there * only migrate issues over to GitHub if some MRs just won't close
Should new patches be raised in gitorious or GitHub? I have one that is ready for review (textposition-tests branch), and another that could use some early technical feedback from Friedrich (cursor-styling)… but am not sure whether to put these up on gitorious or GitHub :) Cheers, Philip
Am Montag, 23. September 2013, 07:17:26 schrieb Philip Peitsch:
On 21/09/2013, at 6:32 AM, Tobias Hintze wrote:
After the move I also propose to move from current Redmine to GitHub issues. This lowers the hesitation-threshold for actually filing bugs. This is because of the integration and because people just know how to file bugs at GitHub.Sounds exciting!
What does this mean for the current MR queue? Do you want us to re-raise those on git-hub branches...?
I would say, let us: * start to file new issues at GitHub now already * keep current MR queue at gitorious and work on it there * only migrate issues over to GitHub if some MRs just won't close
Should new patches be raised in gitorious or GitHub?
I have one that is ready for review (textposition-tests branch), and another that could use some early technical feedback from Friedrich (cursor-styling)… but am not sure whether to put these up on gitorious or GitHub :)
Tobias, what is meant with "* only migrate issues over to GitHub if some MRs just won't close"? IMHO we should decide on a certain day and just move other everything completely to github, so also any open MR. The MR queue will never be empty (for good and bad :) ), so let's just move what there is. So we have only one place to look at and care for. What about today, 24.09.? Anyone objecting or wishing another date? Philip, I propose to just push your new ones to gitorous for now, moving them over to github if needed the next days should not be that much work. Let's see how much can be even dealt with already the upcoming workday. Cheers Friedrich -- Friedrich W. H. Kossebau // KO GmbH http://kogmbh.com/legal/
On 24/09/2013, at 8:25 AM, Friedrich W. H. Kossebau wrote:
Am Montag, 23. September 2013, 07:17:26 schrieb Philip Peitsch:
On 21/09/2013, at 6:32 AM, Tobias Hintze wrote:
After the move I also propose to move from current Redmine to GitHub issues. This lowers the hesitation-threshold for actually filing bugs. This is because of the integration and because people just know how to file bugs at GitHub.Sounds exciting!
What does this mean for the current MR queue? Do you want us to re-raise those on git-hub branches...?
I would say, let us: * start to file new issues at GitHub now already * keep current MR queue at gitorious and work on it there * only migrate issues over to GitHub if some MRs just won't close
Should new patches be raised in gitorious or GitHub?
I have one that is ready for review (textposition-tests branch), and another that could use some early technical feedback from Friedrich (cursor-styling)… but am not sure whether to put these up on gitorious or GitHub :)
Tobias, what is meant with "* only migrate issues over to GitHub if some MRs just won't close"?
IMHO we should decide on a certain day and just move other everything completely to github, so also any open MR. The MR queue will never be empty (for good and bad :) ), so let's just move what there is. So we have only one place to look at and care for.
What about today, 24.09.? Anyone objecting or wishing another date?
Philip, I propose to just push your new ones to gitorous for now, moving them over to github if needed the next days should not be that much work. Let's see how much can be even dealt with already the upcoming workday.
Sounds good. I've closed out our remaining MR's on Gitorious, and migrated them to GitHub. I thought about waiting longer, but there is really no advantage when everything in the MR queue is likely to still require further feedback and rework. As you pointed out, migrating branches between the systems is trivial… so I could think of no reason to not do this immediately :-) As of today (24.09!) we're moving our development efforts onto github. If this is too soon, let me know as we can still easily switch back. Cheers, Philip
participants (4)
-
Friedrich W. H. Kossebau
-
Philip Peitsch
-
Philip Peitsch
-
Tobias Hintze