Bugzilla – Full Text Bug Listing
| Summary: | [pmi] Ipzilla - Orbit ATO CQs should be the only type available to the orbit project. | ||
|---|---|---|---|
| Product: | Community | Reporter: | Nathan Gervais <nathan> |
| Component: | Project Management & Portal | Assignee: | Eric Poirier <eric.poirier> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | chris.guindon, david_williams, janet.campbell, pablo, sharon.corbett, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Nathan Gervais
sounds like a good idea to me! 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. I think this bug is (still) a valid enhancement. I can not say it is real important, but more a "nice to have". As such, does not hurt to leave open? Perhaps it could "fit in" if other work planned on that portal? As a result of the recent updates to the IP Policy, there is no further notion of creating reuse/piggyback CQs. As a result, the idea of Orbit filing ATO CQs should no longer be a requirement as projects themselves will not be creating CQs for third party content they leverage only. The only time a project will create a third party CQ is if the license scanner indicates there is an IP violation or restriction or if it falls into one of the following categories: Cryptography Declaration Workswith Exempt Pre-Req As a result, this CQ can be closed out. Thanks, Sharon (In reply to Sharon Corbett from comment #4) > As a result of the recent updates to the IP Policy, there is no further > notion of creating reuse/piggyback CQs. As a result, the idea of Orbit > filing ATO CQs should no longer be a requirement as projects themselves will > not be creating CQs for third party content they leverage only. The only > time a project will create a third party CQ is if the license scanner > indicates there is an IP violation or restriction or if it falls into one of > the following categories: > > Cryptography Declaration > Workswith > Exempt Pre-Req > > As a result, this CQ can be closed out. > > Thanks, > Sharon Hi Sharon, By "this CQ can be closed out" do you mean that this bug can be closed? Thanks. Yes Please close out this bug! My brain new what I wanted to say but my fingers are too well trained on CQs:-) (In reply to Sharon Corbett from comment #6) > Yes Please close out this bug! > > My brain new what I wanted to say but my fingers are too well trained on > CQs:-) Ok no problem Sharon, Thanks for the update. |