I agree with the Github based "follow" logic. The CF mailing list is way too oversaturated with the full GitHub issue tracking thread.
On Wed, Nov 7, 2018 at 2:29 PM Brian Eaton <[email protected]> wrote: > Hi Erik, > > I don't believe that [email protected] is a mailman list. The > cf-metadata mailman list (which I administer at NCAR) is > [email protected]. The LLNL server is the one that gets the github > notifications and sends them to *mostly* the same people who are members of > the mailman list. I say mostly because the membership in these lists is > synchronized by hand. When people sign up or remove themselves from the > mailman list, I send this information to Jeff Painter who then makes the > changes at LLNL. We originally set things up like this so that people > didn't need to sign up in two places to follow the discussions that were > happening on the mailman list and on the trac server at LLNL. As github > has replaced trac the current system was set up. > > I personally would like to see all CF discussion happen on the github site. > This would require people to have github accounts, but then I believe they > would have much better control over the discussions they want to follow. > As this discussion has revealed there is currently a lot of confusion about > where cf-metadata messages are coming from. > > Brian > > > On Wed, Nov 7, 2018 at 1:54 PM Erik Quaeghebeur < > [email protected]> wrote: > >> Dear Jeff, >> >> >> > What can we do? The simplest is to stop the transmission from >> > Github to the mailing list. If only a few people are bothered, >> > I can take them off the LLNL list. I can make either of those >> > changes in a few minutes, once we have a community consensus >> > about what to do. More complicated would be to send some >> > messages but not others to the mailing list. I might be able to >> > do that, depending what criteria we need for choosing messages. >> >> The mailman interface lists an option that may indicate a flexible >> solution: >> >> “Which topic categories would you like to subscribe to?” >> >> You can define a ‘Github’ topic that people can unsubscribe from (or >> people >> are not subscribed to by default). I do not know if and how you easily >> you >> can auto-tag (or however it is done) messages from Github. (Once that >> works, you may create more Github topics so that people can fine-tune >> what >> they get from there through the list.) >> >> If this doesn't work, I am in favor of not sending Github messages to the >> list, but asking interested people to ‘Watch’ the Github repo or selected >> issues there. >> >> >> Best, >> >> Erik >> > -- Doug Schuster [email protected] 303-497-1216 ORCID: 0000-0003-0448-3591 NCAR/CISL Research Data Archive https://rda.ucar.edu
