Brainstorm (Re: Minutes of the Technical Board meeting, 2012-02-20)
kees at ubuntu.com
Mon Mar 19 21:25:19 UTC 2012
On Mon, Feb 27, 2012 at 10:17:37AM -0800, Matt Zimmerman wrote:
> On Mon, Feb 27, 2012 at 10:12:29AM -0800, Jono Bacon wrote:
> > On 22 February 2012 13:32, Ian Weisser <ian at korinthianviolins.com> wrote:
> > > On Tue, Feb 21, 2012, mdz wrote:
> > >> Can we commit to doing this once per release cycle instead? Or should we
> > >> abandon it entirely?
> > >
> > > We in the Brainstorm community see great value in a periodic review and,
> > > of course, want it to continue as often as the Technical Board finds
> > > feasible.
> > >
> > > If there is anything the Brainstorm moderators can do to help, please
> > > let us know.
> > >
> > > Based on TB feedback in previous reviews, a great deal about Brainstorm
> > > has changed behind the scenes. We have found ways to more effectively
> > > redirect non-ideas and wishlist-bugs, tightened up moderation and
> > > sandbox standards, and -for the first time- identified what Brainstorm's
> > > goals and deliverables really are.
> > Ian, with the Technical Board not having the time summarize the most
> > interesting and popular ideas in Brainstorm, is this something that
> > the Brainstorm community could do?
> The main purpose of the reviews was to provide an official response from the
> development team. The technical board selected the ideas to respond to, and
> requested help from individual developers to write up a post about each one.
> It may be worth a try if the brainstorm moderators would like to play this
> role, but I think the responses would probably get more priority if the
> request comes from the TB.
> To be clear, I think this is an important and valuable program and I want it
> to continue. I'm just acknowledging the reality that it isn't working
I'd like to propose that the top-10 review be due the week before Debian
Import Freeze each devel cycle. It's not clear to me if we should do
one immediately, and then another for Q's DIF, or if we should wait
More information about the technical-board