feat: gsoc phase 1 report of jaydip #218
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![accesslint[bot]](https://avatars.githubusercontent.com/in/1502?s=60&v=4){kind=small}
| - A modal to manage moderators was created, displaying current moderators and allowing the addition of new ones. | ||
|
|
||
| ```erb | ||
| <div id="addModeratorsModal" class="modal fade" role="dialog"> |
There was a problem hiding this comment.
Looks like this element is missing an accessible name or label. That makes it hard for people using screen readers or voice control to use the control.
tanmoysrt
requested changes
Jul 11, 2024
Comment on lines
148
to
164
|
|
||
| ``` | ||
| def add_moderators | ||
| emails = params[:emails].split(',').map(&:strip) | ||
| users = User.where(email: emails) | ||
|
|
||
| users.each do |user| | ||
| user.update(question_bank_moderator: true) | ||
| end | ||
|
|
||
| if users.all? { |user| user.errors.empty? } | ||
| redirect_back(fallback_location: root_path) | ||
| else | ||
| render json: { errors: users.map(&:errors).flat_map(&:full_messages) }, status: :unprocessable_entity | ||
| end | ||
| end | ||
| ``` |
There was a problem hiding this comment.
Avoid adding code snippets to this blog, until unless it's too important.
ig All sort of these things are present in your personal blog. Adding link to that blog or code snippet will be better way.
There was a problem hiding this comment.
Same for all the code snippets in the blog @jaydip1235
There was a problem hiding this comment.
You may add gif or video of the feature in the blog also to showcase a ppreview of the feature.
|
|
||
| In the first phase, we have covered | ||
| * Community Bonding Period | ||
| * Creating controllers, schemas and tables for all the use case [Week 1 to 3] |
There was a problem hiding this comment.
Suggested change
| * Creating controllers, schemas and tables for all the use case [Week 1 to 3] | |
| * Creating controllers, schemas and tables for circuitverse practice section [Week 1 to 3] |
| * Community Bonding Period | ||
| * Creating controllers, schemas and tables for all the use case [Week 1 to 3] | ||
| * Manage question moderators[Week 4] | ||
| * Moderator Question Creation and Integration[Week 5 to 6] |
|
|
||
| ### Community Bonding Period | ||
|
|
||
| During the community bonding period for GSoC at CircuitVerse, we engaged in various activities to prepare for the project. We began by participating in meet-and-greet sessions with mentors, contributors, and admins, where we shared our excitement for GSoC, discussed our journeys, and introduced our projects. Mentors [Vaibhav Upreti](https://www.linkedin.com/in/vaibhav-upreti/), [Vedant Jain](https://www.linkedin.com/in/vedant-jain-781006145/), and [Tanmoy Sarkar](https://www.linkedin.com/in/tanmoysrt/), answered questions about the CircuitVerse Practice Section project, and [Aboobacker MK](https://www.linkedin.com/in/aboobacker-m-k/) provided insights into the 12-week project process and discussed open defects in CircuitVerse. |
There was a problem hiding this comment.
Suggested change
| During the community bonding period for GSoC at CircuitVerse, we engaged in various activities to prepare for the project. We began by participating in meet-and-greet sessions with mentors, contributors, and admins, where we shared our excitement for GSoC, discussed our journeys, and introduced our projects. Mentors [Vaibhav Upreti](https://www.linkedin.com/in/vaibhav-upreti/), [Vedant Jain](https://www.linkedin.com/in/vedant-jain-781006145/), and [Tanmoy Sarkar](https://www.linkedin.com/in/tanmoysrt/), answered questions about the CircuitVerse Practice Section project, and [Aboobacker MK](https://www.linkedin.com/in/aboobacker-m-k/) provided insights into the 12-week project process and discussed open defects in CircuitVerse. | |
| During the community bonding period for GSoC at CircuitVerse, there were various activities to provide more context for the project. The project begins with a meet-and-greet sessions with mentors, contributors, and admins, where everyone shared their excitement for GSoC, discussed their journeys, and discuessed about the projects. Mentors [Vaibhav Upreti](https://www.linkedin.com/in/vaibhav-upreti/), [Vedant Jain](https://www.linkedin.com/in/vedant-jain-781006145/), and [Tanmoy Sarkar](https://www.linkedin.com/in/tanmoysrt/), answered questions about the CircuitVerse Practice Section project, and [Aboobacker MK](https://www.linkedin.com/in/aboobacker-m-k/) provided insights into the 12-week project process and discussed open defects in CircuitVerse. |
You can add a context about open defects in CircuitVerse
|
|
||
| Following this, we revisited key technologies by refreshing knowledge of Ruby on Rails through The Odin Project documentation and Vue JS with a YouTube crash course. This preparation was essential for upcoming work on the CircuitVerse codebase. | ||
|
|
||
| We then focused on a detailed exploration of the CircuitVerse codebase, identifying areas for modification and making initial changes. we had in-depth discussions with [Ruturaj Mohite](https://www.linkedin.com/in/ruturaj-mohite/), about potential edge cases and the development of the question practice simulator versus the standard simulator, including how to track and save user progress. |
There was a problem hiding this comment.
Suggested change
| We then focused on a detailed exploration of the CircuitVerse codebase, identifying areas for modification and making initial changes. we had in-depth discussions with [Ruturaj Mohite](https://www.linkedin.com/in/ruturaj-mohite/), about potential edge cases and the development of the question practice simulator versus the standard simulator, including how to track and save user progress. | |
| Then, the focus got shifted to detailed exploration of the CircuitVerse codebase, identifying areas for modification and making initial changes. we had in-depth discussions with [Ruturaj Mohite](https://www.linkedin.com/in/ruturaj-mohite/), about potential edge cases and the development of the question practice simulator versus the standard simulator, including how to track and save user progress. |
|
|
||
| ### Pull Request | ||
|
|
||
| Pull request for phase 1 can be found [here](https://github.com/CircuitVerse/CircuitVerse/pull/5015) |
There was a problem hiding this comment.
This PR CircuitVerse/CircuitVerse#4967 should be added in the list also.
|
|
||
| ### Future Work | ||
|
|
||
| The tasks to be done include developing the UI for the moderators dashboard and integrating it with the backend to enable CRUD operations on questions. Next, efforts will focus on making the question practice page responsive across all screens, implementing filtering logic and backend integration, and setting up auto-verification and submission of questions. Additionally, a progressive dashboard for users will be created to display submission history and progress, followed by backend integration and addition of test cases. |
There was a problem hiding this comment.
It will be better if you can write this things in bullet points.
|
@tanmoysrt made the changes. Please have a look |
| ### Pull Request | ||
|
|
||
| - PR : [Creating controllers, schemas and tables for circuitverse practice section](https://github.com/CircuitVerse/CircuitVerse/pull/4967) | ||
| - PR : [Addig moderators and questions with simulator integration](https://github.com/CircuitVerse/CircuitVerse/pull/5015) |
There was a problem hiding this comment.
Suggested change
| - PR : [Addig moderators and questions with simulator integration](https://github.com/CircuitVerse/CircuitVerse/pull/5015) | |
| - PR : [Adding moderators and questions with simulator integration](https://github.com/CircuitVerse/CircuitVerse/pull/5015) |
|
@VaibhavUpreti corrected the spelling |
VaibhavUpreti
approved these changes
Jul 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Blog of Phase 1