[GRASS-dev] [GRASS GIS Elections 2020] Glitch fixed, voting can proceed
Dear members of the GRASS GIS community, It now seems that the problem with the voting system has been solved and you can now vote. Thanks for your patience and apologies for the trouble. We had a few cases where the same people got more than one invitation. In case you got more than one, please be so kind to vote only once. Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Should we use GitHub Discussions?
On Sun, Jan 17, 2021 at 6:35 PM Brendan wrote: > > Could posts on the mailing list automatically be posted on GitHub Discussions > and vice versa? That's how the GRASS Nabble forums work right? Those look > great. If that would work, perhaps yes. Otherwise I'm with Moritz and the others who see the risk of fragmentation etc. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Should we use GitHub Discussions?
On Sun, 17 Jan 2021 at 15:27, Stefan Blumentrath wrote: > > Dear all, > Dear al,, > In general, I do agree with Moritz on this. > > In addition to the risk of more fragmented communication, I do appreciate the > fact that ML-discussion is archived. Furthermore, GitHub discussion seems to > be a feature that locks us more into GitHub and would it make more > complicated if we should be forced to move to another platform (given the > proprietary nature of GitHub). > > I do also see that some discussion has moved to github issues/PRs, but that > is probably only natural, esp. when point of the discussion is specifics of > an implementation / change. > > However, to address both valid issues (demand for web-based forum and a > coherent communication), we could probably to three things: > 1. Encourage all contributors to discuss/mention more significant changes on > the ML. > 2. Promote nabble > [http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html] on our github > repository > 3. Check whether it would be feasible to sign up to nabble / ML with > OAuth/github to make integration more seamless. I have no idea though if this > would be feasible at all. Maybe OSGeo admins know?... > I also agree with Mortiz and Stefan > Cheers > Stefan > ciao Luca ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] First message went without link, new message on its way
Dear members of the GRASS GIS community, We are having an issue with the voting system and are working to solve it asap. We appreciate if you wait with your vote until it is solved. Also some people had more than one e-mail adress registered and therefore got more than one invitation. Most of the duplicates have been deleted, but in case you got more than one, please be so kind to vote only once. Thanks for your patience Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] First message went without link, new message on its way
Dear members of the GRASS GIS community, By an unfortunate missatke, the first message was sent without a link. A new invitation was now sent, hopefully including a link. This last message had to be sent as a "reminder". Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS Elections 2020] Voting starts today at 12:00 UTC
Dear members of the GRASS GIS community, All eligible voters should have received an e-mail by now with the token needed to vote. Please, send me a message in case you were expecting one but got none. The voting system opens today, 2021-01-18 at 12:00 UTC and voting will be possible until Monday 2021-01-25 at 12:00 UTC. Regards, Hernán Chief Return Officer (CRO) ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
