Hi
Ed,
Just
a question about Mint: this project is quite small (around
100 classes), well structured (releng, tests, etc.) and
provides a nice developer experience with EMF.
Why
not merging its plug-ins in a bigger active project like
EMF? Once moved, I guess the maintenance effort would be
very limited.
Guys,
I've completed a draft of the termination/restructuring review
for the modeling project, which includes the termination of
all container projects.
http://wiki.eclipse.org/Modeling/project_termination_review_2012
This will have
an significant impact on bugzilla organization, which is kind
of a complete mess:
https://bugs.eclipse.org/bugs/enter_bug.cgi?classification=Modeling
In the ideal
world, each remaining project (each direct subproject of the
modeling project) would have its own bugzilla product and that
product's components would be only those components the
project wants for their product. This will also allow the
projects to manage their specific versions properly. The EMF
product, for example, has components for a bunch of things
that are now separate projects so they really should be
separate bugzilla products:
https://bugs.eclipse.org/bugs/describecomponents.cgi?product=EMF
Also as
previously discussed, the website is a disaster area. We need
a landing page with a clear message. I propose the following
content:
Modeling:
Faster, Smarter, Better
The
bewildering complexity of modern software begs for a fresh
approach focusing on high-level design, delegating menial
tasks to tools and frameworks. From a concise description of
your problem domain, a complete solution can be inferred.
What
is Eclipse Modeling?
Eclipse
Modeling is an integrated assortment of extensible tools and
frameworks for solving everyday problems.
At
its core lies the Eclipse Modeling Framework, a rich
abstraction for describing, composing, and manipulating
structured information. Around this core, onion-like
technology layers provide powerful facilities to address most
everything you need.
Why
use Modeling?
· To
produce high-quality results quickly.
· To
reuse tried, tested, and true solutions effectively.
· To
specify complex structured information concisely.
· To
design rich textual and graphical notations easily.
· To
implement powerful runtime solutions efficiently.
· To
exploit industrial standards interoperably.
Any and all feedback is more than welcome.
EMO/Webmaster,
The question to the webmaster/foundation is, how flexible
can "we" be in this reoganization to rename bugzilla
products, to change the components within those products,
and to migrate all the existing bugzillas to use those
restructured products and components? Should all product
names be of the form Modeling.<project-short-name> to
make them globally unique? Or is the
<project-short-name> already globally unique and hence
that will suffice? That would be better. Of course I'll
provide all the details for the remapping, but before I
proceed with that tedious exercise, I'd like to know what's
possible (and supported by the foundation team) so I can
outline the proposal and review it with the PMC and all the
affected projects.
Regards,
Ed
