Rethinking UDS

[Oliver Grawert]

hi,
Am Freitag, den 28.05.2010, 12:38 +0200 schrieb Martin Pitt:
> 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).

while i hate to send "me too" mails, i as someone who participated in
all UDSes that have been held noticed massively that the focus shifted a
lot from community driven to canonical/business driven.

i fully agree that we should shift back parts of that focus towards more
pleasing community requirements than business plans. 

in the mobile team (not sure that happened in other teams) we were
pushed towards picking at least a part of our blueprints from ideas that
were on brainstorm.ubuntu.com or in whishlist bugs in the past. 
indeed there is a lot of crap on brainstorm and it takes some time you
need to invest to weed through these entries and through launchpad to
find something actually relevant for your team, but imho we should make
it mandatory that a certain percentage of specs we implement is based on
community requests to not undergo the risk to turn into a second redhat
at some point.

ciao
	oli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20100529/9f69f44a/attachment.pgp