Hi all, Sorry I didn't answer to the messages that evoke the tasking manager. I'm not giving up with its development at all. I'm just having a hard time finding time and energy to contribute as much as I would like to. I hope I can get more free time to fix some issues and answer the pending emails.
Pierre On Tue, Jan 14, 2014 at 4:18 PM, Mikel Maron <mikel_ma...@yahoo.com> wrote: > > > Thanks Drazen for the update, and apologies for missing the meeting. Looking > at what was discussed, I had few comments .. perhaps we can discuss here. > > First regarding setting priorities, there are actually a couple ways we can > group issues on github to prioritize. We can either assign labels, and/or > assign milestones to issues. I think this would be fairly straightforward. > > For LearnOSM, I think it's well overdue to have a discussion group > specifically of translators and coordinators. If there's been a > restructuring of the English version, then certainly need to get the word > out and help transition. Finding a solution for image handling is something > we can do collectively, and maybe develop a good structured request to > prose.io devs. > > Finally, OSM Tasking Manager version 2. Would be really good to hear from > pgiraud about how much work is left. Basically, which of these issues need > to completed to get functionality up to v1, and retire v1 > https://github.com/pgiraud/osm-tasking-manager2/issues. There's a lot of > interest in building on OSMTM coming up, and we need to know where and how > to focus efforts. > > Cheers > Mikel > * Mikel Maron * +14152835207 @mikel s:mikelmaron > > > On Tuesday, January 14, 2014 8:51 AM, Dražen Odobašić > <dodo...@geoinfo.geof.hr> wrote: > > Tech WG IRC meeting X+5: Summary > > ybon: > * fixed gray problem with DEM in the HDM style > > clara: > * some old postings on the hot.osm don't display the images correctly, > working > on that > * she can spend some time in setting the site up to be multilingual. > Starting > with French, but also allowing other languages in future > * requires help of a person who will do the translation of the relevant > bits > of text > * proposes to update (hot.osm) Get Involved page with more technical > details > about each project developed by HOT, so that potential contributors can > easily > see if they can work with specific technology stack > > skorasaurus: > * will try to tweek hdm-josm style in the coming weeks, as there are a > few > hanging issues for the HDM-JOSM and HDM-carto, but none of them are > critical. > > pirzen: > * Dakar french translation sprint of LearnOsm in november. Intermediate > and > advanced sections are now available. See http://learnosm.org/fr/. > * Restructuration of the english version was started but not announced on > HOT > * we are still faced with LearnOsm and Github issues for Translators : No > progress made and no easy solution to upload images. Neither Github or > Prose.io > offer to upload images via the web > * announces that OsmContributorStatistic module is now available on github > : > https://github.com/pierzen/osm-contributor-stats. It provide historic > statistic > for bbox and dates. > * reports an interesting statistic, comparing Haiti and Haiyan response: > * Haiti 2010 - first 10 days, 304 contributors, 600k edits > * Haiyan 2013 - first 11 days, 1200 contributors, 3mil edits > > sev_hotosm: > * would like to see development version of TMv2 back online to test its > new > functionalities > * wonders if TWG is going to help with TMv2 development > * proposes to somehow prioritize or vote on the projects issues to give > potential developers a clear goal > > > dodobas: > * volunteers to keep TWG wiki page updated > * reports that at the moment there is no apparent load on amelia, after > main > web site migration > * will try to get TMv2 dev version up an running (best to scrap current > instance, and start over) > * concerned about too many active TMs, specifically tasks.hotosm.org and > tasks2.hotosm.org > * can we somehow merge data from tasks2 to tasks... once we migrate > tasks > from Amazon to amelia, or just discard it ? > * proposes that we should write better documentation per project, i.e. > create > a 'how to help' section for each project that would at least contain links > to > the documentation of the modules/libraries that the project is using, and > prepare coding guidelines > * proposes to advertise/advocate HOT project in the local Python user > meetings/Hackathons/... (once we have create 'community participation' > documentation) > > > _______________________________________________ > HOT mailing list > HOT@openstreetmap.org > https://lists.openstreetmap.org/listinfo/hot > > > > _______________________________________________ > HOT mailing list > HOT@openstreetmap.org > https://lists.openstreetmap.org/listinfo/hot > -- ------------------------------------------------------------- | Pierre GIRAUD ------------------------------------------------------------- _______________________________________________ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
