Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 196570

Summary:	[Clean the Graffiti] "non-epl" keyword misleading
Product:	Community	Reporter:	Jeff McAffer <jeffmcaffer>
Component:	IPZilla	Assignee:	Eclipse Foundation IPZilla inbox <foundation.ipzilla-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	P1	CC:	barb.cochrane, denis.roy, gabe.obrien, janet.campbell, sharon.corbett, wayne.beaton
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Jeff McAffer

2007-07-15 09:50:54 EDT

the multiple meanings of the "non-epl" keyword is misleading. It seems to be related to both the license and the origin of the contribution. From the keyword definition in IPzilla
non-epl = Contribution is non-EPL or third-party packages only.

The new CQ workflow does not clarify the matter. People are give two choices:
- EPL and written by Eclipse projects members (project member is a Committer or an active participant who contributes code through Bugzilla)

- Not EPL and/or written by a 3rd party. If your non-EPL contribution contains nested components, please list each nested component individually in the list of packages.

In the case of EPL, what is the point of the "active participant who contributes code through Bugzilla" characterization? Who defines "active"? Isn't the fact that the person is contributing code that warrants a CQ enough to say that they are active?

In the non-epl case the wording of the first sentence is ambiguous. While I understand that the "Not" applies only to "EPL", it could be construed as applying to the "and/or written by a 3rd party" part. More significantly and in light of the EPL section, the definition of third party is unclear.

The way I read this now is as follows:
Q1: is this EPL or not EPL
Q2: is the contribution from a random place that has nothing to do with Eclipse or from someone who is actually involved with Eclipse.

This separates the concerns (licensing and origin) and distinguishes between, for example, stuff from Apache and people who are actualy trying to get involved in Eclipse.

Comment 1 Denis Roy

2007-07-24 14:12:15 EDT

I can't answer this, but Janet likely can.

Comment 2 Denis Roy

2007-09-05 15:24:32 EDT

Assigning bugs to foundation-ipzilla inbox

Comment 3 Janet Campbell

2008-09-22 17:31:08 EDT

I've updated the keyword description for the nonepl keyword in an effort to clarify this.

Janet

Comment 4 Denis Roy

2008-11-20 16:59:19 EST

> I've updated the keyword description for the nonepl keyword in an effort to
> clarify this.
> 
> Janet

Has it worked, or is there anything else that needs to be done?

Comment 5 Barb

2009-10-22 11:16:05 EDT

Adjusted as part of the planning process.

Comment 6 Janet Campbell

2009-10-22 11:50:37 EDT

The confusion related to this keyword continues to exist and is now magnified by the extension of licenses that are non-EPL in nature (e.g. dual licensing with EDL, Apache; Project Licenses other than the EPL such as the EDL).  Two keyword changes are needed to clarify the confusion.

We'd like to change the keywords "nonepl" to "thirdparty" and "epl" to "eclipsecode" in IPZilla.  We would like this change to affect both historical records and newly created records.  We'd like to adjust the historical records without notifying/spamming the committer community.  

This change would also affect the Portal as these keywords are automatically populated in IPZilla when a CQ is created in the Portal (e.g. Currently, the creation of third party CQs related to packages that originate from places other than Eclipse result in the keyword "nonepl" being populated in IPZilla.  The creation of a CQ related to code that is to be maintained in Eclipse results in the population of the "epl" keyword in IPZilla).  It is also anticipated that changes to the IP Log will be required consistent with this change.

Comment 7 Gabe O'Brien

2009-10-22 13:04:12 EDT

(In reply to comment #6) 
> 
> This change would also affect the Portal as these keywords are automatically
> populated in IPZilla when a CQ is created in the Portal (e.g. Currently, the
> creation of third party CQs related to packages that originate from places
> other than Eclipse result in the keyword "nonepl" being populated in IPZilla. 
> The creation of a CQ related to code that is to be maintained in Eclipse
> results in the population of the "epl" keyword in IPZilla).  It is also
> anticipated that changes to the IP Log will be required consistent with this
> change.

The changes in the Portal should be pretty straight forward.  The changes to the current set of PHP scripts for creating an automatic IP Log shouldn't be too hard but not as easy as the Portal.  

I can't say for sure how hard it will be to update IPZilla itself, probably a few well crafted SQL queries could handle it though.

Comment 8 Denis Roy

2009-10-22 13:15:21 EDT

> We'd like to change the keywords "nonepl" to "thirdparty" and "epl" to
> "eclipsecode" in IPZilla.  We would like this change to affect both historical
> records and newly created records.  We'd like to adjust the historical records
> without notifying/spamming the committer community.  

In IPZilla, just go to the keyword management and change your keywords as you'd like.  IPZilla will request you click a link to rebuild the keyword cache, which you would do and Presto.  You're done.  All references to the 'old' keyword would be updated to the 'new' keyword. No spam.

Comment 9 Janet Campbell

2009-11-23 15:13:32 EST

(In reply to comment #7)
> (In reply to comment #6) 
> > 
Gabe,

Can you let me know when this is done and I'll follow with an update to the IPZilla keywords as suggested by Denis in comment #8.

Thanks!
Janet

Comment 10 Barb

2010-06-23 14:30:21 EDT

Hi Wayne,

Is this one in your court now?

Thanks.

Barb

Comment 11 Wayne Beaton

2010-06-23 15:01:16 EDT

(In reply to comment #10)

> Is this one in your court now?

Actually, I think that we need to coordinate our efforts. We can fix the portal to generate whatever keywords we want. I can tune the automated log code to look for a specific set of keywords. This is one of those things that we should sit down and coordinate as a group.

Comment 12 Denis Roy

2015-02-12 10:21:45 EST

nonepl was changed to thirdparty last August.  Closing.