Progress Report 2024-01-07: Difference between revisions

progress report for january 7th towards making wiki ready to publish
 
minor changes and additions
Line 1: Line 1:
i am making a progress report on all of the work i did to developing the wiki today. my goal is for this to be ready for launch within a week or so. without making any serious changes to wording can you fix inconsistencies or oddly worded sentences here that make it difficult for people i am managing to read. my goal is to make it obvious what they need to do and feel like it isn't too complicated to get involved
i am making a progress report on all of the work i did to developing the wiki today. my goal is for this to be ready for launch within a week or so. without making any serious changes to wording can you fix inconsistencies or oddly worded sentences here that make it difficult for people i am managing to read. my goal is to make it obvious what they need to do and feel like it isn't too complicated to get involved
```
<span id="what-got-done-prerequisites-for-launch"></span>
= What Got Done &amp; Prerequisites For Launch =
= What Got Done &amp; Prerequisites For Launch =


Line 16: Line 13:
** [https://wiki.rossmanngroup.com/index.php?title=MediaWiki:suspicious_URLs_detected_on_talk_page&action=edit&preload=MediaWiki%3Aabusefilter-disallowed suspicious urls warning]
** [https://wiki.rossmanngroup.com/index.php?title=MediaWiki:suspicious_URLs_detected_on_talk_page&action=edit&preload=MediaWiki%3Aabusefilter-disallowed suspicious urls warning]
** [https://wiki.rossmanngroup.com/index.php?title=MediaWiki:removing_stub_notice&action=edit&preload=MediaWiki%3Aabusefilter-disallowed removing stub notice as unprivileged user warning]
** [https://wiki.rossmanngroup.com/index.php?title=MediaWiki:removing_stub_notice&action=edit&preload=MediaWiki%3Aabusefilter-disallowed removing stub notice as unprivileged user warning]
* Creation of a [https://wiki.rossmanngroup.com/index.php/StubNotice stub notice] for incomplete articles
* Creation of a [https://wiki.rossmanngroup.com/index.php/StubNotice stub notice] for incomplete articles<span id="to-do---proper-rules-must-be-created"></span>
 
<span id="to-do---proper-rules-must-be-created"></span>
=== TO DO - Proper rules must be created ===
=== TO DO - Proper rules must be created ===


'''WE CANNOT HAVE AI GENERATED RULES. THIS IS ONLY A FIRST DRAFT WIREFRAME STARTING POINT AND MUST BE EDITED TO BECOME REAL, USEFUL RULES AND CHECKLISTS.'''
'''WE CANNOT HAVE AI GENERATED RULES. THIS IS ONLY A FIRST DRAFT WIREFRAME STARTING POINT AND MUST BE EDITED TO BECOME REAL, USEFUL RULES AND CHECKLISTS.'''<span id="stub-notice"></span>
 
<span id="stub-notice"></span>
== Stub notice ==
== Stub notice ==


Line 33: Line 26:
This notice will be placed on articles that have potential to be compliant with our mission statement and rules, that are not yet so.
This notice will be placed on articles that have potential to be compliant with our mission statement and rules, that are not yet so.


Abusefilter rule was added to ensure that a normal user can’t remove a stub notice, and a [https://wiki.rossmanngroup.com/index.php/MediaWiki:Removing_stub_notice warning page was created].
Abusefilter rule was added to ensure that a normal user can’t remove a stub notice, and a [https://wiki.rossmanngroup.com/index.php/MediaWiki:Removing_stub_notice warning page was created].<span id="to-do---stub-notice-tests"></span>
 
<span id="to-do---stub-notice-tests"></span>
=== TO DO - stub notice tests ===
=== TO DO - stub notice tests ===


Line 45: Line 36:


<ol start="4" style="list-style-type: decimal;">
<ol start="4" style="list-style-type: decimal;">
<li>Try to remove stub notice as an administrator. '''This should work, as per rules set in [https://wiki.rossmanngroup.com/index.php/Special:AbuseFilter abusefilter].'''</li></ol>
<li>Try to remove stub notice as an administrator. '''This should work, as per rules set in [https://wiki.rossmanngroup.com/index.php/Special:AbuseFilter abusefilter].'''</li></ol><span id="to-do---stub-moderation-guidelines"></span>
 
<span id="to-do---stub-moderation-guidelines"></span>
=== TO DO - stub moderation guidelines ===
=== TO DO - stub moderation guidelines ===


Line 66: Line 55:
** block the user
** block the user
** ban them by IP address
** ban them by IP address
** audit other articles/contributions they’ve created for related shitposting. lean on the side of removing all of their creations/edits based on the severity of shitposts.
** audit other articles/contributions they’ve created for related shitposting. lean on the side of removing all of their creations/edits based on the severity of shitposts.<span id="to-do---captcha-tests"></span>
 
<span id="to-do---captcha-tests"></span>
=== TO DO - Captcha tests ===
=== TO DO - Captcha tests ===


Line 75: Line 62:
* Make sure that you do not need a captcha if you are someone I have confirmed is a mod.
* Make sure that you do not need a captcha if you are someone I have confirmed is a mod.
* Make sure that normal registered users that I have not personally flagged as trusted &amp; anonymous users do need a captcha
* Make sure that normal registered users that I have not personally flagged as trusted &amp; anonymous users do need a captcha
* Remind me to switch out the google recaptcha for hcaptcha, since recaptcha is worse.
* Remind me to switch out the google recaptcha for hcaptcha, since recaptcha is worse.<span id="to-do---fix-video-list"></span><span id="to-do---fix-video-list"></span>
=== TO DO - replace google recaptcha with hcaptcha ===
recaptcha is getting owned on my other wiki. hcaptcha works better, and isn't google.  


<span id="to-do---fix-video-list"></span>
=== TO DO - fix video list ===
=== TO DO - fix video list ===


Line 89: Line 77:
# a more simplistic way of creating this page must be done that is still easy on the eyes with the visual editor, while being editable by the visual editor.
# a more simplistic way of creating this page must be done that is still easy on the eyes with the visual editor, while being editable by the visual editor.


Given that this is literally a table of URLs and plaintext, there is no excuse for visualeditor to fail that badly at loading it.
Given that this is literally a table of URLs and plaintext, there is no excuse for visualeditor to fail that badly at loading it.<span id="what-needs-to-get-done-before-launch"></span>
 
= BIG PICTURE ITEMS NECESSARY FOR LAUNCH =
<span id="what-needs-to-get-done-before-launch"></span>
= What needs to get done before launch =


'''We need three things in order to be ready for the next stage:'''
'''We need these:'''


# Clear cut rules that are ready to be battle tested.
# Clear cut rules that are ready to be battle tested.
Line 100: Line 86:
# Sample articles of each type demonstrating what we want users to contribute
# Sample articles of each type demonstrating what we want users to contribute
# A fixed version of the '''[https://wiki.rossmanngroup.com/index.php/Videos_to_Convert_to_Articles Videos to Convert to Articles]''' page that actually loads in the visual editor
# A fixed version of the '''[https://wiki.rossmanngroup.com/index.php/Videos_to_Convert_to_Articles Videos to Convert to Articles]''' page that actually loads in the visual editor
# AND/OR a fixed visual editor that can actually load the ''[https://wiki.rossmanngroup.com/index.php/Videos_to_Convert_to_Articles Videos to Convert to Articles]'' page
# AND/OR a fixed visual editor that can actually load the ''[https://wiki.rossmanngroup.com/index.php/Videos_to_Convert_to_Articles Videos to Convert to Articles]'' page<span id="lets-get-it-done."></span>
 
<span id="lets-get-it-done."></span>
= Let’s get it done. =
= Let’s get it done. =


I do not want this to be a forever project that never turns into something real, or stagnates in mediocrity due to lack of attention, leadership, or progress. We have to balance doing things properly with not expecting everything to be perfect.
I do not want this to be a forever project that never turns into something real, or stagnates in mediocrity due to lack of attention, leadership, or progress. We have to balance doing things properly with not expecting everything to be perfect.


The launch day will require all hands on deck to come up with what needs to be handled on the fly as an influx of users come in, and we will have to be ready to edit policies & deal with all sorts of random crap that needs to be updated on the fly. **There is no way for us to anticipate every problem until launch!**
The launch day will require all hands on deck to come up with what needs to be handled on the fly as an influx of users come in, and we will have to be ready to edit policies & deal with all sorts of random crap that needs to be updated on the fly. '''There is no way for us to anticipate every problem until launch!'''
```