| [amalgam-dev] oAW as an Amalgamation package |
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? 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. 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 :-) 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 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: 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 to http://www.eclipse.org/modeling/amalgam/oaw ? 7) will we be able to participate in the Galileo release 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? 10) will we be allowed to provide glue code like wizards, perspectives, online help, PDF manuals to complement oAW Amalgamation? 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 |