| Hi Sébastien,
Zeligsoft was acquired in 2022 by a company called Lumenix. We do something completely different, ( https://www.aimsplatform.io/) developing a system that consists of a network of devices that use AI to detect different things in a hospital setting. But when Zeligsoft was acquired we kept a couple of old customers, in particular doing customizations of Papyrus. And I’m the one maintaining these. But Zeligsoft stopped being an Eclipse member somewhere in 2020, I think.
Cheers
Ernesto Posse eposse@xxxxxxxxx
On Feb 15, 2024, at 12:37 PM, GERARD Sebastien <Sebastien.GERARD@xxxxxx> wrote:
Hi Ernesto, BTW, can I ask for which company your are working for? Best, Séb. <image001.png> | | Sébastien Gérard Fellow, director of research Program Leader of the flagship program Digital Collaborative & Augmented Engineering CEA-List, Paris-Saclay (ou Grenoble)
Département, Service, Laboratoire <image003.jpg> T. +33 (0)1 69 08 58 24 M. +33 (0)6 88 20 00 47 Le CEA-List est membre du réseau des Carnot <image002.jpg><image004.png><image005.png> |
|
De : mdt-papyrus.dev <mdt-papyrus.dev-bounces@xxxxxxxxxxx> De la part de Ernesto Posse via mdt-papyrus.dev
Envoyé : jeudi 15 février 2024 17:37
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Cc : Ernesto Posse <eposse@xxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] Bug 582940 Hi Ansgar, I was wondering about pushing to Gerrit, because our company is no longer an Eclipse member and my understanding was that it means I am no longer an Eclipse Committer, but in Bugzilla I see my messages with an ECA tick mark, so I guess I might still be able to push? I’ll give it a try. As for the future plans, when is the move to Papyrus-Sirius and Papyrus web planned for? Is it for version 7.0? Or later?
Dear Ernesto, good to hear from you after quite some time! Concerning the bug, you should still be able to push to gerrit. I don't think, that required to put the general text (I wrote the code ...) in the commit message as it is not very useful when looking at the history. Make sure, a reference to the bug is in the header of the modified files. I also like to point out that the architectural framework of "classic" (GMF, XWT) Papyrus will not be used in the long run. The successors Papyrus-Sirius and Papyrus Web use different customization mechanisms. Best Ansgar On 15/02/2024 04:05, Ernesto Posse via mdt-papyrus.dev wrote: I’ve submitted a new bug report to Bugzilla, Bug 582940, but I accidentally cut the first few paragraphs with the bug description when I pasted it in the Comment textbox. So I’ve added the full description as a new comment, as I cann’t edit my previous comment. I’ve also added a full diagnosis of the bug and can submit a patch, but I don’t think I can push it to Gerrit as I am no longer an Eclipse Committer. Should I use a particular patch header when creating the patch? Also, according to the guidelines, I should add messages stating that I wrote the code, that it has no cryptography, etc. Where do I write those? In a local git commit comment and then create the patch from that commit?
_______________________________________________ mdt-papyrus.dev mailing list mdt-papyrus.dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|
