|
Hi all
Do we really need this additional
"project natures"?
Do we
and our customers benefit from them or do we make the world for our
"customers" more complicate?
First, we used the different roles for
ourselves for organizing the project and to give him some structure.
Anyhow, the three different roles have their value, but in reality one
physical person can represent 1,N roles and that is the case in our
framework too. The g-Eclipse user will customize its g-Eclipse
workbench to its own needs. So I expect the user NOT to follow the
strict roles of the "Grid project natures".
So
what happens if a "user" plays the "Grid user perspective", "Grid operators
perspective" and the "Grid legacy application developer" and the "Grid service
application developer" in one project?
Does
he then have a well defined "project structure" which can be seen
under the "resource perspective" including all natures? This structure is
then a collection of the "defined structures" of all project
natures.
I'm
therefore not supporting the proposal right now as from my point of view,
the "perspectives" are just different "points-of-view" to the same
structure. Wikipedia gives us "perspective is the way in which objects
appear to the eye" or "one's 'point of view', the coice of a context for
opinions, beliefs and experiences". And as far as I understand the article http://www.eclipse.org/articles/using-perspectives/PerspectiveArticle.html,
I don't see the benefit of to may structures for THE GRID
PROJECT!
As
Thomas, I don't see the very big benefit of the different natures. Therefore I
send my -1 to the proposal and start the discussion.
Harald: -1
Cheers
Harald
-----Ursprüngliche
Nachricht-----
Von: geclipse-dev-bounces@xxxxxxxxxxx
[mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Stuempert,
Mathias IWR
Gesendet: Freitag, 14. September 2007 15:24
An:
Developer mailing list
Betreff: [geclipse-dev] Design
Proposal
Hi
All,
Since I would like to start with
the D1.7 - which is actually the update of the requirements to the
architecture - I would like to discuss a major update that I have in mind and
would therefore ask for your opinions. As you know we have currently three
perspectives that correspond to the three roles we want to support. On the
other hand we have only one grid project nature that is mainly tailored to fit
the ordinary users needs, so I would call it from now on the Grid User
Project. I now would like to introduce two further project types, a Grid
Developer Project and a Grid Operator Project. The main benefit of that
would be that we could set up basic project structures that are tailored to
fit the corresponding roles needs rather than only the users needs (i.e. an
operator would like to have a Batch Systems folder which is useless for a
user). I do not want to get into detail with the specifications of these
projects right now - this should be addressed in further discussions. What I
would like to know is if you would agree to such a change in our architecture
and if I can therefore include this requirement in D1.7. So please give me
some feedback on this soon.
Cheers,
Mathias
|
