Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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

Regards,

Charles Rivet
Senior Product Manager, Papyrus-RT product lead

On 2016.11.03, at 07:30 , Maximilian Koegel <mkoegel@xxxxxxxxxxxxxxxxx> wrote:

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".

Cheers,
Maximilian


On Thu, Nov 3, 2016 at 11:36 AM, LE FEVRE FRANCOIS <francois.le-fevre@xxxxxx> wrote:

Dear all,

 

Back from EclipseCon Europe, where we had a shared stand with Polarys and Capella with a nice demo of Moka and Designer with Nao, and the talk of Francis on Papyrus IC [0],

I would like to know if you have a proposition to name the Papyrus ToolSmith. [1]

I have opened a ticket here [2]

 

My pesonla preference ToolSmithS / tss

 

Thanks for your feedback.

 

Francois

[0]: https://www.eclipsecon.org/europe2016/session/open-source-project-industrial-solution-role-papyrus-ic   

[1]: https://wiki.eclipse.org/Papyrus/Oxygen_Work_Description/NewFeature/Papyrus4Toolsmiths

[2] : https://bugs.eclipse.org/bugs/show_bug.cgi?id=506966


_______________________________________________
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



--

Dr. Maximilian Koegel

Senior Software Architect / General Manager
EclipseSource Munich

Mobil: +49 176 223 619 18
Phone: +49 89 21 555 30 - 10 
Fax: +49 89 21 555 30 - 19
Skype: maximilian.koegel

EclipseSource Muenchen GmbH
Agnes-Pockels-Bogen 1
80992 München

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

Back to the top