From: Greg Freemyer <greg.freemyer@gmail.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: Mulyadi Santosa <mulyadi.santosa@gmail.com>,
Balachandar <bala1486@gmail.com>,
kernelnewbies@nl.linux.org, linux-c-programming@vger.kernel.org
Subject: the kernelnewbies wiki.
Date: Thu, 29 Jul 2010 16:28:26 -0400 [thread overview]
Message-ID: <AANLkTi=-uTg5NnSrcP9_SOLg64Zjt35U5476nCs+5Wyv@mail.gmail.com> (raw)
On Thu, Jul 29, 2010 at 2:10 PM, Jim Cromie <jim.cromie@gmail.com> wrote:
> On Wed, Jul 28, 2010 at 10:51 PM, Mulyadi Santosa
> <mulyadi.santosa@gmail.com> wrote:
>> Hi...
>>
>> On Thu, Jul 29, 2010 at 00:28, Balachandar <bala1486@gmail.com> wrote:
>>> Thank you for your help. I figured out the mistake. I missed a
>>> semicolon in one of the header file that was included in the file that
>>> showed the error.
>>
>> I think it would be great if you and some guys here write about
>> "mistakes I ever did when I write kernel codes" in kernelnewbies
>> wiki....so that others might learn about it.
>>
>> Just 2 cents suggestion...
>>
>> --
>> regards,
>>
>> Mulyadi Santosa
>> Freelance Linux trainer and consultant
>
>
> Hi Mulyadi,
>
> Youre a regular here, and would have some "authority" on making recommendations.
>
> The trouble I have with "edit the wiki" suggestions is that people
> get intimidated by questions of "where to put stuff ?".
>
> I just looked at HelpforBeginners
> http://kernelnewbies.org/HelpForBeginners
>
> and encountered this:
> You are encouraged to edit the WikiSandBox whichever way you like.
> Please restrain yourself from editing other pages until you feel at
> home with the ways a wiki works.
>
> The unintended message I got from this is "dont touch the other stuff",
> which doesnt set the bar low enough to encourage contributions -
> it implies that "judges" might not like your content or its placement.
I don't know the details, but the openSUSE wiki just got a full
re-implementation. In the new version all edits go into a draft that
the author can see when logged in, but not others that are not logged
in.
Then members of the "wiki-team" come along and accept the edits into
the wiki for full publication. The goal is not to avoid spambots. It
is to ensure content ends up in the right place and that it is
properly formatted, etc.
They just launched it on July 12, so there is not much experience with it yet.
Possibly the wiki powers that be could join the opensuse-wiki
mailinglist and track its success and maybe even ask for help to
implement something similar on kernelnewbies.
fyi: It's not a very high-volume list, so it shouldn't be too hard to lurk.
http://lists.opensuse.org/opensuse-wiki/2010-07/date.html
Greg
next reply other threads:[~2010-07-29 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 20:28 Greg Freemyer [this message]
2010-07-29 20:30 ` the kernelnewbies wiki Mulyadi Santosa
2010-07-29 20:44 ` Greg Freemyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=-uTg5NnSrcP9_SOLg64Zjt35U5476nCs+5Wyv@mail.gmail.com' \
--to=greg.freemyer@gmail.com \
--cc=bala1486@gmail.com \
--cc=jim.cromie@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-c-programming@vger.kernel.org \
--cc=mulyadi.santosa@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).