Idea: Forwarding Subteam

Emmet Hikory persia at
Sat Jun 28 14:37:26 BST 2008

On Sat, Jun 28, 2008 at 6:54 PM, Sense Hofstede <sense at> wrote:
> This is a big task and too few people are doing it. What need to be
> done, according to me, is to create a set of packages that need to be
> monitored and checked for confirmed and triaged bugs and create some
> clearer policies(e.g. create bugwatches for all bug reports you can
> find, including other distributions? How do you write the upstream
> summary?). A subteam consisting of people dedicated to forwarding
> upstream and assigned so specific packages(or upstream bug trackers)
> look out for bugs ready to be reported upstream.

    Rather than creating a subteam, and tracking it in LP, and all of
that, I'd encourage the simple definition of the work, and the
organisation of regular times to meet and coordinate/report current
progress.  While some people are excited about joining a new team,
this feeling rarely lasts.  If someone is willing to regularly (e.g.
once a fortnight, once a month) organise a drive to meet the goal,
finding people willing to participate in the drive is easier, and
those who cannot commit to joining every session may well be able to
join the occasional session without the stigma of possibly not meeting
team requirements.

    That said, I agree that helping get more upstream is quite
possibly useful, and that building better relationships with specific
upstreams can have tremendous value in ensuring that the version of
the software in Ubuntu is as good as it can be.


More information about the Ubuntu-bugsquad mailing list