Status of ALSA documentation?
Quoted 4 lines
If you are interested to reorganize contents of ALSA web site, I can give you CVS write access and you can show your ideas in some subdirectory for clarification.
I have a site where I can put up a revised homepage for now.
I was just responding to the call for people to help with the administration of the site.
I will work on a new layout over the next couple of days and let y'all know when I have it online.
Firstly can Juhana and others please let me know what you consider most important to be on the homepage?
So far I have gleaned this information:
1: Less developer news
2: A mission statement
3: More emphasis on information related to vendors
What else do people want to see changed?
--
Patrick Shirkey - Boost Hardware Ltd
For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.boosthardware.com/LAU/Linux_Audio_Users_Guide/
Quoted 40 lines · --- Jaroslav Kysela
Quoted 10 lines · Patrick Shirkey
ALSA is not an easy code base to come to grips with so we should apply the kiss rule (keep it simple stupid) to help newbies coders get their heads around it.
Quoted 1 line
From my perspective the comments are not standardised enough. I haven't checked the code for a couple of months but last time I looked each file had a different approach to where and when comments were added.
IMO if the developers could agree on a standard layout for every file then new developers would have much more chance of understanding how things work. Simply a matter of repetition.
Apart from that what are the job requirements of an ALSA web maintainer and a documentation leader?
EG.
Quoted 7 lines
- How many hours per week are expected?
- What are the knowledge requirements?
- What are the legalities?
- What are the target responsibilties?
- What are the benefits?I am interested in the web site maintainer depending on the above requirements.
Actually, our web is based on apache and PHP3 scripts. Perhaps, we can move to python (nice language) or PHP4 in future. I've created a CVS repository for WWW contents. Each commit automatically updates the WWW pages, so we have good management system for web.
If you are interested to reorganize contents of ALSA web site, I can give you CVS write access and you can show your ideas in some subdirectory for clarification.
Anyway, I am ready to answer any questions regarding ALSA. It's obvious.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com
Quoted 4 lines
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
_____________________________________________________________
Want a new web-based email account ? ---> http://www.firstlinux.net
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Quoted 6 lines · Patrick Shirkey
Quoted 4 lines
If you are interested to reorganize contents of ALSA web site, I can give you CVS write access and you can show your ideas in some subdirectory for clarification.
I have a site where I can put up a revised homepage for now.
I stated that the current layout is result of combination of HTML code and PHP3 scripts. I don't think that we can get standartized set of pages with static HTML contents. In my opinion, it would be better to debug new web layout directly on server, otherwise we may reach unexpected problems when migrating from some private site.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Quoted 5 lines · Patrick Shirkey
1: Less developer news
2: A mission statement
3: More emphasis on information related to vendorsWhat else do people want to see changed?
Developers are usually familiar with ALSA and know where to look for further information. To me, the main strength of the website should be for end-user information like how to set up and configure ALSA drivers and modules so clear links to HOWTOS and anything that eases the pain for new ALSA users to get the most out of their audio systems would be great.
I recently showed a Mac user interested in using Linux for live stage work (no gui needed) the ALSA site so they could get some idea of progress... they just laughed and said there was _nothing_ there to help them evaluate whether ALSA (therefor Linux) was going to be useful to them... well, not within a 5 minute perusal anyway.
No doubt a slash/nuke-like portal would be asking too much ?
--markc
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Quoted 6 lines
I recently showed a Mac user interested in using Linux for live stage work (no gui needed) the ALSA site so they could get some idea of progress... they just laughed and said there was _nothing_ there to help them evaluate whether ALSA (therefor Linux) was going to be useful to them... well, not within a 5 minute perusal anyway.
i think this is an excellent, critical point.
with ALSA's adoption into the kernel, we have both (1) a chance that more people will write HOWTOs and code but also (2) more people saying "what is it?" and "how do i ....?" the current web site fails completely at both tasks.
as much as i think we are still aiming for uniform operation for all cards (i.e. they just work), i think a good place to start with interface HOWTOs would be to take Dan's soundcard matrix, and add links from each card name to a HOWTO. The default set of HOWTOs can be empty, and we can add to them as time goes on. By empty, what I really mean is a boilerplate document that says "if you have this type of soundcard, just do X, Y, and Z and it will work".
there should also be a way to collect card-specific bug reports and accessing them all from the HOWTO page.
of course a wiki would be an even better way of collecting card/setup specific quirks, but that seems a bit much to ask for right now.
of course, it becomes critical that the matrix be kept up to date, which could also use a wiki-style input system.
--p
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Quoted 5 lines · Paul Davis
of course a wiki would be an even better way of collecting card/setup specific quirks, but that seems a bit much to ask for right now.
of course, it becomes critical that the matrix be kept up to date, which could also use a wiki-style input system.
FWIW here is a quick and dirty Wiki that might encourage someone to set up something for real, if it proves useful. Having a Wiki is one thing, encouraging folks to actually input something useful is another... but, it can't get any easier than this for _anyone_ to contribute.
--markc
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel