Good point Charles. If Papyrus succeed to become a top level project it will be product of the
Papyrus Product Family. Until that, it will be a kind of sub-project of Papyrus Similarly to SysML.
About the naming, we informally agree on having a long name and a short name. The short name should follow this rule (based
on EBNF notation):
·
<Papyrus Product Short Name> = Eclipse Papyrus - <short name postfix>
ð
Here we should decide if we want restrict the postfix to be an acronym of 2, 3 or more letters? Or be something
free including any name?
·
<Papyrus Product Long Name> = Eclipse Papyrus for <long name postfix>
ð
Questions: do we really want “for” to be mandatary? Should <long name postfix> be the expansion of the acronym?
That mean that <short name postfix> should be an acronym. Other?
Séb.
|
|
|
|
|
|
|
Sébastien Gérard
Head of the LISE labs
CEA Research Director
Papyrus project Leader (www.eclipse.org/papyrus)
Commissariat à l’énergie atomique et aux énergies alternatives
Institut List
|
CEA Saclay Nano-INNOV
|
Bât. 862- PC174
F-91191 Gif-sur-Yvette Cedex
M. +33 6 88 20 00 47
T. +33 1
69 08 58 24
sebastien.gerard@xxxxxx
www-list.cea.fr
|
|
|
|
|
|
 
|
|
|
|
|
|
|
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de charles+zeligsoft.com
Envoyé : jeudi 3 novembre 2016 15:21
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] Toolsmith
Although I like what Maximilian proposes, we need to be careful with the Papyrus branding with regards to the names we use and how we use them.
In line with this, my first question is how will this be packaged? Will it be a “Papyrus Additional Component”? Or will it be a full-blown product like those defined by the Papyrus Industry Consortium (Papyrus IC), which has already done
some work on consistent naming for the Papyrus product line [1] ?
If this is to be the former (Additional Component), then I like Maximilian’s proposal of simply calling it “Papyrus SDK.”
If the latter (product in the product line), then I would hope that it could follow the pattern established by the Papyrus IC, that is:
-
Long name: Papyrus for <<task/domain/user type>>
-
Short name: Papyrus-<<short 2-5 characters related to Long Name>>
E.g., “Papyrus for Toolsmiths” as a long name and “Papyrus-TS” as a short name.
In this case, also, it should probably officially become part of the Papyrus IC’s Papyrus product line.
[1] https://wiki.polarsys.org/Papyrus_IC/Product_Management
[[SG] >]
Charles Rivet
Senior Product Manager, Papyrus-RT product lead
Hi,
I like "Papyrus for Toolsmiths", what also comes into my mind is the term "SDK" in this context. So another name could be "Papyrus SDK"
or even a combination of both "Papyrus SDK for Toolsmiths".
--
Senior Software Architect / General Manager
Mobil: +49 176 223 619 18
Phone: +49 89 21 555 30 - 10
Fax: +49 89 21 555 30 - 19
EclipseSource Muenchen GmbH
General Managers: Dr. Jonas Helming, Dr. Maximilian Koegel
Registered Office: Agnes-Pockels-Bogen 1, 80992 Muenchen,
Commercial Register München, HRB 191789
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|
