Re: [crossfire] Platform statement
Happy new year everyone! Actually, I think I'm over-reaching here. All considerations of *how* to deal with gameplay, especially game mechanics, are just IMHO and suggestions. I'll say what I think, reply on threads when asked, but in the end, go with whatever the coders decide :-) No. It's not up to coders/developers to decide. It's up to the gameplay leader to decide game mechanisms. And no gameplay leader is why no one decides anything on the type of game we have, why so many questions aren't replied to, so many things are left as an exercice to the first one to actually move (meaning no coherence yet again). Remember: technical stuff is there FOR THE PURPOSE OF GAMEPLAY AND CONTENTS. Not the other way around. Content and gameplay should state requirements (features, ...) and have a feedback from the technical part about feasability/delays. So to sum up: - content leader = handles the story part of the game, maps that are ok or not story wise, and such - gameplay leader = handles combat mechanisms, has a say on quest rewards and such, works on non combat stuff, ... - technical leader = ensures needs of content/gameplay leaders are met, and maybe planifies development and such (of course it's not a total division, everyone can make suggestions - but at the end of the day the leaders ACTUALLY DECIDE on their domain) And we could obviously add interface/client leader, too. Nicolas PS: to reply to someone's mail, no, I don't want to be technical leader as long as we don't have a gameplay leader - and even so, I'm not sure I'd accept. -- http://nicolas.weeger.org [Petit site d'images, de textes, de code, bref de l'aléatoire !] signature.asc Description: This is a digitally signed message part. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Release 1.12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lalo Martins wrote: All right... with the help of crossfire traffic and svn, I compiled a list of what's in the trunk and branch. http://wiki.metalforge.net/doku.php/trunkbranchchangebreakdown I've added about 10 new points of difference to the wiki page. During the next couple of days, I will go through all the maps again and post the any more differences I find between Trunk and Branches/1.x There are some (infamous) cosmetic changes I've made and will merge back in to Branch which should not have an impact on functionality. Lalo - How do things look for the Jan-20th target date? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJbPGghHyvgBp+vH4RAhwoAKDP6AOKAonS/W7wA4fDpKzS4YhfzwCgpxOD IXUjgtK7f2FSaYRvBWM4E8U= =CQzs -END PGP SIGNATURE- ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Release 1.12
quoth Rick Tanner as of Tue, 13 Jan 2009 13:55:12 -0600: Lalo Martins wrote: http://wiki.metalforge.net/doku.php/trunkbranchchangebreakdown I've added about 10 new points of difference to the wiki page. During the next couple of days, I will go through all the maps again and post the any more differences I find between Trunk and Branches/1.x Thanks! There are some (infamous) cosmetic changes I've made and will merge back in to Branch which should not have an impact on functionality. Oakdoors? :-) Lalo - How do things look for the Jan-20th target date? Well. Actually cutting an alpha is about one day's worth of work for me, so meeting the target date isn't hard. The reason I set the date so far was, rather, to give other people time to act on it. If anyone wanted some particular changes in the release, or out of the release, they had time to speak up. And I also was hoping to see a decision on whether there will be a corresponding code release, although the lack of any comments about it does mean there won't ;-) at least not in the same timeframe. I'm not saying the release is easy work, I'm just saying cutting the alpha is the easy part. Then the real work begins -- lots of testing and fixing for the March 1st target. best, Lalo Martins -- So many of our dreams at first seem impossible, then they seem improbable, and then, when we summon the will, they soon become inevitable. - http://lalomartins.info/ GNU: never give up freedom http://www.gnu.org/ ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
[crossfire] Leaderships(s?) (was Re: Platform statement)
quoth Nicolas Weeger as of Tue, 13 Jan 2009 19:17:18 +0100: - content leader = handles the story part of the game, maps that are ok or not story wise, and such - gameplay leader = handles combat mechanisms, has a say on quest rewards and such, works on non combat stuff, ... - technical leader = ensures needs of content/gameplay leaders are met, and maybe planifies development and such PS: to reply to someone's mail, no, I don't want to be technical leader as long as we don't have a gameplay leader - and even so, I'm not sure I'd accept. Okay, sorry, but this is not going to work. For years, we had just one project leader. That worked in its time, then as Mark got busy with real life, things slowed down. Recently it has been proposed to have separate leaders for code and content. A volunteer appeared for code, but then the need for a content leader was played; quite reasonably, one volunteer claimed he didn't want to go far as code leader unless there was a content leader. So I volunteered to take the job. But now there's a third position that has to be filled as well? And even then we may find we still don't have a coding leader? Come on, people, we're getting nowhere this way. At this point in time, I don't think we even have enough people working on it to be talking about leadership. These are the important questions that need to be asked with regards to people resources: - Who will make content releases? (me, I guess.) - Who will make server releases? - Who will make gtk client releases? - Who will make java client releases? - Who will fix content bugs? - Who will fix server bugs? - Who will fix gtk client bugs? - Who will fix java client bugs? Only after those are answered, are we prepared to talk about adding new content, new features, or even massive rewrites. Oh sure, we could just declare 1.x abandoned; but considering all the cool stuff we have in svn, that would be a waste and a pity. All right then, to Gorokh with this. Here's my new proposal. Short term: I'm naming myself release manager for the 1.12 mini- project. I'll get a release out, code and content. The extra work in carrying the code release through childbirth may (probably will) mean missing the March 1st deadline, but I'll give it my best. I will *not* attempt to release clients, though. If someone wants to coordinate a client release, I'd be very happy and lend my support. (Kevin?) Medium term: I think the best thing to do, as far as separation of work is concerned, is to view this as a number of separate sub-projects: - Server (code and content) for 1.x - GTK/glade client (based on v2 I assume) - Java client - Gridarta for CF - Server (code and content) for 2.x (possibly later) Each of those should have someone taking responsibility. (Gridarta already does, and the Java client unofficially does too.) The necessity of a master overseer over the whole project is arguable; I think the sub-project leaders can work things out between them. But for now, let's concentrate on a release. My hope is that the work involved in doing that will wake us up, and that the right people for each position will rise up in the process. Frankly... this whole thing is silly. Free/Open Source projects aren't representative democracies; it makes no sense to be arguing about who will lead what when there's work to do and nobody to lead. Let's go get this release out. Please. best, Lalo Martins -- So many of our dreams at first seem impossible, then they seem improbable, and then, when we summon the will, they soon become inevitable. - http://lalomartins.info/ GNU: never give up freedom http://www.gnu.org/ ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Leaderships(s?) (was Re: Platform statement)
I have not enough SVN access to do a release. It feels like after all this time waiting without help to get my client work out its only natural to not flip out over someone else' urgency of the day, but, I was ready for a release a long time ago... no point in wondering what I am willing to do. I've probably made that quite clear to anyone who felt inclined to notice. That said, I have a real life, kids, high urgency project that is running over two years old now and ready to pop in a month or so... Not a lot of leftover bandwidth for thinking CF with that going on, and I suspect I'm not alone there. I'll be glad to crank up the scripts and chunk something out. :-) Have a good day... ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
