|RE: [wtp-dev] WTP and DTP collaboration and re-using pre-compiled bundles|
I do not believe that your concept of a project lines up with Eclipse Development Process which states that project scope is the primary defining characteristic of a project. So it’s not (or at least it shouldn’t be) about who is working on the feature that determines it’s placement, but rather which project’s scope the feature falls under. I realize that in reality it often goes the other way, but let’s at least acknowledge that that’s due to convenience rather doing what’s “right”.
Further, the people involved in this are not all server tools project committers. Depending on how the work is organized, I am sure we are going to see some committer elections take place one way or the other. I don’t see that as a big issue.
Having said all that, I did not bring this up to start some sort of a turf war. I don’t view it as a personal goal to pad Common Project with more features. As I’ve stated before, as we learn how to better manage the cost of creating micro-project, we should be able to re-shuffle code around and make do without Common Project. I am not a big fan of projects with vague scopes. I only brought this up to see if placing this code in the Common Project in the short term makes better organizational sense to people involved, especially since this code will have to shut down earlier than the rest of WTP and cannot have any dependencies on anything else in WTP. In the end, it doesn’t matter that much which project code is placed in the near term. For this to be successful in becoming more than just a collaboration between WTP and DTP, this code will without a doubt have to move elsewhere.
Behalf Of David M Williams
Back to the top