[gimp-web] content: news for GIMP 2.99.8 for macOS.

[Jehan <jehanp src gnome org>]

commit b02db5d65f68a1e5b29b94b50a5ef96b88e4b21e
Author: Jehan <jehan girinstud io>
Date:   Sat Dec 4 20:38:34 2021 +0100

    content: news for GIMP 2.99.8 for macOS.

 .../2021/2021-12_GIMP-2.99.8_for_macOS/index.md    | 104 +++++++++++++++++++++
 1 file changed, 104 insertions(+)
---
diff --git a/content/news/2021/2021-12_GIMP-2.99.8_for_macOS/index.md 
b/content/news/2021/2021-12_GIMP-2.99.8_for_macOS/index.md
new file mode 100644
index 00000000..8827b05c
--- /dev/null
+++ b/content/news/2021/2021-12_GIMP-2.99.8_for_macOS/index.md
@@ -0,0 +1,104 @@
+Title: GIMP 2.99.8 macOS package Released (development version)
+Date: 2021-12-06
+Category: News
+Authors: Wilber
+Slug: gimp-2-99-8-for-macos
+Summary: Our first ever 2.99 development release for macOS (GIMP 2.99.8)
+Image: /downloads/downloadsplash-aryeom.jpg
+
+After a year of releasing development versions of GIMP, this is the
+first time we provide a package for macOS! 🥳
+
+» **Download it on [gimp.org "Development Downloads"
+page](https://www.gimp.org/downloads/devel/)** «
+
+So what's happening with GIMP on macOS?
+
+## Regression in recent macOS versions (selection outlines and slowness)
+
+Ever since macOS Big Sur release, a year ago, macOS users were
+[experiencing
+regressions](https://www.gimp.org/news/2020/12/25/gimp-2-10-22-released-macos/#whats-going-on-with-big-sur),
+in particular invisible selection outlines (a.k.a. "marching ants" 🐜)
+and less responsive software. These would happen for everyone using GIMP
+on macOS Big Sur or newer, whatever GIMP version (some people reported
+these problems happened even with old GIMP 2.8 packages), since they are
+changes on the operating system side.
+
+The slowness issue had been mostly worked around by Des McGuinness, our
+previously very active macOS package maintainer, though the software
+reactivity may still not be on-par with other platforms.
+
+We recently fixed the [selection outline
+issue](https://www.gimp.org/news/2021/10/20/gimp-2-99-8-released/#selection-cue-fixed-on-wayland-and-macos)
+and since this announcement, we **backported the fix to GIMP 2.10.28 DMG
+package**! Therefore anyone still having the issue is encouraged to use
+the last packages (both stable 2.10.28 and development 2.99.8 packages
+contain the fix now).
+
+## Team news: new package maintainer
+
+Our new macOS package contributor, Lukas Oberhuber, has been working
+very hard to improve the packaging scripts, clarifying the process by
+merging 2 repositories in one, getting rid of various useless files and
+build rules and directly using modules of the upstream `gtk-osx` project
+(when possible) rather than duplicating rules.
+
+He simplified a lot our [gimp-macos-build](https://gitlab.gnome.org/Infrastructure/gimp-macos-build)
+repository, which should hopefully lower the barrier of entry.
+
+Finally he fixed several bugs or environment code directly in GIMP
+codebase to bring our development code up-to-date with macOS support.
+
+As a consequence, Lukas is now officially a new co-maintainer of the
+macOS package. Welcome and congratulations Lukas! 🥂
+
+## New contributors are still very very welcome 🤗
+
+More serious bugs exist on both the stable and the development series
+for macOS. They are being worked on by Lukas supported by the team core
+developers, yet there are limits to what a single person with OS
+access is able to achieve.
+
+For at least 10 years, it seems GIMP has not been able to have 2 active
+macOS developers at once.
+This is even the second time in a year we publish a
+[macOS-only](https://www.gimp.org/news/2020/12/25/gimp-2-10-22-released-macos/)
+news (which is not a good sign! It means being able to release
+improvements on this OS is exceptional enough that we feel like we
+should inform people).
+
+So we re-iterate our call for contributors: you like GIMP? You use macOS
+and have technical knowledge and skills for packaging and/or development?
+Then you are extremely welcome to break the macOS one-man-show curse.
+
+The first step would be to read the `README` of the
+[gimp-macos-build](https://gitlab.gnome.org/Infrastructure/gimp-macos-build) repository.
+The "*How to build locally*" section might be what you want to try
+first.
+
+Once you make sense of our build scripts and are able to compile your
+own local GIMP, I would recommend to discuss with us on [IRC (#gimp
+channel on GIMPnet - irc.gimp.org)](https://www.gimp.org/discuss.html#irc).
+On IRC, ask `Jehan` or `lukaso` in particular for help (though others
+may be able to help too of course). If you already have specific
+solutions to existing problems, we may propose you a procedure to test
+improvements on our CI for further testing.
+
+# What's next
+
+As usual, we hope that macOS support will improve and that we won't feel
+the need to make dedicated news again. In the end, it depends on macOS
+users, since GIMP is a full community Free Software. It is what we all
+make of it, together. The community has many Linux and Windows
+developers. We also get regular \*BSD and even Hurd patches (seriously).
+How come we barely get any macOS developers?❓
+
+Having M1 support is also a topic we have been discussing obviously. It
+will likely require stabler contributions for this to happen. So come in
+and contribute, everyone, it might be cold ❄ outside, but it's warm 🔥
+in here.
+
+Finally don't forget you can [donate to the project and personally fund
+several GIMP developers](https://www.gimp.org/donating/), as a way to
+give back and accelerate the development of GIMP.