právě jsem si všimnul, že nám v OSM Inspectoru [1] republika trochu "odčervenala". Zdá se, že zatím byly changesety s importy, které dělal pavel [2], označeny za čisté pouze v rámci OSM Inspectoru. LWG chystá v brzké době převod těchto changesetů na jiný účet, kde budou dále žít jako "licenčně čisté" [3]. Pavle, pokud máš k tomuto kroku nějaké konkrétní námitky, směřuj je tam nebo/a LWG; případně, kdybys chtěl připojit k seznamu nějaké další své changesety, které můžou žít v OSM i pod CT+ODbL, určitě budeme všichni rádi.
právě jsem si všimnul, že nám v OSM Inspectoru [1] republika trochu "odčervenala". Zdá se, že zatím byly changesety s importy, které dělal pavel [2], označeny za čisté pouze v rámci OSM Inspectoru. LWG chystá v brzké době převod těchto changesetů na jiný účet, kde budou dále žít jako "licenčně čisté" [3]. Pavle, pokud máš k tomuto kroku nějaké konkrétní námitky, směřuj je tam nebo/a LWG; případně, kdybys chtěl připojit k seznamu nějaké další své changesety, které můžou žít v OSM i pod CT+ODbL, určitě budeme všichni rádi.
So lets start by saying that I don't like ODbL and I hate CT. Now, there's list of imports I did to OSM, with intention of marking them "OK to switch to CT+ODbL". Sorry, but you may not do that without my agreement. I believe I own copyright in most of those. There are three classes of data I uploaded to osm: a) Hand created data, most important paths in the woods. CT+ODbL, is okay for those. b) ODbL compatible - mass imports. I'd be willing to be convinced that ODbL is okay for those, as long data from a) are kept. CT is not. Those imports were lot of work, and saying "you have to update OSM every once in a while to be even able to vote about licensing" is double-plus impolite. c) ODbL incompatible mass imports. Obviously these need to be removed. I have no power to change this.
So lets start by saying that I don't like ODbL and I hate CT. Now, there's list of imports I did to OSM, with intention of marking them "OK to switch to CT+ODbL". Sorry, but you may not do that without my agreement. I believe I own copyright in most of those. There are three classes of data I uploaded to osm: a) Hand created data, most important paths in the woods. CT+ODbL, is okay for those. b) ODbL compatible - mass imports. I'd be willing to be convinced that ODbL is okay for those, as long data from a) are kept. CT is not. Those imports were lot of work, and saying "you have to update OSM every once in a while to be even able to vote about licensing" is double-plus impolite. c) ODbL incompatible mass imports. Obviously these need to be removed. I have no power to change this.
I'm sorry, but I'm starting to loose my patience.
You've already clearly stated, that you don't like license change and want to maximize the damage to OSM community, nothing new here.
I'm sorry, but I'm starting to loose my patience.
You've already clearly stated, that you don't like license change and want to maximize the damage to OSM community, nothing new here.
what do I remember Pavel saying, and I can refer to the "OSM Inspector a stav přijetí licence" talk-cz mailinglist thread, the closest thing to "maximising the damage" is just that he is not going to do someone else's work (he even *constructively* responded to some emails about what to do next, which is better than acting like dead, so you really hardly can speak about "maximising the damage")
so I don't hesitate to call you a liar
You have four options: 1. Ideally, pavel would agree that these changesets come from a free source and are not affected by his general rejection of the Contributor Terms...[shortened]I don't like the license change, nor the new contributor terms and so I don't want to make license change easy.
Relicensing the import and keeping the original data does not make sense, sorry. By that I would cause that most of the users would remain on osm.org and I could work in peace on fosm.org... alone. Which is not quite what I want. So far I have a feeling it would be best not to change the license to OdBL.
what do I remember Pavel saying, and I can refer to the "OSM Inspector a stav přijetí licence" talk-cz mailinglist thread, the closest thing to "maximising the damage" is just that he is not going to do someone else's work (he even *constructively* responded to some emails about what to do next, which is better than acting like dead, so you really hardly can speak about "maximising the damage")
so I don't hesitate to call you a liar
You have four options: 1. Ideally, pavel would agree that these changesets come from a free source and are not affected by his general rejection of the Contributor Terms...[shortened]I don't like the license change, nor the new contributor terms and so I don't want to make license change easy.
Relicensing the import and keeping the original data does not make sense, sorry. By that I would cause that most of the users would remain on osm.org and I could work in peace on fosm.org... alone. Which is not quite what I want. So far I have a feeling it would be best not to change the license to OdBL.
Hi! So lets start by saying that I don't like ODbL and I hate CT. There are three classes of data I uploaded to osm: a) Hand created data, most important paths in the woods. CT+ODbL, is okay for those. b) ODbL compatible - mass imports. CT+ODbL is okay for those, provided data from a) are kept. Richard convinced me that CT is not meant to be evil, and I can live with that. c) ODbL incompatible mass imports. Obviously these need to be removed. I have no power to change this. Mass imports were cities from wikipedia (place=*) and railway stations from around http://www.openstreetmap.org/browse/changeset/188101 187327 I hope this helps, and I'd like to see some reply, thanks, Pavel
Hi! So lets start by saying that I don't like ODbL and I hate CT. There are three classes of data I uploaded to osm: a) Hand created data, most important paths in the woods. CT+ODbL, is okay for those. b) ODbL compatible - mass imports. CT+ODbL is okay for those, provided data from a) are kept. Richard convinced me that CT is not meant to be evil, and I can live with that. c) ODbL incompatible mass imports. Obviously these need to be removed. I have no power to change this. Mass imports were cities from wikipedia (place=*) and railway stations from around http://www.openstreetmap.org/browse/changeset/188101 187327 I hope this helps, and I'd like to see some reply, thanks, Pavel
Hi! So lets start by saying that I don't like ODbL and I hate CT. There are three classes of data I uploaded to osm: a) Hand created data, most important paths in the woods. CT+ODbL, is okay for those. b) ODbL compatible - mass imports. CT+ODbL is okay for those, provided data from a) are kept. Richard convinced me that CT is not meant to be evil, and I can live with that. c) ODbL incompatible mass imports. Obviously these need to be removed. I have no power to change this. Mass imports were cities from wikipedia (place=*) and railway stations from around http://www.openstreetmap.org/browse/changeset/188101 187327 I hope this helps, and I'd like to see some reply, thanks, PavelHi, I admit that I'm pretty confused right now... Are you saying that you've changed your mind and are willing to agree to ODbL+CT, except for the changesets containing imports of incompatible data? That would be really great!
If this is that case, I personally volunteer to help track down your changesets containing the incompatible imports.
The only two are the wikipedia imports of places and railway stations, is this correct?
Pavel Machek wrote:Hi! So lets start by saying that I don't like ODbL and I hate CT. There are three classes of data I uploaded to osm: a) Hand created data, most important paths in the woods. CT+ODbL, is okay for those. b) ODbL compatible - mass imports. CT+ODbL is okay for those, provided data from a) are kept. Richard convinced me that CT is not meant to be evil, and I can live with that. c) ODbL incompatible mass imports. Obviously these need to be removed. I have no power to change this. Mass imports were cities from wikipedia (place=*) and railway stations from around http://www.openstreetmap.org/browse/changeset/188101 187327 I hope this helps, and I'd like to see some reply, thanks, PavelHi, I admit that I'm pretty confused right now... Are you saying that you've changed your mind and are willing to agree to ODbL+CT, except for the changesets containing imports of incompatible data? That would be really great!
If this is that case, I personally volunteer to help track down your changesets containing the incompatible imports.
The only two are the wikipedia imports of places and railway stations, is this correct?
If this is that case, I personally volunteer to help track down your changesets containing the incompatible imports.Thanks!The only two are the wikipedia imports of places and railway stations, is this correct?I think so. Pavel
If this is that case, I personally volunteer to help track down your changesets containing the incompatible imports.Thanks!The only two are the wikipedia imports of places and railway stations, is this correct?I think so. Pavel
Otevře váš e-mailový klient. Odpovědi pak sledujte zde na webu.