Am 03.09.12 08:30, schrieb Olivier: > Hi Yves, > > > > ________________________________ > De : HB-GRAL <[email protected]> > Envoyé le : Dimanche 2 septembre 2012 22h47 > > I didn't know you wanted to send our private mail exchange back onto the > list, with a new content for your replies. > >> Since Martin Spott wrote to the list he will not provide scenery anymore >> I didn’t realise sphere remains the one and only scenery central. > > Martin said was it at the end of February or early March that he was not able > to cope with all the submissions he was receiving from the whole world, which > is - when you imagine the workload it represents - pretty understandable, > Martin being just like us a human, and nearly the only person dealing with > those submissions. > He never stopped managing and enhancing the infrastructure behind, mapserver, > scenemodels, etc. There were quite a lot of exchanges here on the devel or in > private showing he is still there and working ;-) > Now with the webforms import, this workload has somewhat lowered, despite the > increase of 3D model submissions, so that's a good news for all. > Sphere having all the tools, data, and free CPU time (and Terrasync > infrastructure) still looks at the good place for scenery housing and terrain > generation and broadcast. > >> The work done by Pete and Chris for scenery generarion tools will work for >> every scenery build and any server, so it’s not necessary to centralize >> scenery building on a single server. And terrasync can be pointed to >> every subversion repository anyway. > > Why not, but that would be interesting as a spare resource, but while sphere > is there, I don't take the real interest of having two resources to work on, > maintain, update, apart from building a spare machine or testing, which would > be great. However I still think the most important for now is to have the > toolchain working and able to generate worldwide data. This is the top > priority and while this is not done, I, personally, won't take the time to > focus on something else. > It's already hard enough to make people work on a common infrastructure to > build the worldwide scenery. > >>> (don't take it bad, I appreciate what you're doing), >> so please do not blame me to provide resources > ^^. See the above line, I don't think there is any blame in any of my > sentences, I'm just trying to understand. Your private mail was more friendly. > > Oliver >
Hi Olivier Sorry for my harsh words, please do not take that personal. I see a lot of progress at two places at the moment: the objects database frontends and the terragear tools core. For the objects database (and probably also for other scenery data edits) I proposed to move to a gedjango application with free access for all contributors without restrictions, i.e. like the OpenStreetMap project works (works!), with "personal scenery developer responsability" and the philosophy of more self control for users instead of a complicated control mechanism which keeps sphere office full of pending control work. This is some kind of my personal misinterpretation in case it really helped to easy the workflow. I’m happy when this is the case now, and I think this is mainly your work. What I see at the moment is work done that was pending for years and it’s a good progress of course for database submissions, but why to enrich the historical interface only and not start with a complete new and contemporary project in background? ;-) The former sphere developers always stated it’s necessary to work with this and that (i.e. php), but I don’t think it’s a good idea to build a geo island with this, when ~80 percent of the geo world is working with other techniques. What’s about geoserver, geodjango, qgis, mapnik etc. ? Has this been evaluated by sphere? I offered work and help for that direction (and as you noticed probably sphere uses already one small little mapnik script coming from me). I really want to improve that part, but I need the feeling being in a team. Are you helping me with that? Former world scenery developers have the theory that I’m mainly replicating what is already done. But that’s not what I do when you dive deeper into what I’m proposing. I still miss documentation for scenery database/tools on sphere (beside of comments in scripts and automatically generated doc tables). That’s why I imported osm data to postgres 9.1/postgis 1.5 myself and documented how this is done. To be honest I didn’t realize that on sphere it’s done exactly the same way with osm data, I didn’t ask either, because I thought working on scenery data is cancelled there. And also I don’t know who has access to sphere and who is working there (beside of Martin Spott). Now I started to work on a "scenery test suite" some weeks ago for two reasons (third is fun). The first idea is that scenery tools developers (and also texture and shader developers i.e.) can test their work without comparing scenery output from their private machines only. At least there is a small piece of scenery public, versioned and comparable. The second idea is to have a demonstration/example of a possible workflow for future scenery edits and world scenery generation, distributed over a network and not sphere only (even here sphere could act as "master"). The test suite scenery is built with jenkins and updated daily, I don’t see jenkins installed on sphere nor do I think Martin Spott is going to give me sphere as a scenery test tools slave ? ;-) But it can be transferred to any server of course. -Yves ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-scenery mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-scenery
