<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:50:30 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-206] Create a document registry for Princeton provided documents</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-206</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;In general I assert that all documents circulated amongst the PFS team should have a document ID number for easy tracking and referencing (in emails and other documents).&lt;/p&gt;

&lt;p&gt;The PFS Project Office have allowed individual institutions, based on general rules, to determine the ID numbers for documents. In order to ensure that those ID numbers are unique and follow the Princeton-specific rules, a persistent registry for Princeton documents should be established.&lt;/p&gt;

&lt;p&gt;This registry should contain for each document the following information at least:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;The document ID number&lt;/li&gt;
	&lt;li&gt;The full name of the document&lt;/li&gt;
	&lt;li&gt;The author name&lt;/li&gt;
&lt;/ul&gt;

</description>
                <environment></environment>
        <key id="12365">INFRA-206</key>
            <summary>Create a document registry for Princeton provided documents</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</priority>
                        <status id="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="hassan">hassan</assignee>
                                    <reporter username="hassan">hassan</reporter>
                        <labels>
                    </labels>
                <created>Thu, 7 Jun 2018 22:21:50 +0000</created>
                <updated>Wed, 15 Aug 2018 18:35:57 +0000</updated>
                            <resolved>Wed, 15 Aug 2018 18:35:57 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="13470" author="hassan" created="Thu, 7 Jun 2018 22:22:09 +0000"  >&lt;p&gt;A simple realization of this registry is a simple CSV file with the above as fields, persisted in GitHub.&lt;/p&gt;</comment>
                            <comment id="13471" author="hassan" created="Thu, 7 Jun 2018 22:23:05 +0000"  >&lt;p&gt;An additional CSV file, containing:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;The author name&lt;/li&gt;
	&lt;li&gt;The 2-digit author code&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;would also be useful.&lt;/p&gt;</comment>
                            <comment id="13503" author="atsushi.shimono" created="Sun, 10 Jun 2018 22:47:29 +0000"  >&lt;p&gt;is there any reasonable/clear reason to separate this from commonly used ones like doc or *_doc?&lt;/p&gt;</comment>
                            <comment id="13507" author="hassan" created="Mon, 11 Jun 2018 12:58:12 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=atsushi.shimono&quot; class=&quot;user-hover&quot; rel=&quot;atsushi.shimono&quot;&gt;shimono&lt;/a&gt; I&apos;m afraid I do not understand your question: when you say &apos;doc&apos; or &apos;*_doc&apos;, are you referring to a GitHub repository? &lt;/p&gt;

&lt;p&gt;Yes, a short-term solution is to place the &lt;em&gt;registry file&lt;/em&gt; (a CSV file) under GitHub, as mentioned in an earlier comment. There is no need to create a new, separate GitHub repository, if that is what your question is implying. I&apos;m happy to use for example the doc repo &lt;a href=&quot;https://github.com/Subaru-PFS/doc&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/doc&lt;/a&gt; to store this information. I just need the green light from Project Office to do that.&lt;/p&gt;
</comment>
                            <comment id="13787" author="atsushi.shimono" created="Wed, 18 Jul 2018 16:22:59 +0000"  >&lt;p&gt;sorry leaving this ticket. &lt;br/&gt;
for new item (incl git repo, jira project, etc.) we use ticket for gathering information and tracking, but for editing repository (this time adding something into doc?) we just follow normal PR/r? procedure as usual repository, so I think you can create branch to show what will be implemented.&lt;br/&gt;
or, of course you can call &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=naoyuki.tamura&quot; class=&quot;user-hover&quot; rel=&quot;naoyuki.tamura&quot;&gt;naoyuki.tamura&lt;/a&gt; or email to the PO...&lt;/p&gt;</comment>
                            <comment id="13917" author="hassan" created="Wed, 15 Aug 2018 18:35:57 +0000"  >&lt;p&gt;Document registry for Princeton implemented in text form under GitHub successfully.&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|ii04pj:</customfieldvalue>

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