OSCOM's Challenge Loop
One often forgotten aspect in OSCOM is that involvement in the process forces CMSs to evolve through a set of positive challenges.
For example, the Midgard RSS aggregator used to suck until there was proposal that Planet OSCOM could be implemented with another solution. This lead me to improve the aggregator to a level where it works acceptably well.
From #oscom:
daveb: darn! doesn't seem to have category-level feeds. I'll have to fix that.
gregor: hehe
gregor: i like how this forces us all to improve our wares
gregor: ask bergie sometime
bergie: well, there is always the challenge mentality in positive sense.
bergie: "Fix your solution or I'll implement it with *my* CMS"
Similar challenge from Bob Doyle to implement the OSCOM 3 site with skyWriter was what lead us to the Frankenstein CMS concept in the first place.
For example, the Midgard RSS aggregator used to suck until there was proposal that Planet OSCOM could be implemented with another solution. This lead me to improve the aggregator to a level where it works acceptably well.
From #oscom:
daveb: darn! doesn't seem to have category-level feeds. I'll have to fix that.
gregor: hehe
gregor: i like how this forces us all to improve our wares
gregor: ask bergie sometime
bergie: well, there is always the challenge mentality in positive sense.
bergie: "Fix your solution or I'll implement it with *my* CMS"
Similar challenge from Bob Doyle to implement the OSCOM 3 site with skyWriter was what lead us to the Frankenstein CMS concept in the first place.
Continue reading
OSCOM's Visual Identity
We were thinking in OSCOM 4 about how to get the different Open Source CMS projects to feel more connected with the OSCOM process. One part of this was to get some link buttons that would make it easier for the projects to link to OSCOM. Marc Infield from Infield Design responded quickly to Gregor's request. Here are his OSCOM...
First day of OSCOM 4
This conference is smaller than OSCOM 3 held in Harvard university and in about the same range as OSCOM 2 in Berkeley. However, this just means that this time most people attending are developers instead of end-users, and discussion ranges from interoperability topics to cultural issues. I'm chairing the Apache Track of the event. The first day was mostly Jakarta...