Home » Archived » EPF » OpenUP/DSDM
|
Re: OpenUP/DSDM [message #36316 is a reply to message #36107] |
Thu, 02 August 2007 14:32 |
Per Kroll Messages: 60 Registered: July 2009 |
Member |
|
|
Hi Roman,
one of the key characteristics of OpenUP is that it is extensible. We want
to encourage people to just OpenUP as a starting point, and add additional
value to it.
The DSDM plug-in, which contains a small subset of DSDM, not the complete
method, is an example of such a plug-in adding value to OpenUP. We felt it
was useful to make it available as an example of an extension.
We hope that there will be many other extensions down the road, some open
source, some sold, some available for free, and some only inhouse.
If you write extension plug-ins, please let this community know. Also,
provide us feedback on how we can make OpenUP even more extensible...
I hope this helps
/Per Kroll
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f8ckp5$2nc$1@build.eclipse.org...
> Hi,
>
> I've noticed you have included DSDM in the latest release - do you plan
> to distribute it as a part of OpenUP? Why?
>
> Thanks,
>
> Roman
>
|
|
|
Re: OpenUP/DSDM [message #36406 is a reply to message #36316] |
Fri, 03 August 2007 07:34 |
Roman Smirak Messages: 136 Registered: July 2009 |
Senior Member |
|
|
Hi Per,
I understand completely your point about extensibility; however you
distribute a library including both OpenUP + the extension (DSDM in this
case) - although I'm not interested in the extension I have to deal with it;
do you plan to distribute all the extensions in one library? (I'm
experimenting with OpenUP because RUP library is too fat and I see same
threat here.) Let me start with the simplest possible option.
Why not keep them separated? Everyone who is interested in an extension can
download it..
Regards,
Roman
"Per Kroll" <pkroll@us.ibm.com> wrote in message
news:f8spu6$9aa$2@build.eclipse.org...
> Hi Roman,
>
> one of the key characteristics of OpenUP is that it is extensible. We want
> to encourage people to just OpenUP as a starting point, and add additional
> value to it.
>
> The DSDM plug-in, which contains a small subset of DSDM, not the complete
> method, is an example of such a plug-in adding value to OpenUP. We felt it
> was useful to make it available as an example of an extension.
>
> We hope that there will be many other extensions down the road, some open
> source, some sold, some available for free, and some only inhouse.
>
> If you write extension plug-ins, please let this community know. Also,
> provide us feedback on how we can make OpenUP even more extensible...
>
> I hope this helps
>
> /Per Kroll
>
> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
> news:f8ckp5$2nc$1@build.eclipse.org...
>> Hi,
>>
>> I've noticed you have included DSDM in the latest release - do you plan
>> to distribute it as a part of OpenUP? Why?
>>
>> Thanks,
>>
>> Roman
>>
>
>
|
|
|
Re: OpenUP/DSDM [message #36793 is a reply to message #36406] |
Mon, 06 August 2007 20:38 |
Peter Haumer Messages: 228 Registered: July 2009 |
Senior Member |
|
|
As a workaround you can just right-click on the plugin and configuration and
delete them for now. I am sure that once there are many more plugins offered
for EPF that they will be packaged as individual plugin imports.
Peter.
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f8ulqn$c6j$1@build.eclipse.org...
> Hi Per,
>
> I understand completely your point about extensibility; however you
> distribute a library including both OpenUP + the extension (DSDM in this
> case) - although I'm not interested in the extension I have to deal with
> it; do you plan to distribute all the extensions in one library? (I'm
> experimenting with OpenUP because RUP library is too fat and I see same
> threat here.) Let me start with the simplest possible option.
>
> Why not keep them separated? Everyone who is interested in an extension
> can download it..
>
>
> Regards,
>
> Roman
>
> "Per Kroll" <pkroll@us.ibm.com> wrote in message
> news:f8spu6$9aa$2@build.eclipse.org...
>> Hi Roman,
>>
>> one of the key characteristics of OpenUP is that it is extensible. We
>> want to encourage people to just OpenUP as a starting point, and add
>> additional value to it.
>>
>> The DSDM plug-in, which contains a small subset of DSDM, not the complete
>> method, is an example of such a plug-in adding value to OpenUP. We felt
>> it was useful to make it available as an example of an extension.
>>
>> We hope that there will be many other extensions down the road, some open
>> source, some sold, some available for free, and some only inhouse.
>>
>> If you write extension plug-ins, please let this community know. Also,
>> provide us feedback on how we can make OpenUP even more extensible...
>>
>> I hope this helps
>>
>> /Per Kroll
>>
>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>> news:f8ckp5$2nc$1@build.eclipse.org...
>>> Hi,
>>>
>>> I've noticed you have included DSDM in the latest release - do you
>>> plan to distribute it as a part of OpenUP? Why?
>>>
>>> Thanks,
>>>
>>> Roman
>>>
>>
>>
>
>
|
|
|
Re: OpenUP/DSDM [message #37131 is a reply to message #36406] |
Tue, 07 August 2007 17:34 |
Ricardo Balduino Messages: 191 Registered: July 2009 |
Senior Member |
|
|
Roman,
That's valuable feedback. I'll try to make this a topic for discussion in
tomorrow's planning session in order to see what we can do as part of
evolving OpenUP, DSDM and other plug-ins.
In the mean time, Peter's suggestion should work nicely - you can delete the
DSDM configuration and plug-in from your library and work with OpenUP and
Base Concepts plug-ins.
Regards,
Ricardo Balduino.
IBM Rational | EPF Committer
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f8ulqn$c6j$1@build.eclipse.org...
> Hi Per,
>
> I understand completely your point about extensibility; however you
> distribute a library including both OpenUP + the extension (DSDM in this
> case) - although I'm not interested in the extension I have to deal with
> it; do you plan to distribute all the extensions in one library? (I'm
> experimenting with OpenUP because RUP library is too fat and I see same
> threat here.) Let me start with the simplest possible option.
>
> Why not keep them separated? Everyone who is interested in an extension
> can download it..
>
>
> Regards,
>
> Roman
>
> "Per Kroll" <pkroll@us.ibm.com> wrote in message
> news:f8spu6$9aa$2@build.eclipse.org...
>> Hi Roman,
>>
>> one of the key characteristics of OpenUP is that it is extensible. We
>> want to encourage people to just OpenUP as a starting point, and add
>> additional value to it.
>>
>> The DSDM plug-in, which contains a small subset of DSDM, not the complete
>> method, is an example of such a plug-in adding value to OpenUP. We felt
>> it was useful to make it available as an example of an extension.
>>
>> We hope that there will be many other extensions down the road, some open
>> source, some sold, some available for free, and some only inhouse.
>>
>> If you write extension plug-ins, please let this community know. Also,
>> provide us feedback on how we can make OpenUP even more extensible...
>>
>> I hope this helps
>>
>> /Per Kroll
>>
>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>> news:f8ckp5$2nc$1@build.eclipse.org...
>>> Hi,
>>>
>>> I've noticed you have included DSDM in the latest release - do you
>>> plan to distribute it as a part of OpenUP? Why?
>>>
>>> Thanks,
>>>
>>> Roman
>>>
>>
>>
>
>
|
|
|
Re: OpenUP/DSDM [message #37335 is a reply to message #37131] |
Thu, 09 August 2007 23:46 |
Ricardo Balduino Messages: 191 Registered: July 2009 |
Senior Member |
|
|
Roman,
I wanted to follow up on this topic.
During our EPF planning meeting yesterday, we brought this topic to the
table, and carefully considered the various options proposed. You may want
to see the discussion that took place via email (Aug 7 and 8) and decisions
captured on meeting notes (Aug 8) in our developers list here:
http://dev.eclipse.org/mhonarc/lists/epf-dev/maillist.html
In summary, given development constraints, and considering ease of adoption
for major releases of OpenUP, we will keep the various plug-ins inside the
OpenUP library in CVS, making those available for download in EPF web site,
as they are organized now, on our weekly builds. For major milestones and
releases though, we will have separate versions available for download:
- one with all plug-ins in the library
- one with OpenUP and Base Concepts in the library, plus various exported
plug-ins individually available for download (which addresses your original
request)
We hope that this solution addresses your request as a user, and also favors
the development of various plug-ins in parallel with OpenUP.
Thanks for your feedback,
Ricardo Balduino.
"Ricardo Balduino" <balduino@us.ibm.com> wrote in message
news:f9aaej$sr6$1@build.eclipse.org...
> Roman,
>
> That's valuable feedback. I'll try to make this a topic for discussion in
> tomorrow's planning session in order to see what we can do as part of
> evolving OpenUP, DSDM and other plug-ins.
> In the mean time, Peter's suggestion should work nicely - you can delete
> the DSDM configuration and plug-in from your library and work with OpenUP
> and Base Concepts plug-ins.
>
> Regards,
>
> Ricardo Balduino.
> IBM Rational | EPF Committer
>
> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
> news:f8ulqn$c6j$1@build.eclipse.org...
>> Hi Per,
>>
>> I understand completely your point about extensibility; however you
>> distribute a library including both OpenUP + the extension (DSDM in this
>> case) - although I'm not interested in the extension I have to deal with
>> it; do you plan to distribute all the extensions in one library? (I'm
>> experimenting with OpenUP because RUP library is too fat and I see same
>> threat here.) Let me start with the simplest possible option.
>>
>> Why not keep them separated? Everyone who is interested in an extension
>> can download it..
>>
>>
>> Regards,
>>
>> Roman
>>
>> "Per Kroll" <pkroll@us.ibm.com> wrote in message
>> news:f8spu6$9aa$2@build.eclipse.org...
>>> Hi Roman,
>>>
>>> one of the key characteristics of OpenUP is that it is extensible. We
>>> want to encourage people to just OpenUP as a starting point, and add
>>> additional value to it.
>>>
>>> The DSDM plug-in, which contains a small subset of DSDM, not the
>>> complete method, is an example of such a plug-in adding value to OpenUP.
>>> We felt it was useful to make it available as an example of an
>>> extension.
>>>
>>> We hope that there will be many other extensions down the road, some
>>> open source, some sold, some available for free, and some only inhouse.
>>>
>>> If you write extension plug-ins, please let this community know. Also,
>>> provide us feedback on how we can make OpenUP even more extensible...
>>>
>>> I hope this helps
>>>
>>> /Per Kroll
>>>
>>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>>> news:f8ckp5$2nc$1@build.eclipse.org...
>>>> Hi,
>>>>
>>>> I've noticed you have included DSDM in the latest release - do you
>>>> plan to distribute it as a part of OpenUP? Why?
>>>>
>>>> Thanks,
>>>>
>>>> Roman
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
Re: OpenUP/DSDM [message #37437 is a reply to message #37335] |
Sat, 11 August 2007 13:19 |
Roman Smirak Messages: 136 Registered: July 2009 |
Senior Member |
|
|
Hi Ricardo,
that is great, I have already read some related notes you have check in
the CVS.
I guess this topic relates also to my message posted just second ago
(<f9kcmi$idh$1@build.eclipse.org>) - I can basically extend the use case
described there as: the developer can check out the desired plugins from
OpenUP CVS, create some extensions at department X level, etc. You know the
story.
Regards,
Roman
"Ricardo Balduino" <balduino@us.ibm.com> wrote in message
news:f9g917$1f4$1@build.eclipse.org...
> Roman,
>
> I wanted to follow up on this topic.
> During our EPF planning meeting yesterday, we brought this topic to the
> table, and carefully considered the various options proposed. You may want
> to see the discussion that took place via email (Aug 7 and 8) and
> decisions captured on meeting notes (Aug 8) in our developers list here:
> http://dev.eclipse.org/mhonarc/lists/epf-dev/maillist.html
>
> In summary, given development constraints, and considering ease of
> adoption for major releases of OpenUP, we will keep the various plug-ins
> inside the OpenUP library in CVS, making those available for download in
> EPF web site, as they are organized now, on our weekly builds. For major
> milestones and releases though, we will have separate versions available
> for download:
> - one with all plug-ins in the library
> - one with OpenUP and Base Concepts in the library, plus various exported
> plug-ins individually available for download (which addresses your
> original request)
>
> We hope that this solution addresses your request as a user, and also
> favors the development of various plug-ins in parallel with OpenUP.
>
> Thanks for your feedback,
>
> Ricardo Balduino.
>
>
> "Ricardo Balduino" <balduino@us.ibm.com> wrote in message
> news:f9aaej$sr6$1@build.eclipse.org...
>> Roman,
>>
>> That's valuable feedback. I'll try to make this a topic for discussion in
>> tomorrow's planning session in order to see what we can do as part of
>> evolving OpenUP, DSDM and other plug-ins.
>> In the mean time, Peter's suggestion should work nicely - you can delete
>> the DSDM configuration and plug-in from your library and work with OpenUP
>> and Base Concepts plug-ins.
>>
>> Regards,
>>
>> Ricardo Balduino.
>> IBM Rational | EPF Committer
>>
>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>> news:f8ulqn$c6j$1@build.eclipse.org...
>>> Hi Per,
>>>
>>> I understand completely your point about extensibility; however you
>>> distribute a library including both OpenUP + the extension (DSDM in this
>>> case) - although I'm not interested in the extension I have to deal with
>>> it; do you plan to distribute all the extensions in one library? (I'm
>>> experimenting with OpenUP because RUP library is too fat and I see same
>>> threat here.) Let me start with the simplest possible option.
>>>
>>> Why not keep them separated? Everyone who is interested in an extension
>>> can download it..
>>>
>>>
>>> Regards,
>>>
>>> Roman
>>>
>>> "Per Kroll" <pkroll@us.ibm.com> wrote in message
>>> news:f8spu6$9aa$2@build.eclipse.org...
>>>> Hi Roman,
>>>>
>>>> one of the key characteristics of OpenUP is that it is extensible. We
>>>> want to encourage people to just OpenUP as a starting point, and add
>>>> additional value to it.
>>>>
>>>> The DSDM plug-in, which contains a small subset of DSDM, not the
>>>> complete method, is an example of such a plug-in adding value to
>>>> OpenUP. We felt it was useful to make it available as an example of an
>>>> extension.
>>>>
>>>> We hope that there will be many other extensions down the road, some
>>>> open source, some sold, some available for free, and some only inhouse.
>>>>
>>>> If you write extension plug-ins, please let this community know. Also,
>>>> provide us feedback on how we can make OpenUP even more extensible...
>>>>
>>>> I hope this helps
>>>>
>>>> /Per Kroll
>>>>
>>>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>>>> news:f8ckp5$2nc$1@build.eclipse.org...
>>>>> Hi,
>>>>>
>>>>> I've noticed you have included DSDM in the latest release - do you
>>>>> plan to distribute it as a part of OpenUP? Why?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Roman
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
Re: OpenUP/DSDM [message #580945 is a reply to message #36107] |
Thu, 02 August 2007 14:32 |
Per Kroll Messages: 60 Registered: July 2009 |
Member |
|
|
Hi Roman,
one of the key characteristics of OpenUP is that it is extensible. We want
to encourage people to just OpenUP as a starting point, and add additional
value to it.
The DSDM plug-in, which contains a small subset of DSDM, not the complete
method, is an example of such a plug-in adding value to OpenUP. We felt it
was useful to make it available as an example of an extension.
We hope that there will be many other extensions down the road, some open
source, some sold, some available for free, and some only inhouse.
If you write extension plug-ins, please let this community know. Also,
provide us feedback on how we can make OpenUP even more extensible...
I hope this helps
/Per Kroll
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f8ckp5$2nc$1@build.eclipse.org...
> Hi,
>
> I've noticed you have included DSDM in the latest release - do you plan
> to distribute it as a part of OpenUP? Why?
>
> Thanks,
>
> Roman
>
|
|
|
Re: OpenUP/DSDM [message #580990 is a reply to message #36316] |
Fri, 03 August 2007 07:34 |
Roman Smirak Messages: 136 Registered: July 2009 |
Senior Member |
|
|
Hi Per,
I understand completely your point about extensibility; however you
distribute a library including both OpenUP + the extension (DSDM in this
case) - although I'm not interested in the extension I have to deal with it;
do you plan to distribute all the extensions in one library? (I'm
experimenting with OpenUP because RUP library is too fat and I see same
threat here.) Let me start with the simplest possible option.
Why not keep them separated? Everyone who is interested in an extension can
download it..
Regards,
Roman
"Per Kroll" <pkroll@us.ibm.com> wrote in message
news:f8spu6$9aa$2@build.eclipse.org...
> Hi Roman,
>
> one of the key characteristics of OpenUP is that it is extensible. We want
> to encourage people to just OpenUP as a starting point, and add additional
> value to it.
>
> The DSDM plug-in, which contains a small subset of DSDM, not the complete
> method, is an example of such a plug-in adding value to OpenUP. We felt it
> was useful to make it available as an example of an extension.
>
> We hope that there will be many other extensions down the road, some open
> source, some sold, some available for free, and some only inhouse.
>
> If you write extension plug-ins, please let this community know. Also,
> provide us feedback on how we can make OpenUP even more extensible...
>
> I hope this helps
>
> /Per Kroll
>
> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
> news:f8ckp5$2nc$1@build.eclipse.org...
>> Hi,
>>
>> I've noticed you have included DSDM in the latest release - do you plan
>> to distribute it as a part of OpenUP? Why?
>>
>> Thanks,
>>
>> Roman
>>
>
>
|
|
|
Re: OpenUP/DSDM [message #581176 is a reply to message #36406] |
Mon, 06 August 2007 20:38 |
Peter Haumer Messages: 228 Registered: July 2009 |
Senior Member |
|
|
As a workaround you can just right-click on the plugin and configuration and
delete them for now. I am sure that once there are many more plugins offered
for EPF that they will be packaged as individual plugin imports.
Peter.
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f8ulqn$c6j$1@build.eclipse.org...
> Hi Per,
>
> I understand completely your point about extensibility; however you
> distribute a library including both OpenUP + the extension (DSDM in this
> case) - although I'm not interested in the extension I have to deal with
> it; do you plan to distribute all the extensions in one library? (I'm
> experimenting with OpenUP because RUP library is too fat and I see same
> threat here.) Let me start with the simplest possible option.
>
> Why not keep them separated? Everyone who is interested in an extension
> can download it..
>
>
> Regards,
>
> Roman
>
> "Per Kroll" <pkroll@us.ibm.com> wrote in message
> news:f8spu6$9aa$2@build.eclipse.org...
>> Hi Roman,
>>
>> one of the key characteristics of OpenUP is that it is extensible. We
>> want to encourage people to just OpenUP as a starting point, and add
>> additional value to it.
>>
>> The DSDM plug-in, which contains a small subset of DSDM, not the complete
>> method, is an example of such a plug-in adding value to OpenUP. We felt
>> it was useful to make it available as an example of an extension.
>>
>> We hope that there will be many other extensions down the road, some open
>> source, some sold, some available for free, and some only inhouse.
>>
>> If you write extension plug-ins, please let this community know. Also,
>> provide us feedback on how we can make OpenUP even more extensible...
>>
>> I hope this helps
>>
>> /Per Kroll
>>
>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>> news:f8ckp5$2nc$1@build.eclipse.org...
>>> Hi,
>>>
>>> I've noticed you have included DSDM in the latest release - do you
>>> plan to distribute it as a part of OpenUP? Why?
>>>
>>> Thanks,
>>>
>>> Roman
>>>
>>
>>
>
>
|
|
|
Re: OpenUP/DSDM [message #581352 is a reply to message #36406] |
Tue, 07 August 2007 17:34 |
Ricardo Balduino Messages: 191 Registered: July 2009 |
Senior Member |
|
|
Roman,
That's valuable feedback. I'll try to make this a topic for discussion in
tomorrow's planning session in order to see what we can do as part of
evolving OpenUP, DSDM and other plug-ins.
In the mean time, Peter's suggestion should work nicely - you can delete the
DSDM configuration and plug-in from your library and work with OpenUP and
Base Concepts plug-ins.
Regards,
Ricardo Balduino.
IBM Rational | EPF Committer
"Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
news:f8ulqn$c6j$1@build.eclipse.org...
> Hi Per,
>
> I understand completely your point about extensibility; however you
> distribute a library including both OpenUP + the extension (DSDM in this
> case) - although I'm not interested in the extension I have to deal with
> it; do you plan to distribute all the extensions in one library? (I'm
> experimenting with OpenUP because RUP library is too fat and I see same
> threat here.) Let me start with the simplest possible option.
>
> Why not keep them separated? Everyone who is interested in an extension
> can download it..
>
>
> Regards,
>
> Roman
>
> "Per Kroll" <pkroll@us.ibm.com> wrote in message
> news:f8spu6$9aa$2@build.eclipse.org...
>> Hi Roman,
>>
>> one of the key characteristics of OpenUP is that it is extensible. We
>> want to encourage people to just OpenUP as a starting point, and add
>> additional value to it.
>>
>> The DSDM plug-in, which contains a small subset of DSDM, not the complete
>> method, is an example of such a plug-in adding value to OpenUP. We felt
>> it was useful to make it available as an example of an extension.
>>
>> We hope that there will be many other extensions down the road, some open
>> source, some sold, some available for free, and some only inhouse.
>>
>> If you write extension plug-ins, please let this community know. Also,
>> provide us feedback on how we can make OpenUP even more extensible...
>>
>> I hope this helps
>>
>> /Per Kroll
>>
>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>> news:f8ckp5$2nc$1@build.eclipse.org...
>>> Hi,
>>>
>>> I've noticed you have included DSDM in the latest release - do you
>>> plan to distribute it as a part of OpenUP? Why?
>>>
>>> Thanks,
>>>
>>> Roman
>>>
>>
>>
>
>
|
|
|
Re: OpenUP/DSDM [message #581486 is a reply to message #37131] |
Thu, 09 August 2007 23:46 |
Ricardo Balduino Messages: 191 Registered: July 2009 |
Senior Member |
|
|
Roman,
I wanted to follow up on this topic.
During our EPF planning meeting yesterday, we brought this topic to the
table, and carefully considered the various options proposed. You may want
to see the discussion that took place via email (Aug 7 and 8) and decisions
captured on meeting notes (Aug 8) in our developers list here:
http://dev.eclipse.org/mhonarc/lists/epf-dev/maillist.html
In summary, given development constraints, and considering ease of adoption
for major releases of OpenUP, we will keep the various plug-ins inside the
OpenUP library in CVS, making those available for download in EPF web site,
as they are organized now, on our weekly builds. For major milestones and
releases though, we will have separate versions available for download:
- one with all plug-ins in the library
- one with OpenUP and Base Concepts in the library, plus various exported
plug-ins individually available for download (which addresses your original
request)
We hope that this solution addresses your request as a user, and also favors
the development of various plug-ins in parallel with OpenUP.
Thanks for your feedback,
Ricardo Balduino.
"Ricardo Balduino" <balduino@us.ibm.com> wrote in message
news:f9aaej$sr6$1@build.eclipse.org...
> Roman,
>
> That's valuable feedback. I'll try to make this a topic for discussion in
> tomorrow's planning session in order to see what we can do as part of
> evolving OpenUP, DSDM and other plug-ins.
> In the mean time, Peter's suggestion should work nicely - you can delete
> the DSDM configuration and plug-in from your library and work with OpenUP
> and Base Concepts plug-ins.
>
> Regards,
>
> Ricardo Balduino.
> IBM Rational | EPF Committer
>
> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
> news:f8ulqn$c6j$1@build.eclipse.org...
>> Hi Per,
>>
>> I understand completely your point about extensibility; however you
>> distribute a library including both OpenUP + the extension (DSDM in this
>> case) - although I'm not interested in the extension I have to deal with
>> it; do you plan to distribute all the extensions in one library? (I'm
>> experimenting with OpenUP because RUP library is too fat and I see same
>> threat here.) Let me start with the simplest possible option.
>>
>> Why not keep them separated? Everyone who is interested in an extension
>> can download it..
>>
>>
>> Regards,
>>
>> Roman
>>
>> "Per Kroll" <pkroll@us.ibm.com> wrote in message
>> news:f8spu6$9aa$2@build.eclipse.org...
>>> Hi Roman,
>>>
>>> one of the key characteristics of OpenUP is that it is extensible. We
>>> want to encourage people to just OpenUP as a starting point, and add
>>> additional value to it.
>>>
>>> The DSDM plug-in, which contains a small subset of DSDM, not the
>>> complete method, is an example of such a plug-in adding value to OpenUP.
>>> We felt it was useful to make it available as an example of an
>>> extension.
>>>
>>> We hope that there will be many other extensions down the road, some
>>> open source, some sold, some available for free, and some only inhouse.
>>>
>>> If you write extension plug-ins, please let this community know. Also,
>>> provide us feedback on how we can make OpenUP even more extensible...
>>>
>>> I hope this helps
>>>
>>> /Per Kroll
>>>
>>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>>> news:f8ckp5$2nc$1@build.eclipse.org...
>>>> Hi,
>>>>
>>>> I've noticed you have included DSDM in the latest release - do you
>>>> plan to distribute it as a part of OpenUP? Why?
>>>>
>>>> Thanks,
>>>>
>>>> Roman
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
Re: OpenUP/DSDM [message #581523 is a reply to message #37335] |
Sat, 11 August 2007 13:19 |
Roman Smirak Messages: 136 Registered: July 2009 |
Senior Member |
|
|
Hi Ricardo,
that is great, I have already read some related notes you have check in
the CVS.
I guess this topic relates also to my message posted just second ago
(<f9kcmi$idh$1@build.eclipse.org>) - I can basically extend the use case
described there as: the developer can check out the desired plugins from
OpenUP CVS, create some extensions at department X level, etc. You know the
story.
Regards,
Roman
"Ricardo Balduino" <balduino@us.ibm.com> wrote in message
news:f9g917$1f4$1@build.eclipse.org...
> Roman,
>
> I wanted to follow up on this topic.
> During our EPF planning meeting yesterday, we brought this topic to the
> table, and carefully considered the various options proposed. You may want
> to see the discussion that took place via email (Aug 7 and 8) and
> decisions captured on meeting notes (Aug 8) in our developers list here:
> http://dev.eclipse.org/mhonarc/lists/epf-dev/maillist.html
>
> In summary, given development constraints, and considering ease of
> adoption for major releases of OpenUP, we will keep the various plug-ins
> inside the OpenUP library in CVS, making those available for download in
> EPF web site, as they are organized now, on our weekly builds. For major
> milestones and releases though, we will have separate versions available
> for download:
> - one with all plug-ins in the library
> - one with OpenUP and Base Concepts in the library, plus various exported
> plug-ins individually available for download (which addresses your
> original request)
>
> We hope that this solution addresses your request as a user, and also
> favors the development of various plug-ins in parallel with OpenUP.
>
> Thanks for your feedback,
>
> Ricardo Balduino.
>
>
> "Ricardo Balduino" <balduino@us.ibm.com> wrote in message
> news:f9aaej$sr6$1@build.eclipse.org...
>> Roman,
>>
>> That's valuable feedback. I'll try to make this a topic for discussion in
>> tomorrow's planning session in order to see what we can do as part of
>> evolving OpenUP, DSDM and other plug-ins.
>> In the mean time, Peter's suggestion should work nicely - you can delete
>> the DSDM configuration and plug-in from your library and work with OpenUP
>> and Base Concepts plug-ins.
>>
>> Regards,
>>
>> Ricardo Balduino.
>> IBM Rational | EPF Committer
>>
>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>> news:f8ulqn$c6j$1@build.eclipse.org...
>>> Hi Per,
>>>
>>> I understand completely your point about extensibility; however you
>>> distribute a library including both OpenUP + the extension (DSDM in this
>>> case) - although I'm not interested in the extension I have to deal with
>>> it; do you plan to distribute all the extensions in one library? (I'm
>>> experimenting with OpenUP because RUP library is too fat and I see same
>>> threat here.) Let me start with the simplest possible option.
>>>
>>> Why not keep them separated? Everyone who is interested in an extension
>>> can download it..
>>>
>>>
>>> Regards,
>>>
>>> Roman
>>>
>>> "Per Kroll" <pkroll@us.ibm.com> wrote in message
>>> news:f8spu6$9aa$2@build.eclipse.org...
>>>> Hi Roman,
>>>>
>>>> one of the key characteristics of OpenUP is that it is extensible. We
>>>> want to encourage people to just OpenUP as a starting point, and add
>>>> additional value to it.
>>>>
>>>> The DSDM plug-in, which contains a small subset of DSDM, not the
>>>> complete method, is an example of such a plug-in adding value to
>>>> OpenUP. We felt it was useful to make it available as an example of an
>>>> extension.
>>>>
>>>> We hope that there will be many other extensions down the road, some
>>>> open source, some sold, some available for free, and some only inhouse.
>>>>
>>>> If you write extension plug-ins, please let this community know. Also,
>>>> provide us feedback on how we can make OpenUP even more extensible...
>>>>
>>>> I hope this helps
>>>>
>>>> /Per Kroll
>>>>
>>>> "Roman Smirak" <roman.smirak@tietoenator.com> wrote in message
>>>> news:f8ckp5$2nc$1@build.eclipse.org...
>>>>> Hi,
>>>>>
>>>>> I've noticed you have included DSDM in the latest release - do you
>>>>> plan to distribute it as a part of OpenUP? Why?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Roman
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
Goto Forum:
Current Time: Sat Oct 19 13:30:23 GMT 2024
Powered by FUDForum. Page generated in 0.04441 seconds
|