Reviving the 'Trac discussion' - next meeting on July 11th
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/
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
Dear people, I am thinking of moving this meeting to monday august 7 at 1400 utc #tor-project irc channel.. I am also thinking on Teor's email [1] raising a very important issue that gitonion (or gitlab) needs js to beon to be functional and that will exclude a lot of people who blocks js for security reasons. For me this can be a blocker from migrating out of trac. I know this (need of js) is for sure for the ticketing system interactions. But I am not sure for code review, looks like it is in order to be able to see the diffs at the UI. I also don't know how many people would enjoy the idea of having trac for ticketing system and gitonion for code review. I wonder if any of the folks testing it for code review are doing Tor browser on security level high, with js blocked. This is a big deal and as I said, I see as a possible blocker moving forward. I believe our next steps is to confirm this blocker before we invest more on oniongit (gitlab). so lets raise this as main point of the meeting for next monday (august7). Cheers, isabela On 7/12/17 21:44, isabela wrote:
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
Hi All, This meeting is at midnight for me, and I'm on leave that week. So I'll give some extra feedback below:
On 31 Jul 2017, at 23:18, isabela <isabela@torproject.org> wrote:
Dear people,
I am thinking of moving this meeting to monday august 7 at 1400 utc #tor-project irc channel..
I am also thinking on Teor's email [1] raising a very important issue that gitonion (or gitlab) needs js to beon to be functional and that will exclude a lot of people who blocks js for security reasons.
For me this can be a blocker from migrating out of trac. I know this (need of js) is for sure for the ticketing system interactions. But I am not sure for code review, looks like it is in order to be able to see the diffs at the UI.
I also don't know how many people would enjoy the idea of having trac for ticketing system and gitonion for code review.
I think this has been working well for some of us in the network team. But if the code review requires JavaScript, that makes it hard for some people to participate.
I wonder if any of the folks testing it for code review are doing Tor browser on security level high, with js blocked.
I use Tor Browser on high security level, but I haven't used gitlab or oniongit much in that mode. It seems the basic site navigation is not available, so I'm not sure how I could get to tickets or code reviews to test them.
This is a big deal and as I said, I see as a possible blocker moving forward. I believe our next steps is to confirm this blocker before we invest more on oniongit (gitlab).
so lets raise this as main point of the meeting for next monday (august7).
T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
isabela transcribed 3.2K bytes:
Dear people,
I am thinking of moving this meeting to monday august 7 at 1400 utc #tor-project irc channel..
Don't change the time because of me, since it's nigh impossible to accomodate Australia, west and east coast of North America, and western Europe simultaneously, but just pointing out this is early enough west coast time that I'm not very functional (or wouldn't be functional the remainder of the day). I'm happy to provide my 2¢ before/after, if that is helpful. Best, -- ♥Ⓐ isis agora lovecruft _________________________________________________________ OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35 Current Keys: https://fyb.patternsinthevoid.net/isis.txt
On 7/31/17 19:53, isis agora lovecruft wrote:
isabela transcribed 3.2K bytes:
Dear people,
I am thinking of moving this meeting to monday august 7 at 1400 utc #tor-project irc channel..
Don't change the time because of me, since it's nigh impossible to accomodate Australia, west and east coast of North America, and western Europe simultaneously, but just pointing out this is early enough west coast time that I'm not very functional (or wouldn't be functional the remainder of the day).
I'm happy to provide my 2¢ before/after, if that is helpful.
Best,
TBH this was just a random suggestion we can totally change this time and day. Any suggestions are welcomed!
participants (3)
-
isabela -
isis agora lovecruft -
teor