Re: [OSCOM] OSCOM participating at Google Summer of Code, e.g. OSR-101

Chalu Kim <[email protected]>
Newsgroups gmane.comp.cms.oscom
Message-ID <[email protected]>
Michael Wechner wrote:

> Chalu Kim wrote:
>
>> Michael Wechner wrote:
>>
>>> Chalu Kim wrote:
>>>
>>>>
>>>> Or we could talk about best practices or standards and tools such 
>>>> as KUPU, JSR and even AJAX. What kinds of projects OSCOM would have 
>>>> recommended? Something in the inter-operability or standards?
>>>
>>>
>>>
>>>
>>>
>>> yes: Kupu, BXE, JSR-170, OSR-101/AJAX
>>>
>>> Michi
>>
>>
>>
>> There you have it.
>>
>> Instead of focusing on "the package" or CMS matrix
>>
>> The matrix is getting old. I hope you get my meaning.
>
>
>
> yes, I understand, but things are not changing that quickly as they might
> appear to change. Some people have not even heard of Open Source 
> Content Management.

I did not expect it to go differently.  This is a lot like the 60's. 
There were many renegade groups, takes by the general public are very 
different. In ways, current political climates are throw-backs from 
reactions from the 60's.

Most people have not even heard "open-source" period.

>
>>
>> Should you make OSCOM "software" or approved entities or certified 
>> entities in the interest of;
>>
>> 1. interoperability - application level?
>> 2. interoperable content format
>> 3. tools
>
>
>
> all of them
>
>>
>> inkscape is like an illustrator. they got funding. what are you doing 
>> wrong?
>
>
>
> why are we doing anything wrong? Why should we receive funding? Has 
> anyone
> actually tried to get funding?
>
>>
>> Perhaps, OSCOM is viewed as a political body?
>
>
>
> it certainly is, because it's not really neutral, because it's focusing
> on Open Source and Open Source is a "political" issue still, whereas 
> that might
> change in the future, but not for now
>
>>
>> I am just questioning.
>
>
>
> no problem
>
> Michi
>
>>
>>
>>
>
>
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.