[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pmf-dev] Basic rules of PMF and eclipse talks
- From: yves.yang@xxxxxxxxxxx
- Date: Tue, 15 Dec 2009 04:04:36 -0800
- Delivered-to: email@example.com
- User-agent: SquirrelMail/1.4.19
> In general, projects are restricted from including things outside their
> scope. But I don't think the things Olivier are bringing up are
> obviously outside the scope. Therefore, Yves, you need to explain better
> why some things are considered OK to include in the project, and other
> things are not.
> So in the case of PMF, why is model-to-text transformations a natural
> part of the project, and model-to-model transformations not? In both
> cases, the point is ending up with artifacts (code, models, supporting
> files) that can be executed or interpreted by a runtime.
This template "JET" is in the proposal as a demonstrator. The proposal was
passed by project review. It is accepted by PMC and by the Community. Any
change must be proved in the same way.
> pmf-dev mailing list