<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:50:15 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-182] Please create product grouping products</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INFRA-182</link>
                <project id="10001" key="INFRA">Software Development Infrastructure</project>
                    <description>&lt;p&gt;Both for installation and for runtime configuration, it is useful to have &quot;grouping&quot; products, which &lt;b&gt;only&lt;/b&gt; have a &lt;tt&gt;.table&lt;/tt&gt; file listing other products to install or to setup. The point is that several subsystems do not depend on each other, but we often want to handle them together.&lt;/p&gt;

&lt;p&gt;Examples might help; I&apos;ll just list groups for the top-level actors; many important products get picked up automatically from those (tron_actorcore, ics_actorkeys, etc), and I&apos;ll leave the GUI parts off the lists.&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;ics_CORE
	&lt;ul&gt;
		&lt;li&gt;tron_tron&lt;/li&gt;
		&lt;li&gt;ics_archiver&lt;/li&gt;
		&lt;li&gt;ics_alertsActor&lt;/li&gt;
		&lt;li&gt;ics_gen2Actor&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;ics_SM:
	&lt;ul&gt;
		&lt;li&gt;ics_enuActor&lt;/li&gt;
		&lt;li&gt;ics_ccdActor&lt;/li&gt;
		&lt;li&gt;ics_xcuActor&lt;/li&gt;
		&lt;li&gt;ics_hxActor&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;ics_FPS:
	&lt;ul&gt;
		&lt;li&gt;ics_mcsActor&lt;/li&gt;
		&lt;li&gt;ics_fpsActor&lt;/li&gt;
		&lt;li&gt;ics_mpsActor&lt;/li&gt;
		&lt;li&gt;ics_mebActor&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;And I&apos;ll suggest a top-level product, for everything:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;ics_PFS:
	&lt;ul&gt;
		&lt;li&gt;ics_CORE&lt;/li&gt;
		&lt;li&gt;ics_SM&lt;/li&gt;
		&lt;li&gt;ics_FPS&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;If you do not have these, it can be annoying and error-prone to do the equivalent of, say, &lt;tt&gt;eups distrib install ics_SM 2018-03-01&lt;/tt&gt; or &lt;tt&gt;setup ics_SM&lt;/tt&gt;.&lt;/p&gt;

&lt;p&gt;I don&apos;t feel strongly about the names, but would prefer them to be easy to type. The details of what go in the .table files can be dealt with later &#8211; I can easily see having the products listed in &lt;tt&gt;ics_CORE&lt;/tt&gt; above being included in &lt;tt&gt;ics_SM&lt;/tt&gt; or &lt;tt&gt;ics_FPS&lt;/tt&gt;.&lt;/p&gt;

&lt;p&gt;With those caveats in mind, I&apos;ll request two products now:&lt;/p&gt;
&lt;div class=&apos;table-wrap&apos;&gt;
&lt;table class=&apos;confluenceTable&apos;&gt;&lt;tbody&gt;
&lt;tr&gt;
&lt;th class=&apos;confluenceTh&apos;&gt;Repo name&lt;/th&gt;
&lt;th class=&apos;confluenceTh&apos;&gt;JIRA component&lt;/th&gt;
&lt;th class=&apos;confluenceTh&apos;&gt;Responsible&lt;/th&gt;
&lt;th class=&apos;confluenceTh&apos;&gt;License&lt;/th&gt;
&lt;th class=&apos;confluenceTh&apos;&gt;Comment&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;ics_SM&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;?&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;LAM&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;Any&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;A meta-product listing all independent Spectrograph Module products&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;ics_FPS&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;?&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;ASIAA&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;Any&lt;/td&gt;
&lt;td class=&apos;confluenceTd&apos;&gt;A meta-product listing all independent FPS products&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;/div&gt;
</description>
                <environment></environment>
        <key id="12138">INFRA-182</key>
            <summary>Please create product grouping products</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="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="yuki.moritani">yuki.moritani</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>FPS</label>
                            <label>MCS</label>
                    </labels>
                <created>Fri, 6 Apr 2018 17:49:59 +0000</created>
                <updated>Fri, 19 Jun 2020 14:56:31 +0000</updated>
                            <resolved>Fri, 19 Jun 2020 14:56:31 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                <comments>
                            <comment id="13335" author="atsushi.shimono" created="Tue, 1 May 2018 13:28:48 +0000"  >&lt;p&gt;it seems we might be better to have some grouping identification like ics_group_xxx for searchiability etc., but these names shall be accepted.&lt;br/&gt;
please provide a line for other two?&lt;/p&gt;</comment>
                            <comment id="17351" author="cloomis" created="Fri, 19 Jun 2020 14:56:31 +0000"  >&lt;p&gt;I withdraw 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|ii045r:</customfieldvalue>

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