Joel Cornuz posted a note on his Linux Photography blog about CinePaint CMS.
Image courtesy U.S. Air Force
I love that Joel wants a call to action. Unfortunately, a couple of Joel's assumptions aren't quite right.
> color management will be disabled in Cinepaint.
That CMS is being disabled in CinePaint in special cases is true, but that's not to suggest it's being disabled generally. You can always compile it from source.
I made a decision to scale back on the ambition of what we try to get into the next Debian release, to not commit to getting third-party packages included in this go. It's a Debian decision, not a CMS decision.
> it would be cool to have someone willing to help and support Oyranos in Debian
Nobody is saying I can't get a Debian maintainer to help. What we lack is a volunteer to prep 3rd-party libs for Debian.
> Kai-Uwe Behrmann decided to leave the project.
Kai-Uwe is continuing to be supportive off-list. As CMS questions arise, I'm forwarding those emails to him. His latest notes, that I posted here on Friday, are certainly helpful.
> a chance to see Kai-Uwe back to the project (yeah!)
Kai-Uwe will come back when he's ready.
Kai-Uwe has been active in CinePaint for five years. That's longer than anyone should expect from a volunteer. People get burned out or have other things they need to do in their lives. Kai-Uwe's dedication should not be tested with a plea he toil tirelessly another five years. We need to be thankful for what he's already done.
Someone else needs to step up.
An issue we face going forward is CMS was always Kai-Uwe's realm. We need documentation of how CMS works now in CinePaint, with notes what it should do in the future. Beyond that simple task, someone will need to lead CinePaint CMS, to work with our users, me, Kai-Uwe and Debian.
Who will step up?
Love you guys,