Hi Pablo,
Your comments and suggestions are certainly appreciated...and will
be acted upon.
We (and the community) would greatly appreciate any help that you
can/would be willing to provide...and all the committers
understand that ECF contributors are not as familiar with the
details of the various parts of ECF. OTOH...as Markus says:
people who are less familiar with things can/will provide very
important insight for those of us that are more familiar.
Particularly WRT to documentation changes/contributions, what I
would like to suggest we do to coordinate is:
1) Join the ECF documentation sub project bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=329124 (I've added a
comment to this bug with your observations and comments).
2) When you have some time to contribute to the documentation,
either
a) open a new bug/enhancement...and make 329124 dependent upon
this new bug
or b) Add a comment that you are going to work on a certain part
of the docs/links on bug 329124
I would suggest that if it's a significant change, that you do 'a'
rather than 'b'...if at all possible.
If you would like to ask any of the committers: myself, Markus,
Wim, Harshana, etc...about the changes you are proposing...then
please also send a quick note to this mailing list...and we will
do everything to comment and respond...even if it's just +1
(go!). Also...feel free to contact any of us via email...and we
can/could consult with you directly...i.e. via phone, email,
conference call, hangout, etc. to coordinate...and notify you of
other things that could possibly be reused.
>As another suggestion, have you thought about in writing a
book with all the
>available information? I think many people would be interested
in buy it.
Actually...yes we have thought about this...and discussed it
some. Thank you for publicly communicating your interest in such
a thing.
The problem for some of us currently is resources (time). None
of us currently has full sponsorship to undertake such a thing
(i.e. we need to work at other things to support ourselves),
although if there are people in range of this that could help with
that...please say so. :).
We are...however...slowly moving in those directions... WRT OSGi
remote services in particular (RSA, discovery, distribution,
providers, rest, soap, etc., etc)...and it remains my hope that we
will be able to complete a book and support work (e.g. examples,
tutorials, etc) over the next 1.5 years. It's also my hope that
this is something like a 'community-created' book...where not only
I and other committers create sections, but also there are
contributions from consumers (e.g. use cases) and contributors.
FWIW, I am personally not expecting any income from such an effort
but will be doing whatever I can to
IMHO there is more than enough useful content to go into a
book...from content about general issues of using OSGi Services
for SOA (dynamics and reliability, network failure, sync/async),
to using ECF...i.e. using existing providers, to EventAdmin/group
messaging, to customizing ECF's RSA, and/or extending and/or
creating new providers for specific/distributed use cases.
Again...IMHO there's lots to talk about :). The trouble for me
and other currently is: getting the necessary time to do so.
Thanks,
Scott
On 12/4/2013 9:27 AM, Pablo García Sánchez wrote: