Hi all,
I fully agree with Wayne, a top-level Project/page should be
urgently created.( i just browsed around polarsys and was quite
discouraged[not being logged] wrt the image provided to external
public ).
We should at least have a homepage reminding a summary of polarsys
usage :
- components developped/supported by techo&
service-providers can be hosted/long term supported and
qualified
- components hosted can be downloaded and used by
end-users/members
The operation of the polarsys infrastructure is supported :
- by the polarsys organistation for governance & everyday
operation
- by the techno &services providers for qualifying their
components( i.e. uploading them and documenting searchables
attributes)
For categories of projects i see thus at last those:
- Operation tools : supporting the polarsys operation activities
among them catalog to hold a list of all tools maintained with
searchable attributes such as maturity, certifiability and
interoperability qualifiers. such tools will support the
operation of polarsys
- infra or infrastructure tools : as already defined by OPEES,
these tools are basic services ontop of eclipse to support
transversely the development tools
- development tools ( Req capture & analysis, design, verify
, code and test)
- toolchains : support tools for toolchains ( set of integrated
components support all or part of the lifecycle. ), e.g.
configuration ( and possibly automated generation )
On 18.05.2012 2:57, Wayne Beaton wrote:
It time that we define a top-level project for PolarSys.
We have a charter template document [1] that provides a foundation
for the charter. I've also included some links [2,3,4] for a few
existing Eclipse top-level projects.
Note that this is different from the PolarSys charter. It's more
of an operational document for some subset of the projects that
will be developed as part of PolarSys.
The top level project is the umbrella under which projects
(subprojects) operate. Each of the subprojects that fall under a
top-level project fit within the scope of the top level.
The trick here is to provide a scope with the right breadth.
There's no hard and fast advice regarding how to scope a
top-level. But it might help to think a bit about a small handful
of categories of project that we expect to eventually have at
PolarSys. Each of those categories is a potential top-level
project.
Remember that each top-level project operates with a certain
amount of autonomy from other top-level projects.
I recommend that we start by brainstorming the categories of
project, and select one from that list to push forward with a
first top level project charter. We can use the wiki if that
works/makes sense.
Thoughts?
Wayne
[1]
http://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.1.php
[2] http://www.eclipse.org/eclipse/eclipse-charter.php
[3] http://www.eclipse.org/webtools/project-charter.html
[4] http://www.eclipse.org/datatools/charter.php
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
_______________________________________________
polarsys-iwg mailing list
polarsys-iwg@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/polarsys-iwg
--
Maurice HEITZ, Project Manager
Critical Systems
CS Communication & Systems
-----------------------------------------------------
Tel: +33 5 61 17 66 66
mobile:+33 68 974 974 0
Fax: +33 5 61 17 65 78
website : http://uk.c-s.fr/
-----------------------------------------------------
This document is strictly confidential and is intended only for use by
the addressee.If you have received this transmission in error, please use the reply
function to tell us and then permanently delete what you have received.
Any views expressed by the sender of this message are not necessarily
those of the Department for Work.
P Before printing, think about ENVIRONMENTAL responsibility
|
