<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:50:07 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-169] Rename pfi-ics channel to ait_pfi at slack</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-169</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;We currently have pfi-ics channel on PFS slack, but considering we have ics and ait_lam, it would be better to be renamed as ait_pfi.&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;check somewhere we have a list of slack channels&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="12052">INFRA-169</key>
            <summary>Rename pfi-ics channel to ait_pfi at slack</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="1" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="yuki.moritani">yuki.moritani</assignee>
                                    <reporter username="atsushi.shimono">shimono</reporter>
                        <labels>
                    </labels>
                <created>Thu, 25 Jan 2018 07:03:42 +0000</created>
                <updated>Thu, 18 Jun 2020 23:14:59 +0000</updated>
                            <resolved>Thu, 25 Jan 2018 07:03:42 +0000</resolved>
                                                                    <component>web</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                <comments>
                            <comment id="12887" author="atsushi.shimono" created="Mon, 29 Jan 2018 05:35:58 +0000"  >&lt;p&gt;I&apos;ve checked doc/ics_doc/pfs_www_pipe repos, but there was no detailed list of slack channels. We can get a list of channels once someone logged in from browse channels, so there would be no need to have list-all-ish thing (we already have a list of commonly used one in pfspipe web page).&lt;/p&gt;

&lt;p&gt;So, we can go ahead without changing anything in documentations.&lt;/p&gt;</comment>
                            <comment id="12888" author="naoyuki.tamura" created="Mon, 29 Jan 2018 05:38:55 +0000"  >&lt;p&gt;Only PFI? ait_asiaa may be better to cover MCS? One potential downside might be the MCS hardware will be moved to Subaru pretty soon, but I don&apos;t think personally that this should be taken so seriously.&lt;/p&gt;</comment>
                            <comment id="12889" author="atsushi.shimono" created="Tue, 30 Jan 2018 03:50:07 +0000"  >&lt;p&gt;comments were posted about ait_asiaa, but also there were some comments against, &lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;from software point of view (as in PFS software slack), PFI part will not be limited to pfi+mcs, but strongly related to fiber assignment, image distortion, etc, and not kept only in ASIAA&lt;/li&gt;
	&lt;li&gt;considering FPS as a sequencer, other components are sub-module called from it (of course, ETS is not directly called but on-exposure output is relatively similar)&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="17348" author="hassan" created="Thu, 18 Jun 2020 22:55:09 +0000"  >&lt;p&gt;Is this still valid &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=yuki.moritani&quot; class=&quot;user-hover&quot; rel=&quot;yuki.moritani&quot;&gt;yuki.moritani&lt;/a&gt;?&lt;/p&gt;</comment>
                            <comment id="17349" author="yuki.moritani" created="Thu, 18 Jun 2020 23:14:59 +0000"  >&lt;p&gt;Well renaming has not been done yet, but looking the other channels, I&apos;m not sure &quot;ait-pfi&quot; is proper name... if one channel is need analogous to SpS activity, it should be renamed to &quot;ait-asiaa&quot;, I think.&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|ii03uf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10100" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Reviewers</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>chyan</customfieldvalue>

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