[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ormf-dev] Setting out task
|
Yes that does help to a degree. It is my (our?) plan to manage tasks
out of Bugzilla, but the process of getting to agreement on what tasks
need to be addressed, i.e. the direction of the project, needs a
different platform for discussion. My overriding concern is that to
date the ORMF team is simply not gelling. Perhaps I simply have accept
the fact the we simply do not have a viable team at this stage.
Joel
On 3 Sep 2008, at 12:39, Richard Gronback wrote:
Bugzilla is typically where individual tasks are managed, with the
usual practice of CCs and dependency links used to keep everyone
informed of task state changes. There is typically a default *-
inbox alias provided for components in Bugzilla as the default
assignee, which allows everyone on the team to watch all new bugs
arriving so that they can CC themselves to ones of interest.
So while it's not as ideal as everyone sitting in the same office
and having daily interaction, it does work fairly well in
distributed teams. It's just a matter of getting used to it and
sticking to an agreed upon process. Mailing lists work well for
certain things, but as mentioned already, Bugzilla is where the
majority of development tasks and discussions traditionally take
place on Eclipse projects. This doesn't mean you have to do it this
way, of course. There is typically a balance of mailing list,
bugzilla, wiki, and conference call activity on projects. Perhaps
Mylyn would be helpful to use on ORMF to assist with Bugzilla and
task management?
HTH,
Rich
-----Original Message-----
From: ormf-dev-bounces@xxxxxxxxxxx [mailto:ormf-dev-bounces@xxxxxxxxxxx
] On Behalf Of Joel Rosi-Schwartz
Sent: Wednesday, September 03, 2008 7:26 AM
To: The Open Requirements Management Framework project development
list
Subject: Re: [ormf-dev] Setting out task
You bring up an interesting subject that does need to be clarified.
What is the purpose of the ormf-dev mail list? It appears from
perusing other dev lists of Eclipse projectw, that the list usage is
typically of a bureaucratic nature, f.i. votes, releases, etc.. So
if we follow this pattern, which is what I gather Achim is
inferring, then where do we have team communications? In my opinion
lack of communication is a major issue with the ORMF team, so simply
delegating task in Bugzilla is going to do little towards team
building. Surely we should start having regular (weekly?) team
conference calls, but is that sufficient? Personally I do not think
so.
I would very much appreciate advice from our mentors on these points.
Thanks,
Joel
On 3 Sep 2008, at 08:01, Achim Loerke wrote:
Just a short reply: we are currently switching our operating
environment from Windows Server 2003 32bit to Windows Server 2008
64bit. It all works reasonably well but takes up most of my time. I
will start working on the CQs in the next few days.
I think it's best not to use ormf-dev for discussions regarding the
individual tasks if the topic is not of general interest. So if there
are no different opinions I'll limit emails to ormf-dev regarding my
tasks to status reports and the occasional cry for help.
Achim
--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst Amtsgericht
Braunschweig HRB 2450
<Achim_Loerke.vcf>_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev
_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev
_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev
