Re: [vassalengine-devel] Vassal Forum
Brought to you by:
rodneykinney,
uckelman
From: Ben S. <bs...@ne...> - 2007-09-30 16:15:56
|
But if we only have one section for bugs, that means the dev team, which doesn't care about modules, will have to sift through the module bugs too. And the module designers who do not care about the engine, are going to have to read the engine related bugs. And the users who do not care about all the technical code talk related to bugs, will have to sift through all of our boffin talk! -----Original message----- From: Joel Uckelman uck...@no... Date: Mon, 1 Oct 2007 02:10:23 +1000 To: developers' list for VASSAL vas...@li... Subject: Re: [vassalengine-devel] Vassal Forum > Thus spake "Ben Smith": > > I've put my hand up to manage the forum so would take care of moving any stra > > y posts to their rightful locations Tim. I just whipped up those headings ad > > -hoc so they're far from fixed in stone! With PHPBB each will be accompanied > > by a short description also, so users shouldn't have too much difficulty fig > > uring out what goes where. Obviously if some sections are under-used they wi > > ll be dissolved. > > I think Tim's point was not about underdescription, but rather that even > with a full description, the user might not be able to tell whether he's > faced with a module or an engine bug. Maybe there should be one forum for > bugs, instead of three. > > -- > J. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > vassalengine-devel mailing list > vas...@li... > https://lists.sourceforge.net/lists/listinfo/vassalengine-devel regards Ben |