<div class="ace-line" id="magicdomid107"><span class="">Hi all,</span></div><div class="ace-line" id="magicdomid108"><br></div><div class="ace-line" id="magicdomid109"><br></div><div class="ace-line" id="magicdomid159"><span class="">So far, the experiment with SoaS has been a success. </span><span class="author-p-470">Sebastian Dziallas</span><span class=""> reports satisfaction with Launchpad's bug and blueprint functionality, as well as inter-tool integration. </span></div>
<div class="ace-line" id="magicdomid111"><br></div><div class="ace-line" id="magicdomid112"><span class="">== Overview ==</span></div><div class="ace-line" id="magicdomid113"><span class="">Launchpad
has a number of strengths that differentiate it from other tools we
have explored, the most important is the integration of the following
components into a cohesive whole:</span></div><div class="ace-line" id="magicdomid114"><ul class="list-bullet1"><li><span class="">Questions/Answers</span></li></ul></div><div class="ace-line" id="magicdomid115"><ul class="list-bullet1">
<li><span class="">Bugs</span></li></ul></div><div class="ace-line" id="magicdomid116"><ul class="list-bullet1"><li><span class="">Blueprints</span></li></ul></div><div class="ace-line" id="magicdomid117"><ul class="list-bullet1">
<li><span class="">Translations</span></li></ul></div><div class="ace-line" id="magicdomid118"><ul class="list-bullet1"><li><span class="">Code hosting (bzr)</span></li></ul></div><div class="ace-line" id="magicdomid119">
<br></div><div class="ace-line" id="magicdomid120"><span class="">Moreover, if Sugar Labs decides not to make use of all of these components, we can disable them from within the Launchpad UI.</span></div><div class="ace-line" id="magicdomid121">
<br></div><div class="ace-line" id="magicdomid122"><span class="">Finally,
Launchpad is not a PITA to manage. Rather than requiring Bernie (the
only person other than Ivan who has access to dev.sl.o AFAICT) to
constantly wrangle with system updates, scalability issues, and general maintenance, Launchpad is externally hosted by Canonical.</span></div><div class="ace-line" id="magicdomid123"><br></div><div class="ace-line" id="magicdomid124">
<span class="">== Comparisons ==</span></div><div class="ace-line" id="magicdomid125"><br></div><div class="ace-line" id="magicdomid126"><span class="">Compared to Trac: </span></div><div class="ace-line" id="magicdomid127">
<ul class="list-bullet1"><li><span class="">Project-level optional access control on priority, milestone targeting, etc</span></li></ul></div><div class="ace-line" id="magicdomid128"><ul class="list-bullet1"><li><span class="">intergreted spesification/blueprint functionality, with support for milestone targeting, etc.</span></li>
</ul></div><div class="ace-line" id="magicdomid129"><ul class="list-bullet1"><li><span class="">differentiation between support requests and bugs</span></li></ul></div><div class="ace-line" id="magicdomid130"><ul class="list-bullet1">
<li><span class="">the
ability to link bugs as affecting multiple projects, and to pull in
status updates from other projects, even if they use different bug
trackers</span></li></ul></div><div class="ace-line" id="magicdomid131"><ul class="list-bullet1"><li><span class="">hosted gratis, and supported by a team of competent Canonical system administrators</span></li></ul></div>
<div class="ace-line" id="magicdomid132"><ul class="list-bullet1"><li><span class="">support for translating projects using POT files</span></li></ul></div><div class="ace-line" id="magicdomid133"><ul class="list-bullet1">
<li><span class="">a cleaner user interface (opinion)</span></li></ul></div><div class="ace-line" id="magicdomid134"><ul class="list-bullet1"><li><span class="">group support</span></li></ul></div><div class="ace-line" id="magicdomid135">
<br></div><div class="ace-line" id="magicdomid136"><span class="">Compared to GetSatisfaction:</span></div><div class="ace-line" id="magicdomid137"><ul class="list-bullet1"><li><span class="">free and open source software, written in Zope</span></li>
</ul></div><div class="ace-line" id="magicdomid138"><ul class="list-bullet1"><li><span class="">acts as both a bug tracker, a question/answers site, and everything described above</span></li></ul></div><div class="ace-line" id="magicdomid139">
<br></div><div class="ace-line" id="magicdomid140"><br></div><div class="ace-line" id="magicdomid141"><span class="">== Migration ==</span></div><div class="ace-line" id="magicdomid142"><br></div><div class="ace-line" id="magicdomid143">
<span class="">If Sugar Labs does decide to migrate, the process is fairly straightforward. </span></div><div class="ace-line" id="magicdomid144"><br></div><div class="ace-line" id="magicdomid145"><span class="">All bugs can be exported from Trac using a well-documented and supported tool, and be imported into Launchpad projects. </span></div>
<div class="ace-line" id="magicdomid146"><br></div><div class="ace-line" id="magicdomid147"><span class="">Users
who have Trac accounts will have corresponding Launchpad accounts
pregenerated, but they will not be active until the user generates a
password. Users who already have Launchpad accounts will be able to
merge them, or (if they used the same email address) automagically have
bugs reported at SL associated with their extant accounts. (we can opt
to not go this route and have all imported data owned by
~launchpad-janitor)</span></div><div class="ace-line" id="magicdomid148"><br></div><div class="ace-line" id="magicdomid149"><span class="">All Sugar Labs projects would be associated with the "sugarlabs" super-project, and would be seen from </span><span class=" url"><a href="http://launchpad.net/sugarlabs">http://launchpad.net/sugarlabs</a></span><span class="">. We still get the benefit of having a single page to point people who are reporting bugs <</span><span class=" url"><a href="https://launchpad.net/sugarlabs/+filebug">https://launchpad.net/sugarlabs/+filebug</a></span><span class="">> or asking questions <</span><span class=" url"><a href="https://answers.launchpad.net/sugarlabs/+addquestion">https://answers.launchpad.net/sugarlabs/+addquestion</a></span><span class="">>.</span></div>
<div class="ace-line" id="magicdomid150"><br></div><div class="ace-line" id="magicdomid151"><span class="">Since Launchpad does not support native bzr hosting, we have three options:</span></div><div class="ace-line" id="magicdomid152">
<ul class="list-bullet1"><li><span class="">convert to bzr (not probable)</span></li></ul></div><div class="ace-line" id="magicdomid153"><ul class="list-bullet1"><li><span class="">use bzr git imports with Launchpad</span></li>
</ul></div><div class="ace-line" id="magicdomid154"><ul class="list-bullet1"><li><span class="">integrate Gitorious with Launchpad via OpenID, write a script for project mirroring</span></li></ul></div><div class="ace-line" id="magicdomid155">
<ul class="list-bullet1"><li><span class="">don't integrate Gitorious at all, and just have slight duplication of effort
on the developer's part. (even light-weight LP-OID is easy to do)</span></li></ul></div><div class="ace-line" id="magicdomid156"><br></div><div class="ace-line" id="magicdomid157">Based on the above, we'd like to propose that Sugar Labs migrate to Launchpad, at least for Blueprints, Answers, and Bugs, within a release cycle.<br>
</div><div class="ace-line" id="magicdomid106"><br></div>--<br clear="all">This email was jointly constructed by Sebastian Dziallas and Luke Faraone.<br>