On Thursday 22 May 2008, Stephen Wille Padnos wrote:
> I don't have the full list at the moment, and it's unnecessary.

You mean to say you have no idea who has access - As a supposed project admin 
& "board member", that is a very sad state of affairs... But thanks to Chris, 
we now know. Only 24 out of 64 Sourceforge registered names.

> There are several others who could also serve, depending on the
> subsystem you're changing.  You should ask them first, or ask on this
> list for people who are interested in reviewing a particular patch.

As if anything that has gone before has gone through a review process or 
comments & suggestions acted on. i.e.:
*) Configure goes tits up with gettext 0.15
*) Giving explicit "apt-get install" instructions in a configure error is poor 
policy.
*) Hard coding kernel dependencies and/or non-standard paths is bad.
*) Reimplementing common libraries is poor policy in the long term.
*) Ripping off $random chunks of code just stores up problems for the future.
*) Sticking fingers up at published and accepted standards...

Other issues yet to be raised or resolved:
*) Regular copyright & licencing audits.
*) General bit rot.
*) Distribution of compiled binaries, temporary & hidden files, and general 
cruft in "official" tarballs.
*) Excessive memory usage requiring raising of system limits - A result of 
sloppy coding and/or serious bugs ?
*) Bad practices resulting in fragile or unstable systems.

Most users are presented with a flashy GUI and never look behind the scenes, 
and those that do will either leave well alone or say nothing. Throwing in a 
few bells & whistles and covering it all up with reams of documentation (of 
varying quality or relevance) solves nothing, nor does a FU and attempting to 
ignore or stifle a debate.

> In no particular order, and without their endorsement, here are some
> names to choose from, and the subsystems I think they may be most
> interested in:
> Ken Lerman for interpreter changes

Most of the interpreter changes appear to be reasonably well thought out, 
although I wonder who's "standard" has been used as a reference.

> Ray Henry for tkemc or mini UI changes.

The Tcl/Tk interfaces are pretty stable and haven't changed for a long time. A 
couple of bugs still remain in the underlying code..

> Jon Elson would probably be the best person for modifications to drivers
> that support his hardware.

His hardware/driver(s), NMP - A few SMP bugs in there that are easily fixed, 
and some minor changes would reduce the resulting binary by 25-30%.

> Seb Kuzminsky for mesa driver changes.

Not seen that yet (have some cards though) - The code will be posted for 
review before it is released ?

> Chris Morley for classicladder.

Patches for CL are sent to Marc Le Douarain where they benefit a wider 
audience.

> You also have the option of providing your public SSH key to Chris, so
> you can get developer access yourself.

If anonymous access doesn't work, please explain how sending a "key" will fix 
it.

---

 Paul.

-------------------------------------------------------------------------
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/
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to