In the press

Matt Joyce matt.joyce at
Tue Jul 15 09:28:33 CEST 2008

On Tue, Jul 15, 2008 at 2:47 PM, Sean Moss-Pultz <sean at> wrote:

> Jay Vaughan wrote:
> >> This stood out for me "The tangled pile of mostly outdated and
> >> incomplete documentation at the OpenMoko wiki..."
> >> Is this an accurate evaluation of the wiki ?
> >> If so, what can we do to fix it up, how do we identify old content
> >> and schedule it for updating?
> >
> >
> > I think, personally, its time for a 3rd-party site not related to
> > OpenMoko to pick up the slack here. So much stuff happens too quickly
> > for people who /should/ be updating the wiki to feel like its
> > productive to do so ..
> >
> > What I would like to see is something like an ""
> > website come up that has the following:
> >
> > - Daily blog news akin to the good ol' slashdot, of news from the
> > openmoko scene, gleaned from careful inspection of the mailing lists,
> > of IRC, of the codebase, of code delta's, etc.
> >
> > - Public free Repository of all the latest and greatest 'cool apps'
> > found for OpenMoko
> >
> > - Public forum for discussion of the news.
> >
> > This is, of course, sorta what we've got with things like
> > (which I check daily), combined with the
> > Scaredycat repo's and other such things, but ..  for newcomers .. I
> > don't think any of this is as easily approachable as it would be if it
> > were all put under a single umbrella that is a bit more of an
> > 'openmoko pop culture' site than what we've got right now ..
> Jay
> These are all great ideas and would be very helpful for us. We are a
> small company. And really try to focus all we can on our products.
> Community help to make these more approachable is something that would
> make us all very grateful.
> Let me know if there is anything specific you think we (Openmoko) could
> do to help get this all started.
>   -Sean
My take on the problem is that if a new user searches for information, and
finds something promising but it turns out to be wrong, or out of date, they
will probably not update it.
Once they find the information they may not remember (or be inclined) to go
back and update it.

What new user is going to start off by editing an article about stuff they
don't know?

Perhaps one method of identifying information, it to have a simple way to
flagging an article as 'needs checking'.
Wiki moderators and the community at large could focus their efforts there.

-------------- next part --------------
An HTML attachment was scrubbed...

More information about the community mailing list