[OSCOM] heading and direction of OSCOM

Dear Paul, Gregor et al,
   I have started monitoring this OSCOM General and am thinking about
jumping in with both feet.  Can we talk about the current zeitgeist and
possible future directions?  My bent is towards wiki-cms fusion and systems
more obviously linked with economic productivity.
  The non-profit structure is commensurate with a mission of rewarding
programmers for valuable work.  My vision is of an "open" revision control
and release system that facilatates multi-sided collaboration and also
allowers code developers to collect rent.  For worse but also for better,
the latter condition appears to be a sine qua non if the rent collected is
to be competitive with professional programmer's salaries.
  Hence the direction I'd suggest for OSCOM would first of all be very
proactive in terms of obtaining the best source control and release
processes and technology.  (If specifying such is not an appropriate goal
for OSCOM but perhaps something that could be better done at SourceForge,
please say so.)  If OSCOM is willing to go in this direction, I would then
write a proposal for significant grant funds most of which would be
distributed for software that meets agreed specifications.
  This direction will be anathema to zealots for costlessness so I am
concerned about the
" The Apache Foundation-like structure of OSCOM is ok, but has been
anticipated as too exclusive up-to-now. What is needed is a rather loose
interpretation of the existing organizational structure, to give it a more
inclusive spin and to allow more groups and persons to be involved with a
low barrier of entry."

_______________________________________________
General mailing list
[email protected]
http://oscom.org/cgi-bin/mailman/listinfo/general