Open source the SourceTree source code Edited

New SourceTree versions are frequently released with serious new bugs and issues which negatively affect large groups of users.

Atlassian are frequently very slow to address and fix these bugs, with some of them hanging around, unresolved, in JIRA for months if not years.

Open sourcing the SourceTree code would allow the community to contribute to both fixing bugs and issues within the SourceTree product as well as introduce long requested new functionality.

5 comments

Jeremy Mooiman Community Champion Jun 09, 2017

Dear Craig,

This would effectively make them move to open source though.. and might bring even greater security risks. So I doubt that they will be doing that.

Friendly Regards

Yes, "moving to open source" is exactly what I'm asking for.

I don't believe that there would be greater security risks, and in fact if anything, there would be fewer security risks as there would be many more eyes viewing and reviewing the source code and able to spot any potential problems.

Many other tool and utilities operate on an open source basis, for example, Microsoft's entire .NET Core stack, the Visual Studio Code editor, Github's Atom Editor, and even Mercurial's TortoiseHg GUI client, along with many, many others.  

Atlassian would maintain control of the repository and would be the ones to approve or deny any pull requests, but others in the community would have the option to submit code for potential inclusion that can ultimately only help and improve the SourceTree product.

 

It would also let us tailor versions of SourceTree for our own use. Case in point, a lot of Git users are trying to bridge between other more traditional VCSes and Git and fill in the gaps by enforcing practices like 'you must include the branch name in the commits since Git doesn't track that'. We could add a feature to automatically prefix the branch name.

Mind you a scripting system with triggers wouldn't hurt. Most other VCS clients have this concept. Again, something that could be done if it's open sourced.

Totally agreed. Some frustrating bugs are unresolved for years. Also, I catch myself thinking that I want to add some useful features or research performance issues on big repositories.

Totally agreed. There are small usability issues that bug me and I've often whished I could just open a PR fixing the issue. The number of open tickets discourages any new ones.

Totally agreed, and one thing i don't get is GPL states that if you include GPL software into your project and you should make the end product GPL too (as far i know). Sourcetree uses ton on Opensource products and a lot of them are GPL. And Matt from Automattic(wordpress) was arguing about Wix using wordpress content editer in their android app and not making the app opensource. 

YES! This needs to be done.

Comment

Log in or Sign up to comment
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 11, 2018 in Sourcetree

Tip from the team: debugging Sourcetree

Supported Platforms macOS Windows If you're reading this and it's not just educational… we know you're unhappy right now and apologize for that   We're dedicated to improving yo...

724 views 10 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you