Re: Ubuntu development - joining...
> The best approach is to search a project/issue that you are interested > in, which seems to be improving the laptop experience. There is also a > lengthy document from Andreas Lloyd which lots of contacts: > https://wiki.ubuntu.com/ContributeToUbuntu Thanks for the info. The Ubuntu membership is more a kind of reward for contributing a lot to > Ubuntu and expect of getting a nice email address you cannot do a lot > with it. > > You will get commit access (motu/core-dev) if you have proved to be a > trustworthy and productive member of the community and the corresponding > privileges will help you to improve your work flow a lot. I don't think > that this is the case yet. I wasn't implying that I was asking for commit access, just that I was interested in working toward that. If you have a patch just nag the people on IRC about it. OK - I haven't always had the best of luck there, though... All of the above mentioned bugs are very hard to reproduce and a "likely > cause" is not the relevant part of the code that has to be fixed or even > a solution. Furthermore it seems that in general the hardware support of > the MacBook doesn't seems to be very good: Perhaps some ACPI issues. What about #137598? That one has a patch, and several other people experiencing the issue as reported in the bug. Also, #147883 has an upstream patch. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu development - joining...
Am Samstag, den 03.11.2007, 17:42 -0400 schrieb Tim Hull: > Hi, Hello Tim, > I have been generally lurking around Ubuntu development for several > months now (since about the Feisty release), and previously had done > the same around the Warty/Hoary time period. Though I have found > Ubuntu to be superior to other Linux distributions (save for maybe > Debian, except that it doesn't release often enough), I still have > noticed many issues that have stood out like an eyesore - especially > when it comes to laptops and multimedia. I want Ubuntu/Linux to be a > more viable alternative to Windows, and it really seems like some > improvements are needed in these areas especially if Ubuntu is to take > the next step. Welcome! Thanks that you want to contribute to Ubuntu. Wanting to get things done is a good starting motivation. Last week there was the developer summit in Boston and next whole week all Canonical employees will be at an internal meeting. So the lists and IRC have calmed down a bit. > Anyway, stemming from the issues I've been having, I've been quite > interested in becoming involved in Ubuntu development. However, so > far, my attempts have seemed futile. For one thing, I noticed a few > bugs several weeks before Gutsy release - and posted detailed > information (and in one case, even a patch) but never got a response. > I keep gathering more information and updating said bugs, but they > remain unnoticed no matter what I do. Also, from what I gathered, > there is no simple way to become a *developer* - yes, there is MOTU, > but 97% of the issues I'm finding and am concerned about deal with the > main system, not the universe. I've also looked for any kind of > "laptop team" and these seem basically nonexistent save for a couple > dead mailing lists and a couple contacts that I've had no luck with. The best approach is to search a project/issue that you are interested in, which seems to be improving the laptop experience. There is also a lengthy document from Andreas Lloyd which lots of contacts: https://wiki.ubuntu.com/ContributeToUbuntu > Does anybody have any pointers for me? Would it be a good idea to try > to become an "Ubuntu member" and/or join the QA team at this point? > Would this make it easier to get my bugs/patches noticed? I want to > become involved, but as it stands it seems like I'm piping my efforts > to /dev/null :) The Ubuntu membership is more a kind of reward for contributing a lot to Ubuntu and expect of getting a nice email address you cannot do a lot with it. You will get commit access (motu/core-dev) if you have proved to be a trustworthy and productive member of the community and the corresponding privileges will help you to improve your work flow a lot. I don't think that this is the case yet. If you have a patch just nag the people on IRC about it. > P.S. Some of the bugs in question include #151016, #137598, #147883, > #63543 (reopened recently), #137792, and #141001. I didn't file all > of these, but I did reproduce them all and see a likely cause in most > of the cases... All of the above mentioned bugs are very hard to reproduce and a "likely cause" is not the relevant part of the code that has to be fixed or even a solution. Furthermore it seems that in general the hardware support of the MacBook doesn't seems to be very good: Perhaps some ACPI issues. Cheers, Sebastian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu development - joining...
On 11/4/07, Tim Hull wrote: > Anyway, stemming from the issues I've been having, I've been quite > interested in becoming involved in Ubuntu development. However, so far, my > attempts have seemed futile. For one thing, I noticed a few bugs several > weeks before Gutsy release - and posted detailed information (and in one > case, even a patch) but never got a response. I keep gathering more > information and updating said bugs, but they remain unnoticed no matter what > I do. Also, from what I gathered, there is no simple way to become a > *developer* - yes, there is MOTU, but 97% of the issues I'm finding and am > concerned about deal with the main system, not the universe. I've also > looked for any kind of "laptop team" and these seem basically nonexistent > save for a couple dead mailing lists and a couple contacts that I've had no > luck with. It is an unfortunate fact that there are more bugs than developers, and some get missed. Adding the informaiton to the bugs is a great help towards fixing them, but they also need developer time. In terms of joining development, most of the documentation is focused on contributing to Universe as a first step, but many of the practices and processes also apply to main packages. If nothing else, it is a good way to become familiar with the mechanisms of Ubuntu development. > Does anybody have any pointers for me? Would it be a good idea to try to > become an "Ubuntu member" and/or join the QA team at this point? Would this > make it easier to get my bugs/patches noticed? I want to become involved, > but as it stands it seems like I'm piping my efforts to /dev/null :) Joining the QA team is a good start, and will give you a better understanding of various prioritisation procedures. You might also want to contact the Desktop team, as many of your bugs seem to be related to the default end-user experience, which this team follows closely. -- Emmet HIKORY -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Ubuntu development - joining...
Hi, I have been generally lurking around Ubuntu development for several months now (since about the Feisty release), and previously had done the same around the Warty/Hoary time period. Though I have found Ubuntu to be superior to other Linux distributions (save for maybe Debian, except that it doesn't release often enough), I still have noticed many issues that have stood out like an eyesore - especially when it comes to laptops and multimedia. I want Ubuntu/Linux to be a more viable alternative to Windows, and it really seems like some improvements are needed in these areas especially if Ubuntu is to take the next step. Anyway, stemming from the issues I've been having, I've been quite interested in becoming involved in Ubuntu development. However, so far, my attempts have seemed futile. For one thing, I noticed a few bugs several weeks before Gutsy release - and posted detailed information (and in one case, even a patch) but never got a response. I keep gathering more information and updating said bugs, but they remain unnoticed no matter what I do. Also, from what I gathered, there is no simple way to become a *developer* - yes, there is MOTU, but 97% of the issues I'm finding and am concerned about deal with the main system, not the universe. I've also looked for any kind of "laptop team" and these seem basically nonexistent save for a couple dead mailing lists and a couple contacts that I've had no luck with. Does anybody have any pointers for me? Would it be a good idea to try to become an "Ubuntu member" and/or join the QA team at this point? Would this make it easier to get my bugs/patches noticed? I want to become involved, but as it stands it seems like I'm piping my efforts to /dev/null :) Please get back to me... Tim P.S. Some of the bugs in question include #151016, #137598, #147883, #63543 (reopened recently), #137792, and #141001. I didn't file all of these, but I did reproduce them all and see a likely cause in most of the cases... -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
