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: >> https://mail.gnome
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
Re: [Gimp-developer] GIMP development process
Hi Alex and all! On Wed, 2 Jun 2021 11:48:30 +0300 Alexandre Prokoudine via gimp-developer-list wrote: > On Tue, Jun 1, 2021 at 2:59 PM Jack 04 via gimp-developer-list > wrote: > > > > Dear GIMP team, > > I'm a software engineering student of University of Padova and I would like > > to get some information about GIMP development process, in particular on > > which methodology (i.e. waterfall model, v-shape model, agile methods, > > SCRUM, XP, ...) you chose and why, finally how you have organized it and > > implemented in the team. > > Thank you in advance for your attention, I will wait for your answer. > > Hello, > > Simply put, we don't do any of that. > > We are not a company, we don't have any kind of a contract or boss, > and only some of us receive humble donations. > > We have only rough planning of major releases. We usually set one or > two major goals for every major release (e.g. 2.6, 2.8, 2.10, 3.0) and > then work towards those goals. As there are many, many requests made > by users, we end up with features that can be severely out of scope of > major goals. Moreover, some features are contributed by new people who > are not necessarily a part of what I might flamboyantly call the core > team :) > > We don't set particular goals for minor releases (e.g. 2.10.22 or > 2.99.4). It's typically a mix of some work towards a major goal, minor > or major new features, UX/UI improvements, bug fixes etc. > > Please let me know if you need to know more. > > Alex Thanks for replying so well. In addition, I and others have written: * https://www.shlomifish.org/philosophy/computers/software-management/ * http://programming-motherfucker.com/ * https://www.shlomifish.org/philosophy/philosophy/putting-cards-on-the-table-2019-2020/putting-cards-on-the-table-2019-2020/big-minded-vs-small-minded.xhtml > ___ > 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 -- Shlomi Fish https://www.shlomifish.org/ Freecell Solver - https://fc-solve.shlomifish.org/ If Chuck Norris is disappointed by you not following his advice, he’ll survive. On the other hand, you will not. — https://www.shlomifish.org/humour/bits/facts/Chuck-Norris/ Please reply to list if it's a mailing list post - https://shlom.in/reply . ___ 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
