Outreachy: "MapKnitter.org Spam Management System" Project Planning

[PeculiarE]

This is a planning issue breaking down the project goals outlined in my Outreachy proposal into small, measurable tasks.

N.B.: This is a Work-in-Progress which means in the course of this project, some tasks might be added to the list, removed, or even broken down further into smaller chunks or modules.

You can find the designs for the spam dashboard (map and user moderation tables) and go through my entire proposal here: MapKnitter.org Spam Management System proposal

Useful discussions on the project can also be found in this discussion thread: publiclab/plots2/issues/10754

Project Tasks

Back-End

• Create status columns on maps and users tables #1752
• Create batch-spam and single spam endpoints #1761
• Create batch-publish and single publish endpoints #1771
• Create batch-delete endpoint #1779
• Adjust existing fetch map(s) and user(s) endpoints to fetch based on status #1785
• Create batch-ban and single ban endpoints #1793
• Create batch-unban and single unban endpoints #1797
• Create endpoints for fetching maps on the spam dashboard page #1799
• Create endpoints for fetching users on the spam dashboard page #1810
• Edit login process to allow only active users #1815
• Ensure users banned/moderated while already logged in are prevented from carrying out further activities and logged out immediately
• [FTO] Return user's status and role from the PublicLab API
• Create service checking current user's status and role via hourly calls to PublicLab API
• Auto-spam maps of banned users & fetching of recently banned users
• [FTO] Add the first-time-author (P.S: looks like it's new contributor) status to users creating maps for the first time when fetching users

UI Implementation & Integration

Map Moderation Table

• Implement the mobile-responsive design of the map moderation table
• Fetch spammed, published, and unmoderated maps (note to self: number of uploaded images: map.warpables.length, number of placed images: map.placed_warpables.length)
• Fetch recently created maps and recently updated maps
• Implement the single spam and batch-spam features
• Implement the single publish and batch-publish features
• Implement the single delete and batch-delete features

User Moderation Table

• Implement the mobile-responsive design of the user moderation table
• Fetch active users and banned users
• Fetch moderators and admins
• Implement the single ban and batch-ban features
• Implement the single unban and batch-unban features

Navigation, Redirection, and Other Improvements/Additions

• [FTO] Add a link to the MapKnitter spam dashboard from PublicLab.org
• [FTO] Add a link back to PublicLab.org from MapKnitter spam dashboard
• [FTO] Add a link to the MapKnitter spam dashboard from the moderator's profile dropdown
• [FTO] Add pop-up modal to display important map details on click of map name
• [FTO] Change the action of the spam icon beside maps in the gallery (as well as other archive actions elsewhere) to spam and no longer archive maps
• Implement the mobile-responsive design of the 'Recently Banned Authors' page
• Implement redirection/self-clicking to spam all author's maps on author banning

Documentation

• Create a detailed document describing the purpose and usage of the MapKnitter spam dashboard
• [FTO] Link to documentation from the MapKnitter spam dashboard.

[PeculiarE]

Hi @jywarren, @TildaDares, @cesswairimu and other community members....please help review my planning issue for my Outreachy project.

I am very much open to feedbacks, improvements, and suggestions 😊 . Thank you!

[TildaDares]

This looks great @PeculiarE. I love how you’ve broken down your tasks into segments and each item in the checklist solves one problem.

You’ve also identified the issues that are small enough to be solved by first-timers. Preparing a documentation for the Mapknitter spam dashboard is also a great idea.

Overall, I think you’re off to a great start. Great job @PeculiarE!!

[PeculiarE]

Yay!!! That's some serious confidence booster @TildaDares 🚀 😄

Thank you for the feedback, very much appreciated ❤️

[cesswairimu]

I agree, its looking great @PeculiarE 🎉
On the milestone blocker, I could create one for you in the meantime and you should be able to add the issues to that milestone. If you would like to, please give me what you would like the name to be. Thanks

[PeculiarE]

Thank you very much ❤️ @cesswairimu.

Yup, I'd like that. Here goes:

Title: [Outreachy] MapKnitter.org Spam Management System
Description: This project aims to build an effective spam management system for MapKnitter based on and similar to the existing system at PublicLab by integrating MapKnitter with PublicLab's spam management system, creating a unified visual style between both systems, and implementing user status restrictions for moderated users and maps. Refer to #1744 for the planning issue.

Thank you!

[cesswairimu]

cool, here it is

[PeculiarE]

Thank you! @cesswairimu. It looks great 😄

Seems like I can only create new issues from the milestone and cannot add an already existing issue to it 😞

milestone.1.mp4

As I don't plan to create issues from scratch but rather convert each task on the list to an issue using the 'Convert to Issue' option that appears when you hover over a task list, I won't be able to add issues to the milestone for tracking.

[cesswairimu]

oh I see:- @PeculiarE, once you create an issue and open it, e.g this current one , on the right sidebar where you have "assignees", "labels", etc...there is one for "milestone", here, you can select a milestone to associate the issue to(after creation)...if you are not able to add, you can ping Jeff for permission. thanks

[PeculiarE]

Thank you @cesswairimu. Wasn't able to do that as well.

Could I please get permission to add existing issues to the created milestone? @jywarren. Thank you 😄

[jywarren]

Hi all, i don't have much to add beyond agreeing fully with @TildaDares and @cesswairimu that this looks super. I'll add permissions so you can add to milestones!

[jywarren]

@PeculiarE what are some of the things you're interested in doing first? Any information or experience you think you need in the next few days to get started? Just let us know!

[PeculiarE]

@PeculiarE what are some of the things you're interested in doing first? Any information or experience you think you need in the next few days to get started? Just let us know!

@jywarren, so I arranged the tasks in the order I'd like to work on them. I intend to develop the backend functions first before focusing on the user interface that will use these functions.

Yes, I definitely do have questions and have created a separate issue/thread for it here: #1745

[jywarren]

Hi @PeculiarE can you update us on where you are on your project right now? Let us know if you are stuck on anything! Thank you!

[PeculiarE]

Hi @jywarren, so I'm currently working on these tasks simultaneously:

• Adjust existing fetch map(s) endpoints to fetch based on map status
• Adjust existing fetch user(s) endpoints to fetch based on user status

I'm not stuck per se, just a bit overwhelmed, as they have turned out to be a bit more comprehensive than I originally thought they would be.

Hopefully, I should be done with both before the end of today.

Thank you!

[jywarren]

OK, thank you! Anything we can do to help you work through it?

…

On Wed, Jul 20, 2022 at 2:24 AM PeculiarE ***@***.***> wrote: Hi @jywarren <https://github.com/jywarren>, so I'm currently working on these tasks simultaneously: - Adjust existing fetch map(s) endpoints to fetch based on map status - Adjust existing fetch user(s) endpoints to fetch based on user status I'm not stuck per se, just a bit overwhelmed, as they have turned out to be a bit more comprehensive than I originally thought they would be. — Reply to this email directly, view it on GitHub <#1744 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAF6J2GD3O22EZQYYSDK7LVU6LQNANCNFSM5XR4JSYA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[PeculiarE]

Thank you @jywarren. So I'm done (at least, I think I am 😅 ), and the PR is at #1786. I'd really appreciate your review and feedback 😄