Oh, not met by myself! I would work with a small team to iron this out, but we 
would get a better product with a small team participating. Who wants to help? 

___

Here's a rough idea of how this could work. (I may be leaving out some of the 
programming needed. Please comment.) 

Workflow: 

1. One link in the Task Manager "Report a Problem". Maybe in the red header? 
This would hardwire it into Task Manager. 

2. Click goes to a new page. 
(The form automatically picks up the OS, the browser, the date and time, and so 
on. Whatever the team needs.) 

(There would need to be buy in from the teams who fix problems as they would 
have to put these into Github. Could programming populate Github but that 
circumvents the search to see if the problem has been previously reported. In 
other situations, this is called an Open Ticket and these go into the reporting 
workflow whether they come from phone calls, emails, forms.)

Copy: "Thank you for reporting an issue. Please fill in the form below. It will 
automatically be sent to the responsible team."

Radio buttons where only one selection is possible: iD, JOSM, Other. Could be 
added to. 
(These buttons automatically direct where the email is routed.}

Form: 
First name: (It's nice to know who you are talking to, address them my name.)
Last name: (Because there may be more than one "Chris" or "Cliff".
Username: (This is the username you use to log into OSM.)
Email address: (Privacy statement can be noted at the bottom of the page.)
"Please describe exactly what happened in detail:" (Or other prompt.)
Box for the description
Place to upload screenshots with copy describing how to do this. Use Browse and 
Drag and Drop? 
Send

Links to common issues and how to fix them. 
Links to Learning the OSM Track Manager. 
Other links. 






On May 23, 2015, at 5:03 PM, Charlotte Wolter wrote:

Suzan,

       It sound like you would be a great resource in making this happen. Now 
all we need to do is get a clear mandate from the board (important) and some 
programmers. When is the next board meeting? We should get this on the agenda.

Charlotte


> Delivered-To: [email protected]
> From: Suzan Reed <[email protected]>
> To: Charlotte Wolter <[email protected]>
> Date: Sat, 23 May 2015 16:24:50 -0700
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 
> Thunderbird/24.6.0 AquaMail/1.5.7.3 (build: 21070068)
> Subject: Re: [HOT] Fwd: step by step recipe for iD bug reporting (was: 
> Problems saving in ID)
> X-RR-Connecting-IP: 107.14.168.141:25
> X-Authority-Analysis: v=2.1 cv=UbHfSciN c=1 sm=1 tr=0 
> a=CoGJZMXjC9ZqYjZMN9F/3A==:117 a=WSfeHOnGVVNQgzP7+CPq3g==:17 a=ayC55rCoAAAA:8 
> a=0oj8HZZGiqAA:10 a=j0qPZ1vW3qUA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 
> a=c40qY45ZAAAA:8 a=TZb1taSUAAAA:8 a=AUq6ltokAAAA:8 a=h1PgugrvaO0A:10 
> a=glSbvxPMAAAA:8 a=k5cIrk9cAAAA:8 a=595fbENkAAAA:8 a=NEAV23lmAAAA:8 
> a=-btfA0ZSW1iCa6GgQqQA:9 a=CjuIK1q_8ugA:10 a=d6Sr02UbQdMA:10 a=3hlsNCOeBJQA:10
> X-Cloudmark-Score: 0
> 
> Exactly what Charlotte said.
> 
> OSM and HOT are going through a monumental change. A huge influx of 3000, 
> 4000 new to OSM people. We want them to continue to contribute and because we 
> want them to stick around, we owe it to them to make everything about OSM and 
> HOT as easy-to-use as possible.
> 
> Convoluted workflows requiring new login and passwords, searches, and 
> instructions that are scattered, all of that has to change as we grow into 
> this new sized, new era of "anyone can help". Anything we can do to make the 
> experience intuitive and a no-brainer we need to do as good hosts. Either we 
> welcome all these enthusiastic people, or we stay a small, insular, insider's 
> club where diverse contributers find a difficult if not impossible terrain.
> 
> For now your instructions would  be great on an interim page people get when 
> reporting an issue, inbetween the Task Manager and Github.
> 
> Usability! We all need to think about how to make it easy! It's challenging 
> and interesting to figure out the simpliest, easiest way to do something on 
> the web!
> 
> As this is one of the things I do professionally, I would love to make a 
> proposal through a sample website working on a team with programmers.
> 
> Thinking of Dan in Montana who left after one day because he was frustrated 
> with OSM.
> 
> Suzan
> 
> 
> 
> 
> On May 23, 2015 11:51:37 AM Charlotte Wolter <[email protected]> wrote:
> 
>> Carl,
>> 
>>         It's very nice that you spelled out the steps, but
>> you're not getting it. We can't make ordinary mappers go
>> through those steps just to submit a problem report.
>> They need a link to a single page that has the words
>> "Problem Report" at the top. They fill in the blanks and
>> hit "Submit."
>>         Otherwise, we'll lose them. They'll just give up, and
>> we'll never know what issues are happening.
>> 
>> Charlotte
>> 
>> 
>> 
>> >Delivered-To: [email protected]
>> >Date: Sat, 23 May 2015 19:04:59 +0200
>> >From: Carl von Einem <[email protected]>
>> >Organization: www.einem.net
>> >User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
>> >  rv:31.0) Gecko/20100101 Thunderbird/31.7.0
>> >To: [email protected]
>> >X-Provags-ID: V03:K0:o1oj+HV0b/hlamTGseHI+e7OtO3edJdT5Uwby7dPU1D1fshTelQ
>> >  JiXmffTqgMdQe+ga4lbjLMl3ipdPrJKrAsR/RBdKM8Dg8u2X38btUUu2NXmrQhQiQpxaNze
>> >  2TqsMdh/UiRmnWINT/VBAuQ1jDdvHq53U+hP9zXQUbG268FWiCNzE37iFIOKYt6kocEJSku
>> >  I0TNWO8VXoXY3LcRecolg==
>> >X-UI-Out-Filterresults: notjunk:1;
>> >Subject: [HOT] step by step recipe for iD bug reporting (was: Problems
>> >  saving in ID)
>> >X-BeenThere: [email protected]
>> >X-Mailman-Version: 2.1.16
>> >Reply-To: [email protected]
>> >List-Id: Humanitarian OpenStreetMap Team <hot.openstreetmap.org>
>> >List-Unsubscribe: <https://lists.openstreetmap.org/options/hot>,
>> >  <mailto:[email protected]?subject=unsubscribe>
>> >List-Archive: <http://lists.openstreetmap.org/pipermail/hot/>
>> >List-Post: <mailto:[email protected]>
>> >List-Help: <mailto:[email protected]?subject=help>
>> >List-Subscribe: <https://lists.openstreetmap.org/listinfo/hot>,
>> >  <mailto:[email protected]?subject=subscribe>
>> >X-RR-Connecting-IP: 107.14.168.105:25
>> >X-Authority-Analysis: v=2.1 cv=Q5pc4uGa c=1 sm=1 tr=0
>> >a=DB0hE7zaO8GYUp/YqmXQew==:117 a=CRRwbcOFI+X/mpt5jVcafw==:17
>> >a=ayC55rCoAAAA:8 a=0oj8HZZGiqAA:10 a=vp1jIXIPkZwA:10
>> >a=BLceEmwcHowA:10 a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10
>> >a=xqWC_Br6kY4A:10 a=k5cIrk9cAAAA:8 a=TZb1taSUAAAA:8 a=595fbENkAAAA:8
>> >a=lyYuGu4CHa5PaZGX25icmyaRxzw=:19 a=h1PgugrvaO0A:10 a=NEAV23lmAAAA:8
>> >a=X0rGZIHscPEHP_VaLXUA:9 a=QEXdDO2ut3YA:10
>> >X-Cloudmark-Score: 0
>> >
>> >Charlotte Wolter wrote on 23.05.15 16:57:
>> >
>> > > This is my point exactly. Github works only for people who already
>> > > are "insiders," people who know how to use it. It doesn't work if you're
>> > > not used to it.
>> > > We need a simple Problem Report form on the web site. If the coders
>> > > want to use Github to solve the problem, fine. They're welcome to it. But
>> > > for us ordinary people, we need something in simple direct English.
>> > > By the way, there still are a couple of ongoing issues with iD
>> > > that no one seems to be tackling, despite reports on Github.
>> >
>> >I'm no coder and here is my step by step recipe for iD bug reporting:
>> >Visit https://github.com/ and "Sign up" (the platform is independent from
>> >OSM and HOT so you'll need to create a new account first). When
>> >successfully logged in just follow this procedure:
>> >1. on the upper left is a search bar ("Search GitHub"): type 'iD'
>> >and click "enter" on your keyboard
>> >2. in the list of search results click on "openstreetmap/iD" (should
>> >be the first item)
>> >3. click on "Issues" (navigation bar on the right)
>> >4. click on "New issue" (green button)
>> >5. choose a good title and write your problem description
>> >6. click on "Submit..."
>> >Done!
>> >_______________________________________________
>> >HOT mailing list <mailto:[email protected]>[email protected]
>> >https://lists.openstreetmap.org/listinfo/hot
>> >
>> >
>> 
>> Charlotte Wolter
>> 927 18th Street Suite A
>> Santa Monica, California
>> 90403
>> +1-310-597-4040
>> [email protected]
>> Skype: thetechlady
>> 
>> 
>> 
>> _______________________________________________
>> HOT mailing list
>> [email protected]
>> https://lists.openstreetmap.org/listinfo/hot
> 

Charlotte Wolter
927 18th Street Suite A
Santa Monica, California
90403
+1-310-597-4040
[email protected]
Skype: thetechlady



_______________________________________________
HOT mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/hot


_______________________________________________
HOT mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/hot

Reply via email to