On Mon, Oct 31, 2016 at 3:27 PM, Dave Cridland <[email protected]> wrote: > But note that there's a horrible grey area we might want to get the > next Board to look into in cases like this, when there's a protoXEP > being (effectively) worked on within the XSF repository. The original > XEP was rejected on the grounds of - as I recall - IPR issues. But > these having been resolved, further work is now not yet owned by the > XSF, so licensing is very unclear, and becomes less clear with each > edit. > > I don't know what Board might do here; it might be that Council are > advised to lean toward accepting more XEPs in order to avoid IPR > issues even when there's a strong feeling that the work should > progress no further, or it might be that we move the assignment to the > point of submission rather than the point of acceptance (ie, a change > to XEP-0001). Or something else.
This is interesting, and not something I'd thought about when merging the OMEMO changes. I have however thought a bit about the copyright / author release issues with regards to editor workload (it's a real pain sending emails for every submission). I wonder if we could kill two birds with one stone by having copyright assignment hadled by a bot at PR time or when the author emails a protoxep (or any changes) to the editors list for the first time? This would also mean we'd only have to get a copyright release once (just like how companies make contributors sign a CLA once). The first time a GitHub username submits a PR, or the first time an email is sent to editor@ containing an attatched XEP we could have a bot record the person, reply to the email or comment on the PR, and ask them to log in and digitally sign the release. Then post back on the PR (or email) when they'd done so at which point an editor would merge it. Would this solve the issues in the case of protoXEPs too (because the bot would have checked to make sure Daniel had signed his submissions away)? —Sam -- Sam Whited pub 4096R/54083AE104EA7AD3 _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
