Ed,
Comments below.
On 01/04/2012 7:35 AM, Ed Willink wrote:
Hi
Ed
I think there needs to be a vacancy before any election for leader
can start, so I feel that the PMC (or EMO) needs to either declare
the MMT leader post vacant or decide that a co-leader is
appropriate and then declare that post vacant.
Normally someone who becomes inactive will step down. I suggest you
request that on the MMT mailing list rather than asking the PMC or
the EMO to declare it. You'll also need to demonstrate the support
of the other committers to fill the vacant role, so that should be
part of this discussion as well. It's not appropriate for me (as
the PMC lead) or for the EMO simply to replace the leadership of a
project without there being an appropriate dialog within the
project. Our decisions need to reflect the will of the members and
we need to see that will expressed in a transparent way...
[I have some familiarity with the MDT web-site, so I would suggest
cloning the MDT pages as the basis for a replacement MMT web-site.
The M2M web-site has had limited maintenance for four years so it
is probably easier to start from 'scratch' to get the correct
style; migrating content might then be easy.]
I'd like to start, in the summer, to replace all the content from
the top down. Most of it is badly antiquated (including my own
projects), though there are some some notable and excellent counter
examples, e.g.,
http://www.eclipse.org/Xtext/
Regards
Ed Willink
On 01/04/2012 15:14, Ed Merks wrote:
Ed,
Project leaders are normally determined by a vote of the members
of the project, not by appointment. So best you propose this
change on the development mailing list and ask for people to
vote +1.
Note that I won't personally be in a position to look into
making all the necessary changes to the website, including
migration to git, until after the Juno release. At that point I
will also review all the projects with an eye on archiving
inactivate projects and decommiterizing inactive committers.
Regards,
Ed
On 27/03/2012 5:45 PM, ed@xxxxxxxxxxxxx wrote:
Hi
In October 2011 prior to EclipseCon Europe there was
discussion on the M2M
dev list of a name change for M2M. Subsequent to EclipseCon
Europe
consensus on MMT (Model to Model Transformation) appeared in a
PMC thread.
No action has occurred, since we have no active M2M lead to
drive the
change through.
We now have a requirement to migrate the website to GIT and
need an active
component lead to do or organise this.
I feel that the time has now come to thank Frederic for his
past
leadership and appoint a new component lead.
As the strongest M2M project, user-wise and committer-wise, I
feel that
ATL should probably provide the leadership, but after talking
with Cedric
Brun, it would appear that Obeo do not wish to take up this
opportunity.
QVTo is a strong project user-wise, but lacks active
committers.
I am the project lead and sole 'active' committer for the QVTd
project.
(The QVTd activity is not very apparent in EGIT since the bulk
of my work
has been in developing auto-tooling for OCL that can be
re-used for QVT. I
have big plans for both QVTd and QVTo.) It seems to fall to me
to offer to
take on the role of MMT component lead.
I welcome hearing other people's views as to how MMT should
proceed.
Regards
Ed Willink
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2114/4907 - Release Date:
03/31/12
|
