[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] ECF 3.5.1 and no conference call today (4/4/2011)
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Tue, 05 Apr 2011 10:48:32 -0700
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
On 4/5/2011 10:16 AM, Wim Jongman wrote:
Bug fixes are fine but I would like to swap devtime for doctime for
this release if possible .
I would be very happy if 3.5.1 consisted of just a few bug fixes, and a
*lot* of additional documentation content . We are not at all
limited by the EF review process for documentation development, so there
are absolutely no process costs associated with developing lots of new
reference documentation, examples, tutorials, presentations...and even
All forms of documentation...IMHO...are now as important to ECF as code
changes (bug fixes or new features). The reason for this is that ECF
now has quite a lot of functionality...including lots of great
modularity-enabled features (provider architecture), lots of useful
APIs, lots of providers, lots of extensibility and flexibility...but the
main problem (IMHO) is that much of this flexibility (and the value that
it creates) is too hidden in the minds of the ECF committers.
Fortunately...and thanks to everyone...this is changing...but we can
accelerate the change through efforts on documentation and
promotion...and I think that we should, as a community, work together to
explicitly make ECF more open and more transparent by explaining (or
demonstrating) what it can do...to a much larger audience.
Speaking for myself: although I will continue to do as much as I can in
terms of documentation, examples, tutorials, blog postings,
presentations, etc...a few of us cannot shoulder the entire burden for
this documentation effort. We have to get more contributions and more
participation...from ECF committers, from contributors, and users.
This does *not* have to require a huge time commitment by anyone, and
the use of the wiki, blogs, this mail list, the newsgroup, wikitext,
etc...and open cross-organizational communication...makes this a much
lighter weight thing than creating API/sw documentation used to be.
</speech> (you didn't know that was coming, did you? :)
Now...please join the ECF documentation project bug...by clicking on
this link , and adding yourself as a cc to that bug.
Then...contribute in any way you can.