To all members:
Regarding this project we really need more input from the community. Hence,
I would greatly appreciate everyone's comments on the "Made in Linux" text
for the cover. Namely, what should be included on it?
Also, Daniel, what did you do with the copyright notice given that different
pieces have different copyrights. Is this somewhere on-file (i.e. URL) where
we could point users to?
As far as the copyright notice is concerned, my suggestion would be to
simply state something along these lines:
"(c) 2004-6. All works are copyright of their respective authors and are
distributed either by author's permission or according to their respective
licenses which are available <state where>. CD cover design copyright
Thorsten Wilms. 'Made in Linux' copyright Linuxaudio.org."
This should probably be stated in small print at the bottom of the back side
of the cover. I am not sure whether we should state on the cover that the
music was entirely done in Linux, since the title of the series already
clearly implies this and ultimately such a comment may detract from the
artistic value.
Finally, Thorsten, would you be willing to simply readapt the front cover to
fit the CD label (for those who may opt for doing CD labels)?
Best wishes,
Ivica Ico Bukvic, D.M.A.
Composition, Music Technology, CCTAD, and CHCI
Virginia Tech
Dept. of Music - 0240
Blacksburg, VA 24061
(540) 231-1137
(540) 231-5034 (fax)
ico(a)vt.edu
http://www.music.vt.edu/people/faculty/bukvic/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Dec 25, 2006 at 08:16:25AM +1100, Erik de Castro Lopo wrote:
> Ivica Ico Bukvic wrote:
>
> > A quick look at some of the successful forum/mailing list projects, for
> > instance Ubuntu, reveals that not only they have both, but also both methods
> > of communication are teeming with activity.
>
> Teeming with activity but close to zero signal amongst the noise.
>
> I keep on searching google for solutions to Ubuntu based problems.
> All of the top hits on google point to UbuntuForums and when I
> go there there is almost never an answer. The UbuntuForums are
> absolutely chock full of "Me too" or people saying "that didn't
> work for me".
>
> > FWIW, as far as the "speed" of forums is concerned, it largely depends on
> > what you use in combination on what kind of hardware you run. I've seen some
> > that are quite fast despite the often dubious eye-candy.
>
> Connecting to some web server on the other side of the planet
> will always be slower than accessing mail that has been delivered
> to me and is sitting on my hard drive.
>
I rely heavily upon mutt/procmail, but I consider it to be a hack. I don't want a threaded discussion, I want rapid, high-quality access to authoritative answers to technical questions, preferably in documentation where I can find it immediately without having to wait for an answer or navigate down tons of blind alleys to get it. I know how to filter a threaded discussion in order to find it, but it's still sub-optimal.
I will chime in here to suggest a "none of the above" type of answer:
Wiki along with forums + IRC.
For years I hated wikis, for the same reason I still dislike forums, which is the reason you outline above: lots of noise and random flailing about, and few, if any, useful answers. Of course a lot of mailing lists have the same problem, but I use mutt and procmail to wade through the noise.
But then I discovered by far the best Wiki I've ever seen: the wiki for OpenWRT (http://wiki.openwrt.org/)
It is well-maintained. No endless noise of "I tried that and it didn't work" or apples-to-oranges comparisons or random stabs in the dark... all that crap gets deleted or hashed out in the forums and/or IRC, and all that remains on the wiki is *the answer* to how to do what you want to do, or why it's impossible. Their wiki has some great maintainers ([:mbm:], nbd, florian, and others). The information is organized, clear, complete, and correct.
They also have an excellent forum, which I say even though I hate forums. One way they keep the S/N up on the forum is that [:mbm:] wrote a little hack to PHPBB which connected it to a bot. The bot sits in the #openwrt on OPN, and whenever a new post comes in, the "chatty cathy's" and the real developers with the deep knowledge-- both of whom sit on IRC all the time-- are alerted immediately. Blind alleys get closed off nearly immediately. Interesting topics or serious bugs get attention immediately. Thus, it has a "push" component like email, which is sorely lacking from most forums.
I find OpenWRT to be the best-documented, highest-quality FOSS project I've ever used or contributed to. It just works. I think the combination of great developers and clever use of information tools are the reasons for its success.
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFFkZ/je8HF+6xeOIcRAvygAKC/q82PUcHz7kD4tsc0IbOYKocMkwCghDGE
0p6/DX6WxoRyzq7P4DIRQtI=
=U+bM
-----END PGP SIGNATURE-----
> > A quick look at some of the successful forum/mailing list projects, for
> > instance Ubuntu, reveals that not only they have both, but also both
> methods
> > of communication are teeming with activity.
>
> Teeming with activity but close to zero signal amongst the noise.
>
> I keep on searching google for solutions to Ubuntu based problems.
> All of the top hits on google point to UbuntuForums and when I
> go there there is almost never an answer. The UbuntuForums are
> absolutely chock full of "Me too" or people saying "that didn't
> work for me".
Ironically, my experience is that solutions to most of my very hardware and/or
setup-specific problems were found on Ubuntu forums. More so, some of them were
even applicable to Fedora install but were not available on the Fedora forums...
Many of their how-tos are very helpful which points to another advantage of a
well-designed forum: readability.
>
> > FWIW, as far as the "speed" of forums is concerned, it largely depends on
> > what you use in combination on what kind of hardware you run. I've seen
> some
> > that are quite fast despite the often dubious eye-candy.
>
> Connecting to some web server on the other side of the planet
> will always be slower than accessing mail that has been delivered
> to me and is sitting on my hard drive.
You still need to receive such e-mail either actively or passively. It does not
miracoulously teleport into your HD. Either way, we are again talking about
personal preferences, rather than potential needs and/or interests of an
average user (which may or may not be something you find of value and/or
importance).
Best wishes and Happy Holidays to you and the rest of the list!
Ico
A quick look at some of the successful forum/mailing list projects, for
instance Ubuntu, reveals that not only they have both, but also both methods
of communication are teeming with activity. There will always be those who
prefer forums, those who prefer mailing lists, and those who like/dislike
them the same. Hence, it seems to me that the real question is whether the
LAU/LAD community wishes to cater to as wide common user audience as
possible or do we simply want to expect everyone to adapt to our preferred
ways. Given the abysmal state of Linux audio documentation and overall
knowledge of audio platform on Linux in the user-land, I personally vote for
the former.
Ultimately, I am of the opinion that whatever we can do in a way that
actually is well maintained, will help end-users "dig" what we do. Hence,
IMHO it would be nice to see both available even if they are not necessarily
cross-linked so that posts appear in both places (although their
interconnectedness would be certainly a nice addition). For this reason,
consider this yet another offer/call to the LAU/LAD community for the
design/deployment of the forum.linuxaudio.org, volunteers wanted. If
interested please e-mail me.
FWIW, as far as the "speed" of forums is concerned, it largely depends on
what you use in combination on what kind of hardware you run. I've seen some
that are quite fast despite the often dubious eye-candy.
Best wishes,
Ico
On Fri, Dec 15, 2006 at 01:14:56PM -0500, Ivica Ico Bukvic wrote:
> Wonderful work Thorsten!
Thank you :)
> One question, is the back side designed to be a part of a folded booklet or
> is it supposed to be cut and placed on the back side of the CD? IMHO it
> would be nice to have it placed on the back side to make the CD look
> professional from every side. This, however, would also require that tiny
> side part which commonly has simply a title and a subtitle written
> vertically.
Folded booklet.
I will add a backside with side parts. I would use the same design
for it, unless there's more text to place somewhere.
> FWIW, please remove any credit given to me on the cover as it was really you
> who did all the hard work ;-)
Ok.
BTW, is ther any common term to refer to the whole of the printed art
for a CD?
> Finally regarding the text, the track list is perfect, and obviously your
> authorship should be there, bbut we probably need to figure out what needs
> to be on the CD regarding the copyright and/or other info.
I will wait for a decision. Should be obvious there's not much space,
so I would place some text on the inside, other on the backside, if
there's anything to be added. Then again, it's likely some people
would only print out the cover/booklet.
> I believe I speak on behalf of everyone here when I express my deepest
> gratitude to Thorsten for all his hard work and putting up with the
> seemingly endless criticism (predominantly from me :-).
Heh, you're welcome :)
--
Thorsten Wilms
Thorwil's Creature Illustrations:
http://www.printfection.com/thorwil
Hi!
After a bit of back and forth between Ico and me, the front stands,
I think. Lowercase and the curves on the W are all his fault ;)
Today I worked on the cover/case backside.
http://thorwil.affenbande.org/wp-content/uploads/2006/12/made_in_linux_vol_…
I dropped the bla about copyright, as I think it belonging
to the artists is the default and what people will asume anyway.
Replaced the line about Tux, of course :)
Booklet and case backside could be made different, but then
somebody please tell me which text should appear where.
--
Thorsten Wilms
Thorwil's Creature Illustrations:
http://www.printfection.com/thorwil
How about we stop the seemingly endless discussion and instead all roll-up
our sleeves and actually do this?
Here's what I offer on behalf of linuxaudio.org:
1) generous hosting space
2) virtually unlimited bandwidth
3) docs.linuxaudio.org and apps.linuxaudio.org domains
4) accounts to maintainers
5) server support as needed
What we need volunteers to do:
1) port Dave's pages over into a legible and appealing format to
apps.linuxaudio.org
2) cross-link those pages to docs.linuxaudio.org page (in addition to apps
homepages) which will be a wiki with documentation templates and
standardized layout
3) need to design an appealing interface for both sites (hence consider this
an open call for volunteer designers) -- this cannot be emphasized enough:
we do not want an ugly, plain website, but a nice inviting and user-oriented
resource.
4) create a generic wikipedia entry which gives a summary, philosophy, and
notable achievements of the linux audio scene and provides critical links
(hence it would be used as a portal rather than an exhaustive resource for a
moving target which would never fly with the wikipedia editors anyhow)
On a side note, here's another offer:
As per my discussion with Joern, on behalf of linuxaudio.org I also offer
free unlimited space for porting over LAU and LAD lists to
lists.linuxaudio.org in hopes that we continue consolidating these
invaluable resources. Maintainers will be given appropriate access
privileges etc.
Any takers?
Best wishes,
Ico
Ups ;)
-------- Original-Nachricht --------
Betreff: :) Re: [Consortium] zsh: 6462 illegal hardware instruction ardour
Datum: Fri, 15 Dec 2006 12:35:28 +0100
Von: Ralf <drachenpost(a)meocom-online.de>
An: Ivica Ico Bukvic <ico(a)vt.edu>
Referenzen: <00a401c72013$25377f50$0202a8c0@64BitBadass>
Hi Ico :)
thank you for answering my request so quickly. The first thing I've done
was to write Jaromil on Tue, 12 Dec 2006. Now I've to learn how to use
mailing lists, something new for me, that won't get easier by my broken
English ;).
Linux isn't an OS for people who simply want a tool but Computers are
tools at first. Open Sources won't help users, what they need are
manuals including really detailed indexes, something unknown among
Linux. I please the audio-community not to become "stallmanic", like the
majority of leading Linux-Distributions. Every effort with wiki is useful.
"[...] For the aforesaid reasons, I feel that a wikipedia page in
conjunction to project's homepages is IMHO not enough. [...]" (Ivica Ico
Bukvic, Fri, 15 Dec 2006)
That's correct.
Greetz
Ralf
Ivica Ico Bukvic schrieb:
> Hi Ralf,
>
> You may want to forward this to Linux-Audio-User and/or
> Linux-Audio-Developer lists, since they deal more with this kind of stuff.
> Another possibility is to contact Jaromil (dyne:bolic lead) directly.
>
> Hope this helps!
>
> Best wishes,
>
> Ico
>
>
>> -----Original Message-----
>> From: consortium-bounces(a)lists.linuxaudio.org [mailto:consortium-
>> bounces(a)lists.linuxaudio.org] On Behalf Of Ralf
>> Sent: Thursday, December 14, 2006 3:22 PM
>> To: consortium(a)lists.linuxaudio.org
>> Subject: [Consortium] zsh: 6462 illegal hardware instruction ardour
>>
>> Hello :)
>>
>> I've got some trouble with Dynebolic and Linux in general.
>>
>> Relevant for my question(s) is this hardware and Software:
>>
>> Mobo ASRock K7VT2, Chipset VIA KT266A, AMD Athlon 900MHz
>> Swissonic MIDI-USB 1x1, Plug & Play
>> Soundcard TerraTec EWX 24/96 without MIDI
>>
>> Dynebolic ver 2.2 DHORUBA 6Oct06
>> Dynebolic ver 1.4.1 LUMUMBA 15Jan05
>>
>> Question(s) about Version 2.2
>>
>> If I try to run Ardour (by the Terminal) while Jack is running the
>> following messages are displayed:
>>
>> [d:b] ~ #ardour
>> [...]
>> ardour: [INFO]: Jack server started
>> [...]
>> ardour: [INFO]: No H/W specific optimizations in use
>> ardour: [WARNING]: Your system generates "Mod2" when the NumLock key is
>> pressed.
>> This can cause problems when editing so Ardour will use Mod3 to mean
>> Meta rather than Mod2
>> zsh: 6462 illegal hardware instruction ardour
>> [d:b] ~ #
>>
>> Ardour won't be opened.
>>
>> In Version 1.4.1 Jack doesn't recognize the MIDI of the game port and
>> USB but if I run Ardour there the following will be displayed:
>>
>> [d:b] ~ #ardour
>> [...]
>> ardour: [ERROR] MIDI: no such port device
>> ardour: [ERROR] MIDI: no such port device
>> ardour: [WARNING]: Your system generates "Mod2" when the NumLock key is
>> pressed.
>> This can cause problems when editing so Ardour will use Mod3 to mean
>> Meta rather than Mod2
>> []
>>
>> Ardour will be opened.
>>
>> How can I get Ardour running in Version 2.2?
>>
>> More questions are already loaded ;).
>>
>>
>> Greetings
>>
>> Ralf Mardorf
>>
>> Germany
>> Oberhausen Rheinland
> 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.
Best wishes,
Ico