[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [stp-dev] merging SC and SAF
- From: "Beaurpere, David" <David.Beaurpere@xxxxxxxx>
- Date: Fri, 12 May 2006 09:25:32 +0100
- Delivered-to: email@example.com
- Thread-index: AcZ1a1q9myH6IURCSBi/BKXnXNclHAALhgvA
- Thread-topic: [stp-dev] merging SC and SAF
I actually have the same understanding of what a
subproject should be.
I guess where I am thinking differently
is where I see the boundaries of those those coarse grained
To me the core project should focus on the the
development of the core model and its extension mechanisms, which is not what
SAF nor SC are about, instead those 2 projects are about building a tooling
integration/development platform and this is where I would see the logical
also, given the nature of the charter of the STP
project, I believe that the tooling platform side of things will grow to
much more that just a couple of features and a small set of
Here is my two cents on the
I agree that the tooling
from both should be merged into a single subproject. Is there a strong
reason to split the core subproject like this? I view the SAF framework
an extension to the models which would argue that it belongs in the same
subproject. A subproject is typically more coarse grain and is not
typically just a single feature or just a small set of plugins. The
subproject has a cohesive set of code that works together to achieve a goal.
In this case they serve as the core platform for which the STP project
Sent by: stp-dev-bounces@xxxxxxxxxxx
05/11/2006 05:45 AM
STP Dev list
|"STP Dev list"
|[stp-dev] merging SC and
I would like to suggest to
merge the SC and SAF subprojects together in a new project aimed at a dev
The rational behind is basically that:
I do not have a name or particular setup to suggest and I guess that
the idea would have to be approved by the PMC before anything happens but I
just wanted to put the idea out there to see what people think of it.
- The Service Creation project is poorly named
anyway (the name is inherited from the very early days of the STP setup)
and, regardless of it merging with SAF, it will have to renamed.
- SAF doesn't really belong in the core framework
- both projects are effectively complementary and
are focusing on closely related areas.