And BitBucket was an attempt to steal GitHub's business primarily with Mercurial at the time, that Atlassian bought up, and since then GitHub has still been their #1 competitor, (not counting Sourceforge).
I like stash and have been a paying customer since last year. As far as I know, it is written in Scala too (the plugin API docs had a Scala flavour when I last looked at them).
I especially like its Pull Request interface. It separates out the changes into a file tree, which appears as a pane on the left. Makes it much easier to review large PRs.
The only hitch is, Atlassian has very opinionated product managers. I (and a bunch of other users) had to convince them to support "forks" over a long JIRA thread!
> As far as I know, it is written in Scala too (the plugin API docs had a Scala flavour when I last looked at them).
?? Their source code is downloadable to us since we have a license, but I've not checked. Everything else Atlassian purchased has been Java, afaik.
And Atlassian's only opinionated project manager I know about is Jens who does Stash, so I think you are generalizing to apply that to all of Atlassian. I've been using their products a long time now and he is the first that has been like that, but I know what you mean. He doesn't really meet up with Atlassian's typical level of customer service because of his attitude, but maybe he's a "rockstar" that deserves respect.
I would like to clarify that support for Forks was on our roadmap from day one. It was merely a matter of time and priorities to get it implemented as can be seen on the issue discussion: https://jira.atlassian.com/browse/STASH-2495
The core of Stash is actually written in JAVA, with only few plugins being implemented in Scala. But that number will likely grow going forward.
You are probably right that some of us are slightly opinionated. But as was pointed out before, I believe product managers should be opinionated as long as the opinions are formed by knowing your customers and market extremely well.
I'd say that's a good thing. A product can't be all things to all people and when it tries it ends up as a big hogde-podge of compromises that make no-one happy (either that, or being a beast to configure, thus making support painful).
Now, I don't know what the particular issue over forks are (related to branches?) and whether it's reasonable, but the fact that they were eventually convincible only makes it seem better.
In general I agree, but "forking" would be considered as a very essential feature by many in a product like Stash. I don't think dozens of users were needed to argue that it be included.
BSA can't take the name Skouts, could it? Has a K in it for hacKer, and the name is hacked- so it's a double whammy.
BTW- I like Maker Skouts, too. Considering most of the stuff listed is Maker and not Hacker oriented, and Maker has no bad connotations to the uninformed.
BTW2- the first badge stemming from welding == awesome.
And BitBucket was an attempt to steal GitHub's business primarily with Mercurial at the time, that Atlassian bought up, and since then GitHub has still been their #1 competitor, (not counting Sourceforge).