------=_Part_26666_19067874.1215751307251
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inlineI found this yesterday, thought it was quite an ok article.
http://arstechnica.com/reviews/os/open-moko-software.arsThis 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?Matt
------=_Part_26666_19067874.1215751307251
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline<br>I found this yesterday, thought it was quite an ok article.<br><a href="http://arstechnica.com/reviews/os/open-moko-software.ars">http://arstechnica.com/reviews/os/open-moko-software.ars</a><br><br>This stood out for me "<b>The tangled pile of mostly outdated and incomplete
documentation at the OpenMoko wiki</b>..."<br>Is this an accurate evaluation of the wiki ?<br>If so, what can we do to fix it up, how do we identify old content and schedule it for updating?<br><br>Matt<br><br><br>------=_Part_26666_19067874.1215751307251--
Dear Matt:
Openmoko Wiki just like WIKIPEDIA (http://en.wikipedia.org/wiki/Wiki
Wiki) is a public place everyone can create page , and edit.
Actually , on Openmoko wiki, we have thousand pages. Some topic(page) is
very popular , many people maintains the same page, so it updated soon.
And some page takes long time to complete, so difficult to tell if this
page is complete or not?Here is the rule I used ,
1.To use the wiki "History "function, find out this page's status.
2.Pages only have title, no content, more then half years, no one edit ,
I delete it.
Then , if anyone , want to create this topic, can create the new page ,
anytime.
3.Use Google Analytic , to tell which page is most popular , and mail
Google analytic page view report to community mailing list.Brenda
Openmoko Wiki has thousand pages,
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
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 "mokofanboix.org"
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
planet.openmoko.org (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 Vaughan_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
You can check here to get more about the free Repository
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
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
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Man I have to agree. I'm just jumping on to the OM bandwagon with the
purchase of two freerunners but have reservations about it now.Looking through the Wiki is a pain and a chore to find useful data. Yes
there are gems in there but they are buried under tons of old and
inaccurate data.Some people having very basic problems, like making a phone call, or
playing music, charging the phone, right out of the box is really
inexcusable. And for many this list is the only source of "possible"
solutions!If the OM is going to survive and grow into a viable platform something
has to change. Somebody is going to have to take the reins on
documentation. Information is the key to its success and right now its
in shambles. I'm not trying to point a finger or blame anybody. I think
the scope has grown beyond the ad-hoc means used up to now, especially
since we have a new phone added to the mix. There has to be some
distinction between the 1973 and the FR because it appears they are not
completely compatible.I think OM is going to have to step up to the plate and dedicate some
resources to at least organizing/overseeing and enforcing a standard to
the documentation of the project so there is coherence, timeliness
and to reduce the outdated and inaccurate information.Scott
--
-
"Just because I sound like an idiot doesn't mean I agree with the president."....from an ad on Air America Radio_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
I think it's fair to say most open source projects evolve this way. The
wiki isn't that bad, and if you want to develop starting from any sort
of open and active code base you have to expect a learning curve and
documentation that's not going to be exactly up to date.Keep in mind too that following the sort of massive changes prior to a
release it takes a while for the documentation to catch up.-----Original Message-----
From: community-bounces@lists.openmoko.org
[mailto:community-bounces@lists.openmoko.org] On Behalf Of Scott Derrick
Sent: Tuesday, July 15, 2008 9:15 AM
To: sean@openmoko.com; List for Openmoko community discussion
Subject: Re: In the pressMan I have to agree. I'm just jumping on to the OM bandwagon with the
purchase of two freerunners but have reservations about it now.Looking through the Wiki is a pain and a chore to find useful data. Yes
there are gems in there but they are buried under tons of old and
inaccurate data.Some people having very basic problems, like making a phone call, or
playing music, charging the phone, right out of the box is really
inexcusable. And for many this list is the only source of "possible"
solutions!If the OM is going to survive and grow into a viable platform something
has to change. Somebody is going to have to take the reins on
documentation. Information is the key to its success and right now its
in shambles. I'm not trying to point a finger or blame anybody. I thinkthe scope has grown beyond the ad-hoc means used up to now, especially
since we have a new phone added to the mix. There has to be some
distinction between the 1973 and the FR because it appears they are not
completely compatible.I think OM is going to have to step up to the plate and dedicate some
resources to at least organizing/overseeing and enforcing a standard tothe documentation of the project so there is coherence, timeliness
and to reduce the outdated and inaccurate information.Scott
--
...
Well I'm certainly trying to help in any way I can, while I wait
patiently for my first Freerunner to arrive so I can get on withI think the main thing is we should set up a site thats just fanboix
oriented.. and I mean that in a positive way, not derogatorily.
Basically what I'd like to see is something similar to DSFanboy
(dsfanboy.com), which exists for Nintendo DS owners to check
regularly .. if we had such a site set up that could be easily
contributed to with stories and articles and whatnot, it would help a
great deal.I will continue to glean info from the mailing lists, and in a little
while will consider setting up mokofanboix.org, and maybe take it from
there .. unless someone else is more qualified to do so?;
--
Jay Vaughan_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
This kind of "fork" in the documentation and community is pretty typical in the case of a commercial product that isn't necessarily friendly to hackers. So there's an unofficial fan page where enthusiasts can discuss undocumented/unsupported features, odd uses, hacks, cracks, complain about the manufacturer, diss the users of competing products, and the like. The fan site is owned by the user commmunity and is somewhat isolated from being censored or easily closed down by the manufacturer.
In the Free/Open software world, it's usually very different. It's more typical for that user community to be an integral part of the project itself. There is a much blurrier line between users and developers, and that's pretty much the whole point.
Again, I'll point to the OpenWRT Wiki (and forums, and IRC channel, bug tracker, and mailing list) as a great example of what I consider to be excellent documentation and support for a free project.
-ken
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
------=_Part_833_2831937.1216106914054
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inlineMy 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.MJ
------=_Part_833_2831937.1216106914054
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline<div dir="ltr"><br><br><div class="gmail_quote">On Tue, Jul 15, 2008 at 2:47 PM, Sean Moss-Pultz <<a href="mailto:sean@openmoko.com">sean@openmoko.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">Jay Vaughan wrote:<br>
>> This stood out for me "The tangled pile of mostly outdated and<br>
>> incomplete documentation at the OpenMoko wiki..."<br>
>> Is this an accurate evaluation of the wiki ?<br>
>> If so, what can we do to fix it up, how do we identify old content<br>
>> and schedule it for updating?<br>
><br>
><br>
> I think, personally, its time for a 3rd-party site not related to<br>
> OpenMoko to pick up the slack here. So much stuff happens too quickly<br>
> for people who /should/ be updating the wiki to feel like its<br>
> pro...
------=_Part_934_22744363.1216118291220
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inlineActually I can speak from experience that Matt has hit it on the head. I was
having problems with the moko makefile while trying to test QEMU until I can
afford to get the actual phone. I couldn't figure out why it was building
with a broken GUI, luckily I knew about the mailing lists and someone was
able to point me in the right direction.-Shawn
------=_Part_934_22744363.1216118291220
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline<div dir="ltr">Actually I can speak from experience that Matt has hit it on the head. I was having problems with the moko makefile while trying to test QEMU until I can afford to get the actual phone. I couldn't figure out why it was building with a broken GUI, luckily I knew about the mailing lists and someone was able to point me in the right direction.<br>
<br>-Shawn<br><br><div class="gmail_quote">On Tue, Jul 15, 2008 at 12:28 AM, Matt Joyce <<a href="mailto:matt.joyce@gmail.com">matt.joyce@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><div class="gmail_quote"><div><br>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.<br>
Once they find the information they may not remember (or be inclined) to go back and update it.<br>
<br>What new user is going to start off by editing an article about stuff they don't know?<br><br>Perhaps one method of identifying information, it to have a simple way to flagging an article as 'needs checking'.<br>Wiki m...
I agree.
Regardless though, an out of date wiki is not helpful.What approaches can we take to fix up the wiki
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
In my opinion , the Wiki sucks....
Very difficult to find any useful information.
Scott
--
-
The antidote for misuse of freedom of speech is more freedom of speech.Molly Ivans
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
How about to use the Openmoko Index page.
This page collect every topic of Wiki.
And depend on the page's content, pages of wiki will classify into right
category.
But now , Software part
(http://wiki.openmoko.org/wiki/Openmoko_Wiki_Official_Index_Page#Software)
and Technical part , might be not clear enough(
http://wiki.openmoko.org/wiki/Openmoko_Wiki_Official_Index_Page#Technical)
, but in the future, I will make them become more easy to find.
For example, just like thisPart I Choose your software develop tool
Development Environment
For developer
Part II Coding and compile
(OE, Toolchain.....)
Part III Running your program(Emulation .....)
Part IV Program sharing
Part V Install
Part VI Tools used in Openmoko
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
+ 1 to the clasification, but a visual discrimination about uptodate/outdated/work in progress in this pages will be very useful too.
¿No te gusta tu dirección de correo?
Consigue una que te guste de verdad - millones de direcciones de correo disponibles en Yahoo!
http://es.docs.yahoo.com/mail/nueva_direccion.html_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Hi,
Usually, I can find the information I am looking for with one or two
searches on te wiki, for me, that's good enough.Also remember that each and one of us can improve the wiki. Yes, you
can do it yourself.
--
Regards,
Torfinn Ingolfsen_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
------=_Part_21039_9562472.1215755837836
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inlineIt is rather accurate. I went in an updated a few links to openembed and
also ended up asking the community list for how to do proper emulation as
the steps listed for mokomakefile were producing an unusable QEMU image.-Shawn
------=_Part_21039_9562472.1215755837836
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inlineIt is rather accurate. I went in an updated a few links to openembed and also ended up asking the community list for how to do proper emulation as the steps listed for mokomakefile were producing an unusable QEMU image.<br>
<br>-Shawn<br><br><div class="gmail_quote">On Thu, Jul 10, 2008 at 10:14 PM, Vinc Duran <<a href="mailto:uberpfloyd@gmail.com">uberpfloyd@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think it's accurate.<br><br><div class="gmail_quote"><div><div></div><div class="Wj3C7c">On Thu, Jul 10, 2008 at 10:41 PM, Matt Joyce <<a href="mailto:matt.joyce@gmail.com" target="_blank">matt.joyce@gmail.com</a>> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">
<br>I found this yesterday, thought it was quite an ok article.<br><a href="http://arstechnica.com/reviews/os/open-moko-software.ars" target="_blank">http://arstechnica.com/reviews/os/open-moko-software.ars</a><br><br>This stood out for me "<b>The tangled pile of mostly outdated and incomplete
documentation at the OpenMoko wiki</b&g...
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Mariusz Kozlowski | [PATCH 03] drivers/sbus/char/bbc_envctrl.c: kmalloc + memset conversion to kzalloc |
| Yinghai Lu | [PATCH 02/16] x86: introduce nr_irqs for 64bit v3 |
git: | |
| Gerrit Renker | [PATCH 13/37] dccp: Deprecate Ack Ratio sysctl |
| James Morris | Re: [GIT]: Networking |
| Jeff Garzik | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
