Re: [stem-dev] Project Communication

[Daniel Ford <webdaford@xxxxxxxxxxxxxxxx>]

Submitting an agenda item to a phone call that happens once a week and lasts for about half an hour is an inadequate communications channel for a complex software development project like STEM that is being developed by a geographically distributed team.  It is such a small window of opportunity at an inconvenient time for almost half the committers that I don't see what the purpose of the call is.  It certainly isn't enough time to adequately discuss anything; it doesn't leave a lasting record for anyone else to follow.

One of the requirements of the EDP for open communication and transparent activities.  I don't see any communication between committers on stem-dev, and there is scant communication on the phone call.  So, where is the communication between committers?

Dan Ford
STEM Project Lead



Message: 1
Date: Mon, 4 Apr 2011 11:07:38 -0700
From: James Kaufman<kaufman@xxxxxxxxxxxxxxx>
To:stem-dev@xxxxxxxxxxx
Subject: Re: [stem-dev] stem-dev Digest, Vol 25, Issue 3
Message-ID:
	<OFA4AF9029.9A9E5FB3-ON88257868.00620D0A-88257868.00639332@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

I am all in favor of us making better use of stem-dev, and agree on it's
value - especially for people who are in other timezones.
Developers should absolutely use stem-dev for this purpose.

Regarding the call, it is already our practice that anyone can submit
agenda items to the call for discussion. These can certainly include
issues that require in depth discussion.

I do not want to restrict the call to only one topic per call. As Dan
points out, giving everyone an opportunity to speak does not take much
time.
The phone call is also intended as a vehicle for new users (not only
developers) to meet the team, describe their interests, and ask questions,
and make requests.

Yossi,
I like very much your suggestion on the building / releasing roadmap.
Right now the formal dates exist only in the metadata on the Eclipse
Website.
The leads are supposed to maintain this. To make it possible for others to
have input
on upcoming builds and releases I'm thinking we might want to add a wiki
page where
any developer can document changes (new features, new requirements) since
the last release.
We can also put the target dates for future integration builds and release
builds on this page (and of course make sure
the meta-data stays up to date. The wiki page could contain important
information that we can't list right now in the
metadata such as new plugins that must be added. What do you think?

Best Regards,
Jamie

IBM Almaden Research Center, 650 Harry Rd.
San Jose, CA 95120-6099
email:kaufman@xxxxxxxxxxxxxxx
phone: (408) 927-2477  (tie 457-2477)