You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Christofer Dutz <ch...@c-ware.de> on 2022/06/26 11:17:16 UTC
[CALL FOR VOLUNTEERS] Updating the documentation
Hi all,
I have recently noticed that the documentation of most of our drivers, tools and integration modules has grown a bit stale and out-of-date.
Who would be willing to help with giving the existing documents a review and some updates?
I know that I could definitely do that, but I also know that this could be considered low-hanging-fruit for people willing to start contributing and I would like to concentrate on starting to work on the documentation of our code-generation stuff, which I would not consider low-hanging-fruit.
So? Who wants to become a bit more active again or who want's to get started in contributing to our awesome project?
It's actually super simple, as our website is generated as part of the build by the CI server and all you need to do, is update the asciidoc documents in src/site/asciidoc.
As always ... always happy to help if you need help.
Chris
Re: [CALL FOR VOLUNTEERS] Updating the documentation
Posted by Christofer Dutz <ch...@c-ware.de>.
Sounds like a plan :-)
Holen Sie sich Outlook für Android<https://aka.ms/AAb9ysg>
________________________________
From: Lukas Ott <ot...@gmail.com>
Sent: Monday, June 27, 2022 4:56:06 PM
To: dev@plc4x.apache.org <de...@plc4x.apache.org>
Subject: Re: [CALL FOR VOLUNTEERS] Updating the documentation
Hi Chris,
We can discuss the details next week in our PLC4X community meeting.
I would like to support and update the documentation.
So we may do some examples together during the community meeting and I will
then continue updating other parts (based on the example we created
together) of the documentation.
Luk
Am So., 26. Juni 2022 um 13:17 Uhr schrieb Christofer Dutz <
christofer.dutz@c-ware.de>:
> Hi all,
>
> I have recently noticed that the documentation of most of our drivers,
> tools and integration modules has grown a bit stale and out-of-date.
> Who would be willing to help with giving the existing documents a review
> and some updates?
> I know that I could definitely do that, but I also know that this could be
> considered low-hanging-fruit for people willing to start contributing and I
> would like to concentrate on starting to work on the documentation of our
> code-generation stuff, which I would not consider low-hanging-fruit.
>
> So? Who wants to become a bit more active again or who want's to get
> started in contributing to our awesome project?
>
> It's actually super simple, as our website is generated as part of the
> build by the CI server and all you need to do, is update the asciidoc
> documents in src/site/asciidoc.
>
> As always ... always happy to help if you need help.
>
> Chris
>
Re: [CALL FOR VOLUNTEERS] Updating the documentation
Posted by Lukas Ott <ot...@gmail.com>.
Hi Chris,
We can discuss the details next week in our PLC4X community meeting.
I would like to support and update the documentation.
So we may do some examples together during the community meeting and I will
then continue updating other parts (based on the example we created
together) of the documentation.
Luk
Am So., 26. Juni 2022 um 13:17 Uhr schrieb Christofer Dutz <
christofer.dutz@c-ware.de>:
> Hi all,
>
> I have recently noticed that the documentation of most of our drivers,
> tools and integration modules has grown a bit stale and out-of-date.
> Who would be willing to help with giving the existing documents a review
> and some updates?
> I know that I could definitely do that, but I also know that this could be
> considered low-hanging-fruit for people willing to start contributing and I
> would like to concentrate on starting to work on the documentation of our
> code-generation stuff, which I would not consider low-hanging-fruit.
>
> So? Who wants to become a bit more active again or who want's to get
> started in contributing to our awesome project?
>
> It's actually super simple, as our website is generated as part of the
> build by the CI server and all you need to do, is update the asciidoc
> documents in src/site/asciidoc.
>
> As always ... always happy to help if you need help.
>
> Chris
>