[GRASS-dev] hacktober, docs

[Daniel Torres]

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 <wenzeslaus at gmail.com> wrote:

>
>
>
> On Thu, 6 Oct 2022 at 13:46, Daniel Torres <nobeeakon at gmail.com> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20221007/6491fe4d/attachment.htm>