[tor-project] [CHANGING MEETING DATE] Re: Reviving the 'Trac discussion'

[isabela]

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
>