<div dir="ltr"> 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.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 1 Aug 2022 at 14:58, Vaclav Petras <<a href="mailto:wenzeslaus@gmail.com">wenzeslaus@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">...but I should add: Let's see what works.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 1 Aug 2022 at 14:56, Vaclav Petras <<a href="mailto:wenzeslaus@gmail.com" target="_blank">wenzeslaus@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 1 Aug 2022 at 14:17, Daniel Torres <<a href="mailto:nobeeakon@gmail.com" target="_blank">nobeeakon@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Venga, muchas gracias Veronica. <br></div><div><br></div><div>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. <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 1, 2022 at 12:58 PM Veronica Andreo <<a href="mailto:veroandreo@gmail.com" target="_blank">veroandreo@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Hola Daniel,<div dir="auto"><br></div><div dir="auto">None of those at time, but you could open a new discussion in github (though that is in the main grass repo...)</div><br>Vero</div><div dir="auto"><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">El lun., 1 ago. 2022 19:51, Daniel Torres <<a href="mailto:nobeeakon@gmail.com" target="_blank">nobeeakon@gmail.com</a>> escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>thanks Veronica, then I'll try with the ones suggested in Hugo website</div><div><br></div>(is there another communication method you guys use, like Slack, discord or something like kind of more direct or quick questions and stuff? ) <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 1, 2022 at 11:43 AM Veronica Andreo <<a href="mailto:veroandreo@gmail.com" rel="noreferrer" target="_blank">veroandreo@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hello Daniel, <br></div><div><br></div><div>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: <a href="https://github.com/OSGeo/grass-website/issues/19" rel="noreferrer" target="_blank">https://github.com/OSGeo/grass-website/issues/19</a></div><div><br></div><div>Vero<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El lun, 1 ago 2022 a las 15:55, Daniel Torres (<<a href="mailto:nobeeakon@gmail.com" rel="noreferrer" target="_blank">nobeeakon@gmail.com</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Thanks guys, <br></div><div>I'm ok with starting on the website. </div><div><br></div><div>About the search, in Hugo website they suggest a couple of methods <a href="https://gohugo.io/tools/search/" rel="noreferrer" target="_blank">https://gohugo.io/tools/search/</a> , have those been tried? <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 31, 2022 at 3:29 AM Veronica Andreo <<a href="mailto:veroandreo@gmail.com" rel="noreferrer" target="_blank">veroandreo@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Daniel, <div><br></div><div>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: <a href="https://github.com/OSGeo/grass-website/pulls" rel="noreferrer" target="_blank">https://github.com/OSGeo/grass-website/pulls</a> </div><div><br></div><div>Best,</div><div>Vero</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<<a href="mailto:wenzeslaus@gmail.com" rel="noreferrer" target="_blank">wenzeslaus@gmail.com</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Daniel,</div><div><br></div><div>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:<br></div><div><br></div><div><a href="https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45" rel="noreferrer" target="_blank">https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45</a><br></div><div><br></div><div>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.</div><div><br></div><div>I would really like to see changes in the documentation (aka HTML manual pages):</div><div><br></div><div><a href="https://grass.osgeo.org/grass83/manuals/" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass83/manuals/</a></div><div><br></div><div>...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.<br></div><div><br></div><div>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!).</div><div><br></div><div>Let me know if there is any other info which would be helpful.</div><div><br></div><div>Best,<br></div><div>Vaclav<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 30 Jul 2022 at 14:18, Daniel Torres <<a href="mailto:nobeeakon@gmail.com" rel="noreferrer" target="_blank">nobeeakon@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>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. <br></div><div><br></div><div>Happy to contribute, but don't really know where to start. (Maybe something on the website side?)<br></div><div><br></div><div>Cheers, <br></div><div> Daniel<br></div></div>
_______________________________________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org" rel="noreferrer" target="_blank">grass-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/grass-dev" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/grass-dev</a><br>
</blockquote></div>
_______________________________________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org" rel="noreferrer" target="_blank">grass-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/grass-dev" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/grass-dev</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div></div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>