<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:49:05 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-68] Prepare abbreviation list</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-68</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;PFS has a lot of abbreviations.&lt;br/&gt;
Summarise the these words and create a list.&lt;/p&gt;

&lt;p&gt;It is desirable that the list has nor only the full words of each abbreviation, but also category, and short description.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11303">INFRA-68</key>
            <summary>Prepare abbreviation list</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/major.svg">Major</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="yuki.moritani">yuki.moritani</assignee>
                                    <reporter username="yuki.moritani">yuki.moritani</reporter>
                        <labels>
                    </labels>
                <created>Thu, 3 Nov 2016 08:28:59 +0000</created>
                <updated>Fri, 2 Jun 2017 09:50:43 +0000</updated>
                            <resolved>Fri, 2 Jun 2017 09:50:43 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="11503" author="yuki.moritani" created="Thu, 3 Nov 2016 08:45:08 +0000"  >&lt;p&gt;I made a draft:&lt;br/&gt;
&lt;a href=&quot;https://github.com/Subaru-PFS/doc/pull/5&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/doc/pull/5&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The abbreviations are gathered from PFS documents such as design reviews, product trees, fundamental performance requirements, as well as  Atsushi&apos;s documents.&lt;/p&gt;</comment>
                            <comment id="11506" author="atsushi.shimono" created="Fri, 4 Nov 2016 07:56:26 +0000"  >&lt;p&gt;PR branch shall start from master except for special reason.&lt;br/&gt;
Rebase current PR branch, or create new one.&lt;/p&gt;</comment>
                            <comment id="11507" author="yuki.moritani" created="Fri, 4 Nov 2016 12:35:49 +0000"  >&lt;p&gt;Sorry... done&lt;/p&gt;</comment>
                            <comment id="11568" author="atsushi.shimono" created="Wed, 16 Nov 2016 17:13:23 +0000"  >&lt;p&gt;do we have PR for this? branch seems existing.&lt;/p&gt;</comment>
                            <comment id="11575" author="yuki.moritani" created="Wed, 16 Nov 2016 22:11:11 +0000"  >&lt;p&gt;I apologize:&lt;/p&gt;

&lt;p&gt;Just created:&lt;br/&gt;
&lt;a href=&quot;https://github.com/Subaru-PFS/doc/pull/6&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://github.com/Subaru-PFS/doc/pull/6&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="11579" author="atsushi.shimono" created="Thu, 17 Nov 2016 04:42:23 +0000"  >&lt;p&gt;Not reviewing individual items here (file new ticket to correct items), but just from organization point of view.&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;consider to add note in top page (README.md)&lt;/li&gt;
	&lt;li&gt;rather than setting &apos;Subcomponent&apos; to more than half, how about to set name for one level upper, like FPSA -&amp;gt; FSA&lt;/li&gt;
	&lt;li&gt;many of ICS component named as the same as hardware to control, and some software component is in hardware category, we may be better to think about them (but no idea now)&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="11992" author="yuki.moritani" created="Fri, 7 Apr 2017 13:02:59 +0000"  >&lt;p&gt;I&apos;m sorry for delaying my comment so long time...&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;I&apos;ll add README.md . I apologize for it.&lt;/li&gt;
	&lt;li&gt;As I talked directly, I don&apos;t mean hierarchy using group and category.  I should rename &quot;group&quot; and &quot;category&quot; to more proper words.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="12103" author="atsushi.shimono" created="Mon, 17 Apr 2017 10:50:24 +0000"  >&lt;p&gt;I don&apos;t have any further comment.&lt;/p&gt;

&lt;p&gt;Although I may insist to add a feature to make building hierarchy possible, but that shall be new feature request, once initial version released...&lt;/p&gt;</comment>
                            <comment id="12204" author="yuki.moritani" created="Tue, 23 May 2017 15:18:17 +0000"  >&lt;p&gt;I have just updated initial version with comments of individual abbreviations. (in the  the same PR)&lt;br/&gt;
While I was writing, I thought it would be better to have one column where related institutes are described...&lt;/p&gt;</comment>
                            <comment id="12207" author="atsushi.shimono" created="Tue, 30 May 2017 21:34:25 +0000"  >&lt;p&gt;(how about to merge PR, since no comment in one week?)&lt;/p&gt;</comment>
                            <comment id="12210" author="yuki.moritani" created="Wed, 31 May 2017 11:57:17 +0000"  >&lt;p&gt;All right. I&apos;ve merged it.&lt;br/&gt;
I hope each description can be updated at proper stage.&lt;/p&gt;</comment>
                            <comment id="12213" author="atsushi.shimono" created="Fri, 2 Jun 2017 09:50:43 +0000"  >&lt;p&gt;PR merged, closing this.&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|ii00vj:</customfieldvalue>

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