From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Writer's Workbench (was: troff refer and bib)
Date: Fri, 9 Apr 2021 22:17:15 +0000 (UTC) [thread overview]
Message-ID: <9ea5f72a-c675-4604-87d9-c77070a08204@sirjofri.de> (raw)
In-Reply-To: <53063C17-F98B-4771-B219-90DDD9747B6F@gmail.com>
09.04.2021 23:45:47 Xiao-Yong Jin <meta.jxy@gmail.com>:
>> On Apr 9, 2021, at 12:57 PM, sirjofri <sirjofri+ml-9fans@sirjofri.de>
>> wrote:
>>
>> Writer's Workbench
>>
>> https://git.sr.ht/~sirjofri/wwb9
>>
>> (Works on 9, but I need to make it better for different platforms and
>> some tools need adjustments. Send patches.)
>
> What exactly is the license? Even just reading code of unclear license
> could get many people in trouble.
TL;DR: "non-commercial
copying, distribution, performance, display or creation of derivative
works" is allowed.
Sadly the license is not open-source! That's why I added the note and
didn't change much, especially not the license notes. I also didn't add
license information on purpose, so people like you will have to ask and
search for more info.
See this document for more info about why I felt free to port it:
https://www.tuhs.org/Archive/Distributions/Research/Norman_v9/statement_regarding_Unix_3-7-17.pdf
"will not assert its copyright rights with respect to any non-commercial
copying, distribution, performance, display or creation of derivative
works"
If I understand that correctly I should be fine and the distribution of
the port is legal under the mentioned terms, but of course I cannot
simply change the license. It is _not_ my code nor my software, I just
made it work on 9 and added some rc files. My additions can be considered
as open source, but I'm not sure if I can just state that in the repo.
I should add some notes about the original source and the statement, I
think.
I hope this helps. I don't think I can help more than that, and Ianal. If
you need help with the software you can ask, of course.
When testing, I should mention it works on 9front. I didn't test it on
any other fork, but I see no reason why it wouldn't work.
sirjofri
Btw I'd love to release it under an open source license, if I can. These
tools are old, but still helpful and can be used in comparison with
modern tools, maybe even in combination and for developing better tools
in the future.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tcc892c7fea37e56a-M5d7af59ee15eee78fce1bcbd
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-04-09 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 10:57 [9fans] troff refer and bib Maurizio Boriani
2021-04-08 11:27 ` sirjofri
2021-04-09 14:39 ` Charles Forsyth
2021-04-09 15:41 ` Maurizio Boriani
2021-04-09 16:04 ` sirjofri
2021-04-09 16:18 ` Maurizio Boriani
2021-04-09 16:25 ` David du Colombier
2021-04-09 17:57 ` sirjofri
2021-04-09 21:45 ` Xiao-Yong Jin
2021-04-09 22:17 ` sirjofri [this message]
2021-04-09 19:51 ` Charles Forsyth
2021-04-09 20:37 ` sirjofri
2021-04-08 11:45 ` arnold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ea5f72a-c675-4604-87d9-c77070a08204@sirjofri.de \
--to=sirjofri+ml-9fans@sirjofri.de \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).