Create an IPLab template for project code contributions
As part of migrating off of IPZilla, we need a means of requesting a review of project code. Using issues is the obvious choice; setting up a template will make it easier to consistently capture information and apply automation.
What do we need to capture?
- The Project Id
- Link to the source code
- Identity of copyright holders
- License (as understood by the submitting committer)
- Cryptography (yes/no)
What am I missing?
The existing "CQ" form also asks for a "reason"; is there actual value that we derive from this?
Note that, unlike what we do with IPZilla, we're not going to require that source code be uploaded as an attachment. Ideally, we need a point to a relatively static snapshot for the source in some kind of archive format. I believe that we'll also have to be able to handle a pointer to a specific commit in a public Git repository, or a merge/pull request.
What we won't be able to handle is a project code contribution that originates in a private repository (e.g., behind a corporate firewall) with no public links that we can follow. Strictly speaking, this is not a new requirement, but we've certainly relaxed it over the years. This may be especially challenging for initial contributions coming from projects that are not currently working in public repositories (project code contribution to an existing project that originate from a private repository can be delivered via pull/merge requests).
We can leverage tags to mark an initial contribution
(identifying the initial contribution is handy for gathering statistics). I'm hopeful that we can use a single template to capture information for initial contributions and other project code contributions. If we determine that separate templates are required, we can entertain that (a single template should theoretically be easier to maintain).
We should also capture "what's next" instructors for after the review is complete. We should, for example, provide a link to create a helpdesk request to move a repository under management of the IT Team. Note that the next steps may depend on the nature of the contribution (e.g., a pull request does not require any assistance from the IT Team).