Re: [epf-dev] Feedback on OpenUP

[Per Kroll <pkroll@xxxxxxxxxx>]

Hi Jim

great to see that you are adopting OpenUP!

• Who are some of the shops that have already adopted OpenUP for more than just 6 – 10 developers?
  PKR: One of the problems with open source is that you have no clue who downloads and use it. It is all confidential and dependent on people like you telling the world about usage... We have seen e-mails from among others including Siemens (they piloted and planned large rollout, not sure what current status, ILOG, a few univrsities, and a few others. I am also privately aware of a few big adoptions, but am not sure if the companiues want to reveal their adoption...
  I invite anybody aware of companies to respond to this e-mail so we can build a list...
  Also see slide from latest release review below:

• What kind of legal issues, if any, have people run into as they add their own content?

PKR:
In your specfic case, based on what you describe, I think you can divide
the potential issues into two areas, where only 1) would apply to most
people
I think the problems seems to be
reasonably easy and dividable into legal issues around open source and
legal issues around usage of RUP.

1) Open Source - as long as you change
the process by building plug-ins, you are fine... If you change the actual
plug-ins that are open source, you are actually obliged to donate that
changed content back to EPF. (That is why all eclipse products focus on
APIs and extensibility, you cannot change the source code without giving
it back). This may or may not be a poroblem for you, and the tool should
allow you to do changes as extensions through plug-in mechanism, or you
may perhaps even want to have your content to become open source. If there
are changes / extensions you would like to do, but cannot do, then please
let us know, because that indicates that we may have to restructure OpenUP
or enhance the tool.

2) If you have concerns about RUP licensing
issues, and potentially infringing on that license, that should be a discussion
with IBM (and I will send you a separate note on that in the role of "IBMer"
vs. EPF proj lead role), but  in general, you cannot copy text from
RUP straight off. If you write new text, but somewhat influenced by how
you have developed software in the past, you are probably fine... Anyhow,
the easiest is to look at some concrete example and then see whether there
may be an issue, but I am sure that is something that can be easily solved.

• Will there ever be a search feature in OpenUP?  This is one thing that I know our people have liked in the past with RUP.

PKR: There are no
plans that I am aware of, but then plans are always fluctuating and reflective
of what is requested. In general, we would also appreciate more people
getting involved in investing in tooling part, since the burden of evolving
it is very uneven...

• Will there ever be a search feature in your list archive?  I had tried scanning to find answers to some of my questions, but there are a lot of posts to wade through without a search.

 PKR:
I do not know, but will forward request to eclipse WebMaster and see what
they respond.

Cheers

Per Kroll
Project Lead: Eclipse Process Framework
STSM, Manager Methods: RUP / RMC
Rational Software, IBM Corp
(M) 408-219-2963

"Crowley, Jim" <Crowley.Jim@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx

08/21/2007 11:53 AM

Please respond to
Eclipse Process Framework Project Developers List        <epf-dev@xxxxxxxxxxx>

To	<epf-dev@xxxxxxxxxxx>
cc
Subject	[epf-dev] Feedback on OpenUP

On the website you had asked for
feedback, even if we were just considering using OpenUP, so below is my
feedback along with some questions:

If you decided not to use OpenUP, why? – We are still undecided on this, but are leaning heavily towards using OpenUP.

What specific problems did you encounter (e.g. lack of training, couldn't understand a particular guideline, etc)? – While you ask this question in relation to deployment, our biggest problem is getting legal acceptance.  We are going to have to modify the content to some extent, and this raises some concerns about how do we add content without infringing on someone’s intellectual property or copyrights?  The biggest concern would be that whatever we added may end up looking too similar to what is already in RUP.  Because we have employees that have worked with RUP in other shops, they are familiar with the process, so it’s really hard to divorce them from the process when they add new content.        

Are you using it as-is or are you modifying it? - We will definitely be modifying it.  We have some roles, guidance, and artifacts that we use in house that we would like to get added.

If you're using EPF Composer, to what extent are you modifying OpenUP (e.g. minor text changes, replacing templates, changing entire disciplines, etc)?  We would be using EPF Composer to make the changes mentioned in the last question.

What are the characteristics of your project (head count, timeframe, industry, greenfield or maintenance, successful delivery, etc)? - We would start off with projects that had 10 – 50 people on them, and eventually work our way up to 100+ project members.  We could have upwards of 5000 unique people accessing the content over the course of a year.
 
My Questions:

• Who are some of the shops that have already adopted OpenUP for more than just 6 – 10 developers?
• What kind of legal issues, if any, have people run into as they add their own content?
• Will there ever be a search feature in OpenUP?  This is one thing that I know our people have liked in the past with RUP.
• Will there ever be a search feature in your list archive?  I had tried scanning to find answers to some of my questions, but there are a lot of posts to wade through without a search.

Thanks,
Jim Crowley

-----Message Disclaimer-----

This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect@xxxxxxxxxxxxx and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.

Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.

While this communication may be used to promote or market a transaction
or an idea that is discussed in the publication, it is intended to provide
general information about the subject matter covered and is provided with
the understanding that The Principal is not rendering legal, accounting,
or tax advice. It is not a marketed opinion and may not be used to avoid
penalties under the Internal Revenue Code. You should consult with
appropriate counsel or other advisors on all matters pertaining to legal,
tax, or accounting obligations and requirements.
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev