I'd be curious for an example community who handles discussions re: new committers and PMC roles on the dev list. From what I've seen on other projects, those conversations benefit from the level of discretion afforded by having them on the private list.
On Saturday, September 19, 2015, Sean Busbey <[email protected]> wrote: > Hi folks! > > We need to decide which topics of conversation require being limited to the > PMC on private@yetus. > > * security vulnerability reports and handling (per foundation policy since > we don't have security@) > > * I'd like any branding requests (like trademark use by third parties) to > go to dev@ unless the sender needs special confidentiality > > * discussion and votes on new committers and PMC roles often go to private, > but need not. If folks are interested, I can look for an example community > that does this in public. > > What do folks think about the above? In particular, are there folks not > currently on the PMC that can think of topics they'd like to participate in > that might typically and up on private@? > > -- > Sean >
