Provide a few bits of information that will help us
to categorize the package
Name of your contribution
This value corresponds to the name of the package in the
Te X Catalogue. It must consist of ASCII characters only.
It should start with a letter and may contain only letters, digits or
a minus sign.
Version
Specify a meaningful version like 1.2 or 2.3.4.
A release date in the form YYYY-MM-DD can be used as a fall-back in
case you do not have a proper version number. Please consider
Semantic Versioning as widely used in
software engineering.
Maintainer
These are the names of the authors or maintainers.
These names will be published with the package. Several names
are separated by a semicolon (;).
Your name
Your name in case you are uploading a package on behalf
of someone else. Note that the CTAN team checks that you are entitled
to upload the package.
Your email
This email address will not be published. It is meant
for contacting you in case of questions.
Summary
A short one line summary of what the package does. It is
typically just a few words, or at most a sentence.
Description
This is the description of the package as published
with the package description on the CTAN package page.
Suggested CTAN directory
Your suggested CTAN directory is a help (if you are not sure, just
make a guess). You can browse
here . The selected path must start with one of the existing
directories.
Announcement via mailing list and RSS
(features, changes,...)
This text is published for a new package or if an
announcement is requested for an existing package.
Please write in English.
In case of an update you can leave this field empty.
Then no announcement will be published.
About the announcements: we have a mailing list for
people who are interested in hearing about changes in our holdings.
New packages are always announced on this list. For a revision of an
existing package, please note that we don't mail the list about
revisions that are bug fixes, minor feature additions, etc. If you
make a major upgrade and would like an announcement then tell us so,
and include a description of the improvements.
Administrative notes (to the CTAN maintainers)
This text is for internal communication only. It will
not be visible publicly. Please write in English.
Indicate the licenses
We need to know the licenses under which you are sharing your work.
For more information about the different kinds, see the Catalogue License Definitions .
If you don't know what to pick, you might note that the La Te X Project Public
License 1.3c was developed to suit this purpose.
Several licenses can be given. This applies for instance if
parts of the package are distributed under different licenses or the
package is dual licensed under more than one license.
License type
Apache License, version 2.0
Perl Artistic License, version 2
BSD Style License
Simplified BSD License
3-clause BSD License
BSD License
CC BY 1.0
CC BY 2.0
CC BY 3.0
CC BY 4.0
CC BY-SA 1.0
CC BY-SA 2.0
CC BY-SA 3.0
CC BY-SA 4.0
CC0 1.0
European Union Public License 1.2
Free Documentation License
The GUST Font License (GFL)
The GUST Font Source License (GFSL)
GNU General Public License
GNU General Public License, version 1
GNU General Public License, version 1 or newer
GNU General Public License, version 2
GNU General Public License, version 2 or newer
GNU General Public License, version 3
GNU General Public License, version 3 or newer
ISC License
Knuth License
GNU Lesser General Public License
GNU Lesser General Public License 2.1
GNU Lesser General Public License 3
The LaTeX Project Public License
The LaTeX Project Public License 1
The LaTeX Project Public License 1.2
The LaTeX Project Public License 1.3
The LaTeX Project Public License 1.3a
The LaTeX Project Public License 1.3b
The LaTeX Project Public License 1.3c
MIT License
The SIL Open Font License
Open Publication License
Free license not otherwise listed
Public Domain Software
X11 License
Perl Artistic License
CC BY-NC 1.0
CC BY-NC 2.0
CC BY-NC 3.0
CC BY-NC 4.0
CC BY-NC-ND 1.0
CC BY-NC-ND 2.0
CC BY-NC-ND 2,5
CC BY-NC-ND 3.0
CC BY-NC-ND 4.0
CC BY-NC-SA 4.0
CC BY-ND 1.0
CC BY-ND 2.0
CC BY-ND 3.0
CC BY-ND 4.0
No Commercial Use
Do Not Sell Except by Arrangement
No Source Available
License that prevents distribution
Shareware: A fee is required
Please also indicate the license within the package itself, at
least in the top-level README
or README.md
file.
Select your archive file to be uploaded
Archive file
Your file will be uploaded when you submit this form
in the final step.
We only accept a single archive file for upload: the file name must
end in .zip
, .tgz
, or .tar.gz
.
Please do not use any special or non-printable characters (like blank
spaces) in file names.
You can provide some communication channels
Usually you want users of your package to provide some
feedback or have access to communication channels of certain kind.
Home page
This is the URL of the home page for the package.
There the user can expect to receive more information and references
related to the package.
Bug tracker
This is the URL to a bug tracker for the package.
The user can expect to receive more information about open and closed
issues for the package there.
Additionally new issues can be filed there.
Support
This is the URL where the user can get some kind of
support for the package. This can be a mailing list or discussion forum
dedicated to the package.
Announcements
This is the URL where the user can read announcements
for the package. This can be a mailing list or news feed dedicated to
the package.
Repository
This is the URL of the repository of the package. The
complete development versions of the package can be found there.
Developers
This is the URL where the user can participate in the
development of the package.