RE: [vtp-dev] Draft plans available

[Brent D Metz <bdmetz@xxxxxxxxxx>]

Excellent finds, and I'll add them to
the project plan as well. BTW, we already follow the project layout conventions
of WTP described in that first document.

In terms of icons, isn't there an Eclipse
style guide for that? There are a number of Eclipse convention documents
for the platform as a whole that I'll assemble links to while we're looking
at this. There appears to be a lot of work going on to unify processes
across all the Eclipse development communities so we'll have to keep an
eye on this going towards 1.0.

--
Brent D. Metz
Enterprise Voice Tools
bdmetz@xxxxxxxxxx
"Simple things should be simple, and complex things should be possible."
- Alan Kay

"Gloppe, Frederic" <frederic.gloppe@xxxxxx>
Sent by: vtp-dev-bounces@xxxxxxxxxxx

08/25/2005 09:58 AM

Please respond to
Voice Tools general developers

To	"Voice Tools general developers" <vtp-dev@xxxxxxxxxxx>
cc
Subject	RE: [vtp-dev] Draft plans available

It opens an other question for
me: we should adopt some conventions for the documentation of course but
also for the coding and probably also for the graphical element (such as
icons). It can appear as "comestic" but I think that this should
be defined very early in the project.
As one of the mid/long term objective
is to integrate the VTP in the WTP, I suggest to adopt the WTP conventions.

For example the naming convention:
http://www.eclipse.org/webtools/development/guidelines/naming-conventions.html
 
They do not provide a style guide
for the WTP but they reuse the CDT one:
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/cdt-home/user/docs.html?cvsroot=Tools_Project
 
I did not find information about
a graphical style guide.
 
What do you think ?
 
Best regards,
Fred
--
HP OpenCall Partner and developer
enablement

---

From: vtp-dev-bounces@xxxxxxxxxxx
[mailto:vtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Brent D Metz
Sent: jeudi 25 août 2005 15:46
To: Voice Tools general developers
Subject: RE: [vtp-dev] Draft plans available


Every project sets its own processes, but in my mind High Priority Items
are the actual requirements to cut the milestone. In larger projects on
Eclipse.org I have seen a lot of feature fluidity between releases but
since we have a fairly small number of features in mind per milestone I
don't think that will happen here. 

Thanks for catching that problem; I meant to say Medium Priority Items
from M3 (which was only Documentation) were High Priority for the RC. And
this brings up the point that so far we haven't signed anyone up explicitly
to work on organizing the documentation, if anyone is interested. The alternative
is to have the committers work on it but my experience is that having someone
removed from the development process work on the documentation goes a long
way. The IBM XML editor contribution is already fully documented so most
of the structure is already there; it would just be a matter of adding
to what's there and keeping everything properly organized.

--
Brent D. Metz
Enterprise Voice Tools
bdmetz@xxxxxxxxxx
"Simple things should be simple, and complex things should be possible."
- Alan Kay

"Gloppe, Frederic" <frederic.gloppe@xxxxxx>
Sent by: vtp-dev-bounces@xxxxxxxxxxx

08/25/2005 08:49 AM

Please respond to
Voice Tools general developers

To	"Voice Tools general developers" <vtp-dev@xxxxxxxxxxx>
cc
Subject	RE: [vtp-dev] Draft plans available

Hi Brent, 
  
Thanks a lot. Sounds good to me. What is the process when a feature with
a low priority is not implemented for a specific milestone ? Is it automatically
added to the next milestone ? 
I suggest to put the documentation with high priority for the RC. I can
not imagine to deliver such kind of tool without appropriate documentation.
  
Best regards, 
Frederic 
-- 
HP OpenCall Partner and developer enablement

---

From: vtp-dev-bounces@xxxxxxxxxxx
[mailto:vtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Brent D Metz
Sent: mercredi 24 août 2005 23:02
To: vtp-dev@xxxxxxxxxxx
Subject: [vtp-dev] Draft plans available


Hi, 

I've posted draft project and milestone plans to the VTP web site:

http://www.eclipse.org/vtp/plans.html 

Feedback is welcome, especially from contributors. Please note that these
plans do not preclude additional contributions that do not jeopardize the
schedule. 

--
Brent D. Metz
Enterprise Voice Tools
bdmetz@xxxxxxxxxx
"Simple things should be simple, and complex things should be possible."
- Alan Kay_______________________________________________
vtp-dev mailing list
vtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/vtp-dev
_______________________________________________
vtp-dev mailing list
vtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/vtp-dev