[cjakeman]

Serana, on 12 June 2016 - 06:35 PM, said:

I think this is not the best practice.

Thanks, Serana, that's very clear.

Can anyone help with my Step 4 issue, please?

[James Ross]

Thanks for trying this and the comments; I am updating the document to make things clearer.

cjakeman, on 11 June 2016 - 06:46 AM, said:

Step 1: New repository
It wasn't clear that I should create a branch "develop" at this stage as I would need it in Step 4.

This is my mistake with the repository; I should have set up a "real" looking repo for people to test with, as the "develop" branch will exist already. Jeroen has made some good comments, spotting things like this in the private development forum too.

I'll let people know when the document and repo are updated and clearer about what to expect.

[edwardk]

I am in the process of learning about GitHub via Microsoft Virtual Academy. Learning the overall topic is easier for me. I am sure James is slowly working out how the work flow process will take place. One thing that I noticed is that Visual Studio has the ability to work with GitHub as well so this will be something to keep in mind when we get closer to implementing GitHub.

Edit: There is a Github extension for Visual Studio 2015(Community Edition) so it appears that people may have to change to this version if they did not do this already to use GitHub with Visual Studio.

Edward K.

[rdamurphy]

James Ross, on 07 September 2016 - 12:29 PM, said:

Thanks for trying this and the comments; I am updating the document to make things clearer.

Where do I find this document?

Robert

[James Ross]

rdamurphy, on 05 August 2017 - 11:54 AM, said:

Where do I find this document?

It's the specification link in the blueprint.

[rdamurphy]

Thank you. Found it.

Robert

[perpetualKid]

I haven't seen a discussion, but now that the code is moved to GitHub successfully, what are thoughts moving Bugs and Blueprints to GH as well? Bugs would become Issues, and Blueprints could be tracked as Projects.

This would allow direct integration and linking between code and tracking, and safe some external dependencies on 3rd party.

thoughts?

[cjakeman]

edwardk, on 27 September 2016 - 10:18 AM, said:

There is a Github extension for Visual Studio 2015(Community Edition) so it appears that people may have to change to this version if they did not do this already to use GitHub with Visual Studio.

Good point. It's working well for me on Visual Studio 2017.

[wacampbell]

I am working on getting set up with Git. So far the Git-On-Launchpad instructions have been great!

I am curious why we maintain the code on two systems - launchpad and github? Doesn't that add to the workload and potential failure points? I decided to use the SourceTree tools. And I cloned from GitHub - I am too new to know what advantage one has over the other.

As I get set up, let me know if you see me doing anything that causes problems. I'll likely want to test the workflow and push through a change to the doc or something innocuous.



Wayne

[James Ross]

wacampbell, on 04 August 2019 - 05:03 PM, said:

I am curious why we maintain the code on two systems - launchpad and github? Doesn't that add to the workload and potential failure points? I decided to use the SourceTree tools. And I cloned from GitHub - I am too new to know what advantage one has over the other.

In many respects, they're the same. The reasoning behind having both originally was that the Launchpad copy integrates with the existing stuff we have (bug tracking, blueprints, releases, etc.), while the GitHub copy is more discoverable and is where a lot more open source projects are.

As we've worked things out, things are working better in GitHub, and given the choice that seems to be where almost all of our active developers have chosen to work, so we will probably be figuring out a plan to move entirely to GitHub at some point (not for a while yet though).