Access to Repos? about community HOT 7 CLOSED

On Mon, Jun 01, 2015 at 07:44:38PM -0700, Juan Batiz-Benet wrote:

If this is annoying to people though, can consider one big org where
everyone has R/W on everything…

Tightly-scoped commit access makes sense to me, especially since it
makes it more obvious who is responssible for maintaining the code,
and I think ownership like that makes for healthier development (I
feel like we've discussed per-Go-package maintainer assignment, but I
haven't been able to dig up a reference to the earlier discussion).

The only concern I have is with Waffle, because you can't move cards
without write access to the repository that holds the associated
issue/PR 1. It would be nice if the GitHub folks had an
authorization scope that let you manage labels without giving you
commit access to the repository.

from community.

@wking I thought this at first -- was trying to move a card for ipfs/ipfs-webui#56 in https://waffle.io/ipfs/ipfs but I only have write access to ipfs/webui so I could not move it.

However I tried going to https://waffle.io/ipfs/webui and I could indeed move the card, and of course the change is reflected in the other board as well.

https://waffle.io/ipfs/webui does not have all the same columns as the main waffle board, but it could. Not the ideal workflow, but works in the current constraints.

from community.

@harlantwood also if you assign the label by hand in the repo, waffle will pick it up too. sorry the waffle board permissions are annoying. mind pointing this out to the waffle team?

from community.

On Tue, Jun 02, 2015 at 03:48:08PM -0700, Harlan T Wood wrote:

@wking I thought this at first -- was trying to move a card for
ipfs/ipfs-webui#56 in https://waffle.io/ipfs/ipfs but I only have write
access to ipfs/webui so I could not,

I reported that earlier and it's waffleio/waffle.io#1902. My concern
here is how do you collaborate on webui's Waffle board if you don't
have commit access to ipfs/webui. Until GitHub has an issue-labeler
scope, I think everyone who needs to move Waffle cards will need
commit access on the relevant repository. And until
waffleio/waffle.io#1902 is fixed, folks without write access to
ipfs/ipfs will also have to use something other than
https://waffle.io/ipfs/ipfs to manage the labels at all.

from community.

i'll close this for now. comment + reopen if this becomes an issue

from community.

@jbenet @wking I ran across this when looking through our own Waffle board and wanted to offer two options.

The first -- would it be possible to create an Issues Only repository? (ie ipfs/ipfs-issues)? You could grant collaborator access pretty leniently (or maybe even write a script to add anyone who forks the repo as a collaborator, though that might be living on the edge. :)) I've wondered if this could be a solution for cases like your's, and if not, why? (So we can continue to think about how to best solve this problem.)

The other option would be to encourage your contributors to issue pull requests as soon as they start work. If they issue pull requests cross-referencing the original issue (ie: fixes ipfs/ipfs#32), Waffle will visually connect the pull request beneath the issue, even if issued from a fork (as long as the cross-repo reference exists!) The title or description could also include a note like "work started" which would cue a collaborator to pull that issue in progress if they feel like the contributor is reliable and most likely making decent progress on the issue.

Curious to hear what you think?

Ashley
Waffle.io

from community.

Hey @ashumz! thanks for dropping by

Only repository? (ie ipfs/ipfs-issues)? ... I've wondered if this could be a solution for cases like your's, and if not, why?

It would not work for us to have one repo for issues. separate issues is often why it makes sense to split repos-- easier to maintain + figure out problems.

I'm not sure how well things are working out atm on this front -- but maybe others can comment.

from community.