https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INFRA-47 Software Development Infrastructure <p>Add new project "ETS" (Exposure targeting software) for ETS development by MPA. <br/> better project name (and description?) are desired.</p> INFRA-47

Add new project "FiberAlloc"

Task Major Done Done shimono shimono Thu, 28 Jul 2016 06:12:13 +0000 Mon, 10 Apr 2017 11:04:22 +0000 Mon, 10 Apr 2017 11:04:22 +0000 0 4 <p>There's no need for short acronyms (there are already too many in this project). Let's get a short description of the scope before deciding what to call it; for example, "FiberAlloc" might be appropriate if that's what this does. If it does more, it'll need a name that covers more aspects of the problem.</p> <p>We also need to think about whether we need small jira projects like this. If it's part of the operational software we might want to have a single project to cover all this, with a different agile board for the pieces like the MPA parts.</p> <p>In particular, "Exposure" is overloaded (e.g. it is used for a single set of spectrogram images), and "Software" adds nothing to the name.</p> <p>I second Roberts comment on the acronyms. I also believe that FiberAlloc is more appropriate and less likely to be confused with the ?SurveyPlan? that we will need as well? </p> <p><a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kiyoto.yabe" class="user-hover" rel="kiyoto.yabe">Kiyoto Yabe</a> (and/or <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=naoyuki.tamura" class="user-hover" rel="naoyuki.tamura">naoyuki.tamura</a>?) any comment or suggestion from project management aspect of ETS package?</p> <p>How about FiberAssigner? This looks to be consistent with the repository name on GitHub.</p> <p>although no comment on project management point of view, let me add this project for now. only three polls but "FiberAlloc" has points.</p> <p>I understand making project large and using label or epic in extensive is an option, and external boundary of this package is still floating especially to survey coordination (to SPT) and collision avoidance (to ICS). But, this package already has many points such as selection of calibration targets for required level of number, coordinate transformation from sky to F3C (or some), pickup AG targets (acquisition, AG, focusing), etc., also this package is assumed to be released as one separated software to be used by various users, I personally think it is enough for one project.</p> <p>I went through project settings and it seems ok for current requirement. So, let me close this ticket.<br/> If you find any comment/suggestion/request, file new ticket in this project with assigning to project lead (<a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kiyoto.yabe" class="user-hover" rel="kiyoto.yabe">Kiyoto Yabe</a>).</p> <p>project created and used. also description added to web site.<br/> -&gt; DONE.</p> Development Epic Link INFRA-43 Rank 0|ii00lz: