| Re: [mdt-ocl.dev] Question regarding submitting EMF Event Manager |
Guys,
From: mdt-ocl.dev-bounces@xxxxxxxxxxx [mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Kenn Hussey
Sent: 11 January 2011 13:24
To: MDT OCL mailing list
Cc: Stephan Eberle; Sébastien Gérard
Subject: Re: [mdt-ocl.dev] Question regarding submitting EMF Event ManagerIMHO, the Event Manager rightfully belongs in MDT Sphinx. I was sure I had said that before, but maybe I hadn't. In any case, I would suggest discussing it with the Sphinx project leads, Stephan and Sébastien (copied), to see whether there is indeed a good fit on the longer term...Cheers,Kenn
On Tue, Jan 11, 2011 at 5:27 AM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
Hi Adolfo
I completely agree that it would be much better to put the Event Manager in its right place.
Unfortunately it's size and utility puts it on the border of EMF Core.
If it goes in EMF Core it must be thoroughly reviewed before M6. No chance. I'm sure there are many aspects that 'must' be changed to please different reviewer's 'aesthetics'.
If a new EMF Event Manager incubation sub-project is created, this too must happen by perhaps M7. My experiences trying to raise an EMF Model Registry project discourage me from recommending this approach. We also would have a dependency on an Incubation project for OCL Examples.
This leaves OCL Examples as the least bad solution, assuming we don't abandon the Impact Analyzer altogether, which would be very disappointing since I see the impact analysis as having many potential customers, including ourselves.
Regards
Ed Willink
On 11/01/2011 09:05, Adolfo Sánchez-Barbudo Herrera wrote:Axel,
My reasons of committing the enhancement to the proper place are:
- It's an issue which should be sort out. The sooner the better...
- As soon as the event manager is committed in somewhere the enthusiasm of moving it to the proper place could decrease...
As said, I think that asking for a deadline for the review doesn't hurt anybody... Why are we discussing if Ed M could find time to review the contribution this week?
Anyway, Ed W gave his +1 to commit the stuff into OCL Examples, so I'm not stopping this anymore.... my +0.
Cheers,
Adolfo.
El 10/01/2011 14:07, Uhl, Axel escribió:Why do you expect a move to be so difficult. After all it's more or less a package rename which would have to happen anyway when moving out of the examples area. I would hope it doesn't stay in examples/ forever either ;-) -- Axel ------------------ Sent from BB ----- Original Message ----- From: Adolfo Sánchez-Barbudo Herrera [mailto:adolfosbh@xxxxxxxxxxxxxxxx] Sent: Monday, January 10, 2011 02:06 PM To: Uhl, Axel Cc: Ed Willink <ed@xxxxxxxxxxxxx>; mdt-ocl.dev@xxxxxxxxxxx <mdt-ocl.dev@xxxxxxxxxxx> Subject: Re: [mdt-ocl.dev] Question regarding submitting EMF Event Manager Hi all, Coming back from my holidays break... To be constructive... Axel what about if you try to obtain some feedback in the bugzilla or somewhere about when (1 week, 1 month, post indigido, never ?) the contribution could be reviewead and/or committed ?. Depending on such an estimation we could take some decisions about it. We all want to make the different pieces to be placed at the proper place... From my experience, if we committ the event manager into OCL, it will probably stay there forever.... So my preference is waiting until the event manager is committed into EMF, where it should really do exist... Best Regards, Adolfo. El 07/01/2011 0:05, Uhl, Axel escribió:Ed,-----Original Message----- From: Ed Willink [mailto:ed@xxxxxxxxxxxxx] Sent: Thursday, January 06, 2011 11:51 PM To: Uhl, Axel Cc: Adolfo Sánchez-Barbudo Herrera Subject: Re: [mdt-ocl.dev] Question regarding submitting EMF Event Manager Hi Axel As you agreed in an earlier response, you must remove the event manager and (impact analyzer) from CVS because it contains unapproved material. It seems some is not even intended for OCL at all. If it is still there tomorrow, I will have to remove it myself.I "cvs rm"ed the contents, but of course they are still in the history. My ssh account on dev.eclipse.org is restricted, so I can't wipe it from /cvsroot/... by any means. If you can, please go ahead.When I indicated that you could commit to event/impact without approval, I intended that lack of oversight to apply to minor/moderate maintenance, not initial/major commit where Bugzillas await residual review. I was not aware that the event manager was intended for EMF. So long as this is the case it should not be committed to OCL.Ed Merks hasn't done anything in a few months now. I don't see a problem with first committing this to OCL's examples section. If Ed Merks later thinks it should go into EMF Core, fine, then I'm happy to support him in moving it there. Until that happens, we need this for the Impact Analyzer. I won't hold the Impact Analyzer back for this solvable problem.It's very odd that Ed has made no comment at all. Reviewing the comments, it is now very unclear that he needs to comment since you say you're migrating to OCL. However he may wake up in his PMC role and ask why the OCL commit has happened without IP approval... So long as the EMF Bugzilla is open and a comment is expected from Ed, there should be an attachment that Ed can sensibly review. Please provide it; a patch with org.eclipse.emf... names.Ed Merks made it clear at ESE that *he* will look into naming and other implementation details after I explicitly offered my assistance. That's as much as I can do.I'm not clear why you request permission today to do what you did yesterday in breach of committer guidelines. Please read the guidelinesCould we please stop this? I admitted my novice mistake and apologized. I'm now trying to get it fixed. It would be helpful if you assisted me in this rather than keeping reminding me of my mistakes. I asked whether top open a new bug for the MDT/OCL component in preparation of an IP review for a later commit to that component. You now suddenly suggest you don't want the event manager bundle in the examples section although you know the impact analyzer depends on it. This would block the whole thing until Ed Merks moves which he hasn't since ESE. This is unnecessary, in my opinion, because---as I mentioned above---the one event manager bundle can easily be migrated to EMF Core later. It's just a package rename, and only from an *examples* package. Therefore, I just would like to know what the best way is to get IP approval for committing this to the MDT/OCL examples section. If you plan to veto this, let me know now, because then this would mean that the Impact Analyzer gets blocked by Ed Merks' inactivity on https://bugs.eclipse.org/bugs/show_bug.cgi?id=329336 until who knows when. Best, -- Axelcarefully. The integrity of Eclipse repositories is VERY important. Breaking the guidelines leaves both of us in trouble; advertising the breach on Bugzilla is not very helpful either. Please wait for other committers to comment before taking unilateral actions and please ask for advice when in doubt. Regards Ed Willink On 06/01/2011 20:49, Axel Uhl wrote:The event manager is a pre-requisite for the OCL Impact Analyzer. At ESE Ed Merks had indicated he would want to integrate it somwhere in EMF Core. That's why I created https://bugs.eclipse.org/bugs/show_bug.cgi?id=329336. Meanwhile, Ed Merks may not have found the time to look into this. I think this shouldn't hold up the progress of the Impact Analyzer. Therefore, I'd like to commit the event manager to the OCL examples section. Question: For IP review, should I use the existing https://bugs.eclipse.org/bugs/show_bug.cgi?id=329336 bug or should I create a new bug specific to OCL/MDT? Best, -- Axel _______________________________________________ mdt-ocl.dev mailing list mdt-ocl.dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev ----- No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1191 / Virus Database: 1435/3363 - Release Date:01/06/11
Version: 10.0.1191 / Virus Database: 1435/3371 - Release Date: 01/10/11
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
Please consider the environment before printing a hard copy of this
e-mail.
The information contained in this e-mail is confidential. It is intended
only for the stated addressee(s) and access to it by any other person is
unauthorised. If you are not an addressee, you must not disclose, copy,
circulate or in any other way use or rely on the information contained in
this e-mail. Such unauthorised use may be unlawful. If you have received
this e-mail in error, please inform us immediately on +44 (0)118 986 8601
and delete it and all copies from your system.
Thales Research and Technology (UK) Limited. A company registered in
England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne
Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number:
774298
Thales UK Limited. A company registered in England and Wales. Registered
Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone,
Weybridge, Surrey KT15 2NX. Registered Number: 868273