Hi, Apologies for the belated reply.. I thoroughly endorse this application from Thomas. He's been a long term contributor, and i'd like to welcome him into ~mythbuntu-dev.
Thanks Thomas! Kind Regards, Dave Walker On 06/04/12 20:52, Thomas Mashos wrote: > Still waiting on a +1 from Daviey > > Thanks, > > Thomas Mashos > > > > On Mon, Sep 12, 2011 at 10:14 AM, Thomas Mashos <tho...@mashos.com> > wrote: >> Mario, >> >> I know that mythbuntu-dev won't remove the red tape. It is a little >> frustrating though that once my software makes it into the archive, >> I can no >> longer write code and commit directly to the branch (since it is >> then owned >> by mythbuntu-dev) >> >> I'll continue to get my packages into the archive. I was just a >> little >> frustrated when I was doing that. >> >> >> Thomas >> >> >> On Sun, Sep 11, 2011 at 11:31 PM, Mario Limonciello >> <supe...@ubuntu.com> >> wrote: >>> Thomas, >>> >>> I agree, it's easy to get discouraged when trying to get new >>> software into >>> the Ubuntu repositories because of how much human subjectivity is >>> involved >>> as it's reviewed before accepting into the archive. Please keep >>> in mind >>> becoming a developer with upload rights doesn't suddenly remove >>> that red >>> tape. Code review is a healthy procedure that I think should >>> continue to >>> exists. I think it would be good for you to help identify where >>> some of >>> those deficiencies that you encountered with the process for new >>> packages >>> were and specifically why the automated tools (revu, lintian, etc) >>> weren't >>> able to triage them ahead of time. The more that the automated >>> tools grow, >>> the less human subjectivity can play into review. >>> >>> PPAs are a useful tool, but not having red tape and peer review is >>> a >>> double edged sword. Uploading to a PPA that people use on their >>> stable >>> boxes has a lot more potential to break dozens of boxes. We've >>> had these >>> types of problems with the auto-builds mythtv branches in the past >>> with >>> botched patches, and need to keep it to a minimum. This is >>> exactly why the >>> Ubuntu SRU process exists. So I would like you to continue with >>> any new >>> software in the Ubuntu archive even if it ends up being >>> troublesome to >>> initially get accepted. >>> >>> I think that overall you've shown a lot of growth from the first >>> Mythbuntu >>> packages that you worked on to the most recent that i've reviewed >>> (mythbuntu-bare) and seem to have a good concept of how package >>> maintenance >>> works with stuff actually in the Ubuntu archive during the >>> development >>> phases. You take feature freeze seriously and attempt to get all >>> of your >>> work done in time for the freeze. >>> >>> Right now I don't think any of the stuff specific to the Mythbuntu >>> package >>> set fits with Debian because it's all so tightly wrapped around >>> MythTV which >>> isn't yet in Debian. There is however an ongoing effort for >>> MythTV >>> inclusion in Debian. When that happens, I would like to see you >>> explore >>> moving the packages that you've written and maintain in Ubuntu >>> into Debian >>> as well. >>> >>> So as long as you can continue to work directly in the archive >>> even for >>> NEW packages, I think mythbuntu-dev is a good fit for you. >>> >>> Thanks, >>> >>> On Wed, Aug 31, 2011 at 13:38, Thomas Mashos <tho...@mashos.com> >>> wrote: >>>> Name: Thomas Mashos >>>> Launchpad page: https://launchpad.net/~tgm4883 >>>> >>>> Who I am: A Mythbuntu developer that apparently doesn't have >>>> access to >>>> his own software. >>>> >>>> My Ubuntu Story: I got into Mythbuntu when it was being founded, >>>> which >>>> was April 2007. At that point I didn't know much about creating >>>> software, >>>> but was willing to help document things and triage bugs. Through >>>> the support >>>> of Mario Limonciello and Daviey Walker, I am now able to >>>> contribute in more >>>> of a development role. >>>> >>>> Areas of work: I'm the creator or mythbuntu-bare, >>>> mythbuntu-repos, and >>>> mythbuntu-log-grabber. I've written documentation, triaged bugs, >>>> submitted >>>> patches, reproduced issues, and assisted in distributing >>>> Mythbuntu. >>>> >>>> Things I could do better: I could submit software for inclusion >>>> into >>>> Debian, rather that deal with attempting to get my software that >>>> was written >>>> specifically for Mythbuntu into the Ubuntu archives. >>>> >>>> Plans for the future: To continue to patch my software that is >>>> already in >>>> the archive and use PPA's for everything else. >>>> >>>> Examples of my work: See Mythbuntu-bare, mythbuntu-repos, >>>> mythbuntu-log-grabber. >>>> >>>> What I like least in Ubuntu: The red tape required to get things >>>> into the >>>> repositories. How there always seems to be one more hoop to jump >>>> through. An >>>> attempt in making it easier for the Mythbuntu team to patch >>>> software that we >>>> are responsible for has left me without the ability to commit >>>> anything to my >>>> Mythbuntu bzr branches. >>>> >>>> -- >>>> Ubuntu-mythtv mailing list >>>> Ubuntu-mythtv@lists.ubuntu.com >>>> Modify settings or unsubscribe at: >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-mythtv >>>> >>> >>> >>> -- >>> Mario Limonciello >>> supe...@gmail.com >>> >>> -- >>> Ubuntu-mythtv mailing list >>> Ubuntu-mythtv@lists.ubuntu.com >>> Modify settings or unsubscribe at: >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-mythtv >>> >> >> >> -- >> Thomas Mashos -- Ubuntu-mythtv mailing list Ubuntu-mythtv@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mythtv
