Wikipedia describes various types and examples of so called [[wikipedia::Direct action|direct action]]. This article talks about a legal struggle of the [[ApacheNetBeans]] project to get an approval to distribute [[GPLwithClassPathException]] licensed component and the [[DirectAction]] used to resolve it.

Wikipedia describes various types and examples of so called [[wikipedia::Direct action|direct action]]. This article talks about a legal struggle of the [[ApacheNetBeans]] project to get an approval to distribute [[GPLwithClassPathException]] licensed component and the [[DirectAction]] used to resolve it.

=== Animosity ===

=== Animosity ===

Wikipedia describes various types and examples of so called [[wikipedia::Direct action|direct action]]. This article talks about a legal struggle of the [[ApacheNetBeans]] project to get an approval to distribute [[GPLwithClassPathException]] licensed component and the [[DirectAction]] used to resolve it.

Wikipedia describes various types and examples of so called [[wikipedia::Direct action|direct action]]. This article talks about a legal struggle of the [[ApacheNetBeans]] project to get an approval to distribute [[GPLwithClassPathException]] licensed component and the [[DirectAction]] used to resolve it.

=== Animosity ===

=== Animosity ===

were not fully implemented. However that is where the difference between ''requirement'' and ''suggestion'' comes into play in my opinion! ''Requirement'' has to be fulfilled, ''suggestion''s are just ''nice to have'' requests that don't have to be followed to the last letter. Understanding the difference between ''formal aspects'' and the ''spirit of the law'' is a necessity for organizing non-violent [[DirectAction]]s!

were not fully implemented. However that is where the difference between ''requirement'' and ''suggestion'' comes into play in my opinion! ''Requirement'' has to be fulfilled, ''suggestion''s are just ''nice to have'' requests that don't have to be followed to the last letter. Understanding the difference between ''formal aspects'' and the ''spirit of the law'' is a necessity for organizing non-violent [[DirectAction]]s!

[[ApacheNetBeans]] PMC had full right to decide to trust the [https://github.com/oracle/nb-javac/blob/fdfb7bd4843cb9e023e14b9c9f11ef838315d480/make/langtools/netbeans/nb-javac/pom-nb-javac.xml#L18 Oracle deeds] regardless of ''nice to have formal'' suggestions not being implemented. The project could have spend years spinning around the ''formal aspects'' without moving forward. Stepping out from that vicious circle, taking [[DirectAction]] and calling for the vote unlocked the situation and allowed the [[ApacheNetBeans]] project to move forward and bundle [[GPLwithClassPathException]] licensed component.

[[ApacheNetBeans]] PMC had full right to decide to trust the [https://github.com/oracle/nb-javac/blob/fdfb7bd4843cb9e023e14b9c9f11ef838315d480/make/langtools/netbeans/nb-javac/pom-nb-javac.xml#L18 Oracle deeds] regardless of ''nice to have formal'' suggestions not being implemented. The project could have spend years spinning around the ''formal aspects'' without moving forward. Stepping out from that vicious circle, taking [[DirectAction]] and calling for the vote unlocked the situation and allowed the [[ApacheNetBeans]] project to move forward and bundle [[GPLwithClassPathException]] [https://search.maven.org/artifact/com.dukescript.nbjavac/nb-javac/15.0.0.2/jar licensed component].

=== Don't Seek for Permission ===

=== Don't Seek for Permission ===

were not fully implemented. However that is where the difference between ''requirement'' and ''suggestion'' comes into play in my opinion! ''Requirement'' has to be fulfilled, ''suggestion''s are just ''nice to have'' requests that don't have to be followed to the last letter. Understanding the difference between ''formal aspects'' and the ''spirit of the law'' is a necessity for organizing non-violent [[DirectAction]]s!

were not fully implemented. However that is where the difference between ''requirement'' and ''suggestion'' comes into play in my opinion! ''Requirement'' has to be fulfilled, ''suggestion''s are just ''nice to have'' requests that don't have to be followed to the last letter. Understanding the difference between ''formal aspects'' and the ''spirit of the law'' is a necessity for organizing non-violent [[DirectAction]]s!

[[ApacheNetBeans]] PMC had full right to decide to trust the [[Oracle]] deeds regardless of ''nice to have formal'' suggestions not being implemented. The project could have spend years spinning around the ''formal aspects'' without moving forward. Stepping out from that vicious circle, taking [[DirectAction]] and calling for the vote unlocked the situation and allowed the [[ApacheNetBeans]] project to move forward and bundle [[GPLwithClassPathException]] licensed component.

[[ApacheNetBeans]] PMC had full right to decide to trust the [https://github.com/oracle/nb-javac/blob/fdfb7bd4843cb9e023e14b9c9f11ef838315d480/make/langtools/netbeans/nb-javac/pom-nb-javac.xml#L18 Oracle deeds] regardless of ''nice to have formal'' suggestions not being implemented. The project could have spend years spinning around the ''formal aspects'' without moving forward. Stepping out from that vicious circle, taking [[DirectAction]] and calling for the vote unlocked the situation and allowed the [[ApacheNetBeans]] project to move forward and bundle [[GPLwithClassPathException]] licensed component.

=== Don't Seek for Permission ===

=== Don't Seek for Permission ===

<blockquote>

<blockquote>

''...PMC should be fully capable of reading and understanding ... the issue seems to be resolved here and it seems that PMC will be following up separately...''

''...PMC should be fully capable of reading and understanding ... the issue seems to be resolved here and ... PMC will be following up separately...''

</blockquote>

</blockquote>

=== Requirement vs. Suggestion ===

=== Requirement vs. Suggestion ===

Of course, [https://lists.apache.org/thread.html/r1ddbb8f62ffb02a50db688c958dcd52e1dd3652974550bad9c24e95d%40%3Cdev.netbeans.apache.org%3E the vote] was not an unisimo vote. Some even tried to call the vote illegal and threaten the remaining voters. True, it wasn't easy to find the four +1 votes. Do you know a programmer who'd vote about legal issues rather than do a bit of coding? Most of us wants to stay away from the legal stuff. However three brave members of the [[ApacheNetBeans]] ''Project Management Committee'' cast their votes, thank you guys! [[I]] added mine (while asking my [[OracleLabs]] co-workers to abstain to not pervert the vote) and that was it.

Of course, [https://lists.apache.org/thread.html/r1ddbb8f62ffb02a50db688c958dcd52e1dd3652974550bad9c24e95d%40%3Cdev.netbeans.apache.org%3E the vote] was not an unisimo vote. Some even tried to call the vote illegal and threaten the remaining voters. True, it wasn't easy to find the four +1 votes. Do you know a programmer who'd vote about legal issues rather than do a bit of coding? Most of us wants to stay away from the legal stuff. However three brave members of the [[ApacheNetBeans]] ''Project Management Committee'' cast their votes (thank you guys!) [[I]] added mine (while asking my [[OracleLabs]] co-workers to abstain to not pervert the vote) and that was it.

It wasn't surprising there were votes against. At the end certain legal suggestions like

It wasn't surprising there were votes against. At the end certain legal suggestions like

</blockquote>

</blockquote>

...into the hands of ''Project Management Committee''. Hearing that the final decision is fully hands of ''PMC'' just called for a [[DirectAction]]!

...into the hands of ''Project Management Committee''. Such setup just called for a [[DirectAction]]!

[[Apache]] foundation ''project management comittees'' have only one decision process: a vote. As such a vote had to be organized! I am thankful that the [https://lists.apache.org/thread.html/r1ddbb8f62ffb02a50db688c958dcd52e1dd3652974550bad9c24e95d%40%3Cdev.netbeans.apache.org%3E community decided in April 2021] that nb-[[javac]] is trusted to be [[GPLwithClassPathException]] licensed with '''4:2''' majority.

[[Apache]] foundation ''project management comittees'' have only one decision process: a vote. As such a vote had to be organized! I am thankful that the [https://lists.apache.org/thread.html/r1ddbb8f62ffb02a50db688c958dcd52e1dd3652974550bad9c24e95d%40%3Cdev.netbeans.apache.org%3E community decided in April 2021] that nb-[[javac]] is trusted to be [[GPLwithClassPathException]] licensed with '''4:2''' majority.

However [[GPLwithClassPathException]] isn't as viral as [[GPL]]. The [[GPLwithClassPathException|Classpath Exception]] allows redistribution of such binaries under any (including [[Apache]]) license. The problem is to get [[Apache]] legal to agree to it! Because as soon as the true [[Apache]]rs see the three [[GPL]] letters, they block and stop reading. As it is very hard to spell [[GPLwithClassPathException]] without spelling [[GPL]] prefix, it is really hard to convince a true [[Apache]]r to read [[GPLwithClassPathException]] fully!

However [[GPLwithClassPathException]] isn't as viral as [[GPL]]. The [[GPLwithClassPathException|Classpath Exception]] allows redistribution of such binaries under any (including [[Apache]]) license. The problem is to get [[Apache]] legal to agree to it! Because as soon as the true [[Apache]]rs see the three [[GPL]] letters, they block and stop reading. As it is very hard to spell [[GPLwithClassPathException]] without spelling [[GPL]] prefix, it is really hard to convince a true [[Apache]]r to read [[GPLwithClassPathException]] fully!

Moreover while [[GPLwithClassPathException]] is quite common among [[Java]] projects, the roots of [[Apache]] foundation are in its HTTP server written in [[C]]. ''Classpath'' has no meaning in the [[C]] language. People with mostly [[C]] skills are going to recognize [[GPL]] in [[GPLwithClassPathException]] rather than the [[GPLwithClassPathException|exception]]! Finally, with [https://issues.apache.org/jira/browse/LEGAL-563 LEGAL-563] things moved forward.

Moreover while [[GPLwithClassPathException]] is quite common among [[Java]] projects, the roots of [[Apache]] foundation are in its HTTP server written in [[C]]. ''Classpath'' has no meaning in the [[C]] language. People with mostly [[C]] skills are going to recognize [[GPL]] in [[GPLwithClassPathException]] rather than the [[GPLwithClassPathException|exception]]!

 

Regardless of that things moved forward with [https://issues.apache.org/jira/browse/LEGAL-563 LEGAL-563].

=== [[DirectAction]]: Organize a Vote! ===

=== [[DirectAction]]: Organize a Vote! ===

However [[GPLwithClassPathException]] isn't as viral as [[GPL]]. The [[GPLwithClassPathException|Classpath Exception]] allows redistribution of such binaries under any (including [[Apache]]) license. The problem is to get [[Apache]] legal to agree to it! Because as soon as the true [[Apache]]rs see the three [[GPL]] letters, they block and stop reading. As it is very hard to spell [[GPLwithClassPathException]] without spelling [[GPL]] prefix, it is really hard to convince a true [[Apache]]r to read [[GPLwithClassPathException]] fully!

However [[GPLwithClassPathException]] isn't as viral as [[GPL]]. The [[GPLwithClassPathException|Classpath Exception]] allows redistribution of such binaries under any (including [[Apache]]) license. The problem is to get [[Apache]] legal to agree to it! Because as soon as the true [[Apache]]rs see the three [[GPL]] letters, they block and stop reading. As it is very hard to spell [[GPLwithClassPathException]] without spelling [[GPL]] prefix, it is really hard to convince a true [[Apache]]r to read [[GPLwithClassPathException]] fully!

Moreover while [[GPLwithClassPathException]] is quite common among [[Java]] projects, the roots of [[Apache]] foundation is its HTTP server written in [[C]]. ''Classpath'' has no meaning in the [[C]] language. People with mostly [[C]] skills are going to recognize [[GPL]] in [[GPLwithClassPathException]] rather than the [[GPLwithClassPathException|exception]]! Finally, with [https://issues.apache.org/jira/browse/LEGAL-563 LEGAL-563] things moved forward.

Moreover while [[GPLwithClassPathException]] is quite common among [[Java]] projects, the roots of [[Apache]] foundation are in its HTTP server written in [[C]]. ''Classpath'' has no meaning in the [[C]] language. People with mostly [[C]] skills are going to recognize [[GPL]] in [[GPLwithClassPathException]] rather than the [[GPLwithClassPathException|exception]]! Finally, with [https://issues.apache.org/jira/browse/LEGAL-563 LEGAL-563] things moved forward.

=== [[DirectAction]]: Organize a Vote! ===

=== [[DirectAction]]: Organize a Vote! ===

=== [[GPLwithClassPathException]] isn't [[GPL]] ===

=== [[GPLwithClassPathException]] isn't [[GPL]] ===

However [[GPLwithClassPathException]] isn't as viral as [[GPL]]. The [[GPLwithClassPathException|Classpath Exception]] allows redistribution of such binaries under any (including [[Apache]]) license. The problem is to get [[Apache]] legal to agree to it! Because as soon as the true [[Apache]]rs see three [[GPL]] letters, they block and stop reading. As it is very hard to spell [[GPLwithClassPathException]] without spelling [[GPL]] prefix, it is really hard to convince a true [[Apache]]r to read [[GPLwithClassPathException]] fully!

However [[GPLwithClassPathException]] isn't as viral as [[GPL]]. The [[GPLwithClassPathException|Classpath Exception]] allows redistribution of such binaries under any (including [[Apache]]) license. The problem is to get [[Apache]] legal to agree to it! Because as soon as the true [[Apache]]rs see the three [[GPL]] letters, they block and stop reading. As it is very hard to spell [[GPLwithClassPathException]] without spelling [[GPL]] prefix, it is really hard to convince a true [[Apache]]r to read [[GPLwithClassPathException]] fully!

Moreover while [[GPLwithClassPathException]] is quite common among [[Java]] projects, the roots of [[Apache]] foundation is its HTTP server written in [[C]]. ''Classpath'' has no meaning in the [[C]] language. People with mostly [[C]] skills are going to recognize [[GPL]] in [[GPLwithClassPathException]] rather than the [[GPLwithClassPathException|exception]]! Finally, with [https://issues.apache.org/jira/browse/LEGAL-563 LEGAL-563] things moved forward.

Moreover while [[GPLwithClassPathException]] is quite common among [[Java]] projects, the roots of [[Apache]] foundation is its HTTP server written in [[C]]. ''Classpath'' has no meaning in the [[C]] language. People with mostly [[C]] skills are going to recognize [[GPL]] in [[GPLwithClassPathException]] rather than the [[GPLwithClassPathException|exception]]! Finally, with [https://issues.apache.org/jira/browse/LEGAL-563 LEGAL-563] things moved forward.