Skip to content

Commit a256a50

Browse files
authored
Clarify requirements for authors/maintainers project metadata (#1103)
It's a bit ambiguous as to whether leaving out both `name` and `email` is okay, an error, etc. The original intent was that _at least_ one key would be specified, but no specific key is required.
1 parent c4f8407 commit a256a50

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

source/specifications/declaring-project-metadata.rst

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,8 @@ These fields accept an array of tables with 2 keys: ``name`` and
158158
``email``. Both values must be strings. The ``name`` value MUST be a
159159
valid email name (i.e. whatever can be put as a name, before an email,
160160
in :rfc:`822`) and not contain commas. The ``email`` value MUST be a
161-
valid email address. Both keys are optional.
161+
valid email address. Both keys are optional, but at least one of the
162+
keys must be specified in the table.
162163

163164
Using the data to fill in :ref:`core metadata <core-metadata>` is as
164165
follows:

0 commit comments

Comments
 (0)