12:03 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/19/2012 03:48 PM, Manuel Ospina wrote:
Hello Brendan,
I'd like to help. I went through the list of to do and I think I
can help with "packaging the Fedora Musician's guide". is it
written using publican? I would need some guidance though.
Manuel:
Yes, Chris worked with Fedora Docs to use Publican and adopted other
processes that should make it easier to package. However, it might be
packaged already? I thought that was how Publican deployed to the webUI:
https://docs.fedoraproject.org/en-US/Fedora/16/html/Musicians_Guide/index...
Regardless, I'm sure Chris will welcome your expert help. :)
- - Karsten
Regards, Manuel
----- Original Message ----- From: "Brendan Jones"
<brendan.jones.it(a)gmail.com> To: music(a)lists.fedoraproject.org
Sent: Monday, February 20, 2012 1:24:59 AM Subject:
[Fedora-music-list] Call to arms - Fedora Audio Spin
Hi all,
Traditionally Fedora has been known to walk the bleeding edge in
free and open source software development but for some reason this
has never been realised in the realms of pro-audio/music creation.
Fedora has never really attracted the support of the audio
development community, and as a direct result has only flagging
support from audio users, enthusiasts and professionals alike.
I think there are a number of reasons for this: 1) Strict
packaging and licensing guidelines, 2) relatively short release
support cycles 3) the absence of an stock RT kernel 4) the effort
required to tailor an installation for audio use
Distributions like Debian/Ubuntu/Arch (and others like AVLinux)
have garnered strong support because they in some way address all
of these issues. Fedora however...
1) and 2) we can't change. In fact at the end of the day these
strengthen the distribution by making the packages we ship more
robust and closer to upstream. It also demands a certain amount of
love to ensure that updates/ABI bumps/breakages are dealt with
decisively and swiftly. It also means that audio developers are
more unlikely to maintain their own packages in Fedora (we need
more maintainers)
3) I can't see happening any time soon. The kernel team maintain
so many out of tree patches already that I don't think they really
have the time nor desire to maintain the realtime kernel as well. I
don't see this as a problem - recent kernels have incorporated much
of the the rt kernel patches of old and should satisfy most users.
For those with more stringent requirements can rely on the CCRMA
patched kernels
4) is where I think an audio spin comes into play. If we can
collate/automate all of the steps involved in setting up Fedora for
audio production we will attract both users and maintainers alike
alleviating the problems caused by 1 and 2.
I'm proposing to formally revive the past Fedora Audio Spin / Music
Creation efforts of a couple of years ago in time for an F18
Audio spin release. This means we have one whole release cycle to
get all of the packages we require into stable so they can be
available for Live composes for the F18 release cycle.
Apart from packaging efforts, the last few weeks for me has been an
information gathering exercise. More on this soon, but briefly,
the current to do list is: - pulling in all of the must have
packages from CCRMA - determining the package list - packaging the
Fedora Musician's guide - repackaging/patching rpmfusion packages
for Fedora (qtractor and others if required) - developing sane RT
priorities for the stock kernels (threadirqs) - consensus on
distribution media, default desktop/supported desktops - default
systemd enabled services - themes and artwork - resubmit the Spin
proposal for F18
If you want to contribute, here's how: - become a contributor/get
a FAS account [1] and join the music-creation group - help maintain
the audio creation wiki's (formalize the to do list)[2][3] - this
is really out of date. Many packages have been orphaned or are
already in Fedora. Needs to be brought in line with the package
database [5]. I'm not convinced that this page really needs to be
so detailed. Wish lsit is probably the most important - register
your interest in the contributor section of the audio spin wiki [3]
- help test new packages - I will be listing all upcoming changes
on this list and I encourage other package maintainers to do the
same [3] - become a tester or packager of audio packages [4][5] -
help test the new spins as we make them available. - join Chris in
his documentation efforts [7] - volunteer desktop artwork - and
most importantly, voice your opinion on how this project should be
realized! Choice of media/desktop/applications /configuration etc.
More proposals on this coming soon.
Packaging the software and building the media constitutes less than
a quarter of the effort required here. What we need most is strong
community support so please respond to this email if you are
interested!
Lets do it
Brendan
[1] https://admin.fedoraproject.org/accounts/ [2]
http://fedoraproject.org/wiki/Audio_Creation [3]
http://fedoraproject.org/wiki/AudioCreationSpinDevelopment [4]
http://fedoraproject.org/wiki/QA [5]
http://fedoraproject.org/wiki/Join_the_package_collection_maintainers
[6] https://admin.fedoraproject.org/pkgdb/
_______________________________________________
music mailing list music(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/music
_______________________________________________ music mailing list
music(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/music
- --
name: Karsten 'quaid' Wade, Sr. Community Architect
team: Red Hat Community Architecture & Leadership
uri: http://communityleadershipteam.org
http://TheOpenSourceWay.org
gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFPQorw2ZIOBq0ODEERAlWeAJ4wNvx2cJiEL90M5BYPp5hz++golACbBhRB
V6GPeVf3zDcVchnx8eCxPLc=
=2e+O
-----END PGP SIGNATURE-----