Re: [Warzone-dev] We got the OK for 9 maps.
On Thu, Oct 20, 2005 at 03:09:10AM -0400, Qamly wrote: Good news! RBL-4NiK8r has given us permission to include his maps in the package! Did he agree to publish them under some liberal license or simply distribute them without modifications? regards fEnIo -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
Re: [Warzone-dev] Comments about the project.
Per Inge Mathisen wrote: As for maps, what maps do we have permission to distribute, apart from the standard ones? - Per Have you guys asked lav_coyote? his mars maps are rather good. ___ Warzone-dev mailing list Warzone-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/warzone-dev
Re: [Warzone-dev] Getting this project back on its knees
On Thursday, 20 October 2005 at 1:12, Qamly wrote: On 10/19/05, Christian Ohm [EMAIL PROTECTED] wrote: On Wednesday, 19 October 2005 at 1:30, Qamly wrote: On 10/11/05, Per Inge Mathisen [EMAIL PROTECTED] wrote: On 10/11/05, Christian Ohm [EMAIL PROTECTED] wrote: Speaking of access rights, for SVN at least, that is given to people Now you speak as if you are leading the project. Hmm.. Mind you, I'm OK with that, if you want to do it. But I was under the impression nobody wanted to do it, and I think it needs to be done (at least until a few guidelines are established). who can show they can do good patches, we can't just give SVN access to everyone who asks without knowing what they will do. But we can give access to people that have sent useful patches, and then just trust them not to misuse their access. If you can't trust people to do that, why even make them project members? Having access control is a form of control for me (something I was accused of wanting to exert). Yes, I said if they have good patches, they should get access to svn. However, granting anyone access rights on trivial patches shouldn't be done IMO. I am in the side of prove to us that you can do a somewhat good job with the patches, then they should ask for access, and then the team member decide. That's what I meant - not SVN access for everyone who sends one patch. What's wrong with removing those who don't do anything? If they want to, they can be readded easily. The only thing wrong is some people will take that the wrong way. I's aks them beforehand - like Hey, you are a member of the Berlios project, but haven't done anything there lately. As we are currently trimming the memberlist (it led some people to believe that we don't get done a lot for having 17 members), can we remove you, if you don't want to work on warzone in the near future? If you want to work on it later, just ask us to readd you. Yes, we need more people to do action (ie code/test/gfx work) than Just to reiterate: That's what I think the current course won't bring, and my proposed changes will. And I hope you are wrong. It seems things have started to change (and that's really all I wanted to achieve). ___ Warzone-dev mailing list Warzone-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/warzone-dev
Re: [Warzone-dev] Re: [Warzone-svncheckins] Revision 326: Commit in trunk/prerelease/branches/crossplatform (29 files)
On Thursday, 20 October 2005 at 1:22, Qamly wrote: On 10/19/05, Christian Ohm [EMAIL PROTECTED] wrote: On Wednesday, 19 October 2005 at 7:11, Victor Qamly at BerliOS wrote: Note, you need new data set which I will release shortly (for menu). Why don't you do this in the branch, and change the data accordingly? Why do people have to wait for a new data release that will happen at some undefined time in the future? (Apart from the question Why should all changes on the branch be ported here instead of doing stuff there?) Do what in branch? Upload the dataset? You *can* still use the original .wz set I have, but it will have 'error text' in the menu option. Apply your menu patch to branches/crossplatform, and change the data there accordingly. -- I'm not tense, just terribly, terribly alert! ___ Warzone-dev mailing list Warzone-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/warzone-dev
[Warzone-dev] Authors.txt --PLEASE READ RESPOND!
warzone-dev@lists.berlios.de PLEASE modify the attached file, and fix whatever is wrong/missing. This is what I have so far. If you want changes, then MODIFY THE FILE, and send that back to me. And yes, I know some people did nothing for the project, but are still listed. If you do not think they should be here, then fine, delete the line in the FILE, and send it to me. = Original game developed by Pumpkin Studios, and published by EIDOS Interactive. The Warzone 2100 GPL Development Team (in no particular order): Ben Russon grizzly_37Admingrizzly_37 at users.berlios.de Kevin Maleckevin_010 IRC adminkevin_010 at users.berlios.de kim metcalfe kgmetcalfeWeb Designer kgmetcalfe at users.berlios.de Per I Mathisen sendaiDevelopersendai at users.berlios.de Roman C. tromanDevelopertroman at users.berlios.de Christian Ohm cybersphinx Developercybersphinx at users.berlios.de Rodolphe Suescun rodzilla Developerrodzilla at users.berlios.de Victor Qamly vqamlyDevelopervqamly at users.berlios.de Grim Moroe grimandmandy Artist grimandmandy at users.berlios.de Dion Mendelnoid Original Porter noid at users.berlios.de Adam Holland coppercoreTester coppercore at users.berlios.de Dennis SchriddedevurandomTester devurandom at users.berlios.de Denis Dupeyron charunebuilds ? charun at users.berlios.de Mike Gilmore chojun?? chojun at users.berlios.de Marcus Hasthast ?hast at users.berlios.de Henri Valtahenrivee ?henrivee at users.berlios.de Rage silentrage?? silentrage at users.berlios.de Original game developed by Pumpkin Studios, and published by EIDOS Interactive. The Warzone 2100 GPL Development Team (in no particular order): Ben Russon grizzly_37Admingrizzly_37 at users.berlios.de Kevin Maleckevin_010 IRC adminkevin_010 at users.berlios.de kim metcalfe kgmetcalfeWeb Designer kgmetcalfe at users.berlios.de Per I Mathisen sendaiDevelopersendai at users.berlios.de Roman C. tromanDevelopertroman at users.berlios.de Christian Ohm cybersphinx Developercybersphinx at users.berlios.de Rodolphe Suescun rodzilla Developerrodzilla at users.berlios.de Victor Qamly vqamlyDevelopervqamly at users.berlios.de Grim Moroe grimandmandy Artist grimandmandy at users.berlios.de Dion Mendelnoid Original Porter noid at users.berlios.de Adam Holland coppercoreTester coppercore at users.berlios.de Dennis SchriddedevurandomTester devurandom at users.berlios.de Denis Dupeyron charunebuilds ? charun at users.berlios.de Mike Gilmore chojun?? chojun at users.berlios.de Marcus Hasthast ?hast at users.berlios.de Henri Valtahenrivee ?henrivee at users.berlios.de Rage silentrage?? silentrage at users.berlios.de
Re: [Warzone-dev] Comments about the project.
- Original Message - From: Christian Ohm [EMAIL PROTECTED] To: warzone-dev@lists.berlios.de Sent: Thursday, October 20, 2005 9:47 AM Subject: Re: [Warzone-dev] Comments about the project. On Thursday, 20 October 2005 at 1:14, Qamly wrote: Seeing as your the only one left (active), I guess your first thought is correct, and nobody else cared--well besides that windows guy in the rts.net forums, and the people who e-mailed me. Do you know why they emailed you and not the list (or forums or whatever)? I guess they e-mail who they think is in charge of whatever platform. If you read most of my stuff, I guess you can say I was the 'windows' person in charge. I am also the most vocal on the mailing list. Or at least I was. If revision 400 needs data set 459, then it can get that specific version. Same with any branch that needs that specific set. Say we release 2.0.2.3 and then continue with changing all graphics to PNG. Now we find a bug in 2.0.2.3 where we need to change some of the data. How do you want to handle that? (Assuming, of course, that we keep all data revisions in SVN (and I think we should)). But there's one case where I think it makes sense to have a separate branch, and that's with new data. I.e. every source tree (branch... has the according data (based on the original, just with format changes etc.), and we have one data set in (e.g.) branches/new-data with new models, textures etc. and a note like This data set needs at least revision XXX. When we change something major, we would tag out a new version was my way of thinking. I just don't know how much space we have available, and I don't like wasting resources when we don't have to. We could make a release plan and add that to our homepage, so we have a handy list with all steps needed for a release. I'll look at that, and will add that later. Ok, sounds good. I do want 2.0.2.3 to be released ASAP, before the weekend is out though. ___ Warzone-dev mailing list Warzone-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/warzone-dev
Re: [Warzone-dev] Pre release version
- Original Message - From: Christian Ohm [EMAIL PROTECTED] To: warzone-dev@lists.berlios.de Sent: Thursday, October 20, 2005 10:41 AM Subject: Re: [Warzone-dev] Pre release version Well, anyway, I think we need some clean versioning scheme. The current 2.0.2.3 doesn't imply beta, while we still call it that. My preference currently is to continue with 0.XXX until 1.0 since with Warzone 2100 GPL as the name the confusion shouldn't be too great (especially since it'll probably take a while until we actually reach 1.0). I think that is wrong. There IS a 1.x version already. If we try to make another 1.x version, then we have more confusion. As I said in the other post, 2.x was made because we had a major change in NET code, that made it NOT work at all with the original 1.x game. This was done to prevent confusion. ___ Warzone-dev mailing list Warzone-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/warzone-dev
