<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:49:13 JST 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>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INFRA-80] Restructure gitolite permissions file</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-80</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;Looking at the gitolite config file it appears much more repetitious and hard to maintain than the &lt;a href=&quot;https://dev.lsstcorp.org/trac/wiki/GitDemoAndTutorial#Fullgitoliteconfigfile&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;LSST one&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;We should consider simplifying it.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10323">INFRA-80</key>
            <summary>Restructure gitolite permissions file</summary>
                <type id="1" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10503&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/major.svg">Major</priority>
                        <status id="10100" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="No further work should be done on this.">Won&apos;t Fix</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="atsushi.shimono">shimono</assignee>
                                    <reporter username="rhl">rhl</reporter>
                        <labels>
                    </labels>
                <created>Wed, 30 Jul 2014 17:49:34 +0000</created>
                <updated>Thu, 1 Dec 2016 06:58:25 +0000</updated>
                            <resolved>Thu, 1 Dec 2016 06:58:25 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="10215" author="cloomis" created="Wed, 30 Jul 2014 21:06:25 +0000"  >&lt;p&gt;Wildcards in repo names are disabled. Specifically &lt;tt&gt;$GL_WILDCARDS=0&lt;/tt&gt; in {{.gitolite.rc}&lt;/p&gt;

&lt;p&gt;I understand the security concern about turning that on, but will make the case that it is OK. a) I think you can trust the @admins, and b) the stanza we want to add to &lt;em&gt;all&lt;/em&gt; repos is something like:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;  RW+                            = @dev
  R                              = @bot
  RW+C                           = @admin
  RWC     tickets/[0-9]+$        = @dev         # Allow creating and pushing to tickets
  RW+C    u/USER/                = @dev         # Allow full control over personal branches
  RW+C    refs/tags/u/USER/      = @dev         # Allow full control over personal tags
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;We could avoid turning wildcards on and apply those rules to &lt;tt&gt;repo @all&lt;/tt&gt;, then override with:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;repo gitolite-admin
   - = @dev

repo www_publications
  RW+D = @all
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I think that&apos;d be good. I will not test it until Shimono-san is online, as I can see myself disabling writes to gitolite-admin, and leaving all repos broken....&lt;/p&gt;

&lt;p&gt;In the short term, I will add the stanza to &lt;tt&gt;drp_stella&lt;/tt&gt;, &lt;tt&gt;ics_mhs_actorcore&lt;/tt&gt;, &lt;tt&gt;ics_mhs_tron&lt;/tt&gt;, and &lt;tt&gt;ics_mhs_config&lt;/tt&gt;.&lt;/p&gt;</comment>
                            <comment id="10217" author="cloomis" created="Wed, 30 Jul 2014 22:11:56 +0000"  >&lt;p&gt;Warning: the&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;  RW+ = @admin
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;line allows admins to push any stupid thing (e.g. invalid branch and tag names). &lt;/p&gt;

&lt;p&gt;But other than that it looks like it works.&lt;/p&gt;</comment>
                            <comment id="10218" author="cloomis" created="Wed, 30 Jul 2014 22:17:57 +0000"  >&lt;p&gt;Added &lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;  RW+                            = @dev
  R                              = @bot
  RWC     tickets/[0-9]+$        = @dev         # Allow creating and pushing to tickets
  RW+C    u/USER/                = @dev         # Allow full control over personal branches
  RW+C    refs/tags/u/USER/      = @dev         # Allow full control over personal tags
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;to the four listed products.  Note that I removed the @admin rule.&lt;/p&gt;</comment>
                            <comment id="10220" author="atsushi.shimono" created="Wed, 30 Jul 2014 23:50:46 +0000"  >&lt;p&gt;&amp;gt; Specifically $GL_WILDCARDS=0 in {{.gitolite.rc}&lt;br/&gt;
not a security reason, but just a default, I think.&lt;br/&gt;
only I am afraid of is adding C to @all will make things messy and un-organized.. (ah, of course I need to trust @admin,s, heh..)&lt;/p&gt;

&lt;p&gt;anyway, if no strong objection, I&apos;d file new ticket for &lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;changing $GL_WILDCARDS&lt;/li&gt;
	&lt;li&gt;adding ics_* drp_* spt_* ets_* pfs_* (targets need to be discussed) to gitolite w/C = @admin&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="11122" author="atsushi.shimono" created="Mon, 18 Jul 2016 12:04:09 +0000"  >&lt;p&gt;closing this since we moved to github, and operation is under discussion at &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/browse/INFRA-38&quot; title=&quot;Document coding standards and procedures&quot; class=&quot;issue-link&quot; data-issue-key=&quot;INFRA-38&quot;&gt;&lt;del&gt;INFRA-38&lt;/del&gt;&lt;/a&gt; or related.&lt;/p&gt;</comment>
                            <comment id="11650" author="atsushi.shimono" created="Thu, 1 Dec 2016 06:58:25 +0000"  >&lt;p&gt;close this. (might be mis-reopened)&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|ii007j:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>