Hi,
I've done a little presentation for Tokyo-area Debian meeting[1] last week.
I've translated the resource into English[2].
It's a summary of what I've been doing and where I want to go from
now, and an introduction to what the Debian scene currently looks like.
I would be interested in what you think about the presentation, and
what might be missing from my perspective.
[1] http://www.netfort.gr.jp/~dancer/column/2005-debianmeeting.html.en
[2]
http://www.netfort.gr.jp/~dancer/column/data/debianmeetingresume200602-pres
entation-uekawa-english.pdf
Yes, there's a couple of pieces that stood out for attention:
"""
DAW: Debian Audio Workstation An uneducated attempt to use Debian to perform
recording and mastering with many audio tracks. It was known to be a
difficult path until beginning of 2006. With improvement of real-time
response times, it became popular by year 2007... (hope)
"""
!?!uneducated!?!
Ardour has been useable in Debian for a while now. A/DeMuDi has provided a
stable (i.e. useable) multimedia distribution since the release of the 1.2
series. I would s/2006/2005 at least. Debian is already becoming the platform
of choice for many musicians and sub-distributions like (off the top of my
head) 64studio, Musix, the Lionstracs Mediastation uses Debian and studio to
Go! is based on Knoppix. Most of these systems work ootb in most cases.
I realise that you're talking about mainstream Debian here and the remark is
possibly a little tongue in cheek, but I also you are being a little
conservative / pessimistic too.
Yup, this is a forward looking statement with tongue-in-cheek,
requesting other developers to participate in debian-multimedia so
that we can have an excellent etch system released by 2007 :).
Tokyo Area Debian Meeting is a meeting held every month targeted at
Debian Developers, and new maintainers in Tokyo area.
"""
Quality assurance. Want to start adding regression testsuites. Most of
applications I donʼt know how to use; starting with researching the usage
scenarios.
"""
This paragraph needs explaining better, or at least, I need to educate myself
better. Possibly this is opening up a whole new subject for
discussion. ?regression testing? ?usage scenarios? Along with identifying who
the multimedia maintainers are and trying to keep tabs on whether they are
active or need help. Multimedia QA would be a Good Thing. Count me in.
Background: I'm most interested in QA on Debian as a whole, and always
looking for possibilities of introducing some automated testing to
help a project of this size.
Considering we have a lot of audio-communication protocols, and many
tools support multiple protocols, it's unlikely that all of them will
be tested through each release.
I'm looking for possibilities of automating some of it, and also
facilitating some parts of the manual testing.
As in, "I'm starting to think aloud about this topic, you're welcome
to help."