[teampractices] Team membership, what does it mean.

[Jeremy Baron]

On Wed, Dec 3, 2014 at 4:28 AM, Matthew Flaschen
<mflaschen at wikimedia.org> wrote:
> On 12/02/2014 05:32 PM, Jeremy Baron wrote:
>> I think we should generally prohibit projects from containing tasks if
>> those projects are used as ACLs or limit membership for any other
>> reason.
>
> What would the ACL do if there are no tasks involved?

project membership can be used as part of a policy. policies can then
in turn be used to set restrictions. but the task would not actually
have that ACL project listed as one of the projects for the task. (or
at least I think it shouldn't)

to clarify, I'm thinking mostly about tasks that would have been
public bugs in bugzilla, not security bugs. I don't know enough about
security in phab to figure out what to do with security bugs. (but
ideally there would be some kind of classification for bugs in
mediawiki vs. an extension vs. an on-wiki gadget. instead of just
lumping everything into a catch-all "security")

>> Any brand new contributor with no special privileges should be
>> able to get phab's equivalent of "default CC" on those projects that
>> interest them.
>
> Does Phabricator actually have default CC?  I would guess you could
> accomplish it through Herald, but I don't know another way.

Not to be listed on the CC list in the web interface. But you will be
listed as CC in email notifs (even those sent to other users) and you
will (AFAIK) get all the same messages as if you were actually on the
CC list.

-Jeremy