Page MenuHomePhabricator

[GSOC 2023 Proposal] 5. Improve Programs & Events Dashboard UX for Article Scoped Programs:
Closed, DeclinedPublic


Profile Information
Name: Chalice Prajwal
Nickname: Honey
Web Profile:
Location: India
Typical working hours (include your timezone): 17:00 - 23:00 (UTC+5:30)


Project: Improve Programs & Events Dashboard UX for Article Scoped Programs
Description: The goal of this project is to improve the event creation user experience of the Programs & Events Dashboard so that event organizers can more easily configure the Dashboard to track only the articles they want to track, using whichever of the available scoping methods is most appropriate for their program. The project will require familiarity with web design/prototyping, React.js, and user research. Knowledge of wikis and/or Wikidata and Ruby are helpful but not required.

Possible Mentor(s):
Mentor(s): Sage Ross

Have you contacted your mentors already?

Relevant past works:
Relevant links:

Deliverables :

1. User research report : A report outlining your research findings and insights into user needs and preferences for the Programs & Events Dashboard.

2. Wireframes and mockups : A set of high-fidelity wireframes and mockups that depict your proposed design for the improved Programs & Events Dashboard UX. These should be annotated with explanations of the design decisions and features.

3. Interactive prototypes : Interactive prototypes of the Programs & Events Dashboard that demonstrate how users will interact with the new features and design.

4. Design documentation : Detailed documentation on the design specifications, including typography, color palette, user flows, and design elements.

5. User testing report : A report on the user testing results of the new Programs & Events Dashboard design. This should include feedback from users and any necessary revisions that were made based on the testing results.

6. Implementation guidelines : Guidelines and instructions for developers on how to implement the new design into the existing Programs & Events Dashboard.

7. Final design assets : All design assets in their final form, including any icons, images, and graphics used in the new design.

Community Bonding (May 17 - June 6): This phase is all about getting to know my mentor and the Wikimedia community. During this period, I will conduct extensive research on the project and familiarize myself with the technology stack and tools that will be used.

Design Research and Wireframing (June 7 - June 27, 30 hours): This phase involves conducting user research and developing wireframes and mockups for the Programs & Events Dashboard. Working closely with my mentor, I will ensure that my designs meet the project requirements and align with Wikimedia's design principles.

Design Prototyping (June 28 - July 11, 25 hours): During this phase, I will create interactive prototypes of the new user interface, using my wireframes and mockups as a guide. Tools like Adobe XD and Figma will be used to create the designs, and my mentor will provide feedback and guidance throughout the process.

Design Refinement (July 12 - July 25, 30 hours): Based on feedback from my mentor and the Wikimedia community, I will refine my design prototypes and make any necessary revisions. I may also conduct additional user research to validate my design decisions.

Design Implementation (July 26 - August 29, 80 hours): During this phase, I will work closely with the development team to ensure that my design is implemented correctly into the Programs & Events Dashboard. I will collaborate with the developers to ensure that the design is technically feasible and that any necessary adjustments are made. I may need to learn new skills, such as working with React.js or Ruby, but my mentor and the Wikimedia community will be available to help me as needed.

Design Testing and Final Touches (August 30 - September 5, 20 hours): Finally, I will spend time testing my design to ensure that it works as expected. Working with my mentor, I will identify any bugs or issues that need to be addressed and make any necessary fixes. I will also work on putting the finishing touches on my design, such as refining the visual design and ensuring that it meets all of the project requirements.


I am currently a third-year student pursuing a degree in Computer Science Engineering with Honors in Advanced Computer Architecture at NSRIT College. In terms of programming courses, I have taken a variety of courses including C, C++, DSA with C++, Python, HTML, CSS, JavaScript, Ruby, Ruby on Rails, XML, and Flutter.

Group Projects:

I have participated in various group projects, including programming and non-programming projects. I have also led several teams, and we have won many prizes in hackathons. For instance, we created a web application that helps organize events.

Role in the Group:

In these group projects, I have primarily contributed as a UI/UX designer, utilizing my passion for creating visually appealing and user-friendly designs for web and mobile applications. Additionally, I have taken on the role of team lead, ensuring that everyone is working efficiently and effectively towards our goals. Based on my experience and skills, I am excited to continue contributing to open-source projects and applying my design knowledge to create impactful solutions.

What does making this project happen mean to you?

Making this project happen is a significant opportunity for me as a first-time contributor to open source. I am excited to have the chance to work with a team of experienced developers and learn from their expertise. In addition to improving my technical skills, I believe this project will also enhance my communication abilities as I collaborate with the team to ensure that my design vision is executed in a way that is feasible and effective.

At the same time, I am motivated by the potential impact this project can have on the Programs & Events Dashboard UX for Article Scoped Programs. After we research and analyze the user needs, and then propose design which will make it easier and more intuitive for users to add their events to the dashboard. By making this process smoother, we can encourage more participation in Article Scoped Programs and ultimately increase the number of quality articles on Wikipedia.


HMI ENGINEERING SERVICES, Visakhapatnam — Data science with ML (June 2022 - July 2022)

  • Assisted senior designers with editing and choosing KPIs to Google Cloud.
  • Embedded code into Microprocessors.
  • Created a LogisticRegression model which has 87% accuracy in predicting heart disease.
  • Created and presented portfolios of growth, pointing out key trends.
  • Made smart systems to connect to the Cloud (ThingSpeak).

Honey Companion - UI/UX Designer (October 2021 - present) (Pair project-chalice & divya)

  • Designed a student-centered app that offers courses and tools to help students learn efficiently and maintain good health.
  • Conducted user research and created paper wireframes to establish the app's concept and design.
  • Created digital wireframes, prototypes, and mockups using Adobe XD and Figma.
  • Utilized frame-by-frame animation to enhance the user experience.
  • Iterated on the design based on user feedback to improve the overall user experience.
  • Contributed to the development of the app's branding and marketing materials.

Event Timeline

Hi! This looks like a proposal that is primarily a design project, rather than a UX development project that also includes a design element. It will not be realistic to both learn the necessary programming skills and implement a new design in ~80 hours. It also won't be a competitive application without an accompanying track record of preliminary contributions to the Dashboard codebase. I usually encourage prospective applicants to explore the codebase and make several contributions first, before attempting to put together a proposal, as a strong proposal needs to demonstrate an understanding of the codebase and how the proposed project fits into it specifically.

Hi @Chalice346, as the deadline for GSoC is quickly approaching in less than 48 hours (April 4th, 2023, 18:00 UTC), it's crucial that you submit your proposal on Phabricator and Google's program website in the recommended format as soon as possible. To avoid any potential last-minute rushes or server failures, we highly recommend that you submit your proposal early and keep updating it as needed before the deadline. Once you have submitted your proposal, please move it from the "Proposals in Progress" column to the "Proposals Submitted" column on the Phabricator workboard by simply dragging it. If you have any inquiries, please do not hesitate to ask. Good luck with your application!

Shure sir I am working on it and will do changes according to what my mentor suggested and let you know soon.

@Gopavasanth thanks for reminding me to do required changes , I have done changes according to my mentor @Ragesoss and I will add updated file in GSoC page and also make this proposal into summited column.

thank you,


@Chalice346 We are sorry to say that we could not allocate a slot for you this time. Please do not consider the rejection to be an assessment of your proposal. We received over 100 quality applications, and we could only accept 9 applicants. We were not able to give all applicants a slot that would have deserved one, and these were some very tough decisions to make. Please know that you are still a valued member of our community and we by no means want to exclude you. Many applicants who we did not accept in previous rounds have become Wikimedia maintainers, contractors and even GSoC students and mentors this year!

Your ideas and contributions to our projects are still welcome! As a next step, you could consider finishing up any pending pull requests or inform us that someone has to take them over. Here is the recommended place for you to get started as a newcomer:

If you would still be eligible for GSoC next year, we look forward to your participation!