Hello Tor!

We had this meeting last Tuesday and decided on a couple action items for now.

1. Tor Browser and Network teams will look on how to get oniongit.eu (gitlab) as part of their code review workflow so they can start testing it for realz ;) 2. Isabela and hiro will work on a doc summarizing what we collected from the survey as requirements for issue tracker and create a table comparing it with what trac and gitlab can offer 3. we will meet again on Tuesday August 1st at 1400UTC!

We start a discussion about having CI for external contributors ticket #22636 has a suggestion on how we can get that done.

We still have some open question related to this: a) should we create hooks from different places to track PR and tickets from external contributors so they can use whatever they prefer to use when contributing with a patch? b) does it matter where we have the canonical repos? should they be on our own infrastructure?

If you have any suggestions on the above, feel free to add your thoughts at this pad:

https://pad.riseup.net/p/trac-meeting-notes

cheers, isabela

On 6/27/17 12:07, isabela wrote:

Hi everyone,

It has been a while since we started evaluating if we want to find alternatives to Trac.

You might remember we sent a survey out to collect more info, and based on the answers we believe we should figure out a better solution.

https://lists.torproject.org/pipermail/tor-project/2017-March/000975.html https://lists.torproject.org/pipermail/tor-project/2017-March/000978.html

In Amsterdam meeting we hosted a discussion on the results of our survey and up to this moment we have been evaluating gitlab as a possible alternative to Trac or eventually as a possible code review tool we can use.

But this has been a little 'loose' and we wanted to organize things better in order to be able to make decisions and move forward.

Therefore we are thinking of breaking this into 3 'tasks' we want to cover for development:

* continue integration - jenkins is doing this now for us (only used

for internal contributors tho, would be nice to think of a way external contributors could use it / maybe setting up travis for them)

* code review - We have a test gitlab instance running at

https://oniongit.eu [or emuo4mf6vwghcaqn.onion]. Network team has accounts on it and we would like to have more people testing it. Please bear in mind that this is a test machine, it is not backed up, and can be slow on occasions.

* issue tracker - could be gitlab or another solution, we are still

looking into how to solve this one

(yes, the wiki is not on this list for now)

So! We would like to propose the following moving forward:

1. Meet on irc to answer any questions on this new approach and get more

people trying our gitlab testing installation [MEETING IS ON JULY 11TH TUESDAY AT 1400 UTC ON #tor-project channel]

2. Set up a 'end date' for our gitlab testing phase - that is why we

would like more folks trying it out

3. Look into a plan to provide CI for external contributors (using

travis maybe?)

4. Create a list of requests for what we need for issue tracker and see

what to do about that

We believe that covering the points above will help us move forward with this project.

Please reach out to hiro if you'd like to have access to the gitlab test set up. Any questions/feedback is welcome as always.

thanks! isabela and hiro o/ _______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project