[iam-dev] Target platform, the Embedder and IP

[Abel Muiño Vizcaino <amuino@xxxxxxxxx>]

Current target definition includes bundles needed by the embedder, and  
the embedder's source is expected to be in the workspace.

This might be not "clean", since the embedder is not an eclipse project.

My proposal would be to have IAM and the embedder completely separated  
(at least while the IP review for the embedder is not done... eclipse  
legal suggested not processing it for IP review in its current  
state... maybe after an alfa/beta release).

Embedder releases would be generated on q4e/googlecode and the  
generated bundles will be installed in the IAM target platform.

On top of that, we will need to request the PMC and EMO accept our  
dependency on the embedder (even if it is not hosted at eclipse). It  
should be a "pre-req" dependency per: http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf
I'll take care of that.

Finally, for your reference, here is the list of IP links that I've  
collected so far :-)
IP Poster:
http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf

Committer Guidelines
http://www.eclipse.org/legal/committerguidelines.php

The three Laws of Eclipse
http://www.eclipse.org/projects/dev_process/three-laws-of-eclipse.php

Third Party:
http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf

Yours,
Abel Muiño