alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@suse.cz>
Subject: Re: Will the real alsa wiki please stand up?
Date: Fri, 03 Aug 2007 10:37:35 +1200	[thread overview]
Message-ID: <200708031037.36014.linux@audioscience.com> (raw)
In-Reply-To: <s5hfy32rtgc.wl%tiwai@suse.de>

On Friday 03 August 2007 00:50:43 Takashi Iwai wrote:
> At Tue, 31 Jul 2007 21:54:54 +1200,
>
> Eliot Blennerhassett wrote:
> > If the (currently active) contributors to the developer wiki agreed, I'd
> > be willing to do the grunt work of moving the pages.
>
> That'd be greatly appreciated.
>
> > but the page 'owners' might
> > prefer to do the copy and keep the  authorship intact...
> >
> > JamesCourtierDutton 15 pages
> > LiamGirdwood 2 or 3 pages
> > ClemensLadisch 1 page
> > NormanSchleicher 2 pages
> > JohnUtz 3 pages
> > JaroslavKysela 5 pages
>
> Any of you have objections about this?
> (sorry I couldn't find Norman's address...)

If I don't hear back otherwise, I will start some time next week copying the 
pages, with backlink and attribution

> > And, in the official wiki,  would we want a separate Development:
> > namespace? Something the wiki-master needs to create.
> > or is a Development: category a better way to go.

I created development category  (just need to add [[Category:Development]] to 
any page.  
http://bugtrack.alsa-project.org/main/index.php/Category:Development

> I think the catgoery should suffice.  But I'm no Wiki expert al all,
> so would like to hear from other skilled guys.

However it seems there is already a namespace "AlsaWiki" which contains only 2 
pages. By default its excluded from search.  Maybe this was intended for the 
alsa dev wiki content (Jaroslav?)

http://bugtrack.alsa-project.org/main/index.php/AlsaWiki:About
http://bugtrack.alsa-project.org/main/index.php/AlsaWiki:Developer_Zone

--
Eliot

  parent reply	other threads:[~2007-08-02 22:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 21:40 Will the real alsa wiki please stand up? Eliot Blennerhassett
2007-07-27  9:40 ` Takashi Iwai
2007-07-31  9:54   ` Eliot Blennerhassett
2007-08-02 12:50     ` Takashi Iwai
2007-08-02 18:15       ` Ingo Müller
2007-08-02 21:24         ` Official wiki migration from website Eliot Blennerhassett
2007-08-02 22:37       ` Eliot Blennerhassett [this message]
2007-08-03  7:19         ` Will the real alsa wiki please stand up? Ingo Müller
2007-08-03  9:22           ` Jaroslav Kysela
2007-08-03 18:44             ` Wiki login, Was: " Wallace, Brooke
  -- strict thread matches above, loose matches on Subject: below --
2007-05-26  9:00 j t
2007-05-26  9:43 ` Ingo Müller
2007-05-26 11:16   ` j t
2007-05-27 21:10     ` Ingo Müller
2007-05-30 19:29       ` j t
2007-05-30 22:16         ` Lee Revell
2007-05-31 10:17         ` Takashi Iwai
2007-05-28  8:53 ` Jaroslav Kysela

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=200708031037.36014.linux@audioscience.com \
    --to=linux@audioscience.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@suse.cz \
    --cc=tiwai@suse.de \
    /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 NNTP newsgroup(s).