[Themaintainers] Introductions: Don from GitHub

Camille E. Acey connect at camilleacey.com
Fri Apr 12 06:49:37 EDT 2019

Count me in to this conversation!
I just took over customer support and success at Nylas (https://nylas.com) and I'm trying to facilitate a culture change where people stop equating happy customers with all bugs being fixed. I'd love to learn more about how bugs get diagnosed, assigned, fixed, or wontfixed (!) at scale.

On April 11, 2019 3:07:27 PM EDT, Emma Humphries <ech at emmah.net> wrote:
>Team _wontfix in the house!
>I'm Emma Humphries, bugmaster at Mozilla. I'm part of the Release
>Management team. 
>The elevator pitch of my job is that it's product management of bugs:
>analysis, policy, and process. 
>I'm working with the Bugzilla team and our contractor, Kohei Yoshiro
>(@bugzilla_ux) on improvements to Bugzilla as a bug tracker, and on our
>bug handling documentation: https://mozilla.github.io/bug-handling/. 
>I'd like to talk about how you do process change in established
>projects, the tensions between stakeholders in bug tracking, how your
>bug tracker is not your feature backlog (I just spoke about that at
>Launch Darkly's conference in Oakland this week), and I'd really like
>to meet more maintainers. 
>I blog at https://emmas.site/.
>-- Emma 
>On Wed, Apr 10, 2019, at 08:14, Don Goodman-Wilson wrote:
>> Howdy! 
>> I’m Don Goodman-Wilson, co-chair of the Software Track for The
>Maintainers III. I'm a recovering academic now working in the software
>industry at GitHub. One of my focus areas is discovering the best ways
>to support the maintainers of open source software (OSS). OSS provides
>the backbone for our digital lives (for better or worse), but such
>maintainers are increasingly finding themselves unsupported and
>under-appreciated. The result is that our digital infrastructure is in
>an incredibly delicate and precarious place, moreso than many realize.
>> I discovered The Maintainers at APIdays in Paris last December, where
>Mehdi and Andrew held a day-long unconference on sustaining
>maintainers—and I realized pretty quickly that I had found my people.
>In the Maintainers, I feel like I’ve found kindred souls who understand
>not only the gravity of the situation, but the urgency to find
>solutions in partnership with practitioners who really understand the
>> There are a lot of places where we could use your experience and
>expertise. Are there lessons from other disciplines that could be
>applied to software maintenance? What’s different about maintaining
>legacy software vs open source software? Do you know of interesting
>case-studies we should be aware of? Do _you_ maintain software, and
>have a story to share? What existing institutions exist that could be
>extended to cover software, or that might have resources for software
>maintainers that we aren’t aware of? Does open source as a practice
>have the deck stacked against it, and maybe we need to fundamentally
>rethink the way we approach open, collaborative software creation for
>the public good?
>> If all this is new to you, there are a lot of interesting resources
>out there:
>> (I’d love to read more if you know other recent takes on the current
>state of open source software!)
>> Looking forward to seeing you at The Maintainers III!
>> Developer Advocate, EMEA
>>  GitHub
>> 📮
>> degoodmanwilson at github.com
>> Twitter
>> DEGoodmanWilson <https://twitter.com/DEGoodmanWilson>
>> 📆
>> calendly.com/degoodmanwilson/
>> _______________________________________________
>> Themaintainers mailing list
>> Themaintainers at lists.stevens.edu
>> https://lists.stevens.edu/mailman/listinfo/themaintainers
>> *Attachments:*
>>  * 8726510AB61E49709DF68E4C818833CD.png
>Themaintainers mailing list
>Themaintainers at lists.stevens.edu

Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.stevens.edu/pipermail/themaintainers/attachments/20190412/62c08403/attachment.html>

More information about the Themaintainers mailing list