On Mon, Nov 5, 2018 at 12:44 PM Dave Fisher <dave2w...@comcast.net> wrote: > > > > > On Nov 5, 2018, at 8:35 AM, Christopher <ctubb...@apache.org> wrote: > > > > On Mon, Nov 5, 2018 at 3:49 AM Bertrand Delacretaz > > <bdelacre...@apache.org> wrote: > >> > >> Hi, > >> > >> On Fri, Nov 2, 2018 at 7:02 PM Christopher <ctubb...@apache.org> wrote: > >>> ...it would be a mistake if ASF were to try to impose a more spammy > >>> workflow to dev@ onto every PMC, as a requirement... > >> > >> FWIW I didn't suggest imposing anything like that - my only concern is > >> that it should be possible to follow the action of any of our projects > >> just by subscribing to their dev list. > >> > > > > That problem is not specific to GitHub. Are you equally concerned > > about JIRA activity going to notifications@ and SVN activity going to > > commits@ (especially with commit-then-review) ? > > > >> Watching GitHub repositories is fine but some of our projects have > >> many repositories and just finding out which ones to watch depending > >> on what one's interested in can be problematic, IMO. > >> > >> -Bertrand > >> > > > > A weekly summary of active issues/PRs for all of that project's repos, > > posted to the dev@ list might be useful, but it could also be too > > large to be useful. > > > > It might also be useful to contributors to have an automated monthly > > email from INFRA to remind the project of all INFRA resources used by > > the project, such as mailing lists, git repos, git mirrors, reserved > > svn paths, issue trackers, Maven staging profiles, etc. That way, > > newcomers can be made aware of all resources in use by the project (in > > case they missed that info on the project website), so they can have > > an opportunity to subscribe to them as they choose, or ask questions > > about them on the dev@ list. > > The Whimsy Roster for a PMC has most of this information. It might be nice to > have a public version of the project information. > > Links > Mailing Lists > Committers > PMC > Prior Reports
I think Bertrand was specifically concerned about making more information about project activity locations available to dev@ subscribers. In my opinion, that information should already be on the project's website, so Whimsy making that public is redundant. But, a periodic reminder to dev@ subscribers might be useful to communicate to dev@ subscribers directly. > > Regards, > Dave > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
