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
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 <nobeeakon@gmail.com> 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
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 (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
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 <veroandreo@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 worked fully as expected. Have a look at the PRs here: https://github.com/OSGeo/grass-website/pulls
Best,
VeroEl sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
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 (<nobeeakon@gmail.com>) 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 <veroandreo@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 worked fully as expected. Have a look at the PRs here: https://github.com/OSGeo/grass-website/pulls
Best,
VeroEl sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
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 <veroandreo@gmail.com> 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 (<nobeeakon@gmail.com>) 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 <veroandreo@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 worked fully as expected. Have a look at the PRs here: https://github.com/OSGeo/grass-website/pulls
Best,
VeroEl sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 (<nobeeakon@gmail.com>) 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 <veroandreo@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 worked fully as expected. Have a look at the PRs here: https://github.com/OSGeo/grass-website/pulls
Best,
VeroEl sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
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 <veroandreo@gmail.com> 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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 (<nobeeakon@gmail.com>) 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 <veroandreo@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 worked fully as expected. Have a look at the PRs here: https://github.com/OSGeo/grass-website/pulls
Best,
VeroEl sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 (<nobeeakon@gmail.com>) 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 <veroandreo@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 worked fully as expected. Have a look at the PRs here: https://github.com/OSGeo/grass-website/pulls
Best,
VeroEl sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
…but I should add: Let’s see what works.
On Mon, 1 Aug 2022 at 14:56, Vaclav Petras <wenzeslaus@gmail.com> 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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 (<nobeeakon@gmail.com>) 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 <veroandreo@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 worked fully as expected. Have a look at the PRs here: https://github.com/OSGeo/grass-website/pulls
Best,
VeroEl sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
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 <wenzeslaus@gmail.com> wrote:
…but I should add: Let’s see what works.
On Mon, 1 Aug 2022 at 14:56, Vaclav Petras <wenzeslaus@gmail.com> 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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 (<nobeeakon@gmail.com>) 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 <veroandreo@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 worked fully as expected. Have a look at the PRs here: https://github.com/OSGeo/grass-website/pulls
Best,
VeroEl sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
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 <wenzeslaus@gmail.com> 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 <wenzeslaus@gmail.com> wrote:
…but I should add: Let’s see what works.
On Mon, 1 Aug 2022 at 14:56, Vaclav Petras <wenzeslaus@gmail.com> 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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 <nobeeakon@gmail.com> 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 <veroandreo@gmail.com> 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 (<nobeeakon@gmail.com>) 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 <veroandreo@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 worked fully as expected. Have a look at the PRs here: https://github.com/OSGeo/grass-website/pulls
Best,
VeroEl sáb, 30 jul 2022 a las 23:46, Vaclav Petras (<wenzeslaus@gmail.com>) 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 <nobeeakon@gmail.com> 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
Hi Daniel,
El mié, 3 ago 2022 a las 14:56, Daniel Torres (<nobeeakon@gmail.com>) escribió:
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.
Well, this sounds similar to Nick’s attempt here: https://github.com/OSGeo/grass-website/pull/131. Have you seen that one? When I tested it it was super fast too, but for some reason it was not searching within the page. The link you point claims to be super fast, so which would be the disadvantages then?
Other options listed in Hugo’s website are paid, like Algolia.
IMHO, paid options are not an option
So, maybe it would be better to just take the other approach of using Duckduckgo or google in the mean time?
If you prefer any of these, it’s also fine. Which would be the advantages/disadvantages?
In any case, I’d suggest discussing these in the issue, so it’s all in the same place 
Thanks for taking over this! We really appreciate it!
Vero
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 <wenzeslaus@gmail.com> 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 <nobeeakon@gmail.com> 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