Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [modeling-pmc] Notifcation to let QVTO contribute to Juno

Hi Philipp

The current system works.

For projects supported by major companies such as itemis or Obeo there is no problem. But when a major company such as Borland (QVTo, GMF) or IBM (EMF, UML2, OCL) retrenches or when a residual individual retires we get these panics and a solution is found.

A solution cannot be found until then because anyone genuinely keen to contribute is probably already on board. The panic is needed to stimulate companies to place a real value on 'free' software.

For shoestring projects such as EMF core, UML2, OCL or GMF, users must consider whether they can risk dependency on almost a single individual.

In the case of OCL, when the original IBM team retired, the resulting panic stimulated so much enthusiasm for rescue that the competing offers had to be mediated. Sadly little of this enthusiasm supports ongoing activities.

[I don't see the system improving much unless Eclipse employs its committers and companies make significant contributions to pay the corresponding salaries.]


        Ed Willink
On 17/12/2011 12:55, Philipp W. Kutter | Montages AG wrote:

I wish you all Happy Holidays!

It is a great feeling that the OMG standards based projects are going strong and will all be on the Juno releasse train!

If there is a doubt in the future that any of these projects will not be on the release train, simply because nobody is there to fulfill the formalities of the project or the details of the newest build project, we can always help. As Miles mentions, this may need to add some people of other modeling projects to the committer teams.

Could the modeling PMC send out a mail and ask the modeling teams
a) who sees a risk they will not be on the release train, simply because of lack to fulfill the formalities and the build project
b) who would volunteer to help out for other projects.

As well, it might be a good policy, to have a backup plan, if a component lead is either not available, or ill, or otherwise gone in the very moment he needs to promote the project. Immagine an important project, with lots of dependencies does not release, simply because the component lead is in-available. The costs can be huge.

Thanks for the great work of the Eclipse Foundation,

On 17.12.2011 01:44, Ed Willink wrote:
Hi Miles

There is no need to panic. In view of some delicacies, considerable correspondence has happened off-list.

Nicolas Rouquette has now resolved both the problem and the delicacies by his open email to these lists that you must have missed.

Thanks to Nicolas' generosity, QVTo will be available in Juno supported by the existing QVTo team.

The only process exception that may be needed is tolerance of a one or two day tardiness in setting the contribution flag.

I'm sure we all wish to thank Nicolas for being so helpful to Eclipse. Thank you Nicolas.


        Ed Willink

On 16/12/2011 23:57, Miles Parker wrote:

You should identify QVTO leadership, which means M2M nee MMT, so that they can make the change in their portal. (This of course would have to be in the middle of a project renaming!) That would require all of MMT to join train, I don't know if it's possible to do this more fine-grained than that. PMC can flip the bit for MMT, but I don't think we should do that unless/until we have support from project leadership or at least active committers if they exist. Comments?

William, I'm cc'ing you because I note that you have contact with Frédéric Jouault who is project lead..? Perhaps you could pass on his email to Phillip.

FWLIW, I'll support any process exception if needed/possible once that is sorted out. Phillip, thanks for taking the initiative on this. Why don't you report back to PMC list as you make progress?



On Dec 16, 2011, at 12:29 PM, Philipp W. Kutter | Montages AG wrote:

Dear PMC.

I would like to notify that QVTO should flip the bit for Juno. I hope
this has already been done by the QVTO team itself.

In the unexpected case, that the current QVTO team will not have time to
trigger the newest ways of building the QVTO, I can guarantee
development time from the GMF Tolling component lead Michael Golubev,
who knows well the newest ways of building.

As well, there is a cummulative patch from Nicolas Rouquette, which we
would love to integrate in the new build, if the QVTO team has not yet done.

The GMF Tooling project has a strong dependency on QVTO and would fail
in their efforts to do their releases in the future, if QVTO build fails.

As well, the sponsor of the 3 FTE working on GMF tooling requests that
GMF Tooling as well as the project it depends on are remaining in Juno, so we have a multiyear 3 FTE sponsorship at risk, if this does not happen.

We want to do all to support the current team to do the Juno builds.
There is a budget from Nicolas Rouquette and us, which would offer $
2000 to who ever in the QVTO team wants to do this. And we support with
development time from the 3 FTE working on GMF Tooling, if needed.

Please forward this message as well to the QVTO team, whom I do not know personally. Please assure them of our full support. I did not find a mailing list for them.

And, as today is the deadline, please accept this notification, even if
formally it comes from the wrong side.


modeling-pmc mailing list
cross-project-issues-dev mailing list

No virus found in this message.
Checked by AVG -
Version: 2012.0.1890 / Virus Database: 2108/4684 - Release Date: 12/16/11

No virus found in this message.
Checked by AVG -
Version: 2012.0.1890 / Virus Database: 2108/4685 - Release Date: 12/16/11

Back to the top