Re: [ubuntu-studio-devel] Documentation for 16.04
On 2015-10-21 15:43, Kaj Ailomaa wrote: > First, a short version: > > We need a documentation lead who is responsible for organizing > documentation, but I'm not just going to name one as I have done before > - we need an official and transparent way of dealing with that, so I > will get back to that shortly (15.10 is soon out and we can begin > focusing on 16.04). It's a great idea! A lead would help, because the wiki has many pages linking to and from each other that are incomplete or vague... Its complex structure, and it is difficult to focus on a subject, while retaining a global vision of what needs to be done/has been done. Frankly speaking, I'm not sure i have got what it takes to be a lead of anything. But i will gladly assist anyone who does. > I like the way you write, and my first impression of this was that it > would be a nice start on an education on computer graphics. And, it fits > well together with the idea of the user guide as it had been organized > (long ago, by me and Scott, I believe), in that it includes just about > everything you need in order to learn how to use the system for > multimedia production. So, in that respect, I'm very satisfied. Let's see how it looks once finished, but Thank you! :) -- Set -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Documentation for 16.04
On Tue, Oct 20, 2015, at 07:05 PM, Set Hallstrom wrote: > On 2015-10-20 12:25, Kaj Ailomaa wrote: > > > You can just add a page at the wiki somewhere. It can always be redone > > and renamed so it's all pretty safe. > > I started this: > https://help.ubuntu.com/community/UbuntuStudio/UserGuide/Graphics/draftpage > (...) First, a short version: We need a documentation lead who is responsible for organizing documentation, but I'm not just going to name one as I have done before - we need an official and transparent way of dealing with that, so I will get back to that shortly (15.10 is soon out and we can begin focusing on 16.04). Long version (with thoughts on documentation as a whole): I like the way you write, and my first impression of this was that it would be a nice start on an education on computer graphics. And, it fits well together with the idea of the user guide as it had been organized (long ago, by me and Scott, I believe), in that it includes just about everything you need in order to learn how to use the system for multimedia production. So, in that respect, I'm very satisfied. Though, my idea for the next LTS was to do something simple, like the quick instruction you get when you buy a new product. Something like: "here's the power button, here's where you do A, B and C, and, here's where to look when something went wrong." Something which helps the user but doesn't become too big of a project for the author. For audio the biggest problem is how to handle the jack audio system, both in terms of usage and troubleshooting. For graphics and video (but also audio), I suspect we are more dealing with installing drivers and other nonfree stuff to get support for formats. Maybe also learning which applications may be used for what - the more technical aspects of just getting stuff to work, so we can actually get working. So, yeah. I was thinking more in those terms, but I wasn't expecting to get such a great response, so I'm moving my attention to another problem instead, namely leadership and organization. I haven't looked in the user guide for a long time, so I don't remember what I or anyone else were thinking back then. Also, we've discussed youtube videos, see here - https://wiki.ubuntu.com/UbuntuStudio/YoutubeVideoFormat, which is a less structured way of providing things like tutorials (each video can either be something very specific, or very general - up to the author of the video, works for wikis too, but not manuals or general user guides). Putting all that together, there is one thing that becomes clear. There is structure, but no content, basically. And restructuring would not hurt anyone. When I put out the call for someone to help with documentation, I was actually loosely disregarding all of that, and I'm sure most others were too, just out of not being aware of it for obvious reasons. Since there seems to be some interest in this topic, I think it might be best we have someone in charge of documentation, who can work independently with organizing at least what is currently being discussed in a couple of threads. My first thought was to just improvise and just get someone be doc lead, which is not a bad idea when there are so few people in the team. But, perhaps it is best we do that in a structured and officially (yet undocumented) way :). 15.10 is almost out, so we may just as well begin preparing for next release, and start by deciding who is responsible for what. We have established a few lead positions over the years, though they haven't always been populated. So, I will start discussions about that. - A year ago, this would have been pointless, since there was pretty much no one involved, but this time perhaps we can do things differently. -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] New User Documentation
On Wed, 21 Oct 2015 13:33:02 +0100, floccul...@gmx.co.uk wrote: >On 21/10/15 12:55, Ralf Mardorf wrote: >> On Wed, 21 Oct 2015 19:28:38 +0800, C. F. Howlett wrote: >>> I'm not qualified to do all the tutorials, but I am willing to edit >>> and standardize the writing. Any interest??? >> A proofreader [translator for Phantom English to English English] >> would be useful for the Ubuntu (Studio) help and Wiki pages ;). >> >perhaps host it on LP like xubuntu-docs > >then even when it's dealt with now - fixes can be followed from bug to >fix > >it can also then (I assume) be translated as well > >just a thought I just wanted to point out that users like me probably have knowledge about a software domain, but will write help pages and Wikis in broken English. Since everybody can create an Ubuntu One account, everybody can edit the help pages and Wikis. Any changes made are stored by the page histories, so nothing gets lost, if somebody edits it, even if somebody by accident should remove the entire text. We shouldn't invent concepts of rocket science to provide help pages/Wikis. The concept of a Wiki is very simple and already worked for a long time. Let's stay with the KISS principle, https://en.wikipedia.org/wiki/KISS_principle. If you find any errors or if you even could provide useful links go and edit https://help.ubuntu.com/community/UbuntuStudio/UserGuide/Graphics/draftpage https://help.ubuntu.com/community/UbuntuStudio/UserGuide/Video https://help.ubuntu.com/community/UbuntuStudio/TroubleShooting https://help.ubuntu.com/community/CategoryUbuntuStudio and other pages. Some contributed much, e.g. Set and Kaj, others contributed close to nothing, e.g. me. Many a little makes a mickle. The German equivalent saying: "Small domestic animals poo too." (Kleinvieh macht auch Mist.) Regards, Ralf PS: Unfortunately the login is a PITA. It takes very long and often fails. -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] New User Documentation
On 21/10/15 12:55, Ralf Mardorf wrote: On Wed, 21 Oct 2015 19:28:38 +0800, C. F. Howlett wrote: I'm not qualified to do all the tutorials, but I am willing to edit and standardize the writing. Any interest??? A proofreader [translator for Phantom English to English English] would be useful for the Ubuntu (Studio) help and Wiki pages ;). perhaps host it on LP like xubuntu-docs then even when it's dealt with now - fixes can be followed from bug to fix it can also then (I assume) be translated as well just a thought -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] New User Documentation
On Wed, 21 Oct 2015 19:28:38 +0800, C. F. Howlett wrote: >I'm not qualified to do all the tutorials, but I am willing to edit >and standardize the writing. Any interest??? A proofreader [translator for Phantom English to English English] would be useful for the Ubuntu (Studio) help and Wiki pages ;). -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
[ubuntu-studio-devel] New User Documentation
I have had a project in mind for some time. Ubuntu used to include GIMP. On the desktop, there was a tutorial to introduce very basic GIMP functions in the form of a user-built Ubuntu logo image. Cool stuff. Sadly, removed in later releases. Likewise the old Ubuntu sample media folder. So, to my project; Target audience: "I just installed ubuntustudio. Now what?" people Format: a series of easy peasy, introductory tutorials using the major apps in the focus areas. For instance: SOUND > AUDACITY > Record your voice. Sample and remove background noise. Edit sound for Darth Vader voice. Save and export. Upon completion of the project, supply at least one tutorial. Fortunately, the major apps already have basic tutorials. We just need to highlight them. Obviously, this is not the in-depth documentation currently under discussion in another channel, but I believe it fills a need and would give useful and welcome advice. I'm not qualified to do all the tutorials, but I am willing to edit and standardize the writing. Any interest??? -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Documentation for 16.04
On Wed, 21 Oct 2015 09:22:26 +0200, Set Hallstrom wrote: >The link to troubleshooting resources should probably be either in the >header or the sidebar. That was my first thought too, but to make it noob-prove it's probably better to add it as a chapter to each help. >Placed within the guide, i would expect it to be specifically for >troubleshooting graphic applications, which in itself would be nice >too. It's possible to link against a specific chapter. https://help.ubuntu.com/community/UbuntuStudio/TroubleShooting#Help.21_Qjackctl_is_not_able_to_shut_down_jack https://help.ubuntu.com/community/UbuntuStudio/TroubleShooting#I_can.27t_seem_to_get_sound_when_I_use_qjackctl instead of https://help.ubuntu.com/community/UbuntuStudio/TroubleShooting We also could make it vice versa and link from the trouble shooting page to the trouble shooting chapters of the application help. >The good reflex would be to add an entry in >https://help.ubuntu.com/community/UbuntuStudio/TroubleShooting each >time a support case has been solved. +1 At least such information should be collected and if it got enough "hits" moved to troubleshooting FAQ. Consider troubleshooting not only something that has to do with bugs or misconfigured settings, but also with completely cluelessness on how computerized tools work. Self-reliant learning and testing how such tools work in their imagination might spark a war, damage the International Space Station or worse. Humans have different levels of abstract reasoning. Qtractor 1. Why can't I hear sound from MIDI tracks? The sound card works, I can hear audio tracks. 2. What is the difference between a MIDI and an audio track? GIMP 1. I draw a background and now I draw on a layer. If I draw with real watercolours on a background drawn on real paper, the new drawn colour doesn't cover the background. Drawing with the GIMP brush the colour does cover the background. Regards, Ralf -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
[ubuntu-studio-devel] 15.10 RC Testing - release tomorrow, thursday
Hi everyone. Tomorrow, thursday, Ubuntu Studio 15.10 will be released. So, if anyone would like to give a hand in testing the ISO, that would be great. A good time to do testing is before ~18.00 UTC, preferably many hours before. In short, to test, we boot the ISO, install it, and try a few applications to make sure everything is tip top. If all of that worked out, you may mark the test a success at http://iso.qa.ubuntu.com. A longer version can be read here - https://wiki.ubuntu.com/UbuntuStudio/Testing/ISOTesting. -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Documentation for 16.04
On 2015-10-20 12:22, Ralf Mardorf wrote: > I linked to the Ubuntu TroubleShootingGuide, > https://help.ubuntu.com/community/UbuntuStudio/TroubleShooting . Thanks for adding those links, i think you are right: it is essential to have a consolidated troubleshooting. The link to troubleshooting resources should probably be either in the header or the sidebar. Placed within the guide, i would expect it to be specifically for troubleshooting graphic applications, which in itself would be nice too. I've been trying to think about what kind of common trouble arise while working on graphics, but i guess i don't really have much trouble in that workflow anymore... Maybe thread-digging in the forum could give an overview of common problems when working with graphics?... The good reflex would be to add an entry in https://help.ubuntu.com/community/UbuntuStudio/TroubleShooting each time a support case has been solved. Have a good day y'all! -- Set -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
