Rethinking UDS

[Martin Pitt]

Thierry Carrez [2010-05-28  9:24 +0200]:
> If we want to have leaner, more implementation-focused UDS, one way to
> do it is to move it to the third or fourth week after release (rather
> than the second one), leaving time for strategy sprints, planning and
> basic technical investigation to occur before.

This would reintroduce the problem that UDS is very late in the game,
and taking away the already scarce time that we have until the beta to
implement everyhing.

Perhaps even more importantly, I think we should rather aim UDS the
other way: At least personally I find large gatherings like UDS a lot
more productive and enjoyable for talking about ideas, rough
designs, and strategy planning than trying to discuss implementation
details in a large group. IME a lot of participants have valuable
input in the former, but once it comes to implementation details then
one of two things usually happen: (1) the discussion gets reduced
between two or three experts, and most other people get bored, or (2)
too many people are discussing different things or in different
directions, which in the end produces no outcome at all.

I'd much prefer devoting UDS to idea gathering and networking between
upstreams, community developers, Canonical developers, etc., and cut
back on talking about Canonical strategy and technical implementation
details. Once the direction is clear, figuring out the implementation
details is done in a much more productive way the week after UDS by
the drafter and very few experts (such as a project upstream).

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20100528/8eae39a1/attachment.pgp