Open PeculiarE opened 2 years ago
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!
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!!
Yay!!! That's some serious confidence booster @TildaDares π π
Thank you for the feedback, very much appreciated β€οΈ
I agree, its looking great @PeculiarE :tada: 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
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 https://github.com/publiclab/mapknitter/issues/1744 for the planning issue.
Thank you!
cool, here it is
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 π
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.
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
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 π
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!
@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 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
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!
Hi @jywarren, so I'm currently working on these tasks simultaneously:
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!
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 https://github.com/publiclab/mapknitter/issues/1744#issuecomment-1189877580, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAF6J2GD3O22EZQYYSDK7LVU6LQNANCNFSM5XR4JSYA . You are receiving this because you were mentioned.Message ID: @.***>
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 π
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
UI Implementation & Integration
Map Moderation Table
User Moderation Table
Navigation, Redirection, and Other Improvements/Additions
Documentation