Subj : exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg
To   : Andre
From : Digital Man
Date : Sat Apr 16 2022 01:06 pm

  Re: exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg
  By: Andre to Rob Swindell on Sat Apr 16 2022 07:45 am

 >   Re: exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg/
 >   By: Rob Swindell to Git commit to main/sbbs/master on Sat Apr 16 2022
 > 12:52 am
 >
 >  RS> If a sysop wants to prevent new users from using an email address of an
 >  RS> existing user, they can set SCFG->System->New User Values->Question
 >  RS> Toggles->Force Unique E-mail/NetMail to "Yes".
 >
 >  RS> This partially addresses issue #127, at least for the terminal server.
 >
 > Do you think there's any value in tracking todo/issues for when the wiki
 > needs an update to match a feature change?

Sure. "Update docs" is a work-flow step I often miss or put off, especially when I already put a lot of time into word-smithing and formatting the online help text in SCFG (as in this example).

 > Aside from me reading every commit and then writing it down somewhere that
 > an update is needed, I'm not sure it would get done. It seems like some
 > created item (gitlab issue? separate project?) or a reassigned issue before
 > close might help make sure things stay up-to-date.
 >
 > Or maybe in your experience with Sync it's just additional overhead and just
 > one more area where things get out of date or pile up.

Probably a new issue to be created whenever someone realizes/notices that a page is out of date. I do like to close issues with commits to the source code, so I wouldn't want to change that work-flow. GitLab also has a built-in wiki which I haven't used yet. Perhaps it has some better integration with commits we could utilize.
-- 
                                            digital man (rob)

Rush quote #63:
He's got a problem with his poisons, but you know he'll find a cure
Norco, CA WX: 65.0øF, 59.0% humidity, 6 mph S wind, 0.00 inches rain/24hrs

.