If a sysop wants to prevent new users from using an email address of an existing user, they can set SCFG->System->New User Values->Question Toggles->Force Unique E-mail/NetMail to "Yes".
This partially addresses issue #127, at least for the terminal server.
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
If a sysop wants to prevent new users from using an email address of an existing user, they can set SCFG->System->New User Values->Question Toggles->Force Unique E-mail/NetMail to "Yes".
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?
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.
Re: exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg
By: Digital Man to Andre on Sat Apr 16 2022 01:06 pm
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.
The only thing that made sense to me in my brief thinking about it is the manual creation of a new issue (in a separate project?), since AFAIK there's no way to create an issue with a commit. Just website, email, url, etc.
I certainly don't see any value on a project like this to do some sort of docs-like-code or something like that, which leads me to...
GitLab also has
a built-in wiki which I haven't used yet. Perhaps it has some better integration with commits we could utilize.
Aside from having proper markdown, managing wiki pages like code files, and being able to use git to manage the wiki, I don't see any features that it offers beyond doku.
I don't have any great ideas, much less a solution. Probably not something that matters that much, given the context of the Sync project.
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.
The only thing that made sense to me in my brief thinking about it is the manual creation of a new issue (in a separate project?),
since AFAIK there's no way to create an issue with a commit. Just website, email, url, etc.
Log Message:
Implement duplicate new-user email address checking (optional)
If a sysop wants to prevent new users from using an email address of
an existing user, they can set SCFG->System->New User Values->Question Toggles->Force Unique E-mail/NetMail to "Yes".
This partially addresses issue #127, at least for the terminal server.
| Sysop: | MarisaG |
|---|---|
| Location: | South San Francisco, CA |
| Users: | 81 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 153:03:11 |
| Calls: | 1,430 |
| Files: | 7 |
| Messages: | 22,125 |