[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-dev] WTP and DTP collaboration and re-using pre-compiled bundles

David,

 

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.

 

- Konstantin

 

 

Oracle
Konstantin Komissarchik | Consulting Member of Technical Staff
Phone: +1 425 201 1795 | Mobile: +1 206 898 0611
Oracle Eclipse Tooling
411 108th Ave NE, Suite 2100 | Bellevue, WA 98004

 


From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Wednesday, October 22, 2008 9:23 AM
To: wtp-dev@xxxxxxxxxxx
Subject: RE: [wtp-dev] WTP and DTP collaboration and re-using pre-compiled bundles

 


> On a somewhat related subject, I didn’t occur to me to bring this up
> at the meeting, but does it make sense to put these plugins into WTP
> Common project rather than Server Tools since they “out-bound
> pieces”? Just asking.


Offhand I don't think so. My concept of projects is that they are based on teams of committers,  not so much architecture or "level" or even "re-use by other projects" ... so the code would belong where the team of committers are (small as they are in this case :). Depending on the purpose and vision of where Common Project is headed, I could imagine other outcomes, but that's my view given the way things stand right now. I thought you wanted to dismantle the Common Project? :)

GIF image