As list administrator, your authorization is requested for the
following mailing list posting:

    List:    developer-membership-bo...@lists.ubuntu.com
    From:    doak.jack...@gmail.com
    Subject: Re: Applying for Xubuntu Packageset and MOTU by email
    Reason:  Post by non-developer to moderated list.

At your convenience, visit:

    https://lists.ubuntu.com/mailman/admindb/developer-membership-board
        
to approve or deny the request.
--- Begin Message ---
What's happening with this? It's been over two weeks.


On Wed, Jan 1, 2014 at 6:25 AM, Jackson Doak <nosk...@ubuntu.com> wrote:

> Thanks Iain.
>
> >Do you mind if I re-direct this thead to devel-permissions?
> why would i?
>
> > - Can you tell us about Ubuntu's freezes? Which ones exist, how you
> >   find out when they are and how they might affect what you upload?
> The freezes affect what can be uploaded, and how. The Debian import freeze
> means automatic syncs stop happening, The feature freeze means that all
> non-bugfix uploads have to be approved by the release team, The final
> freeze means that there should be non uploads except very high priority
> bugfixes, and you shouldn't upload around beta and alpha releases.
>
> >  As a MOTU or indeed as a Xubuntu developer, are there any times
> >  (outside of the freezes listed above) when you shouldn't upload a
> >  particular package? How would you check when and what shouldn't be
> >  uploaded?
>
> When the upload is proven to be buggy, when the upload will FTBFS, when
> another (upstream/debian/ubuntu) dev has requested that you don't, when the
> upload requires a transition or has large API changes and you've not fully
> checked the related packages.
>
> >   It's a bit concerning to me that uploads might happen without even
> >    build testing (let alone runtime testing)—how can you improve on
> >    this?
>
> My internet is slightly better now (less random crashes, now 500kbps), but
> i still stay away from larger packages. My hardware has also not allowed me
> to do much, since it's a slow, old laptop. I recently got a $200 grant from
> linux au to finish my dev PC, which will make test building far easier, and
> i'll be able to test run more important packages, as well as test build on
> PPC.
>
> > Also inspired by pitti: How do you check that a merge you're
> > performing doesn't drop any changes we need to keep?
>
> Reading the changelog, reading the diff shown on the debian PTS, and if
> there are a lot of changes, debdiff against the old ubuntu version.
>
>
> On Wed, Jan 1, 2014 at 12:48 AM, Iain Lane <la...@ubuntu.com> wrote:
>
>> Hi Jackson,
>>
>> Do you mind if I re-direct this thead to devel-permissions?
>>
>> On Fri, Dec 27, 2013 at 06:00:52PM +1100, Jackson Doak wrote:
>> > What is the process for applying for Xubuntu Packageset and MOTU by
>> email?
>>
>> Just ask, like you did. I'll take this as a request to start the
>> application.
>>
>> > I cannot attend 15UTC meetings, and 19UTC is difficult, especially late
>> > january.
>> > My current testimonials are at
>> https://wiki.ubuntu.com/Noskcaj#Testimonials.
>> >
>> > Xubuntu is especially important, since we no longer have a head of
>> > developement, nad both the current devs have time issues.
>>
>> We'll ask you some questions over email and then once everyone is
>> satisfied we'll vote also over email. You need 4 +1s to succeed, which
>> is the same as on IRC.
>>
>>   - Can you tell us about Ubuntu's freezes? Which ones exist, how you
>>     find out when they are and how they might affect what you upload?
>>   - As a MOTU or indeed as a Xubuntu developer, are there any times
>>     (outside of the freezes listed above) when you shouldn't upload a
>>     particular package? How would you check when and what shouldn't be
>>     uploaded?
>>
>> QA:
>>
>>   - I came across
>>
>> https://bugs.launchpad.net/ubuntu/+source/fcoe-utils/+bug/1258727/comments/2
>>     and pitti's comments in your application also seem to back this up.
>>     It's a bit concerning to me that uploads might happen without even
>>     build testing (let alone runtime testing)—how can you improve on
>>     this?
>>   - Also inspired by pitti: How do you check that a merge you're
>>     performing doesn't drop any changes we need to keep?
>>
>> Cheers,
>>
>> --
>> Iain Lane                                  [ i...@orangesquash.org.uk ]
>> Debian Developer                                   [ la...@debian.org ]
>> Ubuntu Developer                                   [ la...@ubuntu.com ]
>>
>
>

--- End Message ---
--- Begin Message ---
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message.  Do this if the message is
spam.  If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list.  The Approved: header can also appear in the first line
of the body of the reply.

--- End Message ---
-- 
technical-board mailing list
technical-board@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/technical-board

Reply via email to