Re: [GRASS-dev] hacktober, docs
cool, done, created a PR for it https://github.com/OSGeo/grass-website/pull/336 I'd say it would be good to create some issues for non coding enthusiasts (sorry, I'm not too familiar with the project so can't help with that) and maybe tag some first-issues as hacktober > On Fri, Oct 7, 2022 at 3:14 PM Vaclav Petras wrote: > >> Sounds good to me. Let's get it quickly there. We will take it down soon >> too in any case :-) >> >> On Fri, 7 Oct 2022 at 15:05, Daniel Torres wrote: >> >>> What about something like >>> >>> >>> >>> It is just to have something to show, any suggestion and improvement is >>> welcomed. Otherwise, if you think is ok let me know to do the PR >>> >>> >>> On Fri, Oct 7, 2022 at 9:12 AM Vaclav Petras >>> wrote: >>> >>>> >>>> >>>> On Fri, 7 Oct 2022 at 09:18, Daniel Torres wrote: >>>> >>>>> >>>>> I see that all issues tagged with 'Hacktober' are coding related, do >>>>> you guys have any idea of non coding stuff that could work? like >>>>> first-issue but non coding? mmm I don't know, documentation, missing >>>>> examples, and so on? >>>>> >>>> >>>> Images for documentation are often missing, e.g.: >>>> >>>> https://grass.osgeo.org/grass82/manuals/raster_graphical.html >>>> >>>> (Often it is enough to use the existing example to generate the image.) >>>> >>> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] hacktober, docs
Thanks Vaclav, ok cool, I can do something on the website to promote it. I'll try to do it today. I think it is a good opportunity for people to make contributions to the project, but also for engagement and in terms of community. I see that all issues tagged with 'Hacktober' are coding related, do you guys have any idea of non coding stuff that could work? like first-issue but non coding? mmm I don't know, documentation, missing examples, and so on? I think even simple stuff would be ok. In the grass repo, all the issues are at least 1 year old, are those still relevant today? On Thu, Oct 6, 2022 at 7:52 PM Vaclav Petras wrote: > > > > On Thu, 6 Oct 2022 at 13:46, Daniel Torres wrote: > >> Hi guys, >> are we doing anything for hacktober? I see some 2021 issues in the grass >> repo tagged as hacktober, >> > > ...and the grass and grass-addons repos are tagged and I'm ready to do > some reviews. I just didn't have any capacity to do the promotion myself > and I don't know how many people here follow Hacktoberfest (you can, after > all, do the proper Octoberfest), but yes, we are active although there was > no announcement. > > >> but wondering if it would make sense to make some announcement on the >> site (maybe a dialog when landing in the home, or somewhere in the home ) >> > > Yes. > > >> and if there are non coding (docs and so on) or first issues we could >> add for this (for the grass website or the grass repo). >> > > I did not check the new rules in relation to the website, but non-coding > PRs in grass and grass-addons will count for sure and with the label, we > are set. > > >> Also, asking again about the docs improvements. Vaclav mentioned some >> time ago he would like to see some work on that side, and on JavaScript >> checks in Super-Liner . >> > > The checks are more straightforward, so a better fit for Hacktoberfest. > Also, having HTML/CSS/JS checks in place is a good basis for changing the > documentation because we can merge with greater confidence. > > >> As said before, I'm mostly on frontend stuff and happy to help with that >> (although I'd need some guidance as I'm not familiar with the code and so >> on...) or if you think I'd be helpful in other things, let me know. >> > > If you see something which hurts your eyes or feels really clunky, that > might be a place to start (that might be code, CLI, or documentation on > mobile). Someone will likely be able to point you to the right code. ...or > suggest trying something else first :-) > > Best, > Vaclav > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] hacktober, docs
Hi guys, are we doing anything for hacktober? I see some 2021 issues in the grass repo tagged as hacktober, but wondering if it would make sense to make some announcement on the site (maybe a dialog when landing in the home, or somewhere in the home ) and if there are non coding (docs and so on) or first issues we could add for this (for the grass website or the grass repo). Also, asking again about the docs improvements. Vaclav mentioned some time ago he would like to see some work on that side, and on JavaScript checks in Super-Liner . As said before, I'm mostly on frontend stuff and happy to help with that (although I'd need some guidance as I'm not familiar with the code and so on...) or if you think I'd be helpful in other things, let me know. ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] hi
Hey, getting back to this old email. I´ve made some PRs on the website, I could now have a look at the docs or the other task that Vaclav mentioned (JS checks in Super-Liner) , but will need some guidance on those as I´m not familiar with the repo, the code, and so on. PS. please if you guys can take a look at https://github.com/OSGeo/grass-website/pull/333, which has been hanging there for some time now Thanks, Daniel On Sat, Jul 30, 2022 at 4:46 PM Vaclav Petras wrote: > Hi Daniel, > > Welcome. That sounds great. For Python, check this presentation I'm > preparing for FOSS4G where are I describe how to do good PRs which fix > coding standards and the load of tools which can be applied: > > https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45 > > JavaScript at this point means starting with your own idea which may or > may not be what you are looking for. Website is certainly one option. > > I would really like to see changes in the documentation (aka HTML manual > pages): > > https://grass.osgeo.org/grass83/manuals/ > > ...but that's certainly "bring your own idea." It likely involves some > HTML and CSS design, but perhaps there is something more functional that > can be done. An alternative to this is migrating to Sphinx first, but > that's just a thought from the past. > > Now when I think about it, the full JavaScript checks in Super-Liner are > not enabled, so that's perhaps a small JavaScript task to tackle before > starting a bigger project (that's up to you!). > > Let me know if there is any other info which would be helpful. > > Best, > Vaclav > > > On Sat, 30 Jul 2022 at 14:18, Daniel Torres wrote: > >> Hi guys, I'm Daniel , I work as Front end dev. I would like to contribute >> to the project, as I find it really nice. I have experience with JS and >> front end stuff, but also with Python. >> >> Happy to contribute, but don't really know where to start. (Maybe >> something on the website side?) >> >> Cheers, >> Daniel >> ___ >> 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
[GRASS-dev] website prs
hi guys, could you please give a check to these prs, they have been there for some days - https://github.com/OSGeo/grass-website/pull/334 - https://github.com/OSGeo/grass-website/pull/333 Thanks in advance, Daniel ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] hi
Hi guys, going back to the search feature in the Grass website. I've taken a look at the options in Hugo docs. I think it may not be the best approach to have a client based search as it will require loading big pieces of data... in principle all pages, so loading ... all website pages + all manual pages in a single page. Take this one for example: https://gist.github.com/cmod/5410eae147e4318164258742dd053993 ; using Hugo it creates a json from all pages and then in the search implementation it loads a js library and the json. Other options listed in Hugo's website are paid, like Algolia. So, maybe it would be better to just take the other approach of using Duckduckgo or google in the mean time? On Mon, Aug 1, 2022 at 2:23 PM Vaclav Petras wrote: > Now, I see I misunderstood here. The Discussion is about the communication > channels, not about the website. I guess my comments are still generally > valid, but irrelevant here. Sorry for the noise. > > On Mon, 1 Aug 2022 at 14:58, Vaclav Petras wrote: > >> ...but I should add: Let's see what works. >> >> On Mon, 1 Aug 2022 at 14:56, Vaclav Petras wrote: >> >>> There is no difference in discussing things in the PR or issue versus in >>> a Discussion in terms of notifications, no? If it is about development, it >>> should be part of this mailing list or the PRs/issues in the relevant repo. >>> I don't see what Discussion would add here. ...that's of course different >>> from considering the more "chatty" channels. >>> >>> On Mon, 1 Aug 2022 at 14:17, Daniel Torres wrote: >>> >>>> Venga, muchas gracias Veronica. >>>> >>>> Nice, thanks, I'll open a discussion. I mean, I'm just joining and >>>> possibly there are some downsides of doing so and most probaly it has >>>> already been discussed, but I think it would be useful to ease the >>>> communication. >>>> >>>> On Mon, Aug 1, 2022 at 12:58 PM Veronica Andreo >>>> wrote: >>>> >>>>> Hola Daniel, >>>>> >>>>> None of those at time, but you could open a new discussion in github >>>>> (though that is in the main grass repo...) >>>>> >>>>> Vero >>>>> >>>>> El lun., 1 ago. 2022 19:51, Daniel Torres >>>>> escribió: >>>>> >>>>>> thanks Veronica, then I'll try with the ones suggested in Hugo >>>>>> website >>>>>> >>>>>> (is there another communication method you guys use, like Slack, >>>>>> discord or something like kind of more direct or quick questions and >>>>>> stuff? ) >>>>>> >>>>>> On Mon, Aug 1, 2022 at 11:43 AM Veronica Andreo >>>>>> wrote: >>>>>> >>>>>>> Hello Daniel, >>>>>>> >>>>>>> IIRC, I suggested using something similar to what wowchemy (former >>>>>>> hugo academic) has, but the path chosen was different. Paulo, also made >>>>>>> a >>>>>>> suggestion, but I didn't have the time to try, honestly. I think it's >>>>>>> all >>>>>>> in the PRs and probably this issue too: >>>>>>> https://github.com/OSGeo/grass-website/issues/19 >>>>>>> >>>>>>> Vero >>>>>>> >>>>>>> El lun, 1 ago 2022 a las 15:55, Daniel Torres () >>>>>>> escribió: >>>>>>> >>>>>>>> Thanks guys, >>>>>>>> I'm ok with starting on the website. >>>>>>>> >>>>>>>> About the search, in Hugo website they suggest a couple of methods >>>>>>>> https://gohugo.io/tools/search/ , have those been tried? >>>>>>>> >>>>>>>> On Sun, Jul 31, 2022 at 3:29 AM Veronica Andreo < >>>>>>>> veroand...@gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi Daniel, >>>>>>>>> >>>>>>>>> Welcome! Besides what Vashek pointed out, if you feel comfortable >>>>>>>>> starting with something for the website, we are missing a search >>>>>>>>> engine >>>>>>>>> there. There were a couple of attempts in the past but none of them >>>>>>>>>
Re: [GRASS-dev] hi
Venga, muchas gracias Veronica. Nice, thanks, I'll open a discussion. I mean, I'm just joining and possibly there are some downsides of doing so and most probaly it has already been discussed, but I think it would be useful to ease the communication. On Mon, Aug 1, 2022 at 12:58 PM Veronica Andreo wrote: > Hola Daniel, > > None of those at time, but you could open a new discussion in github > (though that is in the main grass repo...) > > Vero > > El lun., 1 ago. 2022 19:51, Daniel Torres escribió: > >> thanks Veronica, then I'll try with the ones suggested in Hugo website >> >> (is there another communication method you guys use, like Slack, discord >> or something like kind of more direct or quick questions and stuff? ) >> >> On Mon, Aug 1, 2022 at 11:43 AM Veronica Andreo >> wrote: >> >>> Hello Daniel, >>> >>> IIRC, I suggested using something similar to what wowchemy (former hugo >>> academic) has, but the path chosen was different. Paulo, also made a >>> suggestion, but I didn't have the time to try, honestly. I think it's all >>> in the PRs and probably this issue too: >>> https://github.com/OSGeo/grass-website/issues/19 >>> >>> Vero >>> >>> El lun, 1 ago 2022 a las 15:55, Daniel Torres () >>> escribió: >>> >>>> Thanks guys, >>>> I'm ok with starting on the website. >>>> >>>> About the search, in Hugo website they suggest a couple of methods >>>> https://gohugo.io/tools/search/ , have those been tried? >>>> >>>> On Sun, Jul 31, 2022 at 3:29 AM Veronica Andreo >>>> wrote: >>>> >>>>> Hi Daniel, >>>>> >>>>> Welcome! Besides what Vashek pointed out, if you feel comfortable >>>>> starting with something for the website, we are missing a search engine >>>>> there. There were a couple of attempts in the past but none of them worked >>>>> fully as expected. Have a look at the PRs here: >>>>> https://github.com/OSGeo/grass-website/pulls >>>>> >>>>> Best, >>>>> Vero >>>>> >>>>> El sáb, 30 jul 2022 a las 23:46, Vaclav Petras () >>>>> escribió: >>>>> >>>>>> Hi Daniel, >>>>>> >>>>>> Welcome. That sounds great. For Python, check this presentation I'm >>>>>> preparing for FOSS4G where are I describe how to do good PRs which fix >>>>>> coding standards and the load of tools which can be applied: >>>>>> >>>>>> https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45 >>>>>> >>>>>> JavaScript at this point means starting with your own idea which may >>>>>> or may not be what you are looking for. Website is certainly one option. >>>>>> >>>>>> I would really like to see changes in the documentation (aka HTML >>>>>> manual pages): >>>>>> >>>>>> https://grass.osgeo.org/grass83/manuals/ >>>>>> >>>>>> ...but that's certainly "bring your own idea." It likely involves >>>>>> some HTML and CSS design, but perhaps there is something more functional >>>>>> that can be done. An alternative to this is migrating to Sphinx first, >>>>>> but >>>>>> that's just a thought from the past. >>>>>> >>>>>> Now when I think about it, the full JavaScript checks in Super-Liner >>>>>> are not enabled, so that's perhaps a small JavaScript task to tackle >>>>>> before >>>>>> starting a bigger project (that's up to you!). >>>>>> >>>>>> Let me know if there is any other info which would be helpful. >>>>>> >>>>>> Best, >>>>>> Vaclav >>>>>> >>>>>> >>>>>> On Sat, 30 Jul 2022 at 14:18, Daniel Torres >>>>>> wrote: >>>>>> >>>>>>> Hi guys, I'm Daniel , I work as Front end dev. I would like to >>>>>>> contribute to the project, as I find it really nice. I have experience >>>>>>> with >>>>>>> JS and front end stuff, but also with Python. >>>>>>> >>>>>>> Happy to contribute, but don't really know where to start. (Maybe >>>>>>> something on the website side?) >>>>>>> >>>>>>> Cheers, >>>>>>> Daniel >>>>>>> ___ >>>>>>> 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 >>>>>> >>>>> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] hi
thanks Veronica, then I'll try with the ones suggested in Hugo website (is there another communication method you guys use, like Slack, discord or something like kind of more direct or quick questions and stuff? ) On Mon, Aug 1, 2022 at 11:43 AM Veronica Andreo wrote: > Hello Daniel, > > IIRC, I suggested using something similar to what wowchemy (former hugo > academic) has, but the path chosen was different. Paulo, also made a > suggestion, but I didn't have the time to try, honestly. I think it's all > in the PRs and probably this issue too: > https://github.com/OSGeo/grass-website/issues/19 > > Vero > > El lun, 1 ago 2022 a las 15:55, Daniel Torres () > escribió: > >> Thanks guys, >> I'm ok with starting on the website. >> >> About the search, in Hugo website they suggest a couple of methods >> https://gohugo.io/tools/search/ , have those been tried? >> >> On Sun, Jul 31, 2022 at 3:29 AM Veronica Andreo >> wrote: >> >>> Hi Daniel, >>> >>> Welcome! Besides what Vashek pointed out, if you feel comfortable >>> starting with something for the website, we are missing a search engine >>> there. There were a couple of attempts in the past but none of them worked >>> fully as expected. Have a look at the PRs here: >>> https://github.com/OSGeo/grass-website/pulls >>> >>> Best, >>> Vero >>> >>> El sáb, 30 jul 2022 a las 23:46, Vaclav Petras () >>> escribió: >>> >>>> Hi Daniel, >>>> >>>> Welcome. That sounds great. For Python, check this presentation I'm >>>> preparing for FOSS4G where are I describe how to do good PRs which fix >>>> coding standards and the load of tools which can be applied: >>>> >>>> https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45 >>>> >>>> JavaScript at this point means starting with your own idea which may or >>>> may not be what you are looking for. Website is certainly one option. >>>> >>>> I would really like to see changes in the documentation (aka HTML >>>> manual pages): >>>> >>>> https://grass.osgeo.org/grass83/manuals/ >>>> >>>> ...but that's certainly "bring your own idea." It likely involves some >>>> HTML and CSS design, but perhaps there is something more functional that >>>> can be done. An alternative to this is migrating to Sphinx first, but >>>> that's just a thought from the past. >>>> >>>> Now when I think about it, the full JavaScript checks in Super-Liner >>>> are not enabled, so that's perhaps a small JavaScript task to tackle before >>>> starting a bigger project (that's up to you!). >>>> >>>> Let me know if there is any other info which would be helpful. >>>> >>>> Best, >>>> Vaclav >>>> >>>> >>>> On Sat, 30 Jul 2022 at 14:18, Daniel Torres >>>> wrote: >>>> >>>>> Hi guys, I'm Daniel , I work as Front end dev. I would like to >>>>> contribute to the project, as I find it really nice. I have experience >>>>> with >>>>> JS and front end stuff, but also with Python. >>>>> >>>>> Happy to contribute, but don't really know where to start. (Maybe >>>>> something on the website side?) >>>>> >>>>> Cheers, >>>>> Daniel >>>>> ___ >>>>> 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 >>>> >>> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] hi
Thanks guys, I'm ok with starting on the website. About the search, in Hugo website they suggest a couple of methods https://gohugo.io/tools/search/ , have those been tried? On Sun, Jul 31, 2022 at 3:29 AM Veronica Andreo wrote: > Hi Daniel, > > Welcome! Besides what Vashek pointed out, if you feel comfortable starting > with something for the website, we are missing a search engine there. There > were a couple of attempts in the past but none of them worked fully as > expected. Have a look at the PRs here: > https://github.com/OSGeo/grass-website/pulls > > Best, > Vero > > El sáb, 30 jul 2022 a las 23:46, Vaclav Petras () > escribió: > >> Hi Daniel, >> >> Welcome. That sounds great. For Python, check this presentation I'm >> preparing for FOSS4G where are I describe how to do good PRs which fix >> coding standards and the load of tools which can be applied: >> >> https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45 >> >> JavaScript at this point means starting with your own idea which may or >> may not be what you are looking for. Website is certainly one option. >> >> I would really like to see changes in the documentation (aka HTML manual >> pages): >> >> https://grass.osgeo.org/grass83/manuals/ >> >> ...but that's certainly "bring your own idea." It likely involves some >> HTML and CSS design, but perhaps there is something more functional that >> can be done. An alternative to this is migrating to Sphinx first, but >> that's just a thought from the past. >> >> Now when I think about it, the full JavaScript checks in Super-Liner are >> not enabled, so that's perhaps a small JavaScript task to tackle before >> starting a bigger project (that's up to you!). >> >> Let me know if there is any other info which would be helpful. >> >> Best, >> Vaclav >> >> >> On Sat, 30 Jul 2022 at 14:18, Daniel Torres wrote: >> >>> Hi guys, I'm Daniel , I work as Front end dev. I would like to >>> contribute to the project, as I find it really nice. I have experience with >>> JS and front end stuff, but also with Python. >>> >>> Happy to contribute, but don't really know where to start. (Maybe >>> something on the website side?) >>> >>> Cheers, >>> Daniel >>> ___ >>> 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 >> > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] hi
Hi guys, I'm Daniel , I work as Front end dev. I would like to contribute to the project, as I find it really nice. I have experience with JS and front end stuff, but also with Python. Happy to contribute, but don't really know where to start. (Maybe something on the website side?) Cheers, Daniel ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.3
Hi everyone, I'm new here, the website looks really nice. It would be very cool to have it translated, don't know if this has been discussed before, but if it is possible, I could contribute the spanish translation. Cheers, Daniel On Fri, May 8, 2020 at 9:59 PM Martin Landa wrote: > Hi, > > pá 8. 5. 2020 v 13:28 odesílatel Markus Neteler > napsal: > > Yes. I "just" need to transfer the source code subdirs etc. > > Then we may swap the servers. > > Thanks for hard job. > > > > What do you think? Martin > > > > +1 > > Yes, a new release is a good occasion to come with a new website :-) > > Ma > > -- > Martin Landa > http://geo.fsv.cvut.cz/gwiki/Landa > http://gismentors.cz/mentors/landa > ___ > 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
