Conversation
typst-package-check
bot
changed the title
| @@ -0,0 +1,17 @@ | |||
| [package] | |||
| name = "sorbonne-presentation" | |||
There was a problem hiding this comment.
Because this is not an official package of the University, can you pick another name please? It should be distinctive enough so that another package with the same purpose can be published without one of the two having an unfair advantage, and it should be clear from the name that it is community-built and not officially endorsed by the university.
If you want to make this template official to keep the current name, that's also an option. In that case a member of the University staff should send an email to hello@typst.app stating that they officially endorse your package. In practice it means that they will accept submission of works built using it, and ideally promote it and guarantee that it will be maintained on the long term.
|
|
||
| ## License | ||
|
|
||
| MIT License. See [LICENSE](LICENSE) for details. |
There was a problem hiding this comment.
I can imagine that the various Sorbonne logos that you ship with this template are not under the MIT license. Can you please specify under which terms/license they can be distributed and used?
There was a problem hiding this comment.
Thanks for your feedback! I’ll check whether it’s possible to make this template official. If that’s not feasible, I’ll choose a new name and release the package without the Sorbonne logos. I really appreciate your guidance on this and want to make sure the package can be used smoothly by the community.
There was a problem hiding this comment.
Hi @elegaanz,
I'm going to close this PR and create a new one with a new name and fake logos.
Thanks for your advices.
2 participants
I am submitting
Description: A presentation template based on packages presentate and navigator.
I have read and followed the submission guidelines and, in particular, I
selected a name that isn't the most obvious or canonical name for what the package does
added a
typst.tomlfile with all required keysadded a
README.mdwith documentation for my packagehave chosen a license and added a
LICENSEfile or linked one in myREADME.mdtested my package locally on my system and it worked
excluded PDFs or README images, if any, but not the LICENSEensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.