[HOT] Fwd: Re: Problems saving in ID

Charlotte Wolter techlady at techlady.com
Fri May 22 18:37:17 UTC 2015

Robert et al,

         Surely there are other ways to 
communicte with developers other than Github. Is 
that the only thing they respond to? I don't think so.
         Github has an odd-looking interface (to 
most people), and it's not really clear how to 
use it, unless you are familiar with it, which, 
it seems, you are. Also it has its own little 
language (what does "fork" mean and what does it 
have to do with reporting a problem?).
         However, most people do know how to fill 
out an online form when there is a problem. Does 
Microsoft send me to Github when I have a problem 
with Windows? Does my high-speed cable provider 
send me to Github when I can't download? No, 
because no one would understand it. Guys, 
sometimes the simpler solution is the best.
         I think most developers can read a 
simple problem report and respond. How they 
choose to work together to solve the issue is 
their business. Probably they would use Github, 
because they are familiar with Github. But don't send me there!


At 10:25 AM 5/22/2015, you wrote:
>Hi Charlotte,
>The intention of putting issue reporting there 
>is to create information that's *actionable* for 
>the (primarily Mapbox) folks who maintain and 
>develop iD. That way problems are automatically 
>linked to solutions. As you can tell, I gently 
>disagree with your assessment of github's 
>utility. I'm not a developer but I find it 
>really useful for communicating to developers, 
>who, after all, are the ones to fix things.
>That being said, could you maybe explain how 
>Github is poor for reporting issues with iD? If 
>you can maybe explain your frustrations further 
>we can understand how to either better explain 
>Github to new users *or* create new processes 
>that better match your needs as a user. I’m 
>not opposed to the latter but I would hope to 
>give Github a shot instead of inventing yet another process.
>Sent from <https://www.dropbox..com/mailbox>Mailbox
>On Fri, May 22, 2015 at 1:07 PM, Charlotte 
>Wolter <<mailto:techlady at techlady.com>techlady at techlady.com> wrote:
>You're not alone. Github was designed for people writing
>software. It is an absolutely terrible way to report issues with iD
>or anything else.
>Why isn't there a page on the OSM web site with a simple
>form for reporting these issues?
> >Delivered-To: techlady at techlady.com
> >From: Suzan Reed <suzan at suzanreed.com>
> >Date: Thu, 21 May 2015 21:14:11 -0700
> >To: Nick Allen <nick.allen.54 at gmail.com>
> >X-Mailer: Apple Mail (2.1085)
> >Cc: "HOT at openstreetmap.org" <hot at openstreetmap.org>
> >Subject: Re: [HOT] Problems saving in ID
> >X-BeenThere: hot at openstreetmap.org
> >X-Mailman-Version: 2.1.16
> >List-Id: Humanitarian OpenStreetMap Team <hot.openstreetmap.org>
> >List-Unsubscribe: <https://lists.openstreetmap.org/options/hot>,
> > <mailto:hot-request at openstreetmap.org?subject=unsubscribe>
> >List-Archive: <http://lists.openstreetmap.org/pipermail/hot/>
> >List-Post: <mailto:hot at openstreetmap.org>
> >List-Help: <mailto:hot-request at openstreetmap.org?subject=help>
> >List-Subscribe: <https://lists.openstreetmap.org/listinfo/hot>,
> > <mailto:hot-request at openstreetmap.org?subject=subscribe>
> >X-RR-Connecting-IP:
> >X-Authority-Analysis: v=2.1 cv=ae/vnHYt c=1 sm=1 tr=0
> >a=s24Y6Gjpp1c7EhQxjb5ZoQ==:117 a=CRRwbcOFI+X/mpt5jVcafw==:17
> >a=ayC55rCoAAAA:8 a=0oj8HZZGiqAA:10 a=BLceEmwcHowA:10
> >a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10
> >a=c40qY45ZAAAA:8 a=TZb1taSUAAAA:8 a=595fbENkAAAA:8 a=AUq6ltokAAAA:8
> >a=lyYuGu4CHa5PaZGX25icmyaRxzw=:19 a=h1PgugrvaO0A:10 a=NEAV23lmAAAA:8
> >a=g0IKWTOu3bTzVGJDUssA:9 a=QEXdDO2ut3YA:10
> >X-Cloudmark-Score: 0
> >
> >Nick and all,
> >
> >Would someone be so kind as to add the information way below
> >to the "issues" at the link Nick sent to me? I had a dickens of a
> >time trying to provide the feedback at that link, and I thought I
> >was pretty good with stuff like that.
> >
> >Suzan
> >
> >On May 21, 2015, at 1:31 AM, Nick Allen wrote: Hi,
> >https://github.com/openstreetmap/iD/issues Should be the place to
> >report problems. Nick (OSM=Tallguy) Humanitarian OpenStreetMap Team
> >Member On 21 May 2015 09:25, "Suzan Reed" <suzan at suzanreed.com>
> >wrote: For some time I've been having problems saving when using ID.
> >I don't know who to report this to. Can someone direct me the person
> >or people who can fix the ID editor? Or send the following to them?
> >Suzan Here are the issues: 1. After Saving edits, unlocking the
> >Task, and going to another Task, a dialog box appears with two icons
> >that indicates past edits have not saved, and asks if I want to
> >restore the edits and save them. When saved, I believe these over
> >write the last Task, doubling the images. 2. Other times another
> >dialog box appears: "Errors occured while trying to save Bad
> >Gateway. The proxy server received an invalid response from an
> >upstream server. Apache/2.4.7 (Ubuntu) Server at
> >www.openstreetmap.org Port 80" (html tags have been removed for
> >brevity.) When Saving after getting this kind of dialog box, the
> >Save button has to be pressed several times. There can be long
> >delays. Eventually the edits Save and I get the dialog that shows
> >they are being saved and the blue images in the left column appear.
> >_______________________________________________ HOT mailing list
> >HOT at openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
> >_______________________________________________ HOT mailing list
> >HOT at openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
>Charlotte Wolter
>927 18th Street Suite A
>Santa Monica, California
>techlady at techlady.com
>Skype: thetechlady
>HOT mailing list
>HOT at openstreetmap.org

Charlotte Wolter
927 18th Street Suite A
Santa Monica, California
techlady at techlady.com
Skype: thetechlady

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/hot/attachments/20150522/b98ec527/attachment.html>

More information about the HOT mailing list