<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.14">
<TITLE>Project Steering Committee: Addressing Code submission and contributions</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Courier New">==================</FONT>
<BR><FONT SIZE=2 FACE="Courier New">Source: </FONT><A HREF="http://grass.itc.it/pipermail/grass5/2006-April/022403.html"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Courier New">http://grass.itc.it/pipermail/grass5/2006-April/022403.html</FONT></U></A>
<BR><FONT SIZE=2 FACE="Courier New">><I> Alpha support in the current display architecture isn't going to<BR>
</I>><I> happen (I reverted the last attempt to add it, and will do likewise in<BR>
</I>><I> future).<BR>
</I><BR>
... this is why I really suggest to get interested in a project<BR>
steering committee [1], [2].<BR>
<BR>
Instead of recursively reverted changes of other developers,<BR>
we should come up with a design discussion and then *vote* on it.<BR>
At least for such crucidal pieces of the code I would like to<BR>
see less anarchy and a more formal approach. This will render<BR>
development more transparent to everybody. The scope cannot be to<BR>
have two display management systems in parallel, one without<BR>
and one with alpha support.</FONT>
<BR><FONT SIZE=2 FACE="Courier New">===================</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">I picked this example because it was presented to me. Not because I have an opinion on this particular manner.</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">I thought that the organization of GRASS code was failry streamlined based on a presentation of OSGEO 2005 concerning branches and code history.</FONT></P>
<P><FONT SIZE=2 FACE="Courier New">Perhaps a bit more digging shows some incongruencies to the current system.</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">Someone wants to change, they take initiative. Someone wants to stay the same, and initiaties a counter movement. This could be a flawed ananlysis, but is my general feeling.</FONT></P>
<P><FONT SIZE=2 FACE="Courier New">So maybe, because we have so much code to manage</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">================</FONT>
<BR><FONT SIZE=1 FACE="Courier New">Source: </FONT><A HREF="http://grass.gdf-hannover.de/wiki/GRASS_Project_Steering_Commitee"><U><FONT COLOR="#0000FF" SIZE=1 FACE="Courier New">http://grass.gdf-hannover.de/wiki/GRASS_Project_Steering_Commitee</FONT></U></A>
</P>
<P><FONT SIZE=1 FACE="Courier New">more than 500000 lines of source code in GRASS 6</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">=================</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">What about getting the GRASS backend into OSGEO and leaving the GUI's as they are. No what I'd like to see myself as it has many potential risks in fragmenting the project but maybe we have to sort through less mess.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">What about the concept of the GRASS "Engine". I seem to remember a similar idea back in the days of GRASS Links where the GUI was the web and the engine was barebone GRASS. Or something like that.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">This is not to say that the GUI would not be supported. Or the mutiple GUI's for that matter.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Is there a current verison of this roadmap? For those of us now fluent in CVS</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">=====================</FONT>
<BR><FONT SIZE=2 FACE="Arial">Source: </FONT><A HREF="http://grass.itc.it/devel/roadmap.php"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">http://grass.itc.it/devel/roadmap.php</FONT></U></A>
<BR><FONT SIZE=2 FACE="Arial">Image: roadmap_graphic.jp</FONT>
<BR><FONT FACE="Arial" SIZE=2 COLOR="#000000"> <<roadmap_graphic.jpg>> </FONT>
<BR><FONT SIZE=2 FACE="Arial">========================</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Maybe we need one, two or three GUI streams.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Would this help the coders come on board?</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">What other issues do we have in the contribution department?</FONT>
</P>
</BODY>
</HTML>