1. 28 May, 2022 3 commits
  2. 05 Apr, 2022 6 commits
  3. 21 Jan, 2022 1 commit
  4. 16 Jan, 2022 1 commit
  5. 18 Nov, 2021 1 commit
  6. 13 Nov, 2021 1 commit
  7. 23 Oct, 2021 1 commit
  8. 22 Oct, 2021 1 commit
  9. 19 Apr, 2021 1 commit
  10. 13 Apr, 2021 1 commit
  11. 26 Mar, 2021 2 commits
  12. 25 Mar, 2021 3 commits
  13. 02 Mar, 2021 1 commit
  14. 01 Mar, 2021 5 commits
    • David Runge's avatar
      Add gitlab-ci integration and Makefile · 143f9232
      David Runge authored
      Add Makefile, introducing a simple `make lint` target which runs
      rstcheck against all .rst files.
      Add GitLab CI integration, with a simple lint target, that calls `make
      lint` in an environment with the required dependencies.
    • David Runge's avatar
      Add issue template for RFC ideas · 6b99ac8d
      David Runge authored
      The template is used to lay out an idea, get feedback and find potential
    • David Runge's avatar
      Add RFC about using the RFC process · 771cc4c2
      David Runge authored
      Add a first, fairly simple (most of the relevant **Specification**
      information is found in the README of the repository) RFC about using
      the RFC system to steer Arch Linux.
      Add a section about existing (fairly recent) documentation in the wiki.
      Add a few sentences to outline the different entities Arch Linux
      consists of and what the RFC process is improving upon.
      Clarify the setup of the final comment period, after which the RFC is
      either accepted or rejected.
      Expand upon how and why the specialized communication channels are
      insufficient for solving overarching topics.
      Specify that the discussion takes place in the merge request itself.
      Add information on how RFC ideas may be proposed and existing ones
      Expand specification section by a paragraph on who is allowed to create
      an RFC (anyone) and explain what are the limitations for outside
      contributors (they can only create an RFC if at least one Developer or
      Trusted User supports the topic and helps to develop it).
      Elaborate on how in the current situation the decision making process or
      found consensus may be oblique to newcomers (or even long term staff)
      and that RFCs serve as an ongoing standardized archive of discussions
      and found consensus.
      Mention GitLab's approval feature as a means to approve of an RFC
      alongside the possibility to leave a comment for a more nuanced motion.
    • David Runge's avatar
      Add an RFC template · 9201828a
      David Runge authored
      Add a basic RFC template that provides a structure with Summary,
      Motivation, Specification, Drawbacks and Unresolved Questions.
    • David Runge's avatar
      Add description of RFC process · 9a823092
      David Runge authored
      Add a description about what the RFC process means and how it works in
      the context of using Gitlab with merge requests to assign RFC numbers
      Provide examples for announcements and describe the workflow of how to
      propose, comment on and finalize an RFC.
      Add a section about who can file an RFC and under what circumstances
      outside contributors are able to file an RFC (only if at least one
      Developer or Trusted User supports the effort).
      Add a note for how to create a merge request (i.e. allowing commits from
      members who can merge to the target branch).
      Add note for users without access rights to the arch-dev-public mailing
      Add link to creation of a new ticket for the repository as a way of
      proposing an idea for an RFC.
      Add a note with link to the repository issues for current or previous
      ideas (in ticket form).
      Mention GitLab's approval feature as a means to approve of an RFC in the
      Final Comment Period.
      Add section about licensing the contributions under the terms of the
      CC-BY-SA 4.0 license.
  15. 02 Feb, 2021 1 commit
  16. 25 Jan, 2021 1 commit
  17. 23 Jan, 2021 1 commit