Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
Hi all! On Tue, Jun 15, 2021 at 7:47 PM Jehan Pagès wrote: > Hi all! > > On Mon, Jun 7, 2021 at 11:13 AM Marco Ciampa via gimp-developer-list < > gimp-developer-list@gnome.org> wrote: > >> On Sun, Jun 06, 2021 at 01:38:21PM -0400, Jacob Boerema via >> gimp-developer-list wrote: >> > On 5 Jun 2021 at 23:57, Jehan Pagès via gimp-developer-list wrote: >> > >> > > Damned Lies broke on POT generation for this module though, because of >> > > missing dependencies (cf. >> > > https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/236) >> but I >> > > guess it should be fixed soon. >> > >> > It seems that they are having some trouble adding that dependency. >> > >> > They are suggesting using itstool as a possible better way to extract >> > translation strings from XML files than using xml2po. We should >> investigate >> > this. >> > >> >> As I already wrote in the issue page: >> >> https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/236 >> >> Why don't you install the distro package instead? >> It probably has a name like this: >> >> python3-libxml2 (or at least it is that in Debian-Fedora-CentOS-Ubuntu...) >> >> yum install python3-libxml2 >> >> or >> >> apt install python3-libxml2 >> >> > Now Damned Lies has been updated appropriately and the master branch is > properly processed again. > Thanks to all who helped! > > So I proceeded with the branching which was planned. As of today, > `gimp-help-2-10` is the branch to continue working on GIMP 2.10 series > documentation. `master` is now dedicated to GIMP 2.99/3.0 so we can start > documenting new unreleased features. > I opened a bug report to Damned Lies to ask for this new branch to also be > followed by the translation infrastructure: > https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/239 > Thanks to Claude Paroz for taking care of this last point! Now the gimp-help module on Damned Lies follow both the `master` and `gimp-help-2-10` branches: https://l10n.gnome.org/module/gimp-help/ Documentation is now fully ready to diverge. It also means anyone wanting to help contribute on documentation for future GIMP 3 is very welcome to start opening new sections/pages for the new features coming with GIMP 3, even when they are still unfinished. To get a quick idea on these, the 3 development versions already released are a good start: https://www.gimp.org/news/2020/11/06/gimp-2-99-2-released/ https://www.gimp.org/news/2020/12/25/gimp-2-99-4-released/ https://www.gimp.org/news/2021/05/08/gimp-2-99-6-released/ To go further, the NEWS file is obviously a bit more complete: https://gitlab.gnome.org/GNOME/gimp/-/blob/master/NEWS And finally do not hesitate to ask us directly and discuss with us when you don't understand something. The current mailing list is obviously a good discussion point though the IRC channel may be a bit easier to catch people (#gimp on GIMPnet). It might also be a good starting point to discuss how to better synchronize development and documentation. There is this whole help ID business (we can assign an help ID to various parts of the GUI and when these have focus and one hit F1 for instance, or when hitting the Help button on some dialog, it brings you to the corresponding manual page/section) also which I think would be worth being disentangled. How should devs choose the IDs? How should documenters be made aware of new IDs? I think some process and more communication would definitely be worth it. Jehan > Last point: it has been 10 days since I proposed for Jacob to be > co-maintainer on gimp-help repo. We got agreement from Mitch and Marco and > none speaking against, so I proceeded with this. Jacob is now considered a > new co-maintainer of gimp-help! > Welcome Jacob to your new role on this repository (or as you said yourself > on IRC: maybe you are doomed now! ). > > Jehan > > >> -- >> >> Saluton, >> Marco Ciampa >> ___ >> gimp-developer-list mailing list >> List address:gimp-developer-list@gnome.org >> List membership: >> https://mail.gnome.org/mailman/listinfo/gimp-developer-list >> List archives: https://mail.gnome.org/archives/gimp-developer-list >> > > > -- > ZeMarmot open animation film > http://film.zemarmot.net > Liberapay: https://liberapay.com/ZeMarmot/ > Patreon: https://patreon.com/zemarmot > Tipeee: https://www.tipeee.com/zemarmot > -- ZeMarmot open animation film http://film.zemarmot.net Liberapay: https://liberapay.com/ZeMarmot/ Patreon: https://patreon.com/zemarmot Tipeee: https://www.tipeee.com/zemarmot ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
Hi all! On Mon, Jun 7, 2021 at 11:13 AM Marco Ciampa via gimp-developer-list < gimp-developer-list@gnome.org> wrote: > On Sun, Jun 06, 2021 at 01:38:21PM -0400, Jacob Boerema via > gimp-developer-list wrote: > > On 5 Jun 2021 at 23:57, Jehan Pagès via gimp-developer-list wrote: > > > > > Damned Lies broke on POT generation for this module though, because of > > > missing dependencies (cf. > > > https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/236) but > I > > > guess it should be fixed soon. > > > > It seems that they are having some trouble adding that dependency. > > > > They are suggesting using itstool as a possible better way to extract > > translation strings from XML files than using xml2po. We should > investigate > > this. > > > > As I already wrote in the issue page: > > https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/236 > > Why don't you install the distro package instead? > It probably has a name like this: > > python3-libxml2 (or at least it is that in Debian-Fedora-CentOS-Ubuntu...) > > yum install python3-libxml2 > > or > > apt install python3-libxml2 > > Now Damned Lies has been updated appropriately and the master branch is properly processed again. Thanks to all who helped! So I proceeded with the branching which was planned. As of today, `gimp-help-2-10` is the branch to continue working on GIMP 2.10 series documentation. `master` is now dedicated to GIMP 2.99/3.0 so we can start documenting new unreleased features. I opened a bug report to Damned Lies to ask for this new branch to also be followed by the translation infrastructure: https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/239 Last point: it has been 10 days since I proposed for Jacob to be co-maintainer on gimp-help repo. We got agreement from Mitch and Marco and none speaking against, so I proceeded with this. Jacob is now considered a new co-maintainer of gimp-help! Welcome Jacob to your new role on this repository (or as you said yourself on IRC: maybe you are doomed now! ). Jehan > -- > > Saluton, > Marco Ciampa > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > -- ZeMarmot open animation film http://film.zemarmot.net Liberapay: https://liberapay.com/ZeMarmot/ Patreon: https://patreon.com/zemarmot Tipeee: https://www.tipeee.com/zemarmot ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
On Sun, Jun 06, 2021 at 01:38:21PM -0400, Jacob Boerema via gimp-developer-list wrote: > On 5 Jun 2021 at 23:57, Jehan Pagès via gimp-developer-list wrote: > > > Damned Lies broke on POT generation for this module though, because of > > missing dependencies (cf. > > https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/236) but I > > guess it should be fixed soon. > > It seems that they are having some trouble adding that dependency. > > They are suggesting using itstool as a possible better way to extract > translation strings from XML files than using xml2po. We should investigate > this. > As I already wrote in the issue page: https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/236 Why don't you install the distro package instead? It probably has a name like this: python3-libxml2 (or at least it is that in Debian-Fedora-CentOS-Ubuntu...) yum install python3-libxml2 or apt install python3-libxml2 -- Saluton, Marco Ciampa ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
On 5 Jun 2021 at 23:57, Jehan Pagès via gimp-developer-list wrote: > Damned Lies broke on POT generation for this module though, because of > missing dependencies (cf. > https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/236) but I > guess it should be fixed soon. It seems that they are having some trouble adding that dependency. They are suggesting using itstool as a possible better way to extract translation strings from XML files than using xml2po. We should investigate this. Regards, Jacob Boerema ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
On Sat, Jun 05, 2021 at 11:57:27PM +0200, Jehan Pagès wrote: > By the way, I would like to propose for Jacob Boerema to be promoted as > co-maintainer on the gimp-help repository, since I believe he is now the > one who knows the best its technical logics, scripts and alike among still > active contributors (actually even considering activity on gimp-help in the > last 10 years, he did the most in the last few weeks). For the record, > Jacob has been a very active GIMP contributor for a year now, and he is > doing excellent technical work. > I believe the gimp-help repository can only benefit from having someone > technical-side among its co-maintainers. > > Thus is there any of the current maintainers against adding Jacob as a new > co-maintainer? I'll take an absence of answer as being OK with it, but if > you read and are in favor, I will appreciate even a short answer. > If none is against it, I propose we add him on the maintainers list in a > week or so. It's ok for me... BTW the making process seems to me a little bit faster now... -- Saluton, Marco Ciampa ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
Hi all! On Thu, Jun 3, 2021 at 10:39 PM Marco Ciampa via gimp-developer-list < gimp-developer-list@gnome.org> wrote: > On Thu, May 20, 2021 at 03:46:13AM +0200, Jehan Pagès wrote: > > Hello all! > > Sorry for the late reply... > > > Some efforts is being made to improve a bit the documentation process: > > > > 1. A Python 3 port is being worked on right now by Jacob Boerema (see > > https://gitlab.gnome.org/GNOME/gimp-help/-/merge_requests/50). He nearly > > finished. I don't think anyone is against this since Python 2 is EOL, but > > if anyone has any comment, please feel free. Also Jacob has some issues > > with the `xml_helper.py` script so we wondered if this one was actually > > being used by anyone actually contributing to the documentation (because > if > > not, and it is not considered useful anymore, maybe some time can be > saved > > by dropping this script). > > In any case, feel free to test the associated branch and make any remark. > > It's ok for me. > For the record, we merged the Python 3 port today. So gimp-help is now at least a bit less outdated! 藍 Damned Lies broke on POT generation for this module though, because of missing dependencies (cf. https://gitlab.gnome.org/Infrastructure/damned-lies/-/issues/236) but I guess it should be fixed soon. By the way, I would like to propose for Jacob Boerema to be promoted as co-maintainer on the gimp-help repository, since I believe he is now the one who knows the best its technical logics, scripts and alike among still active contributors (actually even considering activity on gimp-help in the last 10 years, he did the most in the last few weeks). For the record, Jacob has been a very active GIMP contributor for a year now, and he is doing excellent technical work. I believe the gimp-help repository can only benefit from having someone technical-side among its co-maintainers. Thus is there any of the current maintainers against adding Jacob as a new co-maintainer? I'll take an absence of answer as being OK with it, but if you read and are in favor, I will appreciate even a short answer. If none is against it, I propose we add him on the maintainers list in a week or so. By the way, if anyone wants to update some data in the list, please tell me (if you don't want to be considered a maintainer anymore for instance because you went to do something else and have no time anymore for gimp-help; or if you just want to update your email address, etc.). At least one person in the current list has an email address which doesn't work anymore. For current info, see: https://gitlab.gnome.org/GNOME/gimp-help/-/blob/master/gimp-help.doap > > 2. We are considering branching the tree (to `gimp-help-2-10`) so that > the > > `master` branch will be used for preparing the documentation specific to > > GIMP 3, whereas any work specific to the 2.10.x series can continue on > the > > new branch. > > Ok I'll finish updating the Italian translation presumably tomorrow. > Cool. Maybe we'll hold off the branching a day or 2 to first resolve the Damned Lies issues and if we find any more little details to fix before branching. > > > We feel like these 3 plans could be done in about 2 weeks (so let's say > the > > weekend of June 5/6), but if anyone feels like this is wrong, or that > > things should be done differently, please tell us before we merge the > > Python 3 port and branch the `master` tree, please. > > It's ok for me. > > > Róman Joost, Ulf-D. Ehlert, Marco Ciampa, Julien Hardelin, Michael > Natterer > > and Michael Schumacher (all in BCC) in particular, you are the > > co-maintainers of this repository (if the `MAINTAINERS` and .doap files > are > > still up-to-date), so we'd appreciate your input in particular. Any other > > contributor is welcome to give an opinion too of course. We don't want to > > do any mistake. > > > > The third plan we have (not within a 2-week schedule, but hopefully at > > least before GIMP 3 release) is that we wonder if a better process for > > releases of the documentation (on the website in particular) could not be > > done. Maybe we are wrong, but it feels like the release/update into the > > wild could be improved, couldn't it? > > What we are thinking are things like tagging the tree leading to > automatic > > (or at least easier) build then publication of the documentation online, > > probably through the Continuous Integration pipelines (we have been > > improving GIMP release the same way lately, by generating source tarballs > > automatically, and these days, we are doing the same with the Windows > > installer). > > I would appreciate (=volunteer to translate) a multilanguage site... > > > So same here, if anyone has any opinion or wishes on how the > documentation > > process should be improved, we welcome the ideas and propositions. > > I have one for the future... I'll explain after the branch... > Cool. Let's discuss this when the time comes then! Jehan > > Thanks all! > > Thank YOU! > > -- > >
Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
On Thu, May 20, 2021 at 03:46:13AM +0200, Jehan Pagès wrote: > Hello all! Sorry for the late reply... > Some efforts is being made to improve a bit the documentation process: > > 1. A Python 3 port is being worked on right now by Jacob Boerema (see > https://gitlab.gnome.org/GNOME/gimp-help/-/merge_requests/50). He nearly > finished. I don't think anyone is against this since Python 2 is EOL, but > if anyone has any comment, please feel free. Also Jacob has some issues > with the `xml_helper.py` script so we wondered if this one was actually > being used by anyone actually contributing to the documentation (because if > not, and it is not considered useful anymore, maybe some time can be saved > by dropping this script). > In any case, feel free to test the associated branch and make any remark. It's ok for me. > 2. We are considering branching the tree (to `gimp-help-2-10`) so that the > `master` branch will be used for preparing the documentation specific to > GIMP 3, whereas any work specific to the 2.10.x series can continue on the > new branch. Ok I'll finish updating the Italian translation presumably tomorrow. > We feel like these 3 plans could be done in about 2 weeks (so let's say the > weekend of June 5/6), but if anyone feels like this is wrong, or that > things should be done differently, please tell us before we merge the > Python 3 port and branch the `master` tree, please. It's ok for me. > Róman Joost, Ulf-D. Ehlert, Marco Ciampa, Julien Hardelin, Michael Natterer > and Michael Schumacher (all in BCC) in particular, you are the > co-maintainers of this repository (if the `MAINTAINERS` and .doap files are > still up-to-date), so we'd appreciate your input in particular. Any other > contributor is welcome to give an opinion too of course. We don't want to > do any mistake. > > The third plan we have (not within a 2-week schedule, but hopefully at > least before GIMP 3 release) is that we wonder if a better process for > releases of the documentation (on the website in particular) could not be > done. Maybe we are wrong, but it feels like the release/update into the > wild could be improved, couldn't it? > What we are thinking are things like tagging the tree leading to automatic > (or at least easier) build then publication of the documentation online, > probably through the Continuous Integration pipelines (we have been > improving GIMP release the same way lately, by generating source tarballs > automatically, and these days, we are doing the same with the Windows > installer). I would appreciate (=volunteer to translate) a multilanguage site... > So same here, if anyone has any opinion or wishes on how the documentation > process should be improved, we welcome the ideas and propositions. I have one for the future... I'll explain after the branch... > Thanks all! Thank YOU! -- Saluton, Marco Ciampa ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
Hi João, On Thu, Jun 3, 2021 at 6:55 PM Joao S. O. Bueno wrote: > Just so that this does not feel like no one is reading: > although there is a long time I do not fidle with the docs, > all things listed seem quite reasonable. > Thanks! I was not really thinking none was reading so I didn't mind too much the absence of responses (especially as here I don't think there is anything controversial, but who knows…), but I still needed to make the announcement, just to (1) make sure we are not missing anything with our change and (2) because we don't want anyone to be left out of important decisions. Anyway thanks for the answer! Jehan P.S.: Marco, sorry, I realize you were in the main recipient list of my previous email. You were supposed to be in BCC, along with other maintainers of the gimp-help repository. Anyway, not that your email is not known here , but I know many people don't like to be direct recipients of emails. > On Thu, 3 Jun 2021 at 13:36, Jehan Pagès via gimp-developer-list < > gimp-developer-list@gnome.org> wrote: > >> Hi all, developers, documenters and co-maintainers of the gimp-help >> repository, >> >> This is just a small reminder for our plan to merge the Python 3 port (by >> Jacob Boerema) and do the gimp-help-2-10/master branching this week-end, >> i.e. in 2 or 3 days unless outstanding issues appear. If anyone has a >> reluctance, this is the time to make it heard. >> >> Otherwise, my next and last message on the topic will likely be once we >> have done the merge and branching! >> Have fun and thanks everyone! >> >> Jehan >> >> On Thu, May 20, 2021 at 3:46 AM Jehan Pagès >> wrote: >> >> > Hello all! >> > >> > Some efforts is being made to improve a bit the documentation process: >> > >> > 1. A Python 3 port is being worked on right now by Jacob Boerema (see >> > https://gitlab.gnome.org/GNOME/gimp-help/-/merge_requests/50). He >> nearly >> > finished. I don't think anyone is against this since Python 2 is EOL, >> but >> > if anyone has any comment, please feel free. Also Jacob has some issues >> > with the `xml_helper.py` script so we wondered if this one was actually >> > being used by anyone actually contributing to the documentation >> (because if >> > not, and it is not considered useful anymore, maybe some time can be >> saved >> > by dropping this script). >> > In any case, feel free to test the associated branch and make any >> remark. >> > >> > 2. We are considering branching the tree (to `gimp-help-2-10`) so that >> the >> > `master` branch will be used for preparing the documentation specific to >> > GIMP 3, whereas any work specific to the 2.10.x series can continue on >> the >> > new branch. >> > >> > We feel like these 3 plans could be done in about 2 weeks (so let's say >> > the weekend of June 5/6), but if anyone feels like this is wrong, or >> that >> > things should be done differently, please tell us before we merge the >> > Python 3 port and branch the `master` tree, please. >> > >> > Róman Joost, Ulf-D. Ehlert, Marco Ciampa, Julien Hardelin, Michael >> > Natterer and Michael Schumacher (all in BCC) in particular, you are the >> > co-maintainers of this repository (if the `MAINTAINERS` and .doap files >> are >> > still up-to-date), so we'd appreciate your input in particular. Any >> other >> > contributor is welcome to give an opinion too of course. We don't want >> to >> > do any mistake. >> > >> > The third plan we have (not within a 2-week schedule, but hopefully at >> > least before GIMP 3 release) is that we wonder if a better process for >> > releases of the documentation (on the website in particular) could not >> be >> > done. Maybe we are wrong, but it feels like the release/update into the >> > wild could be improved, couldn't it? >> > What we are thinking are things like tagging the tree leading to >> automatic >> > (or at least easier) build then publication of the documentation online, >> > probably through the Continuous Integration pipelines (we have been >> > improving GIMP release the same way lately, by generating source >> tarballs >> > automatically, and these days, we are doing the same with the Windows >> > installer). >> > >> > So same here, if anyone has any opinion or wishes on how the >> documentation >> > process should be improved, we welcome the ideas and propositions. >> > >> > Thanks all! >> > >> > Jehan, on behalf of the GIMP team >> > >> > -- >> > ZeMarmot open animation film >> > http://film.zemarmot.net >> > Liberapay: https://liberapay.com/ZeMarmot/ >> > Patreon: https://patreon.com/zemarmot >> > Tipeee: https://www.tipeee.com/zemarmot >> > >> >> >> -- >> ZeMarmot open animation film >> http://film.zemarmot.net >> Liberapay: https://liberapay.com/ZeMarmot/ >> Patreon: https://patreon.com/zemarmot >> Tipeee: https://www.tipeee.com/zemarmot >> ___ >> gimp-developer-list mailing list >> List address:gimp-developer-list@gnome.org >> List membership: >>
Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
Just so that this does not feel like no one is reading: although there is a long time I do not fidle with the docs, all things listed seem quite reasonable. On Thu, 3 Jun 2021 at 13:36, Jehan Pagès via gimp-developer-list < gimp-developer-list@gnome.org> wrote: > Hi all, developers, documenters and co-maintainers of the gimp-help > repository, > > This is just a small reminder for our plan to merge the Python 3 port (by > Jacob Boerema) and do the gimp-help-2-10/master branching this week-end, > i.e. in 2 or 3 days unless outstanding issues appear. If anyone has a > reluctance, this is the time to make it heard. > > Otherwise, my next and last message on the topic will likely be once we > have done the merge and branching! > Have fun and thanks everyone! > > Jehan > > On Thu, May 20, 2021 at 3:46 AM Jehan Pagès > wrote: > > > Hello all! > > > > Some efforts is being made to improve a bit the documentation process: > > > > 1. A Python 3 port is being worked on right now by Jacob Boerema (see > > https://gitlab.gnome.org/GNOME/gimp-help/-/merge_requests/50). He nearly > > finished. I don't think anyone is against this since Python 2 is EOL, but > > if anyone has any comment, please feel free. Also Jacob has some issues > > with the `xml_helper.py` script so we wondered if this one was actually > > being used by anyone actually contributing to the documentation (because > if > > not, and it is not considered useful anymore, maybe some time can be > saved > > by dropping this script). > > In any case, feel free to test the associated branch and make any remark. > > > > 2. We are considering branching the tree (to `gimp-help-2-10`) so that > the > > `master` branch will be used for preparing the documentation specific to > > GIMP 3, whereas any work specific to the 2.10.x series can continue on > the > > new branch. > > > > We feel like these 3 plans could be done in about 2 weeks (so let's say > > the weekend of June 5/6), but if anyone feels like this is wrong, or that > > things should be done differently, please tell us before we merge the > > Python 3 port and branch the `master` tree, please. > > > > Róman Joost, Ulf-D. Ehlert, Marco Ciampa, Julien Hardelin, Michael > > Natterer and Michael Schumacher (all in BCC) in particular, you are the > > co-maintainers of this repository (if the `MAINTAINERS` and .doap files > are > > still up-to-date), so we'd appreciate your input in particular. Any other > > contributor is welcome to give an opinion too of course. We don't want to > > do any mistake. > > > > The third plan we have (not within a 2-week schedule, but hopefully at > > least before GIMP 3 release) is that we wonder if a better process for > > releases of the documentation (on the website in particular) could not be > > done. Maybe we are wrong, but it feels like the release/update into the > > wild could be improved, couldn't it? > > What we are thinking are things like tagging the tree leading to > automatic > > (or at least easier) build then publication of the documentation online, > > probably through the Continuous Integration pipelines (we have been > > improving GIMP release the same way lately, by generating source tarballs > > automatically, and these days, we are doing the same with the Windows > > installer). > > > > So same here, if anyone has any opinion or wishes on how the > documentation > > process should be improved, we welcome the ideas and propositions. > > > > Thanks all! > > > > Jehan, on behalf of the GIMP team > > > > -- > > ZeMarmot open animation film > > http://film.zemarmot.net > > Liberapay: https://liberapay.com/ZeMarmot/ > > Patreon: https://patreon.com/zemarmot > > Tipeee: https://www.tipeee.com/zemarmot > > > > > -- > ZeMarmot open animation film > http://film.zemarmot.net > Liberapay: https://liberapay.com/ZeMarmot/ > Patreon: https://patreon.com/zemarmot > Tipeee: https://www.tipeee.com/zemarmot > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
Hi all, developers, documenters and co-maintainers of the gimp-help repository, This is just a small reminder for our plan to merge the Python 3 port (by Jacob Boerema) and do the gimp-help-2-10/master branching this week-end, i.e. in 2 or 3 days unless outstanding issues appear. If anyone has a reluctance, this is the time to make it heard. Otherwise, my next and last message on the topic will likely be once we have done the merge and branching! Have fun and thanks everyone! Jehan On Thu, May 20, 2021 at 3:46 AM Jehan Pagès wrote: > Hello all! > > Some efforts is being made to improve a bit the documentation process: > > 1. A Python 3 port is being worked on right now by Jacob Boerema (see > https://gitlab.gnome.org/GNOME/gimp-help/-/merge_requests/50). He nearly > finished. I don't think anyone is against this since Python 2 is EOL, but > if anyone has any comment, please feel free. Also Jacob has some issues > with the `xml_helper.py` script so we wondered if this one was actually > being used by anyone actually contributing to the documentation (because if > not, and it is not considered useful anymore, maybe some time can be saved > by dropping this script). > In any case, feel free to test the associated branch and make any remark. > > 2. We are considering branching the tree (to `gimp-help-2-10`) so that the > `master` branch will be used for preparing the documentation specific to > GIMP 3, whereas any work specific to the 2.10.x series can continue on the > new branch. > > We feel like these 3 plans could be done in about 2 weeks (so let's say > the weekend of June 5/6), but if anyone feels like this is wrong, or that > things should be done differently, please tell us before we merge the > Python 3 port and branch the `master` tree, please. > > Róman Joost, Ulf-D. Ehlert, Marco Ciampa, Julien Hardelin, Michael > Natterer and Michael Schumacher (all in BCC) in particular, you are the > co-maintainers of this repository (if the `MAINTAINERS` and .doap files are > still up-to-date), so we'd appreciate your input in particular. Any other > contributor is welcome to give an opinion too of course. We don't want to > do any mistake. > > The third plan we have (not within a 2-week schedule, but hopefully at > least before GIMP 3 release) is that we wonder if a better process for > releases of the documentation (on the website in particular) could not be > done. Maybe we are wrong, but it feels like the release/update into the > wild could be improved, couldn't it? > What we are thinking are things like tagging the tree leading to automatic > (or at least easier) build then publication of the documentation online, > probably through the Continuous Integration pipelines (we have been > improving GIMP release the same way lately, by generating source tarballs > automatically, and these days, we are doing the same with the Windows > installer). > > So same here, if anyone has any opinion or wishes on how the documentation > process should be improved, we welcome the ideas and propositions. > > Thanks all! > > Jehan, on behalf of the GIMP team > > -- > ZeMarmot open animation film > http://film.zemarmot.net > Liberapay: https://liberapay.com/ZeMarmot/ > Patreon: https://patreon.com/zemarmot > Tipeee: https://www.tipeee.com/zemarmot > -- ZeMarmot open animation film http://film.zemarmot.net Liberapay: https://liberapay.com/ZeMarmot/ Patreon: https://patreon.com/zemarmot Tipeee: https://www.tipeee.com/zemarmot ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Notice to documentation contributors: plans to update the gimp-help repository
Hello all! Some efforts is being made to improve a bit the documentation process: 1. A Python 3 port is being worked on right now by Jacob Boerema (see https://gitlab.gnome.org/GNOME/gimp-help/-/merge_requests/50). He nearly finished. I don't think anyone is against this since Python 2 is EOL, but if anyone has any comment, please feel free. Also Jacob has some issues with the `xml_helper.py` script so we wondered if this one was actually being used by anyone actually contributing to the documentation (because if not, and it is not considered useful anymore, maybe some time can be saved by dropping this script). In any case, feel free to test the associated branch and make any remark. 2. We are considering branching the tree (to `gimp-help-2-10`) so that the `master` branch will be used for preparing the documentation specific to GIMP 3, whereas any work specific to the 2.10.x series can continue on the new branch. We feel like these 3 plans could be done in about 2 weeks (so let's say the weekend of June 5/6), but if anyone feels like this is wrong, or that things should be done differently, please tell us before we merge the Python 3 port and branch the `master` tree, please. Róman Joost, Ulf-D. Ehlert, Marco Ciampa, Julien Hardelin, Michael Natterer and Michael Schumacher (all in BCC) in particular, you are the co-maintainers of this repository (if the `MAINTAINERS` and .doap files are still up-to-date), so we'd appreciate your input in particular. Any other contributor is welcome to give an opinion too of course. We don't want to do any mistake. The third plan we have (not within a 2-week schedule, but hopefully at least before GIMP 3 release) is that we wonder if a better process for releases of the documentation (on the website in particular) could not be done. Maybe we are wrong, but it feels like the release/update into the wild could be improved, couldn't it? What we are thinking are things like tagging the tree leading to automatic (or at least easier) build then publication of the documentation online, probably through the Continuous Integration pipelines (we have been improving GIMP release the same way lately, by generating source tarballs automatically, and these days, we are doing the same with the Windows installer). So same here, if anyone has any opinion or wishes on how the documentation process should be improved, we welcome the ideas and propositions. Thanks all! Jehan, on behalf of the GIMP team -- ZeMarmot open animation film http://film.zemarmot.net Liberapay: https://liberapay.com/ZeMarmot/ Patreon: https://patreon.com/zemarmot Tipeee: https://www.tipeee.com/zemarmot ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
