... | ... | @@ -12,7 +12,7 @@ Initially, it may be best to make your project **private** or **internal**, befo |
|
|
|
|
|
When the project is set up, make sure you **complete all the other information** of the project in the project settings, including the **general** section: description, avatar, topics, features, badges, service desk; the CI/CD setup; and other parts of the settings that may apply, in particular when the project is more established. You can provide detailed documentation of your project in the wiki (this is in a git archive, so can be handled like the main repository). Projects that are insufficiently documented and whose purpose cannot be clearly identify or whose setup is causing problems for the site may be deleted.
|
|
|
|
|
|
**Project titles:** Project titles should start with _TYPE_ - _DESCRIPTIVE_PROJECT_TITLE_ [- MIRROR]. TYPE is Code, Paper, Data, Info, Test (others only if justified). Add MIRROR at the end if this is a local copy from an external source.
|
|
|
**Project titles:** Project titles should start with _TYPE_ - _DESCRIPTIVE_PROJECT_TITLE_ [- MIRROR]. TYPE is Code, Paper, Data, Img, Info, Test (others only if justified). Add MIRROR at the end if this is a local copy from an external source.
|
|
|
|
|
|
**Project tags:** a project tagged (topic) with "email" will get a simple mailing list PROJECT-SLUG@qyber.black for all its members. The distributor is regularly updated, but may be delayed by a day or so until it is set up or updated, if membership changes.
|
|
|
|
... | ... | |