Ben Stott wrote:
> Hi all,
> I put in a request for developer status a few weeks ago so I could
> attempt to work on the 2.0 branch (all this work on 1.3 has given me
> this a renewed drive! :-P), and was just wondering who I should prod to
> get it approved/declined (and/or wondering what else I would have to do
> to get it approved).
Would like to see more CMP (coding standards) compliant patches;
was looking at a patch in STR #2425, and noticed coding style
variations (indenting) not to standard:
http://seriss.com/people/erco/tmp/str-2425-indent.png
The coding standards for FLTK are here:
http://fltk.org/cmp.php
Note that we use tabstops set to 8 (which might be part of the
problem in that patch) and all indenting should be two space.
Basically if 'more' is used to view the code from a default
terminal, indenting should look right. (Even though looking at
a patch as shown above isn't always accurate due to the +/-
inserts, I checked the patch applied and still saw indent issues)
Also, what platforms do you have access to for testing?
Since you'd be the first and only dev on FLTK2 for a while,
we want to be sure you can run well on your own.
Regarding approval, it's up to our devs to give a vote on it,
but it's tough though because none of us are really on 2.0.
Mike has been the overall project lead; you probably need
to talk to him. (He also hosts the website as well as has setup
and admins the entire svn system for FLTK and CUPS).
I imagine we need a strong lead on 2.0 to stay on top of things;
changes compile on all platforms we support (linux/windows/osx),
as I believe there are still regular snapshots made of 2.x that
are copied to downstream mirrors when changes are made.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
