Hi Rich,
thanks for your reply.
As you suggested, we're going to file a bug and attach a patch with what we'd like to contribute to the Amalgamation project. I hope to get that done by the beginning of next week.
Thanks again, Peter
On 09.02.2009, at 10:31, Richard Gronback wrote: Hi Peter,
See comments below...
In summary, given the existence of the DSL Toolkit download from Amalgam and the history associated with the oAW “brand” at Eclipse, I’m not inclined to see such a package created within the project. Contributions to the DSL Toolkit are of course welcome!
Thanks,
Rich
On 2/9/09 9:46 AM, "Peter Friese" <peter.friese@xxxxxxxxx> wrote:
Hi all,
I am writing this eMail on behalf of the oAW team. As you know, there has been a lot of confusion lately around openArchitectureWare: will it remain an Eclipse project, will it move out, or move back in?
[rcg] Yes, a very long intermittent thread with seemingly no end.
We have been having lots of discussions recently and think it might be the best idea for oAW to stay with Eclipse. As pretty much of the whole code of oAW actually is contained in components that already are Eclipse projects, it really doesn't make much sense to move away from Eclipse. Essentially, oAW is a distro that is made up of Xpand, MWE, Xtext and of course all the platform code we rely on such as EMF and the Eclipse platform. In addition to all that, we only have some glue code like the oAW perspective and the project wizards.
[rcg] I’m afraid it may have taken too long to come to this decision. In the meantime, a DSL Toolkit package has been created in Amalgam that has much the same makeup. In fact, I’ve already stated I’ll be adding Xtext to this package. The DSL Toolkit has its own perspective, project type/wizard, etc. So, I really don’t see the point in having another package that is so closely aligned in purpose/content. I’ll continue to reply where appropriate to the questions below...
We have come to the conclusion to propose running oAW as an Amalgamation package. Actually, oAW is being mentioned on the Amalgamation wiki page (http://wiki.eclipse.org/ModelingAmalgam) already :-)
[rcg] Yes, that was a very old reference. I actually removed it yesterday, given my rethinking of the idea in the context of Amalgam and its charter. Adding it nowadays would not serve the community well; in fact, it would create more of the same problem we have already have in Modeling with too much choice for everything.
This would effectively mean we
- archive the oAW code in the SourceForge repository and stop development there
- do all new development under the umbrella of Eclipse
- try to convince our users to use the Eclipse newsgroups for support
- redirect http://www.openarchitectureware.org <http://www.openarchitectureware.org/> to http://www.eclipse.org/modeling(amalagamation/oaw
[rcg] I suggest you keep this website operational if you intend to continue using the oAW name, logo, etc.
We compiled a list of questions that we couldn't answer by looking at the Amalgamation project site and wiki and love to hear your answers. Also, if you've got any questions, we'd be happy to answer them.
So without further ado, here is the list of questions:
1) will we be able to provide an oAW feature that users can install into their existing Eclipse installation
2) what will be the version identifier of what we now call "oAW 5.0" ?
3) will we be able to have a landing page for oAW Amalgamation?
4) will be be allowed to place off-site links on our landing-page?
5) will we be allowed to provide p2 update site URLs, so that users can complement their Eclipse installation with our external add-ons after installing oAW Amalgamation?
6) will we be allowed redirect http://www.openarchitectureware.org <http://www.openarchitectureware.org/> to http://www.eclipse.org/modeling/amalgam/oaw ?
[rcg] I don’t think anyone can prevent an external URL from referencing an Eclipse website.
7) will we be able to participate in the Galileo release train?
[rcg] Amalgam is not currently on the train.
8) how many committers may we suggest? (It seems reasonable to have 2 or 3 committers to get the work done)
9) how will those committers be added to the Amalgamation project? Just ask Rich?
[rcg] Adding committers to Amalgam or any Eclipse project requires the same meritocratic process.
10) will we be allowed to provide glue code like wizards, perspectives, online help, PDF manuals to complement oAW Amalgamation?
[rcg] As already stated, these exist already, while contributions are welcome to improve them.
11) what's the relation of oAW Amalgamation with the Amalmagation Modeling Package? Will we re-use it? Will it re-use us?
Cheers,
Peter
_______________________________________________
amalgam-dev mailing list
amalgam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/amalgam-dev
_______________________________________________
amalgam-dev mailing list
amalgam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/amalgam-dev
|
