What are you working on in this week of October?
by Alex Bradbury
It's a new month, so I figured we should make a new thread rather than
just replying to the old one.
What are you working on this week?
The funding application I was working on last week has ended up taking
an awful lot of time, and I still need to produce a short pitch video.
I think it has been useful in general though, giving me more time to
take a step back and think about the things I'd really like to see
lowRISC CIC achieve over the coming year and beyond.
I'm off to Bologna for ORConf <http://orconf.org/> on Thursday. I
imagine I'll spend a good chunk of Tuesday preparing and polishing my
talk. Otherwise:
1) I've been playing with Sagar's latest qemu-riscv work over the weekend
2) Wei's made great progress on his tagged memory software model, and
I hope to play a small supporting role by helping out with supplying
benchmarks and fiddly test cases
3) Continued riscv-llvm work
Best,
Alex
6 years, 4 months
A prelude to a GitHub vs self-hosted discussion - who owns your bug reports and code reviews?
by Alex Bradbury
Hi all,
I was going to put out a request for comments to collect views about
where lowRISC is best using GitHub vs other tools (e.g. open source
and self-hosted like Phabricator). However, a legal question came to
mind that rather pre-empts the whole thing. I'm not exactly asking a
technical list for legal advice - it just this feels like a discussion
that must have come up before in other communities, so any pointers to
relevant conclusions elsewhere would be very much appreciated.
Let's say a project is hosted on GitHub. It makes extensive use of
code review and the bug tracker, and would actually see huge value in
the information accumulated there. i.e. if the project were to move
from GitHub, losing this history would be seen as a big loss. What
rights do you have to transfer data from a service like GitHub? The
ToS make it crystal clear that GitHub take no claim in the 'material'
uploaded to the service
<https://help.github.com/articles/github-terms-of-service/>, though by
posting publicly you you agree to allow others to view your content.
This leads to the crux of the question:
If every participant in bug reports or code reviews holds the
copyright to their contribution and has entered no explicit licensing
arrangement with the project, does the project actually have the right
to move the bug/review database to another service?
As a followup to the above, is the situation at all different
depending on whether the submission was to a project hosted on GitHub
or a site operated by the project?
It was interesting reviewing ToS from various projects and tools. I
expected a lot of them to have a clause like Reddit's:
https://www.reddit.com/help/useragreement
"""
By submitting user content to reddit, you grant us a royalty-free,
perpetual, irrevocable, non-exclusive, unrestricted, worldwide license
to reproduce, prepare derivative works, distribute copies, perform, or
publicly display your user content in any medium and for any purpose,
including commercial purposes, and to authorize others to do so.
"""
# Mini-survey
The summary is that by my reading (I'm not a lawyer, so this reading
is likely flawed), of the major code hosting sites, only Bitbucket and
SourceForge have a clause in their ToS explicitly giving a
non-exclusive license for use of submitted content like bug reports.
In both cases, this license is for the host rather than the project
the submission was made to. When it comes to large projects, Python
and perhaps Mozilla seem to have terms that explicitly cover user
submissions while LLVM, FreeBSD, and Debian seem to have no notice I
could spot.
## Bitbucket
https://www.atlassian.com/legal/customer-agreement
"""
Subject to the terms of this Agreement, you hereby grant to Atlassian
a non-exclusive, worldwide, royalty-free right to (a) collect, use,
copy, store, transmit, modify and create derivative works of Your
Data, in each case solely to the extent necessary to provide the
applicable Hosted Service to you ....
"""
## GitLab
https://about.gitlab.com/terms/
"We do not claim any ownership rights to the information that you
submit to the GitLab application itself, your code is yours. "
## GitHub
https://help.github.com/articles/github-terms-of-service/
"""
We claim no intellectual property rights over the material you provide
to the Service. Your profile and materials uploaded remain yours.
However, by setting your pages to be viewed publicly, you agree to
allow others to view your Content. ...
"""
## Launchpad
https://help.launchpad.net/TermsofUse
"""
All bug comments are the property of the people who created them.
Metadata and statistics generated by the Launchpad Bug Tracker are the
property of Canonical Ltd and may be used freely for any purpose as
long as accreditation and the Launchpad URL are given along with that
data.
"""
## Sourceforge
https://slashdotmedia.com/terms-of-use/
"""
With respect to text or data entered into and stored by
publicly-accessible site features such as forums, comments and bug
trackers (“Slashdot Media Public Content”), the submitting user
retains ownership of such Slashdot Media Public Content; with respect
to publicly-available statistical content which is generated by the
sites to monitor and display content activity, such content is owned
by Slashdot Media. In each such case, the submitting user grants
SlashDot Media a royalty-free, perpetual, irrevocable, non-exclusive,
transferable license to use, reproduce, modify, adapt, publish,
translate, create derivative works from, distribute, perform, and
display such Content (in whole or part) worldwide and/or to
incorporate it in other works in any form, media, or technology now
known or later developed, all subject to the terms of any applicable
license.
"""
## Mozilla terms of use (covering their bugzilla)
https://www.mozilla.org/en-US/about/legal/terms/mozilla/
See section 4. content submissions. It's unclear to me whether a bug
report is a "submission to Mozilla's open source projects"
## Python legal statements (covering the Python bug tracker)
https://www.python.org/about/legal/
"""
The Python Software Foundation (“PSF”) does not claim ownership of any
third-party code or content (“third party content”) placed on the web
site and has no obligation of any kind with respect to such third
party content. Any third party content provided in connection with
this web site is provided on a non-confidential basis. The PSF is free
to use or disseminate such content on an unrestricted basis for any
purpose, and third party content providers grant the PSF and all other
users of the web site an irrevocable, worldwide, royalty-free,
nonexclusive license to reproduce, distribute, transmit, display,
perform, and publish such content, including in digital form.
"""
## LLVM bugzilla
https://llvm.org/bugs/
No legal notice / terms of service that I could see
## LLVM Phabricator (code review)
http://reviews.llvm.org/
No legal notice / terms of service that I could see
## Debian bug tracker
https://www.debian.org/Bugs/
Not clear to me what, if any terms of service it is governed by.
## FreeBSD bug tracker
https://bugs.freebsd.org/bugzilla/
No legal notice / terms of service that I could see
6 years, 5 months