I think you'll get a different answer for what constitutes a project. What I've seen is projects can be across your organization or in a single repository. This makes working on large, cross-product changes easier.
Your team just has to buy in to the idea of using this tool and only this tool. I like the idea of it in that I can completely live in GitHub for my work. What makes it harder is that in my organization we have people who aren't developers that need access to our private repositories so they can be aware of the current work status. For us, we have to give up a license seat for it (which are limited) and give these members of our team write access to our repositories so they can comment on issues. We haven't come up with a way to address this yet, other than making promises to communicate status in a written way. This isn't hard, but it's a drag on the team some.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think you'll get a different answer for what constitutes a project. What I've seen is projects can be across your organization or in a single repository. This makes working on large, cross-product changes easier.
Your team just has to buy in to the idea of using this tool and only this tool. I like the idea of it in that I can completely live in GitHub for my work. What makes it harder is that in my organization we have people who aren't developers that need access to our private repositories so they can be aware of the current work status. For us, we have to give up a license seat for it (which are limited) and give these members of our team write access to our repositories so they can comment on issues. We haven't come up with a way to address this yet, other than making promises to communicate status in a written way. This isn't hard, but it's a drag on the team some.