Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)
On Mon, Nov 5, 2018 at 12:44 PM Dave Fisher wrote: > > > > > On Nov 5, 2018, at 8:35 AM, Christopher wrote: > > > > On Mon, Nov 5, 2018 at 3:49 AM Bertrand Delacretaz > > wrote: > >> > >> Hi, > >> > >> On Fri, Nov 2, 2018 at 7:02 PM Christopher 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
Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)
> On Nov 5, 2018, at 8:35 AM, Christopher wrote: > > On Mon, Nov 5, 2018 at 3:49 AM Bertrand Delacretaz > wrote: >> >> Hi, >> >> On Fri, Nov 2, 2018 at 7:02 PM Christopher 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 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
Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)
On Mon, Nov 5, 2018 at 3:49 AM Bertrand Delacretaz wrote: > > Hi, > > On Fri, Nov 2, 2018 at 7:02 PM Christopher 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. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Why are large code drops damaging to a community?
Hi, On Sat, Nov 3, 2018 at 8:37 PM Joan Touzet wrote: > ...In a way, it feels a bit like having had bypass surgery, I > guess :) Indeed, thank you very much for sharing this! I think the conclusion at this point is that large code drops are not *necessarily* damaging to a community but handling them requires a lot of attention and work. Along with a strong will of the contributors to help the community in the long term, as opposed to just dropping code and moving on. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Discussions in pull requests vs. dev list (was: The Apache Way and good developers...)
Hi, On Fri, Nov 2, 2018 at 7:02 PM Christopher 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. 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 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
