Thanks for the input Matthias... =>See below
Eric Bresie [email protected] On Wed, Dec 30, 2020 at 3:45 PM Matthias Bläsing <[email protected]> wrote: > Hi, > > Am Mittwoch, den 30.12.2020, 15:31 -0600 schrieb Eric Bresie: > > As I don’t work for Oracle nor did I work on the nbPython work I didn’t > > want to make assumptions on licenses. > > > > I thought I recalled when trying to get the Kolin support brought in, > that > > it required some work from the donator side. If that is not correct then > > we can go ahead and re-license as applicable. > > > > Silly question but which Apache license should these be re-licensed to? > > Oracle formally donated the code. Donation in this case means, that all > copyrights are transfered to the ASF and thus the ASF is free to apply > any license it sees fit. > > At this time the correct license is the Apache License 2.0. The right > header would then be: > > * Licensed to the Apache Software Foundation (ASF) under one > * or more contributor license agreements. See the NOTICE file > * distributed with this work for additional information > * regarding copyright ownership. The ASF licenses this file > * to you under the Apache License, Version 2.0 (the > * "License"); you may not use this file except in compliance > * with the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, > * software distributed under the License is distributed on an > * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > * KIND, either express or implied. See the License for the > * specific language governing permissions and limitations > * under the License. > > This can be found in neary every file on the repository. > > => SO if there are existing licenses from Oracle and/or any others (i.e. JYTHON, nbPython licenses, etc.), these can be stripped and replaced or should the Apache replace the Oracle and any other such licenses left? > The general way (and maybe a reason to redo the PR) is: > > - Get the file(s) oracle donated > => I got most of the files from the hg.netbeans.org repository so assume most of this is good. - Extract the files you want to integrate and document > how it can be verified, that the files came that donated > file > => However there were a few files missing from the hg repository which were available in the "maven-ized" version of the python code base. I've included those as well to get things to compile but not sure if these are "donated" or not. The files in question included (1) a "coverage.py" script for "test coverage" purposes. See https://github.com/nedbat/coveragepy . I think this may be available as some form of node.js type modules so not sure if maybe this could be another type of "external" component to download during prep for the build (2) The package org.netbeans.modules.python.source.scopes related files (3) MiscState and related files How should these be handled? > - Create an orphan branch (a branch without a parent), > add the extracted files to this branch and document > in that file how the files and from where the files > came from > => Silly question, but how do you create a "branch without a parent"? I forked from apache\netbeans -> ebresie\netbeans then created a python (branch) from that with periodic upstream (from apache\netbeans) fetches and merges into my fork and into the branch to try to keep up. > - Do the license clean up > => This is the big part inwork now. I'm trying to use the License Changer Plugin (from 8.2 plugin site - see http://plugins.netbeans.org/plugin/17960/license-changer ) but when attempting after selecting the unpack200.exe (which is apparently no longer available in java 15) and selecting the folder in question in file, during "Preview" pane in the wizard, it keeps showing the Before and After with the After showing "Canceled" without any apparent changes. Tim any ideas on this or any updates on this plugin? > - Make the code compilable (this might mean merging > master into the orphan branch) > => Was made compilable with the added files mentioned above and changes in the build.xml files to the location from contrib to python cluster folder where applicable, and the cluster.properties updates . > - Get approval from PMC for integration of this massive > branch into master > => Assume PR then continue discussion here for that or is there some other process needed? > - Done :-) > > This is the TL;DR version, as you can see with the CND branch, it can > take much time. > > HTH > > Matthias > >
