[teampractices] Triaging bugs and managing task backlog in Phabricator

[svetlana]

On Wed, 3 Dec 2014, at 12:18, Bryan Davis wrote:
> On Tue, Dec 2, 2014 at 5:06 PM, Anne Gomez <agomez at wikimedia.org> wrote:
> > I'm just starting to look at moving fr-tech to phabricator and have been
> > wondering these questions to myself (along with the other thread about
> > teams). I'm wondering if it might make sense to have a project for bug
> > tracking that is public/open and a project for just the internal team to
> > work on that would include the sprint board and not allow editing by others.
> 
> I'd personally like to see everyone default to open rather than closed
> groups.

+1

> If there is significant spam or griefing then closed groups
> might be the only recourse, but assume good faith and embrace the
> openness that we are allowed in our organizational structure.

Spam should not be an issue - there's plenty of volunteers who'd be happy to offer a hand.

What is «griefing»? Sounds like something out of the ordinary (bottom line, it would force people to make things read-only and invite-only), but not hide them from the public view.