New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/pkgsite: How to allow my packages to be on pkg.go.dev #43356
Comments
It seems like the intent for both of those modules is to have an MIT license: Per https://pkg.go.dev/license-policy:
The text we use for the MIT license is at https://opensource.org/licenses/MIT. Since April, we have also open sourced our codebase. You can also run our code for license detection. See here for an example. /cc @jba |
No, the intent is not an MIT license. It's a derivative of a MIT license. |
Why a derivative? That makes it much harder for projects/software like pkgsite to know that it's actually open source. I assume it means a human lawyer would have to manually read and evaluate the license, which does not scale if thousands of Go modules required that kind of work. |
No! Firstly, Google clearly doesn't really care since they are already displaying exotically licensed documentation in godoc.org and have been for 5+ years. If they were genuinely concerned about any legal ramifications, they would have pulled down certain godoc pages years ago. Secondly, as an ex-lawyer myself, I suspect the pkg.go.dev team received faulty legal advice. I can't imagine that a talented in-house lawyer was consulted on this issue and/or they were not properly explained the scenario to give quality legal advice. I'm sure Google's elite lawyers are working on far more important matters. Finally, as explained in the email to @jba, I mentioned that all that is required (if google is risk adverse), is some key phrase to be inserted into the license that permits pkg.go.dev to display it. Alternatively, a special I mentioned this way back in April 2020 in my email. Alternatively an authorization portal can be created where the maintainer can authorize google to display the documentation. Now in a few weeks time, my documentation for some key packages in the Go eco-system are going to go invisible. |
Please be nice. Otherwise there's no point in raising issues or trying to find a solution.
I believe this is part of why godoc.org needs to be taken down in favor of pkg.go.dev - because the older site did not do a good job at only showing/redistributing code which it was allowed to. But don't quote me on this, as I'm not an expert. Lastly, you make some suggestions to possibly fix this problem, so I think we should wait until the maintainers are back and can comment on those. I imagine most people will be back in a week's time. |
Sorry, your license was approved some time ago but we never followed up. Your packages should appear shortly after our next release, in early January. Please list the modules with this license so we can reprocess them. |
github.com/rocketlaunchr/* |
These should be OK now. Let me know if I missed something. |
Rocketlaunchr/dbq doesn't show docs (for version 2) |
OK, just re-fetched it. Wait 10 minutes for it to time out of cache. I thought I had done it before and checked it...let's keep an eye on it to make sure it sticks. |
Thanks @jba for your assistance! |
Why was v2 of dbq treated differently from v1? if I create a v3, would that suffer from the same issue? |
I had to manually reprocess each module to replace its entry in our database. The puzzling thing is that the reprocess command for v2 was in my shell history... New modules (and new versions of old modules) will be processed as they arrive and should be fine. |
I have numerous packages such as: https://godoc.org/github.com/rocketlaunchr/dataframe-go & https://godoc.org/github.com/rocketlaunchr/dbq/v2 (and many more).
Since these packages have eccentric licenses, pkg.go.dev is not listing them.
On 13th of April, I sent an email to go-discovery-feedback@google.com explaining my situation.
On 14th of April, I got a response from
@jba
who said google will add my documentation to pkg.go.dev. I think he also mentioned they are building a site for people to authorize Google to display the documentation if they have non-standard licenses.I am not sure what is happening with the authorization process. At the moment my package documentation is still invisible.
The text was updated successfully, but these errors were encountered: