Hi all Talking about learnosm We are teaching osm.in.our.bootcamp
Can we put.osm.logo.in.our certificate? We use.one.of them.learn osm.material. F On Sep 12, 2013 2:13 AM, "Banick, Robert" <[email protected]> wrote: > Thanks for the awesome feedback Severin. In response to you and Mikel:*** > * > > ** ** > > I like “Translation Lead” and agree that a pull request shouldn’t be > necessary. The less a Translator is forced to learn about Github, the more > likely this is to be successful.**** > > ** ** > > I agree that the issue tracker is pretty straightforward, thanks to its > resemblance to a traditional forum. It might be worth packaging some high > level guidance on what the issue tracker is for and how to use it (e.g. > documenting thoroughly any problems encountered, providing the OS, etc.)** > ** > > ** ** > > I think image naming conventions would be very helpful. Otherwise we’re > setting ourselves up for pain down the line. No idea about the upload > button.**** > > ** ** > > * * > > *Robert Banick* | Field GIS Coordinator | International Services | Ì American > Red Cross <http://www.redcross.org/>**** > > 2025 E Street NW, Washington, DC 20006**** > > Tel 202-303-5017 | Cell 202-805-3679 | Skype robert.banick**** > > ** ** > > *From:* Mikel Maron [mailto:[email protected]] > *Sent:* Wednesday, September 11, 2013 10:01 AM > *To:* Severin MENARD; [email protected] > *Cc:* Kunce, Dale; Joseph, Daniel B. > *Subject:* Re: [HOT] LearnOSM translators, we have guides**** > > ** ** > > Thanks Severin for looking through and giving feedback!**** > > ** ** > > > - it says Sign up and confirm your account, then You won't need to do > anything else on the GitHub website but From the list of projects on the > 'Explore Projects' page click on the **** > > > 'learnosm' folder to open it; If you don't see it, ask the GitHubber > team member if they have added you as a collaborator. So it is supposed > to be done by email and not through GitHub **** > > > pull request right?**** > > **** > > Yes, communication is not necessarily through github with the 'GitHubber' > (we really need to find a better name for this role ... maybe just > "Translation Lead"). The Translator certainly won't need to do a pull > request. **** > > ** ** > > However I guess we could consider some coordination through the Issue > tracker on github, which I consider relatively usable. Thoughts?**** > > ** ** > > > - The image below shows image elements; You should not change images or > links when translating. If we can stay with the same names, we definitely > have to make new images **** > > > as they show by default screenshots of the English interface. How do we > process?**** > > ** ** > > Yes, agreed, there needs to be a way for translators to provide translated > images. Will the upload button in prose.io upload to the "images" > directory? Do we need to specify some kind of image**** > > naming convention in the instructions?**** > > ** ** > > -Mikel**** > > ** ** > > ** ** > > * Mikel Maron * +14152835207 @mikel s:mikelmaron**** > > ** ** > ------------------------------ > > *From:* Severin MENARD <[email protected]> > *To:* "[email protected]" <[email protected]> > *Cc:* "Kunce, Dale" <[email protected]>; [email protected] > *Sent:* Tuesday, September 10, 2013 8:27 PM > *Subject:* [HOT] LearnOSM translators, we have guides**** > > ** ** > > Hi,**** > > ** ** > > I take the opportunity of being in the HOT House to go back to the > LearnOSM translation and review the guide kindly written by Daniel:**** > > > https://github.com/AmericanRedCross/Guides/blob/master/TranslationWorkflow_LearnOSM/translatorWorkflow.md > **** > > ** ** > > Thank you very much for this, it is really clear. Two remarks:**** > > - it says Sign up and confirm your account, then You won't need to do > anything else on the GitHub website but From the list of projects on the > 'Explore Projects' page click on the 'learnosm' folder to open it; If you > don't see it, ask the GitHubber team member if they have added you as a > collaborator. So it is supposed to be done by email and not through > GitHub pull request right?**** > > - The image below shows image elements; You should not change images or > links when translating. If we can stay with the same names, we definitely > have to make new images as they show by default screenshots of the English > interface. How do we process?**** > > ** ** > > Sincerely,**** > > ** ** > > Severin**** > > ** ** > > On Fri, Aug 23, 2013 at 9:49 AM, <[email protected]> wrote:*** > * > > Send HOT mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > > > Message: 1 > Date: Thu, 22 Aug 2013 17:25:40 -0700 (PDT) > From: Mikel Maron <[email protected]> > To: "[email protected]" <[email protected]> > Cc: "\"Kunce, Dale\"" <[email protected]>, "Daniel B. Joseph" > <[email protected]> > Subject: [HOT] LearnOSM translators, we have guides > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi > > We've been working to better document the process of translating LearnOSM > in gitpages/prose.io, as well as uncovering some needs for management of > LearnOSM. The goal is have a well managed and well understood translation > process. As a first step,?Daniel Joseph from the American Red Cross (thank > you!) has put together a draft documentation of the workflow, as well as > capture a few recommendations for the process.? > > We'd appreciated anyone interested to review the docs, and provide > constructive feedback ... the most helpful formulated as issues and pull > requests.? > > > https://github.com/AmericanRedCross/Guides/tree/master/TranslationWorkflow_LearnOSM > > ? > Cheers, and thanks again Daniel. > > Mikel > > * Mikel Maron *?+14152835207 @mikel s:mikelmaron > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.openstreetmap.org/pipermail/hot/attachments/20130822/b9974318/attachment-0001.html > >**** > > > _______________________________________________ > HOT mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/hot > > **** > > > _______________________________________________ > HOT mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/hot > >
_______________________________________________ HOT mailing list [email protected] https://lists.openstreetmap.org/listinfo/hot
