>1) I am not too woried about 3.1.a, it sounds to me like a subset of >right that the GPL gives them anyway Interesting way to think about it. I wonder if that answers Ivanovic's questions.
>2) I am a bit more worried about 3.1.d : obligation to provide >technical support... would we be obligated to monitor the desura >forums or something ? Games can optionally create their own subsections on Desura's forums, so no we won't have to. >3) you didn't mention it, but do you intend to make wesnoth free ? I >assume that's the case, just making sure... Yes it will definitely be free. Money would make this entire thing ten times more complicated. >4) I would rather have wesnoth inc register to desura and then have >you be our desura maintainer rather than have you personally open an >account... I am not too worried about you becoming MIA, but we had >problems like that before (DNS, IPhone) and I think it's a good habit >to have all wesnoth related credentials be held by wesnoth and >"lended" to the one doing the actual job The game is owned by a "team-wesnoth" group that Turuk started on Moddb years ago. I had to ask Moddb for access to it. Moddb, Desura, and Indiedb are all sharing the same database. Anyone with a Moddb account can be added to this group. Just ask me. >5) the desura code we might need to incorporate doesn't seem to be GPL >compatible (3.1.g and 2.4) do we need to include such code, or is it >optional ? this question might become irrelevant if/when the client >becomes GPL, but that's not sure (it's probably DRM related code for >apps that need such thing) It is optional, and isn't even in use by other games that I've seen. I don't even think it's completed. I don't see any section of my profile to check on the stats or achievements that the API is for. There's no documentation for it either, just a contact link. >6) could 3.1.h.i.b become a problem ? We're already following all the laws for distributing the game on wesnoth.org aren't we? >apart from that, I'm a bit curious about the Desura API... what does >it provide, what is it for etc... It's supposed to be for tracking of stats and achievements/trophies. >IMO the part 'ii' does not really apply since this >is probably a clause for programs with monthly fees like eg many MMORPG. >Wesnoth would possibly one "game" per series and that's it, so subscriptions >would not happen. I think it's for when Bob buys game X, game X stops supporting Desura, Bob can still play game X as long as he still abides by the EULA. >3.1.e) This one states that once we enter the agreement we *have* to continue >supporting our binaries with *all* patches and updates in a very timid manner >(7 days). So what happens if I release when gambit is on 3 weeks holidays? Assuming I'm not in the hospital or dead this shouldn't happen. But the worst case scenario for breaking anything here (licensing issues excluded) is that we get removed from Desura. >3.1.d) OUTSCH! That one is possibly really problematic. It is about the >support and I don't know how we can possibly handle this one. We have to >promptly respond to comments, queries and complaints (which we already do in >our own forums and bug tracker) but there is no specification where those >comments reach "us". So they probably think about their forums and boards, >meaning that we would have to monitor an external source for issues. We also >have to provide tech support which can be problematic. Is providing tech >support (in weird cases!) to say "then don't use this program, your system is >simply borked!"? We also have to issue patches (though we basically do this >during our normal development) I think we already satisfy this one with what we're doing. And we don't have to create one of their forums. If the rights they want are already granted to them by the GPL then do we really have to "relicense"? The license we "grant" them would be the terms of the GPL that we already grant everyone who downloads Wesnoth? _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
