| Re: [soa-pmc] It's time to terminate STP |
Hi guys, I think the solution of moving the required stp.model plugins to ebpm’s repository is a good one. Even if other people use them, they would ideally migrate to Mangrove’s project code base, which is just an evolution of the older stp.model component. Engineering will hopefully also migrate soon to Mangrove in the ebpm and spagic future versions. Regarding the termination review I think your suggestion is good Wayne, to simply add stp.model to the overall STP termination review process. Regarding Policy, I am not sure if it’s used, I would expect former SOPERA members (Zsolt?) to know more about this... Best regards, Adrian. From: soa-pmc-bounces@xxxxxxxxxxx [mailto:soa-pmc-bounces@xxxxxxxxxxx] On Behalf Of Andrea Zoppello Hi, FWIW, "Top Level Project" has a specific meaning in the EDP. Your list looks like a bunch of bundles from stp.model (Intermediate Model). Is this correct? Yes we definitely don't need all the stp.model stuff, but only the bundles that ebpm require. The EDP requires that we engage in a Restructuring review. It's a relatively simple affair, requiring only a short description of what needs to move and where. We can include it in the STP termination documentation. i.e. we can combine the STP termination review with a stp.model move review. Once we have all the answers, I'll finish up the termination/move documentation and schedule the review.
The ( ideal )right way to go ( for eBPM too.. ) would be a transition to Mangrove project, What of stp.policy?
-- Andrea Zoppello
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. |
