• exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg/

    From Rob Swindell@VERT to Git commit to main/sbbs/master on Sat Apr 16 00:52:06 2022
    https://gitlab.synchro.net/main/sbbs/-/commit/fb43daf5a9764fa661a28dcf
    Modified Files:
    exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg/scfgsys.c src/sbbs3/text.h text_defaults.c
    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.

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Andre@VERT/RDOMENTR to Rob Swindell on Sat Apr 16 07:45:29 2022
    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.


    - Andre

    ---
    Synchronet Radio Mentor BBS - bbs.radiomentor.org
  • From Digital Man@VERT to Andre on Sat Apr 16 13:06:54 2022
    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

    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?

    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.0F, 59.0% humidity, 6 mph S wind, 0.00 inches rain/24hrs
    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Andre@VERT/RDOMENTR to Digital Man on Sat Apr 16 15:50:53 2022
    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.


    - Andre

    ---
    Synchronet Radio Mentor BBS - bbs.radiomentor.org
  • From Digital Man@VERT to Andre on Sat Apr 16 14:28:08 2022
    Re: exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg
    By: Andre to Digital Man on Sat Apr 16 2022 03:50 pm

    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.

    Yeah, I like that we serve doku wiki via Synchronet's own web server (gitlab uses nginx) and I have the user authentication tied into Vertrauen's userbase, so my preference is to keep using doku too.

    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.

    Well a separate project on gitlab.synchro.net just for the wiki issues/todo items isn't a bad idea, for sure.
    --
    digital man (rob)

    Sling Blade quote #3:
    Karl (re: killing Doyle): That second one just plum near cut his head in two. Norco, CA WX: 66.7F, 54.0% humidity, 6 mph SE wind, 0.00 inches rain/24hrs
    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From deon@VERT/ALTERANT to Andre on Sun Apr 17 10:30:24 2022
    Re: exec/load/sbbsdefs.js src/sbbs3/newuser.cpp sbbsdefs.h src/sbbs3/scfg
    By: Andre to Digital Man on Sat Apr 16 2022 03:50 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.

    While I havent explored it in detail - you (Rob) may be able to open an issue via an API call, when a commit is received (on master for example) - via a commit trigger?. And likewise, when a commit is done to the wikipages, it can auto close the issue if it's referenced in the commit message of the wiki update.

    I can see it getting annoying though, because you'd probably want to suppress a document update (ie: issue creation) to some commits (eg: commits that fixes a bug but doesnt change functionality). That might be addressed by having commits needing a document update going to a particular branch before ending up on master.

    Just spitballing here - I'm sure it's possible with automation but might be overly complex for a little BBS project...


    ...

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
  • From Tracker1@VERT/TRN to Rob Swindell on Mon May 2 19:17:07 2022
    On 4/16/22 00:52, Rob Swindell wrote:
    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.

    Sweet, was doing this via script... actually using email address as a
    login option and to trigger newuser creation.
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    Synchronet Roughneck BBS - roughneckbbs.com