> * Don't change anything at least as long as we don't
have FAS support
> in Phab. Until then, it doesn't really matter whether we manage
> commit permission using Bitbucket accounts or Phab accounts.
I'm not sure that FAS matters much here. Even after we get FAS
integration, there's not going to be any support for FAS groups in
phabricator. AFAIK, phabricator doesn't support externally defined
groups and even if it did, we'd have no way of getting that data since
Persona doesn't have a mechanism to do anything other than auth.
Oh, I didn't know. OK, in that case it's even simpler - I don't see any major
reason now to move the repos to Phab. Let's leave it at Bitbucket. The only thing we
need to do is to update the README files in our repositories and point to Phab if people
want to report issues.
> If this sounds reasonable, I'll probably move
to bitbucket as
> well, so that we start to get rid of fedorahosted and move all code
> into a single place.
If we're going to hold off on migration for everything elase, I'm
inclined to wait a bit on that. I'd prefer to avoid moving stuff twice
when commit privileges etc. are setup and functioning for the
fedorahosted repos right now.
OK, sounds reasonable.