Ubuntu Wiki

Time and place

When: TBA

Where: #ubuntu-meeting on the Freenode Network

Log

Actions

Not Assigned

Assigned

For rescheduled tasks look here.

Agenda and minutes

Membership policy for mozilla-extensions-dev team

• Topic summary: We need to set a membership policy for mozilla-extensions-development team. Do we let everyone in, with trial period to show some development, or do we need candidates to show some work before joining the team? Does the membership expire, and needs to be renewed, or we manually remove inactive members?
• Actions:
  • Basic requirements to get into m-e-d team are 1 package and 3 updates. To preserve the membership a user needs to regularly contribute to the team. A rule of thumb for removing members from the team is 6 months of inactivity, but current memberships can be reviewed ~1 month before new Ubuntu release.

Team Tags and Status changes

• Topic summary: We need a set of tags to keep and others to remove or combine in other tags also i would like feedback on what wikis to update since most are old. Feedback on these wikis would be great or some ideas and i will save everything as notes for a to do list and go from there
• Actions:

  • Add how to upstream patches to the MozillaTeam/Bugs/TriagersHandbook, and how it fits in the general procedure

• Further information:

  • MozillaTeam/Bugs/UpstreamBugProceduresIntrepid

  • MozillaTeam/Bugs/TriagersHandbook

MozillaTeam wiki

• Topic summary: We need to clean up the wikis for the MozillaTeam, for example taking a wiki that has conversations posted should be changed to a complete wiki, this will help users understand it more. All MozillaTeam's and ExtensionTeams's wikis should have CategoryMozillaTeam, CategoryBugSquad at the bottom of wiki page

• Actions:

  • Properly categorize MozillaTeam wiki pages. Check that all MozillaTeam pages have CategoryMozillaTeam and all MozillaTeam bugs pages have CategoryBugSquad

  • gnomefreak and shirish work together on initial MozilaTeam wiki cleanup

Extensions related wiki pages

• Topic summary: Since we have the m-e-d team, we need to see where we maintain extensions related wiki pages. Is MozillaTeam/Extensions/ good, or is there some better option? We also need a wiki start page for m-e-d team.

• Actions:

  • Jazzva to reorganize extension wiki pages. Use MozillaTeam/Extensions for pointers to other sections, and add MozillaTeam/Extensions/Packaging, MozillaTeam/Extensions/List. Add column to the table for compatible programs (use icons).

Thunderbird extensions

• Topic summary: There was talk and a Wiki about Mozilla team before UDS, I would like to know where we are on that or if it was declined.
• Actions:
  • asac to add thunderbird examples to XPI.TEMPLATE and document that on Packaging page

Meetings

• Topic summary: We should have a meeting at least once a month or whatever we can decide on. This will help in membership approval as well as keeping everyone updated and keeping our support docs up to date. Once a month is just a suggestion.
• Actions:
  • gnomefreak and Volans to create meeting schedule for next 6 month and take care of getting those meeting on fridge and sending preannouncements

Large scale Extensions - Next steps

• Topic summary: Define what the next steps are, which areas require work and who takes the lead on the particular topics
• Actions:

  • No current actions, as it's not yet ready. Once it's ready pick out details from LargeScaleMaintenance page, and put them on MozillaTeam/Extensions/Packaging page.

Extension Team Marketing

• Topic summary: How to better communicate our extension efforts
• Actions:
  • Write scripts that gather stats for: extensions updated this month, new extensions suggested this month, new extensions released this month, extensions that need to be updated (a list to the extensions that have a new upstream version), total extensions maintained by m-e-d.
  • gnomefreak to write a blog post/announcement with these stats and a call to join m-e-d team. Include "medal of honor" for the m-e-d member that updated most packages. Jazzva to provide basic blog post layout.
  • Ask UWN to republish the blog post.
  • Target initial m-e-d report for end of July (or if we are good June)

  • Someone to create a MozillaTeam/Extensions/Team page that includes a) short intro, b) requirements to join (as discussed)

Proposed members for MozillaTeam

• Stephen Lau (Stevel_): declined. He didn't show up at the meeting, so we couldn't acknowledge his prior contributions.

mozillateam-community

• Actions:
  • Setup mozillateam-community team and add applicants that do not need branch access or haven't otherwise contributed considerably to mozillateam
  • asac to document redirection procedure to mozillateam-community on mozillateam membership page

Other business

• None

CategoryMozillaTeam