Am 12/05/2016 09:35 PM, schrieb Peter Kovacs:
Because I read much concern about the freedom of activity and
meritocratic spirit of the Project. In my eyes it is not about who does
what, but where we want to go. This has to be a common understanding.
Nothing more, nothing less is the intent. The meritocratic workbase is
not affected by this. If people do not agree, on a single common goal,
then this is as okay as we agree on one vision how Open Office will change.
it's not pro or contra regarding a product roadmap. It's just where to
document this. Maybe this was not clearly enough expressed.
Marcus
On 04.12.2016 15:11, Marcus wrote:
Am 12/03/2016 01:21 PM, schrieb Peter Kovacs:
So I suggest to keep Bugzilla as Bugtracker, and use Jira as a Todo
backlog List type. I love Agile methology. Never came to use it thought,
because companies can not deal well if there is no timeframe. But I
think for us its perfect.
we have already so many tools that some of us still don't know any of
them. So, it won't help us when we have just another tool to document
some tasks. We should use our Wiki like we do for other tasks.
My 2 ct.
I think a Wiki is a good Documenting Platform. For tracking tasks it is
more medicore tool in my Opinion. esspecially when it starts changeing
all the time. And I think that will happen when topics get started and
then delays for some reasons, while other Topics having a drive.
Plans will have to constantly be revised and changed. On the other hand
you are right. To get started again Wiki is as good as any other approach.
@Patricia
In my opinion the building tool is part of our Roadmap. Not only that we
need to document things, but we also need to think to extend its
functionality to support us in future requirements. For example the
requirement to sign Packages as our Product to prohibit that other sites
change our product without changing the name.
Also I agree with Jörg that the Roadmap should contain tasks that this
list is concerned about but are not necessary a programming task.
# Concerning 12h period. (did not find who brought this up :) )
What I mean is that it would be great if we could devide all activities
in good estimate able chunks. Agile methology claims everything that an
experienced developer estimates beyond 24h h (3 working days) of effort
is inaccurate and there is a high propability that something has been
forgotten.
Thanks for you feedback! I will overhaul now our outdated Roadmaps, and
start a base for a new Roadmap.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
