incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Grignon <>
Subject Re: [DISCUSS]: AOO 3.4.1 reflection and lessons learned
Date Fri, 28 Sep 2012 01:42:31 GMT
Hello All,

To me, Rob's quote is about achieving a flow state, where we can just do
perform, without worrying about mechanics. Great goal.

As a designer of software, I realize our work is never done. We will either
add something new, enhance some existing stuff, fix some broken stuff, and
in some cases, take old stuff out.

I really like to identify opportunities for improvement, capture them in a
some-day-maybe list (a.k.a. opportunity backlog). Identifying open design
issues occurs all the time: while working in the tools, while performing
user testing, while sharing thoughts and ideas with others in the community.

I find it difficult to achieve flow with regards to capturing these
identifying opportunities for improvement due to the current process. For
example, I'd like to be able to easily and quickly capture my thoughts on
ideas on things we could improve the tool. My preference would be to
capture them in Bugzilla, and tag them appropriately. If I can maintain
this flow, then I can capture many of my thoughts, rather than keep a list
on my local system that will never get realized. I'm not suggesting that
all the opportunities will be implemented, rather, I would like to have a
backlog of open opportunities or design issues that I could query, and then
investigate via a proper collaboration in the community. If the ideas
reasonate, then would could move forward and work as a community to move
into plan. The current model of having to fully vet ever thought or idea in
the community before capturing a work item kills the flow, and is subject
to community judgement. At this phase, there are no wrong answers. Here
lies an opportunity for process improvement in my opinion.

I will capture my thoughts in the wiki.


On Fri, Sep 28, 2012 at 3:19 AM, Albino B Neto <> wrote:

> Hi
> On Mon, Sep 17, 2012 at 8:24 AM, J├╝rgen Schmidt <>
> wrote:
> > AOO 3.4.1 was our second release and I would like to do some reflection
> > of the past and especially the hot phase in the end where we tried to
> > finalize the version. Things that were not so good and that can and
> > should be improved in the future. I am looking for general remarks and
> > feedback from people who were involved in this release process and who
> > were affected in one or the other way.
> What was written in the wiki I agree!
> We use other communication tools to test bugs, hunting bugs, ,
> eliminate bugs, . I mean, we could have every two months or more, a
> day on irc (or elsewhere) to discuss about the bugs, questions of AOO,
> specific time in UTC (-1, -2, -3, ... 5,6,7), an example in Brazil
> (UTC -3) mark at 8 pm.
> About alpha, beta 1, beta 2, RC1, RC2, be released and circulated in
> networks. So we have a feedback, and when we leave the final say 100%.
> Albino

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message