On Thu, 21 May 2026 at 18:11, Guus der Kinderen <guus.der.kinderen(a)gmail.com>
wrote:
- *IP & Asset Transfer Feasibility* - looks at how easily intellectual
property, trademarks, and other assets can be transferred to or managed
within the proposed structure
Very specifically on these, I think it would be useful to classify the IPR
and related assets that the existing XSF has. My non-exhaustive guesswork
gives me:
* Copyright ownership of the XEPs
* Copyright ownership of the website and other assets
* Trademark licences (I think the XSF has a trademark licence for Jabber,
though I can't find it)
* Trademark sublicensor:
https://xmpp.org/about/xsf/jabber-trademark/
Of these, I think Copyright can be transferred in the XEPs in the same way
it's been transferred into the XSF; that is by the New XSF promising to
make the specifications available to developers etc. That would form a
consideration in a contract, and I believe that's sufficient to easily
reassign the copyright.
The copyright on the website is both harder and also less important; we
might choose to licence rather than reassign. The current website seems to
have no copyright imprimatur on it, and the repository has no licence.
Might be worth doing something about both...? It's harder because there's
no obvious consideration to use here - we couldn't have the New XSF promise
to publish the website (that would be weird). It's less important because a
licence will work just as well for our purposes, and licences are legally
simpler.
The trademark issues I don't know anything about; it's not an area of law
I've ever had to tangle with. I wonder if the simplest solution would be to
keep the Old XSF as a stub organisation holding just the trademark bits
until we figure that out?
Dave.