New SMF Coding Discussion Board

[The Wizard]

Hello:

The following is a suggestion only, and you all may decide to implement it or not.

Break up the "SMF Coding Discussion" board into two different boards -

• SMF Coding Discussion for Version 2.0 and up
• SMF Coding Discussion for Version 1.0 and up

The only reason I even suggest this is that almost every user who post there is in need of some kind of coding help and nobody reads the rules on how we can help you quicker. I have worked in several department stores during my career, and the most common question is where is the bathroom - even though there was a 50 foot wide sign hanging above my head saying bathroom and a big arrow. In short the public is dumb or they want to act that way.

So instead of the support people, developers, etc having to ask what version of SMF are you using why not just make it easy and split the "SMF Coding Discussion" section in two? I know you all are thinking that's allot of work putting the posts in the right places - answer - don't. Just move the first 50 or so threads and leave the rest as the new "SMF Coding Discussion for Version 1.0 and up" board. Anybody we have missed will catch on quick enough and repost in the new board. Your going to have to do this at some point anyway when you do away with 1.0 xxx support. Why not start the process now and save yourself work later on and in the process save the support people, developers, etc one more headache?

Wiz

Mod edit: Please do not add space which is not used.

[Arantor]

Given that people still don't give their version (and will be less inclined to do so with this) it seems like a waste of time and organisation to do so - and more boards = more confusion for users, even if they seem more logical.

As it is, a lot of people don't know whether to post in their respective support board or in the coding discussion board - and remember that 2.1 is coming 'soon' so you'd need at least 3 boards, not 2.

[NanoSector]

As it is, a lot of people don't know whether to post in their respective support board or in the coding discussion board - and remember that 2.1 is coming 'soon' so you'd need at least 3 boards, not 2.

Since 2.1 doesn't contain *mayor* code changes I think a board names 2.x and 1.x will be enough.
There are some advancements in 2.1, sure, but if people report their version we can provide the advancements when available.

[Arantor]

If people report their version, there's no need for the board separation in the first place...

[NanoSector]

If people report their version, there's no need for the board separation in the first place...

I think there is a point in it, 1.x and 2.x have an almost completely different code structure so anyone looking to provide support to 2.x code wouldn't need to go through 1.x support requests. I, myself, have never bothered learning how 1.x works so when I'm handling support things here I find all the 1.x issues a PITA.

[emanuele]

I think there is a point in it, 1.x and 2.x have an almost completely different code structure

mmm...no, not really.
Large parts of the code is still exactly the same.
Something is changed, of course, but not as much as you may think.

[Kindred]

Also, we just went though reorganizing and merging extraneous boards....   So, splitting that board apparat would seem to be contraindicated.