Re: [OSCOM] Re: Michi resigns from OSCOM [Fwd: [Board] OSCOM ordinary meeting of members minutes]

Seth Gottlieb <[email protected]>
Newsgroups gmane.comp.cms.oscom
Message-ID <[email protected]>
Hi Sandro,

I am interested in participating in this dialog of the future of OSCOM 
on the mail list or wiki or whatever you choose.  As for me, I would 
like to see OSCOM pursue the following:

* Develop and promote a message of "why open source.".  In particular, 
fight the fear.  It would be great to come up with some empirical 
rebuttal to the proprietary software industry's claim that open source 
is actually more expensive because it is essentially un-finished and 
requires a disproportionate amount of effort to install and integrate.
* Promote collaboration and fraternity between developers across projects. 
* Participate in and endorse (or reject) standards (JSR170, OSR101, iECM)

:Let me know if I can be of any help.

--Seth





Sandro Groganz wrote:

> Hi!
>
> Pdm wrote:
>
>> Here is a good idea: open a wiki where we can all contribute to write 
>> up a plan for OSCOM
>> that should give you some input to fuel your good thinking over the 
>> next couple of weeks...
>
>
> Good idea, indeed! Yet, I did not even think about the proper way of 
> channeling the discussion, but this is definitely a good and simple one.
>
> So we actually have to main issues:
>
> - discuss the future of OSCOM?
> - how we want to structure and keep track of the discussion?
>
>> I look forward to seeing our future all laid out
>
>
> I can't promise that there will be no more uncertainties :)
>
> Sandro
>
> _______________________________________________
> General mailing list
> [email protected]
> http://oscom.org/cgi-bin/mailman/listinfo/general


-- 
Seth Gottlieb
Optaros, Inc.
60 Canal Street
Boston, MA 02114
e: [email protected]
v: 617.227.1855 ext. 107
f: 617.227.1755
m: 617.852.2956 
b: http://contenthere.blogspot.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.