<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:48:53 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-49] Prepare for request of OSS license for JIRA</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-49</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;ul&gt;
	&lt;li&gt;Define a list of licenses per package&lt;/li&gt;
	&lt;li&gt;Update web page for PFS software&lt;/li&gt;
	&lt;li&gt;Build a list of repositories and where work/ticket are tracked&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="11109">INFRA-49</key>
            <summary>Prepare for request of OSS license for JIRA</summary>
                <type id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10507&amp;avatarType=issuetype">Epic</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="atsushi.shimono">shimono</assignee>
                                    <reporter username="atsushi.shimono">shimono</reporter>
                        <labels>
                    </labels>
                <created>Tue, 9 Aug 2016 15:30:30 +0000</created>
                <updated>Fri, 23 Jun 2017 13:24:40 +0000</updated>
                            <resolved>Fri, 23 Jun 2017 13:24:40 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="11262" author="naoyuki.tamura" created="Sun, 28 Aug 2016 12:24:49 +0000"  >&lt;p&gt;Not clear how much should be done to each issue in what time scale. Here is my proposal. Please review how this will suite:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;PFS website: Make a new section for software on the &quot;instrument&quot; page and give a few-lines overview about the software system. In a longer term, let&apos;s discuss how we should flesh out the web contents for software perspectives.&lt;/li&gt;
	&lt;li&gt;We do have a list of licenses as long as those we have. Is this not enough?&lt;/li&gt;
	&lt;li&gt;Perhaps I still don&apos;t well enough understand the last issue. I guess it is not difficult for one to list issues on Jira as they appear, but I am now sure how issues can be mapped out with repositories (repositories on what?).&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I would appreciate a short description of an issue but it needs to be concise (short AND containing sufficient information) for colleagues to be able to give works right away.&lt;/p&gt;</comment>
                            <comment id="11345" author="atsushi.shimono" created="Mon, 26 Sep 2016 04:27:52 +0000"  >&lt;p&gt;&lt;a href=&quot;https://www.atlassian.com/licensing/purchase-licensing#evaluations-2&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;https://www.atlassian.com/licensing/purchase-licensing#evaluations-2&lt;/a&gt;&lt;br/&gt;
&amp;gt; We&apos;re happy to extend your server product evaluation period for up to 90 days.&lt;/p&gt;

&lt;p&gt;we started evaluation from mid-July 2016, so current evaluation license is the last limit. we need to hurry.&lt;/p&gt;</comment>
                            <comment id="11569" author="atsushi.shimono" created="Wed, 16 Nov 2016 17:15:31 +0000"  >&lt;p&gt;memo: not all work/ticket has done, but OSS license has issued. this ticket kept open until all dependency closed.&lt;/p&gt;</comment>
                            <comment id="12318" author="atsushi.shimono" created="Fri, 23 Jun 2017 13:24:40 +0000"  >&lt;p&gt;All referred tickets are closed!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="11100">INFRA-43</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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_10009" key="com.pyxis.greenhopper.jira:gh-epic-color">
                        <customfieldname>Epic Color</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ghx-label-3</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10007" key="com.pyxis.greenhopper.jira:gh-epic-label">
                        <customfieldname>Epic Name</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>LIC</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10008" key="com.pyxis.greenhopper.jira:gh-epic-status">
                        <customfieldname>Epic Status</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10001"><![CDATA[To Do]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|ii00mf:</customfieldvalue>

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