Notice to documentation contributors: plans to update the gimp-help repository

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list




[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux