<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:14:26 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-8075] Automatically add peer reviewers per the lustre.org community reviewers list</title>
                <link>https://jira.whamcloud.com/browse/LU-8075</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;There is a community list of code reviewers at &lt;a href=&quot;http://wiki.lustre.org/Code_Reviewers&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://wiki.lustre.org/Code_Reviewers&lt;/a&gt;.  While at LUG 2016, John Hammond volunteered to write a script to automatically add the appropriate reviewers from the list for pull requests.  So for example, code affecting the LNDs would automatically the individual signed up for LND work.&lt;/p&gt;

&lt;p&gt;I&apos;m not sure if the implementation can pull from the wiki page directly or if the data should be mirrored in a more accessible format.  I assume that some refactoring may be in order as well.  Further, if there are n reviewers listed for a given sub-system, Gerrit would add all n.&lt;/p&gt;</description>
                <environment></environment>
        <key id="36436">LU-8075</key>
            <summary>Automatically add peer reviewers per the lustre.org community reviewers list</summary>
                <type id="3" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11318&amp;avatarType=issuetype">Task</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="4" iconUrl="https://jira.whamcloud.com/images/icons/statuses/reopened.png" description="This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.">Reopened</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="spitzcor">Cory Spitz</reporter>
                        <labels>
                    </labels>
                <created>Wed, 27 Apr 2016 03:25:54 +0000</created>
                <updated>Sun, 30 Jan 2022 10:07:42 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="150446" author="adilger" created="Thu, 28 Apr 2016 04:18:08 +0000"  >&lt;p&gt;Cory, one option is to use a similar method as the MAINTAINERS list in the kernel, with the &lt;tt&gt;scripts/get-maintainers.pl&lt;/tt&gt; script to map directories/files to individuals.&lt;/p&gt;

&lt;p&gt;That said, I&apos;ve found in the past that having too many people assigned to review a patch can be counter productive, since (I suspect) each individual assumes one of the other people assigned will do the actual work of reviewing the patch.  If there are only 2 or 3 people assigned to review a patch it is more likely that they feel they are on the hook and actually do the review.&lt;/p&gt;</comment>
                            <comment id="152982" author="spitzcor" created="Fri, 20 May 2016 13:55:15 +0000"  >&lt;p&gt;I agree, 2 or 3 people sounds ideal.  I&apos;m a fan of the get-maintainers.pl method.  That way, things are transparent.&lt;/p&gt;</comment>
                            <comment id="324476" author="adilger" created="Sun, 30 Jan 2022 10:05:49 +0000"  >&lt;p&gt;The &lt;tt&gt;get_maintainers.pl&lt;/tt&gt; script was added in patch &lt;a href=&quot;https://review.whamcloud.com/33104&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/33104&lt;/a&gt; &quot;&lt;tt&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11329&quot; title=&quot;add get_maintainer.pl script from kernel&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11329&quot;&gt;&lt;del&gt;LU-11329&lt;/del&gt;&lt;/a&gt; utils: add get_maintainer.pl script&lt;/tt&gt;&quot;.&lt;/p&gt;</comment>
                            <comment id="324477" author="adilger" created="Sun, 30 Jan 2022 10:07:42 +0000"  >&lt;p&gt;Note that the get_maintainer.pl script is not &lt;b&gt;automatically&lt;/b&gt; adding reviewers to patches.  This would need someone to write a small bot to watch patches and add the reviewers, once we had some confidence that the script itself was doing a good job. &lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="53201">LU-11329</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzy9l3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>