Re: CinePaint tasks

Kai-Uwe,

Hi. Some of your questions for Mohanjith may be a result of me not 
pushing everything discussed on-list. I'm bringing this discussion 
on-list. You have many good ideas in you email that should be shared.

Everyone, please keep CinePaint development discussion on-list instead 
of writing me privately. I can't keep track what I tell people off-list 
and on-list about CinePaint development.

 > I am not quite sure what your primary goal is for packaging
 > CinePaint.

Mohanjith is our mew package maintainer, mostly dealing with rpm issues:

http://sourceforge.net/people/viewjob.php?group_id=75029&job_id=30274

 > below are some small to bigger sized
 > things to contribute. They are not limitted to packaging

Mohanjith hasn't finished work on 'make rpm' and other rpm tasks I've 
requested. It seems premature to ask for additional tasks beyond packaging.

> o compile Glasgow easily on Posix systems (BSD/Linux/osX/MinGW)
>   (cmake/autotools/PMK ??)

Glasgow builds fine using CMAKE. There's nothing to be done there that 
I'm aware of. I've asked our CMAKE developer Michel Lesoinne to add 
CMAKE support for Film Gimp.

> o create an LSB compatible package for Gtk2 CinePaint including a 
>   installer script, something like the one for Googleearth
>   a new "make lsb" target beside "make rpm"?
>   (shell scripting, autotools)

I didn't know it wasn't LSB already. What are the changes? Why?

Personally, I detest the LSB sprinkling files all over the system making 
it difficult to uninstall. Something I'd like to see make do is create 
an uninstall script (uninstall.cinepaint.sh).

A build option for segmented installation would be nice. That's 
everything installed in one directory or below. A call of rm -rf removes 
completely. From a system security standpoint, apps installing shared 
libs are evil. From a testing standpoint, it would be nice to install 
multiple CinePaint versions that can't collide.

> o translations (po file editing and testing)

If we need a translations maintainer we should post that as an open 
position. What tasks and skills are needed? Will you supervise?

> o dcraw + plug-in update (small C coding)

Sounds like a good small tasker for someone. Does anyone want to do? 
What exactly is needed?

> o last but not least a 0.23 release of the Gtk2 version, including the 
>   many testing, say playing and spotting obvious bugs 
>   (muse, bug communication and fixing, autotools, 
>    testing on various architectures and cutting edge distributions like 
>    on the Novells build server + Open/FreeBSD, possibly Solaris)

I have an UltraSparc. I'll build on Solaris. We have maintainers on 
OpenBSD and FreeBSD.

Anything rpm packaging is within Mohanjith's mandate, should definitely 
be involved in 0.23. By the way, it's my goal that the next version be 
1.0, not 0.23. What needs to be done specifically?

QA beyond rpm testing is outside Mohanjith's mandate. We could post an 
opening for a QA position, but that implies someone will follow through 
to squash bugs. Kai-Uwe, are you doing that? Do we have all the bugs 
squashed in the database?

Kai-Uwe, in case you don't know, you're our autotools maintainer. Nobody 
else is willing to touch it. I've given up on autotools. CMAKE is 
already in place for Glasgow. I want to build with cons, too.

Cheers,

Robin
-- 
Robin Rowe
CinePaint Project Leader
Beverly Hills, California
www.CinePaint.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/