An issue came up on the Apache Legal bug tracker that has a similar situation to ours.
https://issues.apache.org/jira/browse/LEGAL-339 Apache Heron is in a similar stage to us in incubation. They are working to transition over to the ASF infrastructure. Their original code is under a permissive license (Apache v2), but they do not have SGAs in place yet, and they wanted to know if they could import their code to ASF. The result of the issue is that since the code is under a permissive license, it is okay to import the code to the ASF git, and just not change any license headers yet. Once the remaining SGAs are in place we can change the headers. We can even do releases, but it will prevent graduation, but I suspect we'll have SGAs in place before our first ASF release. Related, I was thinking that if we were to do it, now would be a good time to rename all the old branches and tags to use the new Branch & Tag workflow [1] so that all future tags/branch are consistent with the old. This would just mean that all rc/alpha tags would have a 'v' prepended (e.g. 1.0.0-rc1 -> v1.0.0-rc1), all other tags have 'rel/v' (e.g. 1.0.0 -> rel/v1.0.0), and all branches have a 'support/v' prepended and the last digit becomes an 'x' (e.g 1.0.0 -> support/v1.0.x). This won't change what the tags/branches point to, just changes their names. Since this would mean the tags change (which git tends to avoid), this will mean that we should all clone the new repo and work out of that, no longer using our old clones. This will ensure no old tags stick around. For any ongoing work, something like git format-patch would be a good method to get the changes to the new repo. Any thoughts/concerns with this? - Steve [1] https://cwiki.apache.org/confluence/display/DAFFODIL/Branch+and+Tag+Workflow
