commit 5c5baaf17d688151d5c72eb6535ca499ba916fdf · pyrox.dev/nixpkgs

+1 -1

.github/CONTRIBUTING.md

···

       43
       43
        
       

     

       44
       44
        
       ## Writing good commit messages

     

       45
       45
        
       

     

       46
       46
       -
       In addition to writing properly formatted commit messages, it's important to include relevant information so other developers can later understand *why* a change was made. While this information usually can be found by digging code, mailing list archives, pull request discussions or upstream changes, it may require a lot of work.

     

       46
       46
       +
       In addition to writing properly formatted commit messages, it's important to include relevant information so other developers can later understand *why* a change was made. While this information usually can be found by digging code, mailing list/Discourse archives, pull request discussions or upstream changes, it may require a lot of work.

     

       47
       47
        
       

     

       48
       48
        
       For package version upgrades and such a one-line commit message is usually sufficient.

     

       49
       49

-1

README.md

···

       38
       38
        
       Communication:

     

       39
       39
        
       

     

       40
       40
        
       * [Discourse Forum](https://discourse.nixos.org/)

     

       41
       41
       -
       * [Mailing list](https://groups.google.com/forum/#!forum/nix-devel)

     

       42
       41
        
       * [IRC - #nixos on freenode.net](irc://irc.freenode.net/#nixos)

+5 -4

doc/reviewing-contributions.xml

···

       605
       605
        
       -->

     

       606
       606
        
       

     

       607
       607
        
         <para>

     

       608
       608
       -
          In a case a contributor leaves definitively the Nix community, he should

     

       609
       609
       -
          create an issue or notify the mailing list with references of packages and

     

       610
       610
       -
          modules he maintains so the maintainership can be taken over by other

     

       611
       611
       -
          contributors.

     

       608
       608
       +
          In a case a contributor leaves definitively the Nix community, he

     

       609
       609
       +
          should create an issue or post on <link

     

       610
       610
       +
          xlink:href="https://discourse.nixos.org">Discourse</link> with

     

       611
       611
       +
          references of packages and modules he maintains so the

     

       612
       612
       +
          maintainership can be taken over by other contributors.

     

       612
       613
        
         </para>

     

       613
       614
        
        </section>

     

       614
       615
        
       </chapter>

+2 -2

nixos/doc/manual/manual.xml

···

       17
       17
        
         <para>

     

       18
       18
        
          If you encounter problems, please report them on the

     

       19
       19
        
          <literal

     

       20
       20
       -
           xlink:href="https://groups.google.com/forum/#!forum/nix-devel">nix-devel</literal>

     

       21
       21
       -
          mailing list or on the <link

     

       20
       20
       +
           xlink:href="https://discourse.nixos.org">Discourse</literal>

     

       21
       21
       +
          or on the <link

     

       22
       22
        
           xlink:href="irc://irc.freenode.net/#nixos">

     

       23
       23
        
          <literal>#nixos</literal> channel on Freenode</link>. Bugs should be

     

       24
       24
        
          reported in