I was checking recent years and there was nothing in the Code Sprints table, so I did as in 2019 and put a note "(included in project request above)" ;)
El vie, 20 ene 2023 a las 15:58, Anna Petrášová (<kratocha...@gmail.com>) escribió: > Should we move the $3000 to the code sprint section? > https://wiki.osgeo.org/wiki/OSGeo_Budget_2023#Code_Sprints > > > On Fri, Jan 20, 2023 at 1:31 PM Veronica Andreo <veroand...@gmail.com> > wrote: > >> Hi all, >> >> I'd try to get into the Google Summer of Docs first. If that doesn't >> work, we can assign one of the 2 budgeted student grants to documentation >> tasks. >> >> Since the budget presentation deadline is today, I will complete the >> OSGeo table (https://wiki.osgeo.org/wiki/OSGeo_Budget_2023) asking for >> 5000 usd mainly for GRASS GIS 40th bday community sprint and student >> grants. See the details at: >> https://wiki.osgeo.org/wiki/GRASS_GIS_Budget_2023 and >> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2023. >> >> Cheers, >> Vero >> >> El vie, 20 ene 2023 a las 13:49, Michael Barton (<michael.bar...@asu.edu>) >> escribió: >> >>> I think it is a good idea. The docs are very important but for a lot of >>> reasons often get lower priority. >>> >>> Michael >>> _____________________________ >>> >>> C. Michael Barton >>> Associate Director, School of Complex Adaptive Systems ( >>> https://scas.asu.edu) >>> Professor, School of Human Evolution & Social Change ( >>> https://shesc.asu.edu) >>> Director, Center for Social Dynamics & Complexity ( >>> https://complexity.asu.edu) >>> Arizona State University >>> Tempe, AZ 85287-2701 >>> USA >>> >>> Executive Director, Open Modeling Foundation ( >>> https://openmodelingfoundation.github.io) >>> Director, Network for Computational Modeling in Social & Ecological >>> Sciences (https://comses.net) >>> >>> personal website: http://www.public.asu.edu/~cmbarton >>> >>> >>> On Jan 20, 2023, at 8:39 AM, Markus Neteler <nete...@osgeo.org> wrote: >>> >>> Hi PSC, >>> >>> here an idea: our software documentation and Wiki pages are getting >>> older, lacking examples, screenshots, overviews and so on. >>> In the Wikis, redundant material should be streamlined. >>> >>> I see two possibilities: >>> - participate in the recently announced Google season of docs >>> ( >>> https://urldefense.com/v3/__https://developers.google.com/season-of-docs/docs/timeline__;!!IKRxdwAv5BmarQ!dZCTWD1i4KdlFTwbbn2snZP_fbm_K-uQhpFLEqhyV88msQjJY7YnlADF8p9e2U-h65NBxN3hEXnwfnNE3gk$ >>> ) >>> - offer a documentation related mini grant, ideally financed by OSGeo >>> (then it would be relevant for today's budget submission) >>> >>> What do you think? >>> >>> best >>> Markus >>> _______________________________________________ >>> grass-psc mailing list >>> grass-psc@lists.osgeo.org >>> >>> https://urldefense.com/v3/__https://lists.osgeo.org/mailman/listinfo/grass-psc__;!!IKRxdwAv5BmarQ!dZCTWD1i4KdlFTwbbn2snZP_fbm_K-uQhpFLEqhyV88msQjJY7YnlADF8p9e2U-h65NBxN3hEXnwGvfioIU$ >>> >>> >>> _______________________________________________ >>> grass-psc mailing list >>> grass-psc@lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/grass-psc >>> >> _______________________________________________ >> grass-psc mailing list >> grass-psc@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/grass-psc >> >
_______________________________________________ grass-psc mailing list grass-psc@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-psc