|[aperi-dev] Re: Aperi Project status|
I found your email answer to Wayne interesting. Specifically I'm curious what you believe Aperi is providing to the greater Eclipse community? You stated that:
Since I see Eclipse as more than just a place for projects to have a CVS and Bugzilla, it's my personal opinion that Eclipse projects are obligated/should be involved in the Eclipse venues and efforts. For example, all Eclipse projects should be moving towards joining the annual release train; and they should be working to educate the rest of the Eclipse community about their area of expertise; and they should be working to integrate with the rest of the projects (for example, BIRT and DTP and TPTP have been great in that way, making use of each other's frameworks in mutually beneficial ways). After all, if a project is not involved in something more than just itself, then it's not really "part of" Eclipse and perhaps should be hosted at Google Code or Sourceforge or some other location, n'est pas?
Good you elaborate a bit on the connections between Aperi and "the greater Eclipse community"?
[end of message]