13 ms·
This is a rough summary of what all I read in the blog post: 1. projects. replaces trello, waffle.io, zenhub and many other similar services. 2. code reviews
by captn3m0 10y ago
This is a rough summary of what all I read in the blog post:
1. projects. replaces trello, waffle.io, zenhub and many other similar services.
2. code reviews allow approval/request changes as sunny's screenshot shows
3. reviews can be made mandatory.
4. github platform integrations is getting a roadmap
5. a graphql api to query their database
6. enforce 2fa in organizations (much love for this one)
7. summarized timeline for your contibutions
Just a few days back, at the GitLab release, I'd noticed a lot of complains about gitlab releasing useful and impactful features and github being slow on releases. Moreover, now with a public roadmap (even if it is just for platforms), it is a great start.
I'm really liking this change in pace.
mods: Can we make this the canonical discussion for this topic? Otherwise, a lot of branching will happen
- thegarside 10y agoDoesn't look like Projects comes close to replacing ZenHub / Waffle.. Not for proper teams anyway – real project management needs to be much more robust so I'm keeping ZenHub for now.
- jglovier 10y ago>projects. replaces trello, waffle.io, zenhub and many other similar services. This is really not about replacing those services, it's more about building a better foundation for integrators like Waffle and ZenHub to build on.
- captn3m0 10y agoI'm looking at https://www.zenhub.com/product https://www.zenhub.com/product, and while it does have some extra features (filters on priority, labels), but for most people the base set provided by github is gonna be sufficient. Sure, it won't completely replace them, but GitHub building this as a platform counts as competition.
- ma138 10y agoUsing ZenHub also provides additional features like time estimation, burndown charts and Epics (for issue hierarchy) - we find that for larger teams, these are must-have features to work inside GitHub.
- homeyer 10y agoAt Waffle.io, we're all about making project management better for engineers. We believe it's awesome that GitHub is investing in this too, and we'll continue to make GitHub delicious :). More here: http://blog.waffle.io/say-hello-to-wafflebot/ http://blog.waffle.io/say-hello-to-wafflebot/
- ma138 10y agoAt ZenHub, we have already starting working on some integrations with this functionality which you can read more about here - https://www.zenhub.com/blog/dispatches-from-github-universe/ https://www.zenhub.com/blog/dispatches-from-github-universe/ Our focus is going to remain on how to integrate a full-featured project management suite within the GitHub eco-system. The GitHub projects release will make a great foundation, and ZenHub will be there to provide the more advanced features like issue hierarchy (epics), time estimation and reporting. Lots of exciting releases coming soon for ZenHub users :)
- deleted 10y ago[deleted]
- bigkahunaburger 10y agoExcept all those services have already built a foundation ... This will inevitably force out GH's integration partners once users start to complain how feature-deficient projects are in their current state.
- jenniferDewalt 10y agoFounder of Zube here. GitHub Projects seems like a nice solution for very small teams, side projects and open source projects. However, serious teams need more powerful features like a well thought out workflow, support for multiple repos and burndown charts. Shameless plug: Zube has all these things and more - https://zube.io https://zube.io :)
- mstade 10y agoIt looks like enforcing 2fa in an org (finally!) means anyone who doesn't have 2fa will be booted out (included whoever may be paying for it at the time) with an email explaining why. I'm afraid to tick the box because of this. :o/
- jedberg 10y agoContact everyone, tell them they have a week, then tick the box. If they didn't do it within the week it's either not important to them or they'll add it right quick after you tick the box.
- mwarkentin 10y agoWe have some "shared" users for things like bots, etc.. wonder how to deal with that since we don't want to enable MFA for them. Otherwise I'd be all over this..
- RyJones 10y agoThis is a huge issue for us at the Linux Foundation. Infra accounts make enforcing MFA for orgs impossible Even if I could do classes of accounts. Owners and admins, MFA required. Users (bots) that just update CI status, not required.
- sciurus 10y agoFor CI bots I think in the future you will be able to build an "integration" instead of using a user account. From the blog post "We’re rethinking our integrations model to provide better ways for tools to extend and integrate with GitHub. We’ve added the ability for an integration to act on its own behalf instead of impersonating a user—making it a first class actor on GitHub without using a paid seat. Admins will have the ability to configure integrations directly on Organizations and control which repositories they allow access to." https://developer.github.com/changes/2016-09-14-Integrations-Early-Access/ https://developer.github.com/changes/2016-09-14-Integrations... https://developer.github.com/early-access/integrations/ https://developer.github.com/early-access/integrations/
- elliotec 10y agoI agree with you that the pick up in pace of Github's lacking features has been phenomenal, and I don't really quite understand all the love of GitLab except rooting for the underdog. Github is the clear industry leader, has been since essentially it's creation. It is very fast and feature-filled. It is the central location for the vast majority of code I use and see. Since the open letter to Github with the complaints of feature requests, they've really stepped up their game and made competitors really non-starters from my point of view.
- markdog12 10y ago> I don't really quite understand all the love of GitLab - Open Source - Free private repos - Free self-host (edit to add "Free") - Everything in one spot (repos, ci, review, coding environment, etc...)
- bentlegen 10y ago> 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/features/ https://about.gitlab.com/features/
- detaro 10y agoUse fast-forward merges when possible GitHub (annoyingly) can't do fast-forward merges from non-squashed PRs either. Display merge request status for builds on Jenkins CI GitLab implements basically the same API as GitHub for updating build status of commits from external services, or do I misunderstand what feature you mean? But in general I agree, there are some options GitLab reserved for EE that really feel like they should be part of the CE as well.
- bentlegen 10y ago
- tootie 10y agoThis all seems like baby stuff compared to Atlassian though. JIRA, Confluence, Bitbucket, HipChat. That's hard to beat.
- obi1kenobi 10y agore: enforced 2FA, it does not appear to play well with bot accounts -- it's either all on or all off, and bots don't count as using 2FA.
- draw_down 10y agoI thought the stuff about Github's pace was funny too. People have short memories, I guess.