15 Dec
2006
15 Dec
'06
5:23 a.m.
"Ivica Ico Bukvic":
This sounds like an extremely good good idea. Speaking for myself, I very
seldom bother to make homepages for all of my software, but if there had
been a system (preferably some kind of wiki), it wouldn't be much hassle
to create them.
No, the idea
is very good. However, it should be of the same
quality as Dave's page. And therefore, we need all the categories
he has. (list below). Because I think the first thing to do would be to
copy all the contents from Dave's page into wikipedia.
And the question then is, will wikipedia allow us to create all
these sub-categories? (linux-audio-Demos, linux-audio-digital-dj, and so
on.)
I'd say that wikipedia should be used as a summary page, rather than an
exhaustive resource with app-specific documentation. So, I guess in that
respect I do agree with your ideas. However, I do not see it as an
exhaustive documentation resource for every app.
Another observation is that while most of the apps have decent documentation
on their homepages, none of it is standardized in terms of
layout/cross-referencing/etc. and therefore an easy read. This is where our
documentation page could shine providing a streamlined/standardized
resource. More so, if we generate such a resource, I am convinced that a
quorum of Linux audio users who may not be able to contribute code, may be
more willing to donate their time in maintaining/contributing to the
documentation project, especially if the format for such contributions is
demystified with appropriate templates. Ultimately, this would also help
project developers not worry as much about the documentation, so it would be
a win-win situation for all. Heck, in due time, we may even attract some
financial support from various commercial distros in order to maintain this
distro-agnostic resource.
For the aforesaid reasons, I feel that a wikipedia
page in conjunction to
project's homepages is IMHO not enough. That is not to say that we shouldn't
have one, but I simply see it as a summary resource which leads user towards
the real documentation site.
Yes.