You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had a few discussions recently with developers looking for the best ways to use GitHub for efforts that span organizations and even campuses.
A recurring challenge is the need to invite collaborators ad-hoc to projects that are hoped in advance to be campus or system level collaborations.
Another challenge is that discussion spaces for collaborative efforts (like the one we have here), are less effective when they are spread across many repositories.
Before we start creating new spaces modeled after this one, the first question is - should we start with expanding here?
Should this space be expanded to include all developer topics?
Yes. We should maximize participation here by encouraging all U of I community development topics, repositories and resources.
100%
No. This discussion space should focus on GitHub use by the U of I developer community.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I've had a few discussions recently with developers looking for the best ways to use GitHub for efforts that span organizations and even campuses.
A recurring challenge is the need to invite collaborators ad-hoc to projects that are hoped in advance to be campus or system level collaborations.
Another challenge is that discussion spaces for collaborative efforts (like the one we have here), are less effective when they are spread across many repositories.
Before we start creating new spaces modeled after this one, the first question is - should we start with expanding here?
3 votes ·
Beta Was this translation helpful? Give feedback.
All reactions