[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [geclipse-dev] geclipse documentation structure
|
Hello!
I attached current structure of our help documentation and first
proposition of changes.
I think that as general rule each chapter should be written as
middleware independent, with assumption that user has no any middleware
installed.
If middleware has special feature to given functionality, we should
create subchapter with description for that.
For example: in chapter "VO Setup" we can describe conception of Virtual
Organization based of generic VO.
In subchapters gLite, gria, AWS we could write about settings for VOMS
VO, GRIA VO, AWS VO.
We can discuss it during today conference.
--
Regards,
Mariusz Wojtysiak
Moritz Post pisze:
My proposal would be to introduce a subchapter under the "g-Eclipse User
Guide" entitled "Middlwares" or "Technologies" or something along those
lines. Here each individual middleware implementation could integrate
documentation specific to their usage scenarios. This could lead to some
duplication in documentation but it is more specific and would thereby
be closer to the actual user. Specifically guides like "How to do XY"
are very valuable.
