Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing new tools, forums, and features

github.com

Post reply on HN
Print view View original

191–200 of 282 posts

Re: Announcing new tools, forums, and features

#191

Post by vacri »

bentlegen wrote: post #133
Nimimi wrote: post #97

Earlier quoted context omitted.

Take a look at Phabricator. It's a former Facebook project and been battle-tested at very large companies for years now. Huge open source projects like Blender, Haskell, Wikimedia and LLVM use it since it's the best open source code review tool and issue tracker. Wikimedia had a lengthy decision process and thoroughly vetted the alternatives. It has many enterprise features including code ownership, issue templates,…

I used Phabricator at a former employer, and it was one of the best software tools I've used. I'm always flabbergasted that it doesn't have more mindshare, especially when it's used internally at Facebook.

I haven't seen it running yet, but just from reading the features page, I'm already a fan

https://www.phacility.com/phabricator/

Re: Announcing new tools, forums, and features

#192

Post by brandur »

Myrmornis wrote: post #184
old-gregg wrote: post #183

This is the example of how hard it can be for companies, especially successful companies, to alter their course even slightly. Github success was about making code repositories pretty and social. But this is no longer enough to keep evolving as a company of their size. Yet the internal product DNA still revolves around repos, so as a result, issues, wikis and now Projects (!) live under a single repository. This is b…

Although there will still be lots of projects (e.g. `an open source project with one repo`, `some company with a huge monolithic repo`) that will be able to use per-repo Projects profitably. But yes, someone, please make something that kills JIRA as soon as possible.

I think they could iterate on this to a place where projects are repository-specific, but still useful for high-level organization and planning.

For example, if they allowed repo projects to reference issues in other repos, that would you get you 99% of the way there. You could start a single meta-repository that referenced as many repo-specific issues as you cared to consider.

Re: Announcing new tools, forums, and features

#193

Post by elwell »

ajsharma wrote: post #31
sgarrity wrote: post #16

Some nice improvements here. It appears, though, that Projects suffer from the same problem we've had with Issues: they are limited to one repo. I know there are some tools to manage Issues across repos, but for the most part, the tools seem to assume you work on only one repo, or that milestones only affect a single repo. I would love to see projects/milestones become more capable when dealing with cross-repo issues…

At Goldbely, our solution has been to have a single GitHub repo that's just for issues and use tags to highlight the actual code repos involved. Works pretty well, if a little awkward at first.

We do this as well at Purple [0]. It does make issue referencing in commit messages a bit unwieldy; you have to include the full path to the issue (e.g., org-name/repo-name#34).

[0] - http://purpleapp.com

Re: Announcing new tools, forums, and features

#194

Post by exception_e »

moby wrote: post #169
exception_e wrote: post #159

Earlier quoted context omitted.

I'm liking the recent design changes, however, I don't like the new implementation of contrib. activity... information overload!

Ah, noted - so you'd like to have some customization on what you choose to show on your profile?

No, I'm saying that the "contribution activity" timeline thing is leaning towards information overload (hard to follow; there is a lot to look at). I felt that the last implementation (which focused on the high-level activities that one could click into) made sense.

I'm not a designer or anything so take my feedback with a grain of salt.

Re: Announcing new tools, forums, and features

#195

Post by vacri »

StevePerkins wrote: post #137
elliotec wrote: post #77

Earlier quoted context omitted.

I think it was more the open letter to Github, which motivated both Github and GitLab (seen as an opportunity to compete). GitLab's roadmap yesterday surely didn't motivate or spawn the "New GitHub Universe," and I wouldn't think that Github is very nervous about GitLab currently due to it's massive lead in the market. Maybe this new round of funding made some of the folks at Github look over at Gitlab, but I doubt t…

> massive lead in the market Ehh... dominance among open source projects, and Hacker News and Reddit thread cool points, is one thing. But in boring old terms of actually making money, how IS GitHub doing? "Enterprise" is practically a swear word here, but that's where the meaningful paying customers are. From my anecdotal experience, Atlassian absolutely dwarfs GitHub in the enterprise world... and that's just the e…

At a small company here, and we moved from GitHub to BitBucket because both the pricing (a couple dozen private repos) and user-management were more friendly. User management is one of those things people hand-wave away until they're the poor sap who has to manage it.

Re: Announcing new tools, forums, and features

#196

Post by FireBeyond »

Dobbs wrote: post #165
FireBeyond wrote: post #94

Earlier quoted context omitted.

No-one said it was. But the answer of self-hosting is a perfectly valid answer for "Why the love for GitLab?" when one = $0 in licensing, and the other = > $2,500/year in licensing.

> No-one said it was. That is literally what the comment I replied to said. That "self hosting" was a reason to root for gitlab.

"Reason to root for GitLab" does not necessarily equal "product differentiator".

Similar to the "you can't use price to differentiate the two" - why not?

Re: Announcing new tools, forums, and features

#197

Post by bentlegen »

sytse wrote: post #155
bentlegen wrote: post #80

Earlier quoted context omitted.

> Open source* The Enterprise edition features[1] are closed source, and these aren't strictly "enterprise-y" features like SAML authentication. It includes plenty of "basic" workflow features found on GitHub: - Rebase merge requests before merge - Use fast-forward merges when possible - Create templates for issues and merge requests - Display merge request status for builds on Jenkins CI [1] https://about.gitlab.com…

To make sure there is no confusion we now refer to ourselves as open core https://about.gitlab.com/about/#stewardship I want to echo here what I said in https://news.ycombinator.com/item?id=12501271 "If there are features that people think that should belong in the open source edition we're all ears. We've done so before https://news.ycombinator.com/item?id=10931347 A feature comparison between CE and EE can be found…

So, when reading the features page, I was considering 1 and 2 in terms of a feature that I use at GitHub religiously: squashed pull requests (that are automatically fast-forwarded) [1].

If I'm reading this correctly, this exists in GitLab as an enterprise feature, so I think my earlier comment isn't too far off. There also appears to be some community feedback suggesting this should be a CE feature [2].

[1] https://help.github.com/articles/about-pull-request-merges/ [2] https://gitlab.com/gitlab-org/gitlab-ce/issues/4106

Re: Announcing new tools, forums, and features

#198

Post by inopinatus »

moby wrote: post #141
sgarrity wrote: post #16

Some nice improvements here. It appears, though, that Projects suffer from the same problem we've had with Issues: they are limited to one repo. I know there are some tools to manage Issues across repos, but for the most part, the tools seem to assume you work on only one repo, or that milestones only affect a single repo. I would love to see projects/milestones become more capable when dealing with cross-repo issues…

Thanks for providing the feedback here - I've passed it along to the Engineering team building out Projects.

I'm curious as to whether you are dogfooding Projects, especially when feature work spans multiple repos. If so a "how Github uses Projects" tutorial may be worth considering.

Re: Announcing new tools, forums, and features

#199

Post by bhldr »

sytse wrote: post #190
old-gregg wrote: post #183

This is the example of how hard it can be for companies, especially successful companies, to alter their course even slightly. Github success was about making code repositories pretty and social. But this is no longer enough to keep evolving as a company of their size. Yet the internal product DNA still revolves around repos, so as a result, issues, wikis and now Projects (!) live under a single repository. This is b…

I agree that putting projects under repositories looks counterintuitive. In BitBucket you have multiple repositories under one project https://confluence.atlassian.com/bitbucket/projects-79249795... We at GitLab are trying to keep it simple by having only one repository, one wiki, one issue tracker, one CD pipeline, and one set of milestones per project. Projects always below to a group. We aggregate on the group lev…

Enough with the ads here.

Re: Announcing new tools, forums, and features

#200

Post by rickycook »

garethadams wrote: post #164
sytse wrote: post #155

Earlier quoted context omitted.

To make sure there is no confusion we now refer to ourselves as open core https://about.gitlab.com/about/#stewardship I want to echo here what I said in https://news.ycombinator.com/item?id=12501271 "If there are features that people think that should belong in the open source edition we're all ears. We've done so before https://news.ycombinator.com/item?id=10931347 A feature comparison between CE and EE can be found…

> 1. Can you rebase in the GitHub interface? > 2. Does GitHub have an option to fast forward merges? So is Gitlab's aim to just play catchup to Github?

are you joking? it's the other way around. github is only just now playing catch up to gitlab
Post reply on HN