[GRASS-dev] endian & generic library

[Brad Douglas]

On Sat, 2006-05-20 at 16:09 -0700, Michael Barton wrote:
> I would like to humbly mention that the issues below are another reason why
> GRASS probably needs something like a PSC and process for formalizing such
> decisions now. It has grown from a CERL in-house project to an enormous,
> exceedingly complex, wonderfully active, and very powerful geospatial
> research tool. A year or so ago, before some code clean up, someone
> (Hamish?) noted that GRASS is one of the largest open-source projects in
> existence with respect to the size of its code base.
> 
> These features that make this such a great project and useful software also
> make it increasingly complex to self-manage in an organized way. We all do
> an impressive job of it, but a more structured way of coming to design
> decisions would be helpful and will become increasingly important if the
> project continues to grow and be dynamic. Maybe we need a fairly loose and
> hierarchical kind of organization, but some kind of more formal process
> would be helpful to me at least.

Agreed.  Completely.

Markus, what is the current status of the PSC and foundation?


-- 
Brad Douglas <rez touchofmadness com>                      KB8UYR
Address: 37.493,-121.924 / WGS84    National Map Corps #TNMC-3785