The Foundations team (https://launchpad.net/~canonical-foundations) would like to become part of Ubuntu Bug Control (thanks to Adrien Nader for preparing the application).
# Reasoning A (growing) number of team members are not able to fully triage bugs despite analyzing, planning and ultimately fixing them. I believe this also hinders cleaning the (large) backlog of bugs on launchpad. I believe that Foundations not being part of Bug Control has its roots in the team having a large number of Core Devs, MOTUs and PPUs, and therefore being able to work around the consequences. This belief is made stronger by the fact that Desktop, Server and Security teams are already members of Bug Control. Due to the recent team enlargement, the proportion of people part of bug control has been shrinking. We cannot predict how this ratio will evolve in the future and new hires will continue to be unable to make Launchpad reflect the reality of their planning. Moreover, Bug Control experience will be an additional asset when applying for roles such as MOTU. The current ratio of Bug Control members to non-members can incur a large additional workload to the former group; similarly, a dozen applications to review will incur a lot of extra work compared to having a distributed team do the education. # Source packages the team works on The list is at the address below: https://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html#foundations-bugs (see also https://bugs.launchpad.net/~foundations-bugs/+packagebugs). This list is probably not perfect but it's probably already pretty good. In practice, people work on subsets of this list (more on this below). # Representative The representative is Nick Rosbrook ( https://launchpad.net/~enr0n ). Launchpad page: https://launchpad.net/~enr0n Despite having only one representative, we will have a wide base of mentors. # Requirements ## The team must be a closed or moderated one. The Foundations team is within Canonical, and hence ~canonical-foundations is closed to those employees working on the Foundations team. ## The team must require its members to sign the Ubuntu Code of Conduct. The team requires members to sign the Ubuntu CoC. ## The team must have at least one representative tasked with educating new members on Ubuntu Bug Control policies. New members of the team have mentors; these mentors will educate new members on the policies. ## The representative above must be a current member, directly or indirectly, of Ubuntu Bug Control. The representative, @enron, has been a member of Ubuntu Bug Control since 2022-09-08. ## The team must limit their use of Ubuntu Bug Control permissions to a specific set of packages. (They should not be setting the importance of bugs about every package in Ubuntu.) The set of packages which fall under Foundation's responsibility is well-known. In addition to that, team members have specific responsibilities for subsets of these packages which is where they will exercise their privileges. PPUs, MOTUs and Core Devs in the team will obviously continue with their current rights under bug control rules. Thanks, -- The Foundations Team _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-bugcontrol Post to : ubuntu-bugcontrol@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol More help : https://help.launchpad.net/ListHelp
