Re: [GRASS-dev] communication of community sprint decisions
On Thu, Jan 23, 2020 at 5:55 PM Markus Neteler wrote: ... > - GitHub > - issues enabled: https://github.com/OSGeo/grass/issues (yet empty ;-) ... > - define a GitHub issue template. I have added a bug report and a feature request template: https://github.com/OSGeo/grass/tree/master/.github/ISSUE_TEMPLATE/ .. feel free to improve them or discuss here. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
done :) https://grass.osgeo.org/news/88/15/GRASS-GIS-issues-now-in-GitHub/ El jue., 23 ene. 2020 a las 14:14, Veronica Andreo () escribió: > Great news! > > El jue., 23 ene. 2020 13:55, Markus Neteler escribió: > >> Hi all, >> >> I have now modified >> >> - trac permissions: >> - For the role "authenticated" I have remove [X] TICKET_CREATE >> - trac menu [1]: >> - View Tickets --> https://github.com/OSGeo/grass/issues >> - New Ticket --> https://github.com/OSGeo/grass/issues/new >> - GitHub >> - issues enabled: https://github.com/OSGeo/grass/issues (yet empty >> ;-) >> >> Let me know if I overlooked anything. >> >> TODOs: >> - write an announcement to the lists / "News" section on the web site >> - define a GitHub issue template. >> >> Volunteers welcome. > > > I can help with the announcement part > > Vero > > > > [1] trac menu modified in trac.ini, according to >> >> https://trac.edgewall.org/wiki/TracInterfaceCustomization#CustomNavigationEntries >> >> Cheers, >> Markus >> ___ >> grass-dev mailing list >> grass-dev@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/grass-dev > > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
Great news! El jue., 23 ene. 2020 13:55, Markus Neteler escribió: > Hi all, > > I have now modified > > - trac permissions: > - For the role "authenticated" I have remove [X] TICKET_CREATE > - trac menu [1]: > - View Tickets --> https://github.com/OSGeo/grass/issues > - New Ticket --> https://github.com/OSGeo/grass/issues/new > - GitHub > - issues enabled: https://github.com/OSGeo/grass/issues (yet empty > ;-) > > Let me know if I overlooked anything. > > TODOs: > - write an announcement to the lists / "News" section on the web site > - define a GitHub issue template. > > Volunteers welcome. I can help with the announcement part Vero [1] trac menu modified in trac.ini, according to > > https://trac.edgewall.org/wiki/TracInterfaceCustomization#CustomNavigationEntries > > Cheers, > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
Hi all, I have now modified - trac permissions: - For the role "authenticated" I have remove [X] TICKET_CREATE - trac menu [1]: - View Tickets --> https://github.com/OSGeo/grass/issues - New Ticket --> https://github.com/OSGeo/grass/issues/new - GitHub - issues enabled: https://github.com/OSGeo/grass/issues (yet empty ;-) Let me know if I overlooked anything. TODOs: - write an announcement to the lists / "News" section on the web site - define a GitHub issue template. Volunteers welcome. [1] trac menu modified in trac.ini, according to https://trac.edgewall.org/wiki/TracInterfaceCustomization#CustomNavigationEntries Cheers, Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
Hi, On Tue, Jan 14, 2020 at 3:34 PM Vaclav Petras wrote: > On Mon, Jan 13, 2020 at 3:00 PM Markus Neteler wrote: >> On Mon, Jan 13, 2020 at 8:22 PM Vaclav Petras wrote: >> > On Sat, Jan 11, 2020 at 6:10 AM Markus Neteler wrote: ... >> >> > Yes. I wrote it there and what I meant by putting this into "Decisions >> >> > made" section is that we >> >> > made that decision, but it won't happen until the steps are done, i.e. >> >> > until >> >> > we allow opening issues on GitHub, disallow opening new issues on Trac, >> >> > and announce this on mailing lists. >> >> >> >> Shall we go for this? What do you think? >> >> I would like to see GH issues enabled now. >> > >> > The plan assumes that Trac allows removing the privilege to create tickets >> > for all users, but leaving tickets editable. Can you please check that? >> >> We could change it to this: >> >> [X] TICKET_VIEW >> [ ] TICKET_CREATE >> [X] TICKET_MODIFY > > > Sounds right. ... so, that would be the easy part. But: >> > Perhaps even the New Ticket in top menu bar could be replaced by link to >> > GitHub for those used to Trac, but that's a low priority. >> >> That seems to be easy: >> https://trac.edgewall.org/wiki/TracInterfaceCustomization#CustomNavigationEntries ... I tried it and it didn't have any effect, or I tried the wrong way. @Martin Landa could you support me here? (trac is nowadays a container on osgeo7) thanks Markus PS: we could activate the issues on GH anyway! ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
El mar., 14 ene. 2020 a las 15:34, Vaclav Petras () escribió: > > > On Mon, Jan 13, 2020 at 3:00 PM Markus Neteler wrote: > >> On Mon, Jan 13, 2020 at 8:22 PM Vaclav Petras >> wrote: >> > On Sat, Jan 11, 2020 at 6:10 AM Markus Neteler >> wrote: >> >> Hi Prague-2019 sprinters, all, >> >> >> >> On Fri, Dec 20, 2019 at 8:52 AM Vaclav Petras >> wrote: >> >> > On Wed, Dec 18, 2019 at 9:44 AM Veronica Andreo < >> veroand...@gmail.com> wrote: >> >> >> >> >> >> >> >> >> I've been reading the discussion page at: >> https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019 >> and I see that we should open new bug reports or feature requests directly >> in GitHub. When does this decision start to take effect? >> >> >> >> >> >> I think it is important to communicate this broadly to the user >> community through grass-user list >> >> > >> >> > >> >> > Yes. I wrote it there and what I meant by putting this into >> "Decisions made" section is that we made that decision, but it won't happen >> until the steps are done, i.e. until we allow opening issues on GitHub, >> disallow opening new issues on Trac, and announce this on mailing lists. >> >> >> >> Shall we go for this? What do you think? >> >> I would like to see GH issues enabled now. >> > >> > >> > The plan assumes that Trac allows removing the privilege to create >> tickets for all users, but leaving tickets editable. Can you please check >> that? >> >> We could change it to this: >> >> [X] TICKET_VIEW >> [ ] TICKET_CREATE >> [X] TICKET_MODIFY >> > > Sounds right. > > >> >> > Perhaps even the New Ticket in top menu bar could be replaced by link >> to GitHub for those used to Trac, but that's a low priority. >> >> That seems to be easy: >> >> https://trac.edgewall.org/wiki/TracInterfaceCustomization#CustomNavigationEntries > > > Great! > > >> Let's go for it! >> > > Yes! > +1! ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
On Mon, Jan 13, 2020 at 3:00 PM Markus Neteler wrote: > On Mon, Jan 13, 2020 at 8:22 PM Vaclav Petras > wrote: > > On Sat, Jan 11, 2020 at 6:10 AM Markus Neteler > wrote: > >> Hi Prague-2019 sprinters, all, > >> > >> On Fri, Dec 20, 2019 at 8:52 AM Vaclav Petras > wrote: > >> > On Wed, Dec 18, 2019 at 9:44 AM Veronica Andreo > wrote: > >> >> > >> >> > >> >> I've been reading the discussion page at: > https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019 > and I see that we should open new bug reports or feature requests directly > in GitHub. When does this decision start to take effect? > >> >> > >> >> I think it is important to communicate this broadly to the user > community through grass-user list > >> > > >> > > >> > Yes. I wrote it there and what I meant by putting this into > "Decisions made" section is that we made that decision, but it won't happen > until the steps are done, i.e. until we allow opening issues on GitHub, > disallow opening new issues on Trac, and announce this on mailing lists. > >> > >> Shall we go for this? What do you think? > >> I would like to see GH issues enabled now. > > > > > > The plan assumes that Trac allows removing the privilege to create > tickets for all users, but leaving tickets editable. Can you please check > that? > > We could change it to this: > > [X] TICKET_VIEW > [ ] TICKET_CREATE > [X] TICKET_MODIFY > Sounds right. > > > Perhaps even the New Ticket in top menu bar could be replaced by link to > GitHub for those used to Trac, but that's a low priority. > > That seems to be easy: > > https://trac.edgewall.org/wiki/TracInterfaceCustomization#CustomNavigationEntries Great! > Let's go for it! > Yes! ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
On Mon, Jan 13, 2020 at 8:22 PM Vaclav Petras wrote: > On Sat, Jan 11, 2020 at 6:10 AM Markus Neteler wrote: >> Hi Prague-2019 sprinters, all, >> >> On Fri, Dec 20, 2019 at 8:52 AM Vaclav Petras wrote: >> > On Wed, Dec 18, 2019 at 9:44 AM Veronica Andreo >> > wrote: >> >> >> >> >> >> I've been reading the discussion page at: >> >> https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019 >> >> and I see that we should open new bug reports or feature requests >> >> directly in GitHub. When does this decision start to take effect? >> >> >> >> I think it is important to communicate this broadly to the user community >> >> through grass-user list >> > >> > >> > Yes. I wrote it there and what I meant by putting this into "Decisions >> > made" section is that we made that decision, but it won't happen until the >> > steps are done, i.e. until we allow opening issues on GitHub, disallow >> > opening new issues on Trac, and announce this on mailing lists. >> >> Shall we go for this? What do you think? >> I would like to see GH issues enabled now. > > > The plan assumes that Trac allows removing the privilege to create tickets > for all users, but leaving tickets editable. Can you please check that? We could change it to this: [X] TICKET_VIEW [ ] TICKET_CREATE [X] TICKET_MODIFY > Perhaps even the New Ticket in top menu bar could be replaced by link to > GitHub for those used to Trac, but that's a low priority. That seems to be easy: https://trac.edgewall.org/wiki/TracInterfaceCustomization#CustomNavigationEntries Let's go for it! Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
On Sat, Jan 11, 2020 at 6:10 AM Markus Neteler wrote: > Hi Prague-2019 sprinters, all, > > On Fri, Dec 20, 2019 at 8:52 AM Vaclav Petras > wrote: > > On Wed, Dec 18, 2019 at 9:44 AM Veronica Andreo > wrote: > >> > >> > >> I've been reading the discussion page at: > https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019 > and I see that we should open new bug reports or feature requests directly > in GitHub. When does this decision start to take effect? > >> > >> I think it is important to communicate this broadly to the user > community through grass-user list > > > > > > Yes. I wrote it there and what I meant by putting this into "Decisions > made" section is that we made that decision, but it won't happen until the > steps are done, i.e. until we allow opening issues on GitHub, disallow > opening new issues on Trac, and announce this on mailing lists. > > Shall we go for this? What do you think? > I would like to see GH issues enabled now. > The plan assumes that Trac allows removing the privilege to create tickets for all users, but leaving tickets editable. Can you please check that? Perhaps even the New Ticket in top menu bar could be replaced by link to GitHub for those used to Trac, but that's a low priority. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
Hi Prague-2019 sprinters, all, On Fri, Dec 20, 2019 at 8:52 AM Vaclav Petras wrote: > On Wed, Dec 18, 2019 at 9:44 AM Veronica Andreo wrote: >> >> >> I've been reading the discussion page at: >> https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019 >> and I see that we should open new bug reports or feature requests directly >> in GitHub. When does this decision start to take effect? >> >> I think it is important to communicate this broadly to the user community >> through grass-user list > > > Yes. I wrote it there and what I meant by putting this into "Decisions made" > section is that we made that decision, but it won't happen until the steps > are done, i.e. until we allow opening issues on GitHub, disallow opening new > issues on Trac, and announce this on mailing lists. Shall we go for this? What do you think? I would like to see GH issues enabled now. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] communication of community sprint decisions
Hi Vero, On Wed, Dec 18, 2019 at 9:44 AM Veronica Andreo wrote: > > I've been reading the discussion page at: > https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019 > and I see that we should open new bug reports or feature requests directly > in GitHub. When does this decision start to take effect? > > I think it is important to communicate this broadly to the user community > through grass-user list > Yes. I wrote it there and what I meant by putting this into "Decisions made" section is that we made that decision, but it won't happen until the steps are done, i.e. until we allow opening issues on GitHub, disallow opening new issues on Trac, and announce this on mailing lists. I don't mean any legal talk, just the same as with the startup. We made the decision, even a concrete plan, but until we actually do that, there is no new startup. I guess I should have included what are the actions to follow, especially since in the past, we did not report that much on "decisions with no actions now, but actions to follow." Best, Vaclav ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] communication of community sprint decisions
Hi devs, I've been reading the discussion page at: https://grasswiki.osgeo.org/wiki/Talk:GRASS_GIS_Community_Sprint_Prague_2019 and I see that we should open new bug reports or feature requests directly in GitHub. When does this decision start to take effect? I think it is important to communicate this broadly to the user community through grass-user list Best, Vero ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
