[tor-project] User queries and issues for Nov-Dec'17

[Parinishtha Yadav]

On 12/01/18 3:23 PM, Georg Koppen wrote:
> Parinishtha Yadav:
>>
>> On 08/01/18 5:32 PM, Georg Koppen wrote:
>>> Parinishtha Yadav:
>>>> Hello people of Tor
>>>>
>>>> Wish you all a very happy new year! As an Outreachy intern with Tor, I
>>>> spent the last month gathering data and user queries from different
>>>> platforms on the internet (IRC, mail handles, Tor blog comments,
>>>> stackexchange, tor subreddit, RT, etc.). The aim was to have all these
>>>> queries in one place, in a sorted and organised manner. Some of the
>>>> queries identified will be added to the support portal by the community
>>>> team.
>>>>
>>>> I have created a spreadsheet on storm, with the following read only link
>>>> - https://storm.torproject.org/shared/RV8v026JvwzZ_82ZMRO_4GHAxUtqUhW8Abu6xaQpONd
>>>> <https://storm.torproject.org/shared/RV8v026JvwzZ_82ZMRO_4GHAxUtqUhW8Abu6xaQpONd> (the
>>>> first sheet has bugs/errors and the second one contains doubts/queries).
>>>> You can find the legend for colors used on the top right of the sheet.
>>>> In case anyone feels this will be relevant to their work in any way, or
>>>> is looking to pick some bugs to fix or areas to work on, you are welcome
>>>> to refer to this spreadsheet.
>>>>
>>>> This is my first time sending this spreadsheet out, and I plan to keep
>>>> doing so around the same date every month. So in case there are any
>>>> suggestions that come to mind, don't hesitate to shoot me a mail and I
>>>> will do my best to take them into account and make this as helpful as
>>>> possible.
>>> Thanks for collecting the information and putting it into that
>>> spreadsheet. Really appreciated. I wonder about the workflow in case
>>> changes to the spreadsheet are necessary. E.g. if one opens a bug on
>>> Trac after reading a report and now wants to update the spreadsheet with
>>> the bug number. Or if one wants to add already existing bug numbers.
>>>
>>> Sending a mail to the tor-project list for those small changes seems too
>>> noisy to me. Should we just send an email to you and you'll update the
>>> spreadsheet accordingly? Or could we just make it editable (if we are
>>> worried about that in general then only for a bunch of folks) to make
>>> that process more efficient?
>>>
>>> And how do we developer interact with you ideally in case we have
>>> follow-up questions about some of the spreadsheet items? Are you on IRC
>>> in one of the tor channels? Or should we write you an email? Or...
>>>
>>> Georg
>>>
>>> Hey Georg
>>>
>>> As for the workflow, I agree that there is no need to send out a mail
>>> on tor-project with small issues. There are two strategies we can
>>> follow simultaneously:
>>> 1. I can give edit rights to a small group of people. This is for
>>> people who regularly work on this stuff and they then may not email or
>>> contact me every time, but can make the necessary updates on their
>>> own. Please let me know who all to share access with. I am attaching
>>> my public key and signature along.
> Thanks. I'll talk to the team next Monday in our meeting (1900UTC in
> #tor-meeting) figuring out how we want to handle it. Let's go with
> access rights from there.
I will try to join in on that meeting. In case there's anything that
pops up then..
>
>>> 2. People can mail me personally with the information they want
>>> updated on the spreadsheet and I will take care of it. This method can
>>> be used by people who will be sending out this information
>>> occasionally and do not have edit rights.
> Let's start with some observations:
>
> 1) Regarding row 30: I wonder whether Malwarebytes is responsible for
> that we have https://trac.torproject.org/projects/tor/ticket/24709 where
> another weird issue got resolved once this tool got disabled. I wonder
> if that could help with row 26 and row 25 as well.
>
> 2) I think row 3 and row 18 can got together (maybe just mentioning the
> two different error codes in column D.
>
> 3) row 21 and 40 is #24136. I wonder whether we should have just one row
> for both.
>
> 4) re row 45: Did anybody contact the Tails people about that? Might be
> worth it. At least to know whether they are aware of this issue and have
> a ticket number for us for the spreadsheet.
I have added #24709 as a "possible issue" for 30, 26 and 25.
Have combined 3 and 18 as suggested.
Also added #24136 as the ticket for 21 and 40. (Didn't combine them yet
since they were listed under different operating systems, but have
mentioned in both rows that the same issue exists on the other operating
system)

>
>>> As for developer interactions, I am available on IRC on #tor-project
>>> and #tor-meeting with the username pari. Let me know if you want me to
>>> be active on any other channels too. (like #tor-dev) 
>>> And of course, writing me a mail is always another option you can
>>> exercise. I usually reply within an hour.
> That's perfectly fine, no worries. And welcome!
>
> One thing I am wondering is how the update to the spreadsheet is
> working. I am especially interested in easily finding out changes over
> time. How is that planned?
I discussed this with Alison in our meeting on Wednesday, and for now,
we have decided that I should go ahead and create a new sheet on the
same spreadsheet, called 'January bugs' and 'January doubts'. That will
keep track of any new issues that are coming up this month, while I will
keep updating items on the older sheet as they are fixed,etc.

Having just one link to the spreadsheet for several months will make it
easier to keep track of things. Maybe after a few months, I can create a
whole new fresh spreadsheet as this one will have way too many sheets.

During the first week of every month, I will send out a mail that calls
out issues and changes over the previous month, and also outlines the
areas that users have been reporting for the particular month. For eg:
my mail for first week of February will list the issues that have been
coming up over January, and also mention issues that were fixed from the
Dec spreadsheet.

Let me know what you think of this!

Cheers,
Pari
> Georg
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-project/attachments/20180112/6b955f42/attachment.sig>