Commit Graph

10 Commits

Author SHA1 Message Date
Pili Guerra 9167093320
Update CONTRIBUTING.md (#8304)
We have deprecated the RFC process
2024-02-22 10:52:35 +00:00
Alfredo Garcia 081d2d1ec2
release(docs): Refactor bug report template (#6858)
* try a github form the user bug report template

* make fixes

* apply suggestions

* Apply suggestions from code review

Co-authored-by: teor <teor@riseup.net>

---------

Co-authored-by: teor <teor@riseup.net>
2023-06-08 05:34:23 +00:00
Dimitris Apostolou 859b67d512
docs: fix typo (#3877) 2022-03-22 22:01:35 -04:00
Janito Vaqueiro Ferreira Filho f9817c8b65
Link to Conventional Commits specification (#3858)
And explain why PR titles should follow that specification.
2022-03-13 16:44:15 +00:00
teor 8b72e8627b
Make the RFC TOC into a separate step (#2126)
We might remember it better that way.
2021-05-10 10:17:42 -03:00
teor c4c0b6705a Use small xxxxs 2021-03-30 18:22:03 -04:00
teor b5bc8576a8 Update the RFC process to include drafts
We put RFCs in drafts, and only assign them a number when they merge.
2021-03-30 18:22:03 -04:00
Jane Lusby b835a04a5e document coverage workflow 2021-03-20 14:59:02 -04:00
Henry de Valence b212becb67 Add issue and PR templates, document RFC process 2020-08-31 00:58:50 -04:00
Henry de Valence bdf66387d6
Reorganize the book. (#843)
* Reorganize the book.

This PR has one unfortunate change, which is that the README.md and
CONTRIBUTING.md files in the book are symlinks to files in the parent
directory.  The motivation for this is to ensure that we don't maintain two
copies of the same data, and that the landing page of the website matches the
landing page of the Github repo, etc.   However, I'm not sure whether these
symlinks will work correctly on Windows.

The alternatives are:

- Duplicate the contents of the files and expect that people will know to keep
  them in sync;

- Use relative links `../../README.md` in the `SUMMARY.md`.  This seemed like
  it caused mdbook to dump the rendered files into the repository root rather
  than keeping them in the `book` directory.

- Use a symlink (chosen option).  This may not work on Windows but I think that
  the worst outcome would be that the book would be unbuildable unless someone
  used WSL or something.  This seems like the least bad option.

* Remove symlinks in favor of #include 

Turns out the symlinks aren't required!
2020-08-06 15:39:54 -07:00