KateStewart

Differences between revisions 3 and 5 (spanning 2 versions)
Revision 3 as of 2010-12-13 04:08:05
Size: 2038
Editor: 99-191-111-134
Comment:
Revision 5 as of 2010-12-14 20:00:55
Size: 3359
Editor: eth3
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<BR>><<TableOfContents>>|
|
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<BR>><<TableOfContents>>||
Line 43: Line 42:
As the Ubuntu Release Manager, I work with the release team to manage the Ubuntu development and long term support releases. As the Ubuntu Release Manager, I work with the release team to manage the Ubuntu development and long term support releases. Some of the areas I'm responsible for are:
 * holding weekly release meetings to get status across teams and highlight issues for the approaching milestones
 * coordinate pulling together the release notes for each of the milestones and final releases
 * review key open bugs to determine impact to release and specific milestones
 * work with release team to update and maintain release process pages
 * work with release team to manage image building and publishing
 * host sessions at UDS/rally's to deal with release issues ( post-release process analysis, licensing and copyrights, metric improvements, etc.)
Line 45: Line 50:
'''TO DO: add more here - Release meetings, Release Notes, Release/Milestone Bug Review, process pages, 3 UDS sessions, Licensing and copyright ''' Recent impacts:
 * worked with launchpad team to get o-series and p-series opened up for targeting future releases bugs/features to enable better planning
 * started bi-weekly SRU and LTS release meetings to get cross functional discussion as work out bi-weekly kernel SRU process intersecting with development release.
 * reworked release notes framework for 10.10, and technical overview notes for milestone releases.
Line 47: Line 55:
'''TO DO: SPDX - co-chair, technical lead, www.spdx.org ''' In addition, I am a co-chair of the SPDX working group, sponsored by FOSSbazaar and the Linux Foundation (www.spdx.org). The purpose of this group is to come up with a standard way to exchange copyright and licensing information that can be shared among software supply chain providers. Some of this has been modeled after the DEP-5 approach, but is looking to extend it to be more rigorous for commercial purposes.
Line 51: Line 60:
'''TO DO: Add Links" '''TO DO: Add Links'''
Line 55: Line 64:
* LCA business track (January)
* Invited talk at Linux Collaboration Summit and 1/2 day work session on SPDX (April)
* Linux Conference 2010 (August)
* Panel participant at ACI Software Licensing (September)
* Linux Plumbers- Licensing BOF (November), and was on program committee.
 * LCA business track (January)
 * Invited talk at Linux Collaboration Summit and 1/2 day work session on SPDX (April)
 * Linux Conference 2010 (August)
 * Panel participant at ACI Software Licensing (September)
 * Linux Plumbers- Licensing BOF (November), and was on program committee.
Line 63: Line 72:
* LCA business track (January)  * LCA business track (January)
 * Linux Collaboration Summit ( SPDX working session )
Line 65: Line 75:

== Testimonials ==
##== Testimonials ==

Hello! I am Kate Stewart, and I work as the Ubuntu Release Manager for Canonical.

Contact Details

  • IRC: skaet (irc.freenode.net)

  • Email: kate(at)canonical(dot)com

  • Jabber: skaet

Also see my Launchpad Profile.

Where to find me

Ubuntu Mailing Lists:

  • ubuntu-devel
  • ubuntu-devel-announce
  • ubuntu-devel-discuss
  • ubuntu-announce
  • ubuntu-release

Upstream Mailing Lists:

  • spdx
  • spdx-tech

IRC:

Contributions

As the Ubuntu Release Manager, I work with the release team to manage the Ubuntu development and long term support releases. Some of the areas I'm responsible for are:

  • holding weekly release meetings to get status across teams and highlight issues for the approaching milestones
  • coordinate pulling together the release notes for each of the milestones and final releases
  • review key open bugs to determine impact to release and specific milestones
  • work with release team to update and maintain release process pages
  • work with release team to manage image building and publishing
  • host sessions at UDS/rally's to deal with release issues ( post-release process analysis, licensing and copyrights, metric improvements, etc.)

Recent impacts:

  • worked with launchpad team to get o-series and p-series opened up for targeting future releases bugs/features to enable better planning
  • started bi-weekly SRU and LTS release meetings to get cross functional discussion as work out bi-weekly kernel SRU process intersecting with development release.
  • reworked release notes framework for 10.10, and technical overview notes for milestone releases.

In addition, I am a co-chair of the SPDX working group, sponsored by FOSSbazaar and the Linux Foundation (www.spdx.org). The purpose of this group is to come up with a standard way to exchange copyright and licensing information that can be shared among software supply chain providers. Some of this has been modeled after the DEP-5 approach, but is looking to extend it to be more rigorous for commercial purposes.

Trade Shows/Ubuntu/Linux Events

TO DO: Add Links

I spoke at the following events in 2010:

  • LCA business track (January)
  • Invited talk at Linux Collaboration Summit and 1/2 day work session on SPDX (April)
  • Linux Conference 2010 (August)
  • Panel participant at ACI Software Licensing (September)
  • Linux Plumbers- Licensing BOF (November), and was on program committee.

Planned Speaking Events for 2011

  • LCA business track (January)
  • Linux Collaboration Summit ( SPDX working session )

KateStewart (last edited 2012-11-04 01:17:49 by 83)