let's get this organized

[zantetsuken]

i like both ideas not to get into anything.. i think everyone both have good ideas.. i believe that having separet places would be a good idea and having them @ the same site is a good idea too.. just lookin at some of the post's @ boardmod and yabb people are going to get confused no matter what u do .. some people just cant read   . and btw yabb is the greatest no matter how many scripts or programming lang's its in keep up the good work fellehs  

[iamdamnsam]

I agree with Dave 100%

[irbrian]

For the record, I think that Dave really knows what he's talking about.

Here are the most important highlights from my perspective (in no particular order, with my personal comments in italics):

1) There MUST BE a web-based YaBB SE Mod Community. There is no better way for Board Admins to search through all available mods and find exactly what they need, and keep track of which Mods have just recently been released. I also think that this community should include step-by-step Mod-writing tutorials... and if someone gets around to it, an explanation of YaBB SE variables and files would be great also.

2) [CV]XXL or whatever his name is will probably have a part in designing and administering the new community, which will be 100% seperate from YaBB's own BoardMod. Regardless of YaBB's affiliation with Xnull or lack thereof, YaBB SE's PHP-MySQL coding is VERY different from YaBB's, as is the whole Mod'ing gameplan we're discussing here, and imho they MUST be seperated for clarification.

3) The MUST BE a "Mod Team" that would be exclusively responsible for collecting, testing, adjusting, and rewriting each and every Mod for 100% Compatibility, Quality, Compliance with the installation procedures/rules/whatever, and Consistency in design and functionality. The SE Mod Team needs to work closely with each other and be very responsible about testing and then posting Mods ASAP, to allow the progression of YaBB expansion to proceed at a quick enough rate.

Anything I'm missing?

[Matt Siegman]

damn, you are good

[irbrian]

I should add that I think this should be a top priority for those responsible for the YaBB SE project, and anyone else who's concerned! I move that we "elect" a SE Mod Chairperson

[Shoeb Omar]

if we do: i elect XXL

[curious]

@omario

Before you can elect XXL you have to first nominate him.

So I nominate [CV]XXL for becoming president of all modders.

[irbrian]

I guess we can assume Omario is a second?

In which case, I nominate Dave. Is there a second?

[Shoeb Omar]

nah - dave's waaaaaaaay too busy to do it from what i know of him...

so i elect/nominate XXL

[Jeff Lewis]

Nice to know all of you have decided on a course of action for us  

[Omar Bazavilvazo]

Heh, this topic is fun

Anyway, shall we first decide which caracteristics must have a mod? I think the actual method of boardmod is good, but lacks some things (i love boardmod btw).

For example, a mod _must_ store all messages in vars instead of hardcode (that's design, not infrastructure, I know) so it can be changed easily for all languages supported.

And for example, and "optional" file tag _I think_ is useful. many times i installed a mod, and had to add some lines to spanish.lng because mod was written in english... maybe an autodetection of in which language is yabb, and then install in that language? (overwriting all .lng that exists maybe?)

and an automatic process to copy files?? hmm.. maybe a merge btw packages & mods? (copy file, change some code -without making conflicts for other mods-)

well, just an idea

[Matt Siegman]

That is what the mod team would do, a program can't do something that advanced

I elect (and nominate) myself to be Mod God

[irbrian]

Lol.. well, whomever, just so long as there is one, Matt. I'm glad we all (so far) seem to agree on this course of action. I'm looking forward to seeing Great Mods come down the line as SUPERB and COMPATIBLE Mods!!

Where will they be posted, though?

[irbrian]

I would suggest that the Mod Team (whenever its created) ought to come up with standard methods to be used in checking Mods. For example.. they should be required to add a comment before and after any code that is Added, Changed, or Removed.. and be required to accurately document in Detail each step they take to adjust the mod for compatibility and stability.

Along the same lines, though, it sure would be nice if Mod writers would do the same thing, so that the Mod Team knows where to start! Especially if the Mod Team is required to do so!