<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi,<div><br></div><div>I won't be at the meeting. I've read the migration proposal and the network team feedback pad.</div><div><br></div><div>Here is my extra feedback/notes:</div><div><br></div><div>Migrate / Test / Rollback</div><div><div><div><span style="background-color: rgba(255, 255, 255, 0);">* What is the plan for testing the migration?</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* What data must be successfully transferred?</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* What is the rollback plan, if the migration fails?</span></div></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Data migration</span></div><div><div><div id="magicdomid2154" class="ace-line" style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">* how does Parent ID get transferred?</span></div><div id="magicdomid2156" class="ace-line" style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">* note: will will lose the ability to have multi-level parent/child relationships</span></div><div id="magicdomid2258" class="ace-line" style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">Proposal: parent-NNNNN tag, placed on child tickets *and* parent ticket</span></div></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">New processes</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* When we replace fields with tags, how do we ensure consistent milestone, version, etc. spelling?</span></div></div><div><br></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">We might want to use Kanban boards / lanes (or GitLab tasks) rather than:</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">  - ticket queries embedded in wiki pages</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">  - CI tags</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">  - sponsors?</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">  - releases?</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">  - parent / child tickets?</span></div></div><div><div id="magicdomid774" class="ace-line" style="margin: 0px; padding: 0px;"><div><br></div><div>Ticket ID process changes</div><ul class="list-indent1" style="margin: 0px 0px 0px 1.5em; padding: 0px; list-style-type: none;"><li style="margin: 0px; padding: 0px;"><span style="background-color: rgba(255, 255, 255, 0);">In Trac, people can use a ticket ID to find a ticket.</span></li></ul></div><div id="magicdomid1035" class="ace-line" style="margin: 0px; padding: 0px;"><ul class="list-indent1" style="margin: 0px 0px 0px 1.5em; padding: 0px; list-style-type: none;"><li style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">In GitLab, each project can create *new* tickets with the same ID as tickets in other projects. </span><span style="background-color: rgba(255, 255, 255, 0);">(Even if we block all Trac ticket numbers, new tickets won't be blocked.)</span></li></ul></div><div id="magicdomid1125" class="ace-line" style="margin: 0px; padding: 0px;"><ul class="list-indent1" style="margin: 0px 0px 0px 1.5em; padding: 0px; list-style-type: none;"><li style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">What processes will we need to change, now that ticket IDs need a project?</span></li></ul></div><div id="magicdomid1247" class="ace-line" style="margin: 0px; padding: 0px;"><ul class="list-indent1" style="margin: 0px 0px 0px 1.5em; padding: 0px; list-style-type: none;"><li style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">  - ChangeLog / ReleaseNotes: ok, project can be determined from context</span></li></ul></div><div id="magicdomid1370" class="ace-line" style="margin: 0px; padding: 0px;"><ul class="list-indent1" style="margin: 0px 0px 0px 1.5em; padding: 0px; list-style-type: none;"><li style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">  - ticket bot: needs project prefix</span></li></ul></div><div id="magicdomid1474" class="ace-line" style="margin: 0px; padding: 0px;"><ul class="list-indent1" style="margin: 0px 0px 0px 1.5em; padding: 0px; list-style-type: none;"><li style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">    - can implement search order for non-prefixed numbers: legacy, tor, …</span></li></ul></div><div id="magicdomid1765" class="ace-line" style="margin: 0px; padding: 0px;"><ul class="list-indent1" style="margin: 0px 0px 0px 1.5em; padding: 0px; list-style-type: none;"><li style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">  - any other contexts?</span></li></ul></div><div id="magicdomid1768" class="ace-line" style="margin: 0px; padding: 0px;"><div><br></div><div>Migration - existing projects</div></div><div id="magicdomid1894" class="ace-line" style="margin: 0px; padding: 0px;"><ul class="list-indent1" style="margin: 0px 0px 0px 1.5em; padding: 0px; list-style-type: none;"><li style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">If a project is already set up in GitLab, what do we do with Trac / GitLab ticket number conflicts?</span></li></ul></div><div id="magicdomid2059" class="ace-line" style="margin: 0px; padding: 0px;"><ul class="list-indent1" style="margin: 0px 0px 0px 1.5em; padding: 0px; list-style-type: none;"><li style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">Proposal: each project consists of (GitLab tickets before migration)(blocked ticket numbers)(migrated tickets)(new tickets)</span></li><li style="margin: 0px; padding: 0px;"><span class="author-a-spz90z997z78zcphz72zz87z25yf" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">Proposal: we create a new project for each transferred project, block the Trac ticket numbers</span><span style="background-color: rgba(255, 255, 255, 0);"> out, transfer the legacy tickets, transfer the test project ticket, start opening new tickets</span></li></ul></div><div id="magicdomid2149" class="ace-line" style="margin: 0px; padding: 0px;"><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Keyword search</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Copied from the network team pad:</span></div><div><div id="magicdomid100" class="ace-line" style="margin: 0px; padding: 0px;"><span class="author-a-terz73z350l6vz79zgjvz88zz80z" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">When a field migrates to a keyword, is there a good way to search for</span></div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;"><span class="author-a-terz73z350l6vz79zgjvz88zz80z" style="margin: 0px; padding: 1px 0px 2px; cursor: auto; background-color: rgba(255, 255, 255, 0);">tickets lacking any keyword corresponding to that field?</span></div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;"><span style="background-color: rgba(255, 255, 255, 0);">  gaba: yes. you can filter by issues that do not have a labels</span></div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;"><span style="background-color: rgba(255, 255, 255, 0);">  (so for example if sponsors are keywords, how do we search for issues with no sponsor keyword? Do we have to list every sponsor keyword?)</span></div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;"><span class="author-a-8az84zz69ziz77zz68zvz66zz89zz65zz90zz88z6z76zn" style="background-color: rgba(255, 255, 255, 0); margin: 0px; padding: 1px 0px 2px; cursor: auto;">  gaba: there is a value 'None' </span><span class="author-a-8az84zz69ziz77zz68zvz66zz89zz65zz90zz88z6z76zn url" style="background-color: rgba(255, 255, 255, 0); margin: 0px; padding: 1px 0px 2px; cursor: auto;"><a href="https://dip.torproject.org/torproject/core/tor/-/boards?scope=all&utf8=%E2%9C%93&state=opened&label_name" style="margin: 0px; padding: 0px; cursor: pointer !important;">https://dip.torproject.org/torproject/core/tor/-/boards?scope=all&utf8=%E2%9C%93&state=opened&label_name</a></span><span class="author-a-8az84zz69ziz77zz68zvz66zz89zz65zz90zz88z6z76zn" style="background-color: rgba(255, 255, 255, 0); margin: 0px; padding: 1px 0px 2px; cursor: auto;">[]=None</span></div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;"><br></div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;">New questions:</div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;"><span style="background-color: rgba(255, 255, 255, 0);">But what if the ticket has *some other* keywords, but no sponsor keyword?</span></div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;"><span style="background-color: rgba(255, 255, 255, 0);">We'd need a regex like trac's !~=sponsor</span></div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;"><span style="background-color: rgba(255, 255, 255, 0);">It looks like -sponsor or -sponsor* should do what we want, but we should check:</span></div><div id="magicdomid101" class="ace-line" style="margin: 0px; padding: 0px;"><a href="https://docs.gitlab.com/ee/user/search/advanced_search_syntax.html" style="background-color: rgba(255, 255, 255, 0); margin: 0px; padding: 0px; cursor: pointer !important;">https://docs.gitlab.com/ee/user/search/advanced_search_syntax.html</a></div></div></div></div><div><br></div><span style="background-color: rgba(255, 255, 255, 0);">Suggested data migration / test details</span><div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Blockers</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">- If these fields aren't transferred as specified, we must roll back.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Ticket number</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Summary</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Description</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Comments (commenter, comment text)</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Milestone</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Keywords</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Actual Points</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Points</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Sponsor</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Component</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Reviewer</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">Important</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">- If these fields aren't transferred as specified, they should be fixed as soon as possible.</span></div></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">Type</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Version</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Reporter</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Parent ID - how does Parent ID get transferred?</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Optional</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">- It doesn't matter if these fields are transferred or not.</span></div></div></div><div><span style="background-color: rgba(255, 255, 255, 0);">- We probably can't transfer these fields in a useful way</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Cc</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Priority</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Severity</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Trac magic links to ticket IDs and wiki pages</span></div></div><div><br><div id="AppleMailSignature" dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">T</span><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">-- </span></div><div><span style="background-color: rgba(255, 255, 255, 0);">teor</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">----------------------------------------------------------------------</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div></div><div dir="ltr"><br>On 17 Sep 2019, at 02:48, Gaba <<a href="mailto:gaba@torproject.org">gaba@torproject.org</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><span>Hi!</span><br><span></span><br><span>A reminder that we are meeting tomorrow September 17th to discuss this</span><br><span>proposal of migration from trac.</span><br><span></span><br><span>gaba</span><br><span></span><br><span>El 9/6/19 a las 1:52 PM, Gaba escribió:</span><br><blockquote type="cite"><span>Hi!</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>With Pili we have been working on this document to compare features</span><br></blockquote><blockquote type="cite"><span>between trac and gitlab as well as proposal for a structure and</span><br></blockquote><blockquote type="cite"><span>workflows. Please take a look and send</span><br></blockquote><blockquote type="cite"><span>comments/feedback/edits/adds/questions.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span><a href="https://nc.riseup.net/s/SnQy3yMJewRBwA7">https://nc.riseup.net/s/SnQy3yMJewRBwA7</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>It seems that the next step will be to get together between everybody</span><br></blockquote><blockquote type="cite"><span>interested in this transition (or in not doing it) and discuss this plan</span><br></blockquote><blockquote type="cite"><span>as well as how to move forward.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>We are going to meet on</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>September 17th, at 18UTC in #tor-meeting</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Please, send me, pili or to the mailing list any comment if you can not</span><br></blockquote><blockquote type="cite"><span>make it to the meeting.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>cheers,</span><br></blockquote><blockquote type="cite"><span>gaba</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>El 7/29/19 a las 8:07 AM, Gaba escribió:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>Hi!</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>There has been some discussion in the 'corridors' of Tor and in the last</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>meeting face to face during the session on 'internal tooling' and</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>specifically about tickets system. I'm sending this mail to try to</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>summarize what the discussion has been until now, make it transparent</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>and try to get an agreement on how to move forward.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Problem:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- Trac software is not being mantained (from our perspective of users of</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Trac this is a bomb getting ready to explode) [0]</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Solution</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- Move out into a better (possible feature parity with what we use now</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>AND integration between project management tool and tickets) and</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>mantained ticketing system.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Discussion until now</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- A few years ago there was a survey [1] on which features people would</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>like to see in a new ticketing system.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- There is a ticket [2] that has a discussion on features needed and a</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>document [3] that brainstorm features between trac and gitlab.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- The last meeting in Stockholm there has been several discussions on</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>what is needed. [4]</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- In 2017 Hiro and the network team experimented with the <a href="http://oniongit.eu">oniongit.eu</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Gitlab instance.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>- In 2019, a test instance was setup, called "<a href="http://dip.torproject.org">dip.torproject.org</a>"[5],</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>that a few projects are using right now to test its use.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>We are mostly considering Gitlab (until now) because:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>1. We can host it ourselves and not have other company control the data.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>2. It is open source [6].</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>3. It is mantained [7].</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>4. It supports the project management tool that we are interested in.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Before moving forward we need:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>1. Consensus or a clear compromise on what to move into.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>2. A plan on how the migration to a new ticketing system will happen. I</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>started drafting it here (thinking that Gitlab would be the new one)</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[8]. This plan is still a work in progress and we will continue doing it</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>when we all agree on which system to move into.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>cheers,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>gaba</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[0] <a href="https://trac.edgewall.org/roadmap">https://trac.edgewall.org/roadmap</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[1]</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="https://docs.google.com/spreadsheets/d/1V4Faq2y9vv8XTp-OADl4YRMTiRB0G9DHvj23NRpwzcc/edit#gid=0">https://docs.google.com/spreadsheets/d/1V4Faq2y9vv8XTp-OADl4YRMTiRB0G9DHvj23NRpwzcc/edit#gid=0</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[2] <a href="https://trac.torproject.org/projects/tor/ticket/30857">https://trac.torproject.org/projects/tor/ticket/30857</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[3] <a href="https://nc.riseup.net/s/TYX37BDT4eQfTiW">https://nc.riseup.net/s/TYX37BDT4eQfTiW</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[4]</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/Notes/InternalTooling">https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/Notes/InternalTooling</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[5] <a href="https://dip.torproject.org">https://dip.torproject.org</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[6] <a href="https://gitlab.com/gitlab-org">https://gitlab.com/gitlab-org</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[7] <a href="https://gitlab.com/groups/gitlab-org/-/roadmap?layout=MONTHS">https://gitlab.com/groups/gitlab-org/-/roadmap?layout=MONTHS</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>[8] <a href="https://nc.riseup.net/s/SnQy3yMJewRBwA7">https://nc.riseup.net/s/SnQy3yMJewRBwA7</a></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br><span>-- </span><br><span>Project Manager: Network, Anti-Censorship and Metrics teams</span><br><span>gaba at <a href="http://torproject.org">torproject.org</a></span><br><span>she/her are my pronouns</span><br><span>GPG Fingerprint EE3F DF5C AD91 643C 21BE  8370 180D B06C 59CA BD19</span><br><span>_______________________________________________</span><br><span>tor-project mailing list</span><br><span><a href="mailto:tor-project@lists.torproject.org">tor-project@lists.torproject.org</a></span><br><span><a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project</a></span><br></div></blockquote></div></body></html>