|
|
| Line 1: |
Line 1: |
| − | More stuff you wanted to know about IP but were afraid to ask.
| + | #REDIRECT [https://www.eclipse.org/projects/handbook#ip] |
| − | | + | |
| − | <!-- Editors: We use =...= syntax so that other pages can link directly to the question -->
| + | |
| − | | + | |
| − | =What does the IP Team look for when reviewing code attached to CQs? =
| + | |
| − | | + | |
| − | In addition to amusing comments from the authors of the code, we look for [http://wiki.eclipse.org/images/a/ae/Eclipse_Provenance_and_Licensing_Considerations_v1.2.pdf these kinds of things.]
| + | |
| − | | + | |
| − | | + | |
| − | =Why are committers asked to enter one CQ per jar file?=
| + | |
| − | | + | |
| − | Using examples, a long-winded [http://wiki.eclipse.org/images/c/c6/Why_One_CQ_per_Jar_File.pdf answer] to that age-old question.
| + | |
| − | | + | |
| − | | + | |
| − | =To enter a CQ for third party package, or not to enter one.........''that'' is the question.=
| + | |
| − | | + | |
| − | Maybe a handy [http://wiki.eclipse.org/images/6/60/Third_party_package_requirement.pdf flowchart] will help (we like flowcharts :-)).
| + | |
| − | | + | |
| − | | + | |
| − | =What does the IP Team look for when reviewing the IP log?=
| + | |
| − | Q: My project is going to Move or Graduate. I know it's recommended that I create an automated IP log from [http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log here], or if for some funky reason that isn't working, I can create it manually based on this [http://www.eclipse.org/projects/dev_process/project-log.php template]. But what does the IP Team look for when reviewing the IP log?===
| + | |
| − | | + | |
| − | Well, we look at a few things so it may be a good idea to parse it out.
| + | |
| − | | + | |
| − | # We check your committer list to make sure it matches what we have in our database. | + | |
| − | # The contribution section to should uniquely identify the component (CVS directory), bug # (description if there is no bug # or if there are multiple bug #s), contributor's name, contribution size (LOC), committer who committed this contribution.
| + | |
| − | # In the third party software section, we look for CQ numbers, package names and associated licenses. Then we check to make sure that all the CQs listed for the move / graduation have been resolved and fixed as approved. We sometimes end up having quite a bit of feedback with projects on this section, so we've put together another handy [http://wiki.eclipse.org/images/5/57/Project_Graduation_or_Move_v5F.pdf flowchart] that addresses the most common scenarios.
| + | |
| − | | + | |
| − | =Where is the IP Team Work Queue?=
| + | |
| − | | + | |
| − | Committers may view the IP Team's work queue by clicking "[https://dev.eclipse.org/ipzilla/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=IP%20Team%20Work%20Queue&sharer_id=854 IP Team Work Queue]" at the bottom of any [https://dev.eclipse.org/ipzilla/ IPZilla page]. To access the IP Team's work queue requires Committer status. If you are logged in to IPZilla and "IP Team Work Queue" is not visible, then see this [https://dev.eclipse.org/mhonarc/lists/incubation/msg00056.html March, 2016 incubation email message].
| + | |
