sparhawk
-
Posts
21465 -
Joined
-
Last visited
Posts posted by sparhawk
-
-
Bottom line: I don't think it's really something to worry about.
If this is not clear we really can get into trouble. And I don't want the project to go down because of such a small detail.
And considering the reaction of BlackThief in thies thread, it is fairly obvious that this is not clear to everybody.
Therefore I would suggest that you [Fingernail] put this into the project info forum so that everybdoy knows whats up. And you should also inform each new member of that.
-
I think it means anyone can use them. But it would only be polite to ask, really. We can ask that without legally demanding it (obviously we have no control over what people do), but we can politely ask for recognition, etc.
Nobody has to ask or acknowledge you. If you put it under GPL then you give up most of your claims on the stuff that you submitted. And that's exactly why EVERYBODY working on the project has to be aware of that BEFORE he starts submitting files. Once they are submitted they are assumed to be under GPL and we should make this clear to everybody. That's the job of you as a project leader.
Another thing is, that we should get a file for every file that is submitted, that the submitter is either the copyrightholder and can do as he wishes with the file he submitted, OR that he has gained permission from the copyright holder to submit it to our project and it can indeed be put under GPL.
For this it is also important to use a CVS system (not neccessarly CVS but *A* CVS-like system) in order to keep track of who submitted what. In case of copyright infringment this is our only defense.
Since we can not allow everybody to have write access to CVS (at least I wouldn't recommend it) we should select two or three people with write access and everybody has to submit files to them. The job of these guys is to look through the submission for coding standards and probably to check if the code looks ok and to make sure to track who submitted it.
For example in Wine or wxWindows they have a seperate mailinglist for sending in patches and then once a day they are submitted to CVS.
-
hm, what does "are released for free" mean ?
can everybody use our textures, models and sounds in his mod or whatever he does ??
or do you just mean, that we can't sell them ?
GPL mean that EVERYBODY can use it. They are not allowed to seel it or sell derivative work from it, but they can use it in a commercial product. If you don't like this then now is the time to leave the team. That's exactly why I raised this subject NOW instead of when we are finished.
If they are using it in a commercial product then they will have to make this also open source. Or at least the part that contains the GPLed stuff.
-
My system specs:
AMD Athlong XP 2000+
512MB DDR (Semi-soon to be updated to 1GB)
Geforce 4 TI 4200
SB Live! Value
Gentoo Linux running kernel 2.6.7
I can set up a mantis system with all the catagories and stuff if you provide me with a place to set this up. (I think mOdE might be willing to host it, i'll ask him when I see him.) But I think you guys should start building stuff first. It's too soon to set up a bug reporting system as of yet.
Catagories should be something like,
Gameplay, Map, Sound, GUI, Display.
But it is not to soon to think about it. If we have already code to test then it is to late to set it up. At this time we should have a WORKING testenvironment and not only start to think about setting it up.
And even if you have it up and running and don't use it for some time now. So what? We will know that it is there when we need it.
-
All mods that are made are under the GPL, General Public License.If you make a mod for an ID Software game you HAVE TO release it for free, no questions asked.
That's perfectly fine for me, and what I really wanted to aim at.
The question is if all the other members and the project lead is aware of this. What about models, textures and sounds and other stuff beside the code itself?
I will download this and take a look at it.
-
I realise now that, sorry, I'm not a 24-hr admin, I tried my best to make team-members team members, but you and Renz slipped the net (too late registering of course
). Anyway, I agree with the design document thread, but hadn't considered game design. Alright, I'll remove the lightgem board too. Art boards will remain, I like the classifications.Good.
and a new board for SFX. I'll make the design document section read-only, and I'll make a 'team issues/general' board.ok. So we should discuss design in the general board? Well, depends on how much that will need, otherwise it will be good to create a design discussion board as well.
I'm wondering about the special fx board - this is a mixture of art and programming, mostly involving the .mtr files, which the texture artists should learn to deal with anyway. But if you are really stuck on this, then I'll make one of course.Sound good?
Sounds good to me. If traffic grwos to much we can still extend it anyway.
-
Since we started with this project I haven't heard anything about which license we will use. This is IMO quite an important decisision, as some memebrs may not want to use one license modell while others may and still others don't care. As we have seen in the case SCO against IBM this issue is NOT so trivial and can potentially affect everybody here. This is also important to protect our project against copyright claims or others ripping off. So I would suggest to discuss this BEFORE we start to create to much content and afterwards being dissatisfied with the decisions.
One question: If we code for D3 what resctrictions are there for our mod? As with DromEd we had the restriction that all FMs had to be free and were not allowed to be commercially used without permission. I expect that a similar restriction exists for D3 mods (but then again it may not) so this already might affect the decision on which license model we can use.
There are also other considerations, because if we choose i.E. GPL or any other open source compatible license model (there are several of them) we can register for services like webhosting, shell accounts, CVS services and others, which may not be available for closed source developments. I think it is better to use such existing services instead of relaing on private resources, because this gives us a major advantage.
If there ever is a break in the private resources we will have to find new resources where to translocate them. If we use public resources, everybody has access and we don't need to worry over uptime or accessability or support. That doesn't mean that we can NOT use private resources as well, but it gives us many advantages for free and serves as a seamless backup.
If this is comptable with D3 restrictions therfore I would suggest to use GPL/LGPL or a similar license model and I think there is also an Open Content license for art so we could put this there as well. Since this is a community project and we want to use community resources as well, I think this would be a fair decision.
One reason why I also want to have this clarified is, to protect our work (I already have seen such a thing happen). If i.E. somebody writes a good AI code and suddenly decides that the code is so good that he no longer wants to offer it for free, then we are screwed. In this case we woould have to start from scratch and rewrite all this code from new. I don't want something like this to happen, so we really should decide an a license early on, so everybody knows what he can expect or not expect from the project.
Of course this is also true for art (images, sound, models, levels, etc.), despite me writing mainly about code because I'm a programmer myself.
-
Edit: Actually, it'd be a good idea if everyone making textures (which I think is just Blackthief, possibly Alexius, and I) were to get together and started organizing everything. It'll mean alot less work on down the road if we keep everything in order and pack the textures the same way and whatnot.
Actually this is exactly the reason why I said we should synchronize our tools.
-
Since I can not post this in the news/announcment I post this here, because I think it might be interesting for us.
Here you can find a project which does a similar thing like we do.
They convert System Shock 2 to Doom 3. Maybe we can have some synergies with this project. Don't know, but I thought it is interesting for some of us. -
Of course I know that. I'm just saying that should this ever come far enough that it needs testing. I'm willing to do so if I have time.
Nevertheless you can already think about what you can test and how and also how to report it.
Performance, Art, Map glitches, mismatching objectives, Gameplay, Sound, etc.
Of course it would be good to know what system you have. It doesn't help if we have 30 testers all with similar system specs. This information can probably be posted in the (hopefully) soon to be created information board where we can store non-discussable project information.
-
I've already got a great idea for a map, and it'd be cool to have a good place to talk about it at.
Somehow my posting was posted with the wrong button. Whatever "Reporting" means on this board.
Yes. Otherwise it tends to get everything into the general board and clobber it with discussions only a few are interested in. This just makes it harder to read.
We should create a board for every major aspect of the game. I think I listed all of them, but if somebody identifies another one, we shold mention it as well.
-
We need the following boards:
A general discussion board
Design issues
Development related discussions (not programing but in general)
Programming (general)
AI
Sound (programming)
Soundeffects (for the soundengineers)
Special Effects (Water, particle etc.)
Art (Textures, images, etc.)
Level creation/Plot/Objectives (for the level designers)
Modelling (Characters)
We DON't need a seperate Lightgem board.
It's either art or programming.What would be a good idea is to have a read-only report board. This should contain:
Design decisions (no discussions only the conclusions from the design discussions when we agree on something), Allowed tools (or list of tools so we know what is available), A list of available services (like FTP, Webpage, IRC information, CVS server information, etc.). This board can also get links to concept Art for easy reference as soon as we agreed on something and we don't want to change it anymore. So for example, if we agree on a final image for the lightgem, we should post it there so everybody can see it and can easily find it.
Another read-only board would be good as announcment board: This should include who is working on what, if a new release has been released, weekly(?) project progress, new members and other stuff which is not open for discussion.
Wanna Logo?
in Art Assets
Posted
Personally I think the " glowing" looks more thiefy.