6:37 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 14 February 2013 00:01:20 M. Edward Borasky wrote:
I'd start with the perennial "Why Linux Audio Sucks"
threads that can
be found all over the web, and isolate projects that can be closed on
deadline during GSOC, then prioritze. ;-)
For what it's worth, I like the documentation project ideas - there's
too much "code" out there already.
I'm obviously supportive of any attempt to improve documentation of free
software, but we have to keep in mind that this is Google Summer of Code, and
they only want "code"-centred projects. When I wrote the Musicians' Guide,
it
was part of Fedora Summer Coding, in a year when Google wasn't involved.
Also, I just noticed that---although I published it and it is technically
available---the Fedora 18 Musicians' Guide isn't properly listed in the menu
on Fedora's Documentation website. I'll see what I can do to fix that!
Christopher
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBAgAGBQJRHDHjAAoJEGpo1cWDqVnYDCUQAKLcYv0iYxYTMVCw9KYsuQyv
7mOgkP3NKfHOj1AjEq8+QDJM4ArklqMEZ/hrSHYAJ8ZvadaL4k4M44lJhHPb8jGl
vBKHHt4epAn89tqQmOjcKCEO2NpGwkIfMV/ZNa9QMWVMUYH23Z1KiIZI8NpJrtdo
+eaLcRfbFTQ/BEQt5UabCuKbMc4bwl4klQJ/6jqwQawUfWHEgYvL3Rsk9xRjMMVo
lX8LXOZQzmEisINxckVBU5UjUY093reBmsZ9fud2zFxw1CmPM3yrnARuxkonMczE
peKvC5fY65NZ/1doF8961DxHz+NG/15JXlCbbvwRvMANgEPJXDATVPZzEaAIqOU0
8+gGHe4Qrbuao7t3T8gAirPJJg1MS0xvSGqL/SEBLOeU6iLmBRe4dlEbQDhcUR2A
9GKN7ZWmVdNMmm/AV04rU5AvKjgEozHmMXKD0il8eqQ3IbyMa0XiYOgyxVzI5fnn
NBCtwzueXWAPg1UAei5Ou9qjbx5pu7K4EoO5byonvHecg0JILXfNoKD1pcPurzoP
VKlvCta8BfSpCcM+KHZ9Dt4doWJUMkJN0tqqL0sSHwUwe3URX4aFLQoXdfVc+BLG
CHCBJptnx+M5qDlFC4WDzYuvbiGw9cfRNltfVPGXilQzwus47D8m5uvVlOPtsrKy
9ttKfmy8mVNb8UgF7rTE
=hGt0
-----END PGP SIGNATURE-----
5:28 a.m.
New subject: GSOC announced
On 02/14/2013 01:37 AM, Christopher Antila wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 14 February 2013 00:01:20 M. Edward Borasky wrote:
> I'd start with the perennial "Why Linux Audio Sucks" threads that can
> be found all over the web, and isolate projects that can be closed on
> deadline during GSOC, then prioritze. ;-)
>
> For what it's worth, I like the documentation project ideas - there's
> too much "code" out there already.
I'm obviously supportive of any attempt to improve documentation of free
software, but we have to keep in mind that this is Google Summer of Code, and
they only want "code"-centred projects. When I wrote the Musicians' Guide,
it
was part of Fedora Summer Coding, in a year when Google wasn't involved.
Well it could very well be a coding project. Think of "packaging" the
musicians guide with project files and sample templates. It could even
be interactive (ie. clicking on a link would launch said software with
packaged project file etc).
I'm thinking this is probably a project which other distro's could use
as well. I've been talking to the UbuntuStudio maintainer and he is keen
to link to our stuff as well, so perhaps we can float a project that
requires building and installing the docs + project files + samples in
locations defined by what you pass to the makefile. That's where the
coding component would come in - packaging is considered coding.
Here's what Len Ovens, one of the UbuntuStudio maintainers had to say
about the Musicians Guide:
"It is far more detailed than any of our documentation. A great job. It
certainly makes me realize how far I have to go in documenting things."
Seems like a shame to duplicate effort. I certainly have used the Arch
Wiki many times to obtain the perfect audio setup. Be great to have
documentation which is dynamic, interactive and that caters for
different distro peculiarities.
I pretty much know nothing about documentation. How does it work for
Fedora, can you explain the workflow?
Also, I just noticed that---although I published it and it is technically
available---the Fedora 18 Musicians' Guide isn't properly listed in the menu
on Fedora's Documentation website. I'll see what I can do to fix that!
I did notice that. Thanks.
1:06 p.m.
New subject: GSOC announced
On Thu, Feb 14, 2013 at 3:28 AM, Brendan Jones
<brendan.jones.it(a)gmail.com> wrote:
Well it could very well be a coding project. Think of
"packaging" the
musicians guide with project files and sample templates. It could even be
interactive (ie. clicking on a link would launch said software with packaged
project file etc).
I'm thinking this is probably a project which other distro's could use as
well. I've been talking to the UbuntuStudio maintainer and he is keen to
link to our stuff as well, so perhaps we can float a project that requires
building and installing the docs + project files + samples in locations
defined by what you pass to the makefile. That's where the coding component
would come in - packaging is considered coding.
Here's what Len Ovens, one of the UbuntuStudio maintainers had to say about
the Musicians Guide:
"It is far more detailed than any of our documentation. A great job. It
certainly makes me realize how far I have to go in documenting things."
Seems like a shame to duplicate effort. I certainly have used the Arch Wiki
many times to obtain the perfect audio setup. Be great to have documentation
which is dynamic, interactive and that caters for different distro
peculiarities.
Yes ... once upon a time there was an audio project called AGNULA (A
GNU Linux for Audio or something of that ilk). It started before
Ubuntu forked Debian and came in two flavors - Debian (.deb) and Red
Hat (.rpm). I'd love to see some kind of distro-agnostic audio tool
set, along the lines of what I'm attempting to do for computational
journalism. That said, I've had to drop openSUSE and Mageia from my
target distros and focus on Fedora, Linux Mint and Ubuntu.
The gotcha here is that students might find packaging boring, unless
the task somehow involves building tools for dealing with the
cross-distro issues. Along those lines, it's been a while since I
looked at the openSUSE "Open Build Service" tool set - maybe that
wheel's already been invented.
--
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick
http://j.mp/CompJournoStick/
The National Coal Institute reminds you, "There's no fuel like an old
fuel."
1:13 p.m.
New subject: GSOC announced
On Thu, Feb 14, 2013 at 11:06 AM, M. Edward (Ed) Borasky
<znmeb(a)znmeb.net> wrote:
Yes ... once upon a time there was an audio project called AGNULA (A
GNU Linux for Audio or something of that ilk). It started before
Ubuntu forked Debian and came in two flavors - Debian (.deb) and Red
Hat (.rpm). I'd love to see some kind of distro-agnostic audio tool
set, along the lines of what I'm attempting to do for computational
journalism. That said, I've had to drop openSUSE and Mageia from my
target distros and focus on Fedora, Linux Mint and Ubuntu.
The gotcha here is that students might find packaging boring, unless
the task somehow involves building tools for dealing with the
cross-distro issues. Along those lines, it's been a while since I
looked at the openSUSE "Open Build Service" tool set - maybe that
wheel's already been invented.
Another thought I just had - talk to some students at CCRMA, IRCAM,
David Cope's program at UC Santa Cruz, Berklee, etc. and see if they
want to package their favourite technologies that satisfy Fedora's
constraints on licenses, etc.
--
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick
http://j.mp/CompJournoStick/
The National Coal Institute reminds you, "There's no fuel like an old
fuel."
7:31 p.m.
New subject: GSOC announced
On 02/14/2013 08:06 PM, M. Edward (Ed) Borasky wrote:
On Thu, Feb 14, 2013 at 3:28 AM, Brendan Jones
<brendan.jones.it(a)gmail.com> wrote:
> Well it could very well be a coding project. Think of "packaging" the
> musicians guide with project files and sample templates. It could even be
> interactive (ie. clicking on a link would launch said software with packaged
> project file etc).
>
> I'm thinking this is probably a project which other distro's could use as
> well. I've been talking to the UbuntuStudio maintainer and he is keen to
> link to our stuff as well, so perhaps we can float a project that requires
> building and installing the docs + project files + samples in locations
> defined by what you pass to the makefile. That's where the coding component
> would come in - packaging is considered coding.
>
> Here's what Len Ovens, one of the UbuntuStudio maintainers had to say about
> the Musicians Guide:
>
> "It is far more detailed than any of our documentation. A great job. It
> certainly makes me realize how far I have to go in documenting things."
>
> Seems like a shame to duplicate effort. I certainly have used the Arch Wiki
> many times to obtain the perfect audio setup. Be great to have documentation
> which is dynamic, interactive and that caters for different distro
> peculiarities.
Yes ... once upon a time there was an audio project called AGNULA (A
GNU Linux for Audio or something of that ilk). It started before
Ubuntu forked Debian and came in two flavors - Debian (.deb) and Red
Hat (.rpm). I'd love to see some kind of distro-agnostic audio tool
set, along the lines of what I'm attempting to do for computational
journalism. That said, I've had to drop openSUSE and Mageia from my
target distros and focus on Fedora, Linux Mint and Ubuntu.
I do have to ask why?
The gotcha here is that students might find packaging boring, unless
the task somehow involves building tools for dealing with the
cross-distro issues. Along those lines, it's been a while since I
looked at the openSUSE "Open Build Service" tool set - maybe that
wheel's already been invented.
The $$$ from GSOC negates the boring aspect. So there will be
candidates, choosing the right one is the hard part.
I'm happy to work with you to throw a distro-agnostic doc project in the
air. As long as the student catches it and does all the hard work ;)
4088
days inactive
4089
days old
4 comments
3 participants
participants (3)
-
Brendan Jones -
Christopher Antila -
M. Edward (Ed) Borasky