99f0d70da9
github: use multiple issue templates
...
Github now has issue templates in the web interface, and allows
more than one to be specified. Let's split our single template
in two: bug report and RFE.
2018-05-10 07:58:38 -07:00
f09eb7688e
doc: add a new doc/ directory, and move two markdown docs into them
...
I figure sooneror later we'll have more of these docs, hence let's give
them a clean place to be.
This leaves NEWS and README/README.md as well as the LICENSE texts in
the root directory of the project since that appears to be customary for
Free Software projects.
2018-02-27 19:59:09 +01:00
fc696d52b9
Docs: Fix spelling and capitalization ( #7408 )
2017-11-21 14:37:16 +01:00
91b8082096
CONTRIBUTING: stop mentioning "make check"
...
Since the switch to meson this information is no longer valid. HACKING already documents how to run the test suite.
See #6642
2017-08-21 09:47:07 +02:00
75d96e22d2
github: how to report bugs for older distribution versions ( #6146 )
2017-06-20 20:20:25 +02:00
b1e98c643c
github: tweak the issue template a bit more
2017-06-19 12:15:44 +02:00
43311625a0
github: tweak the issue template a bit, comment more
2017-06-19 12:13:28 +02:00
582c53d785
github: comment out submitter note in ISSUE_TEMPLATE
...
It's for the person filling in the form, not for people reading it later.
2017-05-22 16:07:28 +03:00
52c2abed4b
github: remove checkboxes from ISSUE_TEMPLATE
...
The issue list page thinks those are in fact todo items.
2017-05-22 16:06:50 +03:00
dc6c3de1b6
docs: use https in the mailing list url
2017-03-07 12:33:51 -03:00
c2205a0d4f
docs: add a note about reporting security vulns ( #5541 )
...
We *do* have the occasional security issue, where it would be nice to have
non-public disclosure and time to fix the issue before it's fully public. Our
github infrastracture does not make it easy to report vulnerabilities in
confidential manner, so let's leverage the distro mechanisms for that. I
think we're better off with this solution than leaving it up to individual
reporters to discover some mechanism on their own.
2017-03-07 14:33:27 +01:00
b0828828bb
CONTRIBUTING: reword the part about unsetting the label ( #4716 )
...
Only project members can do it.
2016-11-23 08:52:19 +01:00
e4a3e122b2
documentation: add a short document describing how to test your systemd build tree ( #3763 )
2016-07-20 22:15:54 -04:00
d11343ac79
Add RELEASE.md file which lists the steps needed for release
...
I put it in .github, so it doesn't stand out too much; after all
it's not interesting to most people.
2016-06-12 22:23:57 -04:00
476ef627af
CONTRIBUTING: ask people to comment after after force-push
2016-06-12 22:21:49 -04:00
945c6e7cc0
CONTRIBUTING: remove line wrapping
...
GitHub displays this file poorly, because it preserves the newlines.
Let's try how things look without any wrapping.
2016-06-12 22:21:49 -04:00
a87c45a84b
CONTRIBUTING: recommend force-push ( #3273 )
2016-05-16 21:44:35 +02:00
7f4394d2fe
.github/ISSUE_TEMPLATE: Use a list for submission type so that it appears as a checkbox
2016-02-26 09:54:30 +11:00
67b56fb29e
github: add a basic issue template
...
As documented here:
https://help.github.com/articles/creating-an-issue-template-for-your-repository/
2016-02-21 21:15:17 +01:00
67bf157f38
github: move CONTRIBUTING.md into .github subdirectory
...
As suggested by:
https://github.com/blog/2111-issue-and-pull-request-templates
2016-02-21 21:05:02 +01:00
Zbigniew Jędrzejewski-Szmek