summaryrefslogtreecommitdiff
path: root/docs/CONTRIBUTING.md
Commit message (Collapse)AuthorAgeFilesLines
* docs: fix formatting a bitDmitry V. Levin2023-01-231-2/+2
|
* ci: Labeler improvementsDaan De Meyer2022-12-091-0/+3
| | | | | | | | - Mention "/please-review" in the contributing guide - Remove "needs-rebase" on push - Don't add "please-review" if a green label is set - Don't add please-review label to draft PRs - Add please-review when a PR moves out of draft
* doc: CentOS is EOL use CentOS streamJan Macku2022-12-051-1/+1
|
* doc: fix markdown-lint issues in `CONTRIBUTING.md`Jan Macku2022-12-051-6/+8
|
* doc: update link to systemd-rhel GitHub repoJan Macku2022-12-051-1/+1
| | | | | | systemd-rhel GitHub repository has been moved to new location: - https://github.com/redhat-plumbers
* docs/CONTRIBUTING: strenghten language about ABI stability, fix links, other ↵Zbigniew Jędrzejewski-Szmek2022-10-011-13/+11
| | | | | | | | | | | | | tweaks The text made it sound like breaking ABI in libsystemd is allowed with good reasons. In fact, we plan never to do this, so make the language stronger. Also remind people about distro forums for reporting bugs. Those are probably a better place than systemd-devel for new users. Also, add some missing articles and apostrophes, fix URLs, remove repeated phrases, etc.
* docs/CONTRIBUTING: explain various labels and add link to "reviewable" PRsZbigniew Jędrzejewski-Szmek2022-09-301-1/+17
| | | | | | | | | | The linked filter gives an up-to-date list of pull requests that need review. (Yes, there's too many.) We used to set 'needs-review' label, but that is not available to non-members, and also every pull requests which is not labeled 'reviewed/needs-rework'/'ci-fails/needs-rework'/'needs-rebase' can and should be reviewed. If this is merged, I'll drop the 'needs-review' label.
* docs/CONTRIBUTING: ask people to send a ping on stalled reviewsZbigniew Jędrzejewski-Szmek2022-06-101-2/+3
| | | | | | | | | | | | | | A few related changes: be explicit that 'main' is the branch we're referring to. There was a case recently of somebody rebasing on 'master' by mistake. It's better to be explicit, since 'main' is still not the default for git (AFAIK). Also, github seems to send mails about force-pushes, so drop that as a justification. Commenting about changes that were done is useful even if github were to send a notification. And finally, $subject. We do that ourselves, but outside contributors might not know that that's expected.
* docs: update branch namesZbigniew Jędrzejewski-Szmek2022-01-031-1/+1
| | | | | Also use --atomic when pushing multiple items with git; adjust some external URLs.
* docs: add guidelines w.r.t. compatibility to docs/CONTRIBUTING.mdLuca Boccassi2021-10-121-0/+46
|
* add LICENSES/README.md explaining the license situationLuca Boccassi2021-10-011-1/+1
|
* docs: mention that contributed code must be compatible with GPL-2.0-or-later ↵Luca Boccassi2021-09-291-0/+1
| | | | explicitly
* docs: add spdx tags to all .md filesZbigniew Jędrzejewski-Szmek2021-09-271-0/+1
| | | | | | I have no idea if this is going to cause rendering problems, and it is fairly hard to check. So let's just merge this, and if it github markdown processor doesn't like it, revert.
* CONTRIBUTING: be clearer about versions and RFE processLennart Poettering2020-08-311-1/+2
| | | | Fixes: #16550
* docs: update information where to file bugs against RHEL/CentOS versions of ↵Lukas Nykryn2020-07-071-1/+1
| | | | systemd
* docs: point contributors to list of most recent systemd releasesLennart Poettering2020-06-101-1/+1
| | | | Fixes: #16083
* docs: make it prettyTobias Bernard2019-12-111-0/+1
| | | | | | | Add custom Jekyll theme, logo, webfont and .gitignore FIXME: the markdown files have some H1 headers which need to be replaced with H2
* docs: place all our markdown docs in rough categoriesLennart Poettering2019-12-111-0/+1
|
* docs: create new SECURITY.md pageZbigniew Jędrzejewski-Szmek2019-08-301-2/+2
| | | | | github has special support for that name: https://help.github.com/en/articles/adding-a-security-policy-to-your-repository.
* docs: new systemd-security mailing listZbigniew Jędrzejewski-Szmek2019-08-301-1/+1
| | | | | | | | | | | | | | | | | | | | In the past, we asked people to open a security bug on one of the "big" distros. This worked OK as far as getting bugs reported and notifying some upstream developers went. But we always had trouble getting information to all the appropriate parties, because each time a bug was reported, a big thread was created, with a growing CC list. People who were not CCed early enough were missing some information, etc. To clean this up, we decided to create a private mailing list. The natural place would be freedesktop.org, but unfortunately the request to create a mailing list wasn't handled (https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/134). And even if it was, at this point, if there was ever another administrative issue, it seems likely it could take months to resolve. So instead, we asked for a list to be created on the redhat mailservers. Please consider the previous security issue reporting mechanisms rescinded, and send any senstive bugs to systemd-security@redhat.com.
* docs: add a "front matter" snippet to our markdown pagesFilipe Brandenburger2019-01-021-0/+4
| | | | | | | | | | | | | | | | It turns out Jekyll (the engine behind GitHub Pages) requires that pages include a "Front Matter" snippet of YAML at the top for proper rendering. Omitting it will still render the pages, but including it opens up new possibilities, such as using a {% for %} loop to generate index.md instead of requiring a separate script. I'm hoping this will also fix the issue with some of the pages (notably CODE_OF_CONDUCT.html) not being available under systemd.io Tested locally by rendering the website with Jekyll. Before this change, the *.md files were kept unchanged (so not sure how that even works?!), after this commit, proper *.html files were generated from it.
* docs: Update links to updated docsFaheel Ahmad2018-10-301-2/+2
|
* docs: move markdown docs from .github/ to docs/Filipe Brandenburger2018-09-081-0/+37
The GitHub guide on contributing file says: "Decide whether to store your contributing guidelines in your repository's root, docs, or .github directory." https://help.github.com/articles/setting-guidelines-for-repository-contributors/#adding-a-contributing-file But there's really no advantage to keeping it in the hidden .github/, since these are public and really belong together with the other documentation. We can still keep the issue templates under .github/, since they are not really documentation on their own. Updated the links pointing to CONTRIBUTING.md to refer to the one in docs/.
View Lorry Controller Status