Re: How to contribute

2023-06-04 Thread Ralph Corderoy
Hi Michał, > > > > Alas, groff's requirement for copyright assignment to the FSF > > > > ruled out contributions from me many years ago after the FSF's > > > > legal counsel confirmed they'd hold partial copyright on a > > > > non-groff work which contained code of copyrightable expression > > > >

Re: How to contribute

2023-06-03 Thread G. Branden Robinson
[self-follow-up] At 2023-06-03T09:47:13-0500, G. Branden Robinson wrote: > On the other hand, many years ago when I stopped merely listening to > what everybody said about the FSF, and started digging into the > copyright details of various GNU packages, I found more flexibility > there than I had

Re: How to contribute

2023-06-03 Thread G. Branden Robinson
At 2023-06-03T16:00:55+, Michał Kruszewski wrote: > By patches you mean `git diff` output? That should work fine. Regards, Branden signature.asc Description: PGP signature

Re: How to contribute

2023-06-03 Thread Michał Kruszewski
Ced.) > > Let me offer you some perspectives from someone who does contribute to > groff, to contrast with quick responses from someone who's sworn not to. > > At 2023-06-03T10:25:16+, Michał Kruszewski via wrote: > > > Is there any tutorial on how to contribute to

Re: How to contribute

2023-06-03 Thread G. Branden Robinson
any tutorial on how to contribute to the groff? The source distribution contains some files along these lines (or it does as of recent 1.23.0 release candidates). I'd start with "HACKING". https://git.savannah.gnu.org/cgit/groff.git/tree/HACKING > The https://www.gnu.org/so

Re: How to contribute

2023-06-03 Thread Michał Kruszewski
I do not believe it works this way. It would be extremely stupid. I can image this applies when you copy large amount of code, but single 25 lines function? No one would contribute to GNU projects if it worked like this. Best regards, Michał Kruszewski Sent with Proton Mail secure email. ---

Re: How to contribute

2023-06-03 Thread Ralph Corderoy
Hi Michał, > Alas, groff's requirement for copyright assignment to the FSF ruled > out contributions from me many years ago after the FSF's legal > counsel confirmed they'd hold partial copyright on a non-groff work > which contained code of copyrightable expression if I later used

Re: How to contribute

2023-06-03 Thread Michał Kruszewski
Alas, groff's requirement for copyright assignment to the FSF ruled out contributions from me many years ago after the FSF's legal counsel confirmed they'd hold partial copyright on a non-groff work which contained code of copyrightable expression if I later used it in groff; th

Re: How to contribute

2023-06-03 Thread Ralph Corderoy
Hi Michał, > Where do I need to register? For any significant contribution in copyright terms, you'll have to sign an assignment of copyright of your work to the FSF and it's GNU groff. https://www.fsf.org/licensing/contributor-faq That put me off. Alas, groff's requirement for copyrig

How to contribute

2023-06-03 Thread Michał Kruszewski via
Is there any tutorial on how to contribute to the groff? The https://www.gnu.org/software/groff/ website is rather modest in this term. Where do I need to register? How to prepare pull requests? Best regards, Michał Kruszewski Sent with [Proton Mail](https://proton.me/) secure email.