[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[ve-dev] Re: ve-dev Digest, Vol 31, Issue 2
|
Hi Mark,
I agree that the VE project could be documented better, though in some
cases, I think better organization of existing documentation would be a
big step in that direction. For the use you were investigating, have you
(or could you) taken the time to consider specifying what type of
documentation would be helpful? It would help to define the tasks we
need to take on, and might end up shaping some of the upcoming
development work as well.
Since I've had a rather steep learning curve in becoming a VE committer,
I plan to capture some of what I've learned in documentation on the
wiki, with a focus on making the transition a little easier for other
new committers. No timeframe on this yet as I'm currently trying to
update the release engineering project for VE in order to get back to an
automated build capability.
Thanks for your comments,
Steve Robenalt
Message: 1
Date: Sun, 9 Sep 2007 10:33:52 -0600
From: "Mark Millard" <mmillard@xxxxxxxxxx>
Subject: [ve-dev] RE: ve-dev Digest, Vol 31, Issue 1
To: <ve-dev@xxxxxxxxxxx>
Message-ID: <000601c7f2ff$35799050$37a8a8c0@MMILLARDD620>
Content-Type: text/plain; charset="us-ascii"
I did some investigation into using VE about a year ago. It looked promising
for the needs of my project; writing UI plug-ins to an Eclipse-based tool
for iTv application development. Unfortunately, I felt there was not enough
documentation or example code for me to pursue it much further.
For this project to succeed, it must be supported with better documentation.
Most people do not have the time to read source code to determine how things
work before making a decision to commit to new technology. We need to be
told how it will benefit our projects and the steps it takes to get there.
***** Mark Millard *****
