For PBWiki, the pros are:
- no additional hosting infrastructure
- the wiki software used by OpenID, OAuth and Activity Streams
and the cons are:
- their backup format is not directly compatible with a piece of open
source wiki software
- MediaWiki has broader familiarity
For MediaWiki, the pros are:
- broad familiarity among open source projects
- it's open source
and the cons are:
- we need to host it, upgrade it, back it up
To try to judge if we have consensus, where do you stand between the
two options?
--David
S.
I appreciate the "it's there, it works" approach, but I would like to
see the OWF work towards evangelizing Open Web standards & tools by
means of illustrating best practices.
Nascent organizations such as ours always need some bootstrapping - so
getting something up and running ASAP is key. Longer term, however, I
think we should strive to use tools that best exemplify the principles
the foundation exists to protect & promote. So, Wikia (by virtue of
being hosted MediaWiki) seems like a stronger choice. We should be
striving to use Free/ Open Source software that implements/promotes
the Open Web standards that we care about.
my $0.02 CAD ;-)
.j
--
James Walker :: http://walkah.net/ :: xmpp:wal...@walkah.net
In my mind, a hosted option is the clear winner, although the downside
isn't risk free. There's the the lack of customization, and...
...When considering the long term plan for the OWF incubator, I think
that the technology stack we choose now should take into consideration
what we can roll as a packaged solution for open source projects and
orgs in the future. Clearly, this will be most cost effective and
achievable with open source software.
But, back to the matter at hand...If we are looking at both open
source and commercial options, we should check out Confluence. It's a
very powerful enterprise wiki platform and the team at Atlassian may
even offer us a hosted version for free.
-Brady
Sent from my iPhone
HTH
Ian
[1] http://www.webfaction.com/
[2] www.cherrypy.org/
--
http://ianlawrence.info
S.
--David
--David
Would love to see the wiki setup at: wiki.openwebfoundation.org
Thoughts?
--
Brady Brim-DeForest
www.brimdeforest.com (the blog)
www.tubefilter.tv (the company)
Follow me: twitter.com/bradybd
This email is: [ ] bloggable [X] ask first [ ] private
--
Brady Brim-DeForest
www.brimdeforest.com (the blog)
www.tubefilter.tv (the company)
Follow me: twitter.com/bradybd
This email is: [ ] bloggable [X] ask first [ ] private
I'm going to email the OSU OSL to figure out what our plan should be
to help get stuff rolling.
--David
Committees can find their own sweet spot for making decisions. Votes are generally best avoided for stuff like this. This is where the role of a chair is instrumental to running a successful committee. The chair, each according to their own style, has to build consensus and call consensus. That is usually enough to make decisions, appoints people, and get work down. If someone has an objection, the chair has to address it.
Once the committee is formed (tonight), it can quickly elect a chair (a committee member). So far only one person asked to be considered for the role. If more people will want to serve as chair, the committee will hold a quick vote. I would suggest an open vote since this is not a very political issue (but the committee may choose to do it differently).
EHL