G'day folks,
Chiming in here as I've been slack responding to the Github issues:
PyHSS project started off as a little side project when experimenting with
IMS and I never expected it to gain the traction it has, and it's great to
see more folks using it!
Full credit to Dave who has done a fantastic job in evolving PyHSS into
something production ready, and we're in the process of adding support for
the full M3UA/TCAP/MAP stack to allow PyHSS to function as an HLR, of
course GSUP support would be welcome.
The code has always been intended to be open source, hence being public on
Github from the start, but I've never really done my homework on the most
appropriate license for the code. I'll work out what license suits best and
update the Github accordingly, so everyone can submit PRs.
Cheers,
Nick
On Mon, 25 Mar 2024 at 08:24, Keith <keith(a)rhizomatica.org> wrote:
Sounds bizarre.
I really don't know anything about it, but I do remember a call with nick
[at]
nickvsnetworking.com some years back and everything about that
conversation was reasonable.
Isn't it simply a case of reaching out and asking for the license terms to
be clarified, I'd be surprised if the response were to be silence or even
negative.
(OK I really must learn to stop being surprised by what I'm surprised
about, they way the world is.)
Is this simply some situation where Nick has not understood the conundrum
in which the German law-abiding citizen is placed due to a lack of explicit
statement of licensing terms?
Also, (and here I thought I understood correctly), but you may know
better; Github's terms of service:
5. License Grant to Other Users
<https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#5-license-grant-to-other-users>
Any User-Generated Content you post publicly, including issues, comments,
and contributions to other Users' repositories, may be viewed by others. By
setting your repositories to be viewed publicly, you agree to allow others
to view and "fork" your repositories (this means that others may make their
own copies of Content from your repositories in repositories they control).
If you set your pages and repositories to be viewed publicly, you grant
each User of GitHub a nonexclusive, worldwide license to use, display, and
perform Your Content through the GitHub Service and to reproduce Your
Content solely on GitHub as permitted through GitHub's functionality (for
example, through forking). You may grant further rights if you adopt a
license
<https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository#including-an-open-source-license-in-your-repository>.
If you are uploading Content you did not create or own, you are responsible
for ensuring that the Content you upload is licensed under terms that grant
these permissions to other GitHub Users.
Are German user's of Github somehow excluded from this global right to
fork?
I know Mexico updated copyright law over the last few years, but maybe
this implicit exclusive copyright if not claimed is not the same here, I
could ask.. but I think best to reach out, no?
k/