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

Bug 330138

Summary: CQ form does not reflect the types of CQs that need to be entered
Product: Community Reporter: Michael Keith <michael.keith>
Component: IPZillaAssignee: Eclipse Foundation IPZilla inbox <foundation.ipzilla-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: barb.cochrane, janet.campbell, sharon.corbett, wayne.beaton
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Michael Keith CLA 2010-11-12 15:44:32 EST
I have to admit that I get kind of frustrated every time I need to enter a works-with CQ for a jar that doesn't get distributed. The only options that are available on the portal are:

[use] a third-party library from Orbit
[contribution] of code to be maintained at eclipse.org
[request] to use, reference, or distribute third-party code that is maintained elsewhere (not already in Orbit)

I am entering a works-with CQ that is referencing third party code but not distributing it, so the third option, right? The code is not being contributed to Eclipse, yet the resulting form has no place for me to indicate that the code is neither being contributed nor distributed. Rather, it asks me (in required fields no less!):
   a) if I will be "distributing this code in source, binary, or both source and binary?"
   b)will the "code contribution be distributed unmodified or has the code been modified for distribution in Eclipse."

We should have a works-with option that allows me to tick off whether or not I am a)contributing and b)distributing the code. When I first started entering CQs this really bewildered me and I just assumed that I was in the wrong place and ended up going in circles. Now I am less bewildered (although that doesn't stop me from going in circles ;-) but just as confused about why I have to choose options that are not true just so that I can press the submit button.
Comment 1 Eclipse Genie CLA 2014-12-08 12:16:49 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2016-11-28 20:03:58 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Wayne Beaton CLA 2017-03-27 12:45:11 EDT

*** This bug has been marked as a duplicate of bug 509307 ***