Re: Ubuntu Developer Survey and Next Steps
On 09/08/2011 04:03 PM, Iain Lane wrote: Hi there, Thanks for taking the poll. Thanks for reading it. :-) On Thu, Sep 08, 2011 at 03:40:47PM -0700, Jono Bacon wrote: Hi Everyone, I have just published the report highlighting the findings from the Ubuntu Developer Survey I ran recently. It is at http://www.jonobacon.org/2011/09/08/ubuntu-developer-survey-report-and-next-steps/ I think it would be useful to organize a joint TB/DMB meeting to discuss the findings. Maybe we could do this at the next scheduled TB meeting - would you folks be open to that? The next TB meeting isn't for 2 weeks, which is quite a while. We have a DMB meeting on Monday @ 1900UTC though, which could work? We've got one application to do and Micah's appointment to ratify so if you guys join us at 1930? We could maybe carry on until 2100 if necessary. Dunno, just a thought. I think that is a great idea - would others be happy to join this meeting? Having read the report, I'm concerned about the low response rate. Also some of the comments quoted talk about going to the TB or MOTU council, processes which haven't been used for quite a significant amount of time, which makes me wonder that the information isn't fresh. This is further backed up by your graph about Canonical employment. Take a look at Mackenzie's recent record keeping http://people.ubuntu.com/~maco.m/dmb_record_keeping.html and note the proportion of recent (since February) applicants that worked for C. This indicates to me that a serious number of people who have been through the DMB process (and /especially/ a significant number of people who interacted with the current DMB, who were the butt of the recent "discussions") didn't reply to the survey. I think you raise good points, Laney. I am not suggesting we should only look at the data in the report I presented, or that we should consider it empirical (the lower response rate is a valid concern), but I do think it could be a useful start to the discussion and then to bring in other data, such as maco's content too. Jono -- Jono Bacon Ubuntu Community Manager www.ubuntu.com / www.jonobacon.org @jonobacon | www.twitter.com/jonobacon -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Ubuntu Developer Survey and Next Steps
Hi Everyone, I have just published the report highlighting the findings from the Ubuntu Developer Survey I ran recently. It is at http://www.jonobacon.org/2011/09/08/ubuntu-developer-survey-report-and-next-steps/ I think it would be useful to organize a joint TB/DMB meeting to discuss the findings. Maybe we could do this at the next scheduled TB meeting - would you folks be open to that? Thanks, Jono -- Jono Bacon Ubuntu Community Manager www.ubuntu.com / www.jonobacon.org @jonobacon | www.twitter.com/jonobacon -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Re: today's meeting
Likewise I am not able to attend as I'm at the Linux Plumber's Conference On Thu, Sep 8, 2011 at 8:20 AM, Kees Cook wrote: > Hi, > > I will likely not be able to attend today's meeting, as I'll be at the > Linux Security Summit at the Linux Plumber's Conference. > > -Kees > > -- > Kees Cook > Ubuntu Security Team > > -- > technical-board mailing list > technical-board@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/technical-board > -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
today's meeting
Hi, I will likely not be able to attend today's meeting, as I'll be at the Linux Security Summit at the Linux Plumber's Conference. -Kees -- Kees Cook Ubuntu Security Team -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Re: your mail
On Tue, Sep 06, 2011 at 11:36:05PM +0100, Gemma Procter wrote: > i have seen on facebook you are looking for members to be on the > technical support team how do i go about nominating someone? I'm afraid there's been some confusion. We're seeking nominations for the Technical *Board*, which isn't a technical support team: https://wiki.ubuntu.com/TechnicalBoard If you know people who are interested in technical support and would like to contribute in that way to Ubuntu, then this page has some pointers: https://wiki.ubuntu.com/ContributeToUbuntu#Helping_others_with_Ubuntu Regards, -- Colin Watson [cjwat...@ubuntu.com] -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
[no subject]
i have seen on facebook you are looking for members to be on the technical support team how do i go about nominating someone? Thanks Gemma-- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Re: Help requested for Ubuntu Brainstorm response on superuser windows vs. user windows
On Thu, Sep 08, 2011 at 03:18:28PM +0100, Colin Watson wrote: > Subject: Re: Help requested for Ubuntu Brainstorm response on TOPIC I'm sorry, you can probably tell that this mail was written with the aid of a template. :-) I've corrected the subject line now. -- Colin Watson [cjwat...@ubuntu.com] -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on Unity Dash - Contact Lens
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is a request for a contact lens in the Unity Dash: http://brainstorm.ubuntu.com/idea/27584/ Since you are well versed in the technology involved, and Allison expressed interest when we talked about this Brainstorm review, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson[cjwat...@canonical.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on disk space remaining indicator in Unity launcher
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is a request for a disk space remaining indicator in the Unity launcher: http://brainstorm.ubuntu.com/idea/28045/ Since you are well versed in this area, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson [cjwat...@ubuntu.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on adding a pop-up alert on low battery
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is a request to add a pop-up alert on low battery: http://brainstorm.ubuntu.com/idea/28037/ Since you are well versed in this area, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson [cjwat...@ubuntu.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on merging Jockey into Software Center
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is a request to merge Jockey into Software Center: http://brainstorm.ubuntu.com/idea/28205/ Since you are well versed in this area, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson [cjwat...@ubuntu.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on finding software to handle a file
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is a request to make it easier to find appropriate software to handle a file: http://brainstorm.ubuntu.com/idea/28148/ I believe this is on the Software Center roadmap (https://wiki.ubuntu.com/SoftwareCenter#Launching_via_file_of_unknown_type), although it is not as yet well-specified. Since you are well versed in the technology involved, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson [cjwat...@ubuntu.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on volume adjustments for headphone use
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is volume adjustments for headphone use: http://brainstorm.ubuntu.com/idea/27275/ As an audio expert, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson [cjwat...@ubuntu.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on a place for new users to see Ubuntu version
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is a request for a place for new users to see the version of Ubuntu they're running: http://brainstorm.ubuntu.com/idea/27460/ As an expert on user experience, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson [cjwat...@ubuntu.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on TOPIC
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is a suggestion that superuser windows should differ from user windows: http://brainstorm.ubuntu.com/idea/27378/ As a design expert, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson [cjwat...@ubuntu.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on separate music and video player options
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is a request for separate music and video player options: http://brainstorm.ubuntu.com/idea/27730/ To me, this appears to be fixed in Oneiric (System Settings -> System Info -> Default Applications has both Music and Video settings), but I suggest reviewing the comments to see if I'm missing something. Since you are well versed in this area, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson [cjwat...@ubuntu.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
Help requested for Ubuntu Brainstorm response on new default sound pack
Once you've read the details below, please respond with an acknowledgement and let me know if you can participate. The expected time investment is on the order of a couple of hours over the next two weeks. Last November, the Technical Board recently began a new program to respond to top voted topics on Ubuntu Brainstorm: http://mdzlog.alcor.net/2010/11/03/weathering-the-ubuntu-brainstorm/ with the first two rounds of responses summarised here: http://mdzlog.alcor.net/2010/12/10/ubuntu-brainstorm-top-10-for-december-2010/ http://www.piware.de/2011/04/top-ideas-on-ubuntu-brainstorm-march-2011/ Our goal is to improve our responsiveness to the questions, concerns and suggestions we receive from the user community. Note that this does NOT mean that we will commit to following the suggestions, but we will evaluate and respond to them. By explaining what we will (or won't) do and why, we will show that we are paying attention and trying to make good decisions on behalf of our users. The way the program works is that the Technical Board identifies people within the Ubuntu project who are knowledgeable in the specific topics proposed in Brainstorm, and asks each of them to write a short response to one topic. One of the most popular topics in Brainstorm at present is a request for a new default sound pack: http://brainstorm.ubuntu.com/idea/27481/ We turn event sounds off by default for good reason, but I expect some people turn these on; so, while it may not be appropriate to apply the same level of effort to this as to artwork, there may be some untapped talent out there that could be harnessed. Since this has a significant community element and knowing your interest in music, we would appreciate if you could spend a short time reading the Brainstorm content about it and writing a few paragraphs. You don't need to have all the answers, and I encourage you to ask for input from others who might have a view on the issue. This can be in the form of a detailed upstream bug report, a blog post, an email, or any other suitable format. It shouldn't take more than an hour or two to complete. Our goal is to have everything ready for publication by the 27th of September. Can you confirm that you're willing and able to help with this? You can formulate your response as you see fit, but make sure that the tone is sympathetic. Many of the comments in Brainstorm take the form of demands or complaints: just treat these as if they were questions, and answer them politely. Try to listen to the *need* behind the suggestion, not just the suggestion itself, and connect with your audience by telling a story about it. Here are some example formulas which might be helpful to you: * "It sounds like the problem described here is X. We address that in Ubuntu today by doing A, B and C. Maybe that's not working for everyone because of Y. We could improve this by doing Z." * "I would love to see a new feature like that in Ubuntu. It's consistent with the way other parts of Ubuntu work, and seems genuinely useful. We're busy with some higher priority projects at the moment like X, but if someone is interested in writing a patch for this, I will help them get it into Ubuntu and upstream." * "This is a really hard problem without an easy solution. It's complex because of X, Y and Z. It will take some time for this to be completely solved, but here are a few projects we're working on which will make things better, bit by bit." * "That's an easy fix. I've written a patch and uploaded it to Oneiric. It will be in the 11.10 release!" * "That's a great idea, and we already thought of it! Here's the blueprint, and here's how you can follow along as this gets implemented in Natty." * "I passed on your suggestion to the upstream developer of the software, and we had a conversation about it. Here's what we decided." * "This seems like a genuine problem, but I'm not sure that's the right solution, because of X and Y. I asked our usability expert Jill about this, and here's what she suggested." * "I didn't understand what the problem was here, so I had a conversation on IRC with Jamie, who submitted this topic to Brainstorm to understand better. Here's how it went: [...] In the end, we both decided that the best course of action is X." If you have any further questions about what is expected here, please let me know. Thank you in advance! -- Colin Watson[cjwat...@canonical.com] pp. Ubuntu Technical Board -- technical-board mailing list technical-board@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/technical-board
