Website to Wiki migration

Website to Wiki migration

[Eliot Blennerhassett]

Greetings,

IMO the basic content of the static website has been migrated to the wiki.

This doesn't include the following:
* http://alsa-project.org/changes/  Changelogs .txt files are referenced, 
assume they are auto generated?
* Contents of http://www.alsa-project.org/alsa/ftp/
* Contents of http://www.alsa-project.org/~iwai/ include "Writing an alsa 
driver"
* User added comments in the soundcard matrix are referenced.  (Is there any 
way to find out which modules in the matrix have user comments attached so 
that they can be copied across to the wiki?)

Anything missing - tell about it here:
http://bugtrack.alsa-project.org/main/index.php/MigrationPlan

One proposal for prettier front page is here:
http://bugtrack.alsa-project.org/main/index.php/Talk:Main_Page
Go ahead - criticise, praise, make your own...

cheers

Eliot

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Website to Wiki migration

[Takashi Iwai]

At Wed, 08 Aug 2007 13:42:26 +1200,
Eliot Blennerhassett wrote:
> 
> Greetings,
> 
> IMO the basic content of the static website has been migrated to the wiki.

Great.

> This doesn't include the following:
> * http://alsa-project.org/changes/  Changelogs .txt files are referenced, 
> assume they are auto generated?

Yeah, I suppose so.  Jaroslav?

> * Contents of http://www.alsa-project.org/alsa/ftp/
> * Contents of http://www.alsa-project.org/~iwai/ include "Writing an alsa 
> driver"
> * User added comments in the soundcard matrix are referenced.  (Is there any 
> way to find out which modules in the matrix have user comments attached so 
> that they can be copied across to the wiki?)

Oh these are also the stuff we need to clean up.
Most of comments there are outdated.

> Anything missing - tell about it here:
> http://bugtrack.alsa-project.org/main/index.php/MigrationPlan
> 
> One proposal for prettier front page is here:
> http://bugtrack.alsa-project.org/main/index.php/Talk:Main_Page
> Go ahead - criticise, praise, make your own...

Thanks for your work, it's really appreciated!


Takashi

Re: [alsa-devel] Website to Wiki migration

[Frank Barknecht]

Hallo,
Takashi Iwai hat gesagt: // Takashi Iwai wrote:

> At Wed, 08 Aug 2007 13:42:26 +1200,
> Eliot Blennerhassett wrote:
> > * User added comments in the soundcard matrix are referenced.  (Is there any 
> > way to find out which modules in the matrix have user comments attached so 
> > that they can be copied across to the wiki?)
> 
> Oh these are also the stuff we need to clean up.
> Most of comments there are outdated.

I also think, the standard entry on setting up an .asoundrc should be
completely removed from the module pages. The asoundrc example there
is rather useless anyway. Most users for most cards don't need an
asoundrc, so telling them things like "Some very useful applications
will not work without it" is misleading - and wrong, or are there
useful applications that don't work without an asoundrc? ;) I'd say,
that part should just be deleted except for cards that actually need an
asoundrc, like maybe the RME.

Ciao
-- 
 Frank Barknecht                 _ ______footils.org_ __goto10.org__

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Website to Wiki migration

[Ash Willis]

> Anything missing - tell about it here:
> http://bugtrack.alsa-project.org/main/index.php/MigrationPlan
> 
> One proposal for prettier front page is here:
> http://bugtrack.alsa-project.org/main/index.php/Talk:Main_Page
> Go ahead - criticise, praise, make your own...
> 

The Wiki's looking great. It's obvious that you've thought about where
everything should be and how it should all tie in instead of blinding
porting the old pages. It's looking very fresh and making much more sense.

Is it just me though, or is

"Vendor-A-trend    Vendor-ALi    Vendor-AMD"

much harder to read than

"A-trend    ALi    AMD"?

Am I OK to go ahead and remove those prefixes or do we want those kept?
Same with the modules, although I find the module prefixes much easier
to deal with visually for some odd reason.

Also, two of the modules that don't have pages were written by myself.
I'd be glad to make the pages for those modules but I don't really know
what should go on those pages TBH. IMO, most of the info on the module
pages is outdated and pointless. At the very least, it's heavily repeated.
Is this something we should look at? Personally I find that it's letting
down the rather nice new site.

Ash

-- 
We've Got Your Name at http://www.mail.com !
Get a FREE E-mail Account Today - Choose From 100+ Domains

Re: Website to Wiki migration

[Eliot Blennerhassett]

On Thursday 09 August 2007 10:54:29 Ash Willis wrote:
> The Wiki's looking great. It's obvious that you've thought about where
> everything should be and how it should all tie in instead of blinding
> porting the old pages. It's looking very fresh and making much more sense.

Thanks for the feedback

>
> Is it just me though, or is
>
> "Vendor-A-trend    Vendor-ALi    Vendor-AMD"
>
> much harder to read than
>
> "A-trend    ALi    AMD"?
>
> Am I OK to go ahead and remove those prefixes or do we want those kept?
> Same with the modules, although I find the module prefixes much easier
> to deal with visually for some odd reason.

Note that there are cross links between Vendor- and Module- pages.

These prefixes are used to generate the lists of vendors and modules 
automatically.  Another way to do this might be to use categories Vendor and 
Module.   So far I cant see a way to include category list on another page 
see:  http://bugtrack.alsa-project.org/main/index.php/Matrix_Talk:Main

Here are the standalone category pages.  These lists would be better without 
the prefix...
http://bugtrack.alsa-project.org/main/index.php/Category:Module
http://bugtrack.alsa-project.org/main/index.php/Category:Vendor

I'd like to hear from the architect of this part of the wiki (Jaroslav) before 
embarking on wholesale rename of pages.

> Also, two of the modules that don't have pages were written by myself.
> I'd be glad to make the pages for those modules but I don't really know
> what should go on those pages TBH. IMO, most of the info on the module
> pages is outdated and pointless. At the very least, it's heavily repeated.
> Is this something we should look at? Personally I find that it's letting
> down the rather nice new site.

This page says what should be on a Vendor- and Module- page:
http://bugtrack.alsa-project.org/main/index.php/Matrix:Description

The repeated information is generated using a template. One possibility is to 
replace the template contents generic instructions with a link to a single 
page with generic instructions.  The template does give the specific module 
name in the instructions.

For the module that I work on, I have put specific information at the top of 
the page E.g.

http://bugtrack.alsa-project.org/main/index.php/Matrix:Module-asihpi

I suggest you do something similar E.g.

Driver for cards from [[Matrix:Vendor-]]
{| align="right"
 | __TOC__
 |}
==Driver Specific Information==
=== Additional Installation notes===
....
{{Template:Modinfo etc


regards

Eliot

Re: Website to Wiki migration

[stan]

Eliot Blennerhassett wrote:
[snip]
> For the module that I work on, I have put specific information at the top of 
> the page E.g.
>
> http://bugtrack.alsa-project.org/main/index.php/Matrix:Module-asihpi
>   
This is impressive.

[snip]
> regards
>
> Eliot
>