3 ms·

I love that you are also working in the open! At Automattic we do a lot of Open Source development. You can even see my PR introducing Sentry to our frontend:

by artpi 10y ago

I love that you are also working in the open! At Automattic we do a lot of Open Source development. You can even see my PR introducing Sentry to our frontend: https://github.com/Automattic/wp-calypso/pull/2107 https://github.com/Automattic/wp-calypso/pull/2107 (Unfortunately removed, we are running custom solution right now, but thats another story..) How are you dealing with discussions across your team on Github? Sometimes, we have to link to some discussion that is not happening in the open because of this or that business reason and we have to provide a context for colleagues but not everyone else. At other times we want to encourage external contributions but some decisions happen outside of GH and contributors don't feel included. Have you come across similar challenges?

zeeg 10y ago
It's really tough. Even basic problems are extra painful because of the limited tooling on GitHub. One major problem that is still ongoing is code review. How we act on our own mandatory code review requirements as well as make sure we are responding to community issues and PRs. Another big issue was the number of repos and lack of good centralized views. We've sort of simplified this by moving things into monorepos (e.g. All our plugins are going into a single repo). The major missing piece for us on GitHub is being able to assign to teams vs just mentioning, and automating tools to guarantee those assignments exist. The last bit is private discussions (e.g. Stop our competitors from stealing all of our ideas). We keep all of those big product design concerns in Dropbox Paper until we begin implementation. That's not only for keeping them secret but also because it's just easier to collaborate. Also curious to learn more about your custom service and choice. Wanna drop me an email? david at sentry's domain.
- scrollaway 10y ago
  > Another big issue was the number of repos and lack of good centralized views. We've sort of simplified this by moving things into monorepos (e.g. All our plugins are going into a single repo). Have you evaluated zenhub? We started using it and can't ever look back. Allows us to have as many repos as we have but still track everything centrally.
  - zeeg 10y ago
    Skimmed it a while back, but didn't realize it had centralized views. I will say our biggest challenge is mostly around PRs and community issues. We use a big ol' Excel sheet for sprint planning (inspired by my Dropbox days). You can use GitHub's global views for some of it, but they dont show mentions, and no one has the time to try to assign every little thing to the right people.

by artpi 10y ago

zeeg 10y ago

It's really tough. Even basic problems are extra painful because of the limited tooling on GitHub. One major problem that is still ongoing is code review. How we act on our own mandatory code review requirements as well as make sure we are responding to community issues and PRs. Another big issue was the number of repos and lack of good centralized views. We've sort of simplified this by moving things into monorepos (e.g. All our plugins are going into a single repo). The major missing piece for us on GitHub is being able to assign to teams vs just mentioning, and automating tools to guarantee those assignments exist. The last bit is private discussions (e.g. Stop our competitors from stealing all of our ideas). We keep all of those big product design concerns in Dropbox Paper until we begin implementation. That's not only for keeping them secret but also because it's just easier to collaborate. Also curious to learn more about your custom service and choice. Wanna drop me an email? david at sentry's domain.

scrollaway 10y ago
> Another big issue was the number of repos and lack of good centralized views. We've sort of simplified this by moving things into monorepos (e.g. All our plugins are going into a single repo). Have you evaluated zenhub? We started using it and can't ever look back. Allows us to have as many repos as we have but still track everything centrally.
- zeeg 10y ago
  Skimmed it a while back, but didn't realize it had centralized views. I will say our biggest challenge is mostly around PRs and community issues. We use a big ol' Excel sheet for sprint planning (inspired by my Dropbox days). You can use GitHub's global views for some of it, but they dont show mentions, and no one has the time to try to assign every little thing to the right people.