Add a @copying section #4

aitap commented 2024年08月29日 13:15:15 +02:00

Dear @eshom,

What do you think of this @copying section?

I think it's important for such a document to both permit share-alike redistribution (the Latex2e-translated-notice permissions are similar but not identical to those from the R manuals) and to acknowledge the contributors. I'm not sure what's the right way to do that, but it shouldn't be too wrong to follow the example from the R manuals, right?

Dear @eshom, What do you think of this `@copying` section? I think it's important for such a document to both permit share-alike redistribution (the [Latex2e-translated-notice](https://spdx.org/licenses/Latex2e-translated-notice.html) permissions are similar but not identical to those from the R manuals) and to acknowledge the contributors. I'm not sure what's the right way to do that, but it shouldn't be too wrong to follow the example from the R manuals, right?

eshom commented 2024年08月30日 12:07:41 +02:00

I think it's good to have this. Might also be legally necessary. Following R manual examples is seems fine. Maybe even mandatory due to paragraph 2.

What do you think about @insertcopying? I don't mind either way, but R manuals have it, even though legally it is not required.

Disclaimer: I'm not a lawyer :-)

I think it's good to have this. Might also be legally necessary. Following R manual examples is seems fine. Maybe even mandatory due to paragraph 2. What do you think about `@insertcopying`? I don't mind either way, but R manuals have it, even though [legally it is not required](https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#g_t_0040insertcopying). Disclaimer: I'm not a lawyer :-)

eshom commented 2024年08月30日 12:35:21 +02:00

Regarding the PR, I keep funVersions branch ahead of trunk by rebasing it before I do any local change. I suggest to do the same (but rebase in relation to funVersions) before attempting to merge.

Edit: I forced push to funVersions to include the latest trunk commit 49b6abc .
Edit2: I learned after the fact --update-refs option exists for this use case. Sorry about that.

Regarding the PR, I keep `funVersions` branch ahead of `trunk` by rebasing it before I do any local change. I suggest to do the same (but rebase in relation to `funVersions`) before attempting to merge. Edit: I forced push to `funVersions` to include the latest trunk commit 49b6abc . Edit2: I learned after the fact `--update-refs` option exists for this use case. Sorry about that.

aitap commented 2024年08月31日 13:27:44 +02:00

Thank you for fixing the missing {}! Don't worry about force-pushing your branch. I think that --update-refs would have had to rewrite history and result in a force-push anyway.

Thank you for fixing the missing `{}`! Don't worry about force-pushing your branch. I think that `--update-refs` would have had to rewrite history and result in a force-push anyway.