Page MenuHomePhabricator

[GSoC 20 & Outreachy 20 Proposal] Improve Wiki Education Dashboard javascript build pipeline and reduce bundle size
Closed, DeclinedPublic

Description

Profile Information

Name: Soumya Sharma
Mediawiki username: Soumyaa1804
Github: soumyaa1804
Email address: soum.sharma169@gmail.com
Location: India
Timezone: India (UTC+5:30)

Synopsis

  • Short summary describing your project and how it will benefit Wikimedia projects

[WikiEducation Dashboard] Improve Wiki Education Dashboard javascript build pipeline and reduce bundle size
The WikiEducation Dashboard is a web application that facilitates the instructors and program leaders to organize edit-a-thons, create courses and carry out other editing events and make an individual dashboard for every event. It uses MediaWiki OAuth for login and therefore is able to compile the edits made by participants or student editors at one place (individual dashboard) automatically. If it had not been this tool it would become cumbersome to record edits by the participants and for program leaders to organize local edit-a-thons. As this is also a learning platform for higher education in America and Canada and is used for contests it is really important for the tool to load fast.
Currently, the WikiEducation Dashboard uses Gulp and Webpack as the build tools. Gulp is a task runner and Webpack is used for bundling javascript files. As we scaled up the tool, we ended up extending gulp beyond its main function which is as a task runner. We started bundling our stylesheets using gulp which is the main purpose of Webpack. We can bundle interdependent modules into browser understandable .js, .css, .jped and .svg files using suitable plugins in Webpack.
As the frontend development evolved, we no longer need heavy third party libraries like JQuery and can completely replace it with vanilla javascript.

  • Possible Mentor(s)
  • Have you contacted your mentors already?

Yes

Deliverables

Describe the timeline of your work with deadlines and milestones, broken down week by week. Make sure to include time you are planning to allocate for investigation, coding, deploying, testing and documentation

Participation

Describe how you plan to communicate progress and ask for help, where you plan to publish your source code, etc

About Me

Tell us about a few:

  • Your education (completed or in progress)
  • How did you hear about this program?
  • Will you have any other time commitments, such as school work, another job, planned vacation, etc, during the duration of the program?
  • We advise all candidates eligible for Google Summer of Code and Outreachy to apply for both programs. Are you planning to apply to both programs and, if so, with what organization(s)?
  • What does making this project happen mean to you?

Past Experience

I have been contributing to Wikimedia projects since December 2019 and explored various projects, Wikimedia tools and initiatives like Edit-a-thons, Wikimedia hackathons, Wiki Loves Folklore etc. I have contributed to few Wikimedia projects which includes WikiEducation Dashboard, Ores, Hashtags, indic-wscontest and Library Card Platform.

Any Other Info

Add any other relevant information such as UI mockups, references to related projects, a link to your proof of concept code, etc

Event Timeline

Soumyaa1804 set Security to Software security bug.Mar 7 2020, 3:40 AM
Soumyaa1804 changed the visibility from "Public (No Login Required)" to "Custom Policy".
Soumyaa1804 changed the subtype of this task from "Task" to "Security Issue".
Soumyaa1804 triaged this task as Medium priority.Mar 7 2020, 3:47 AM
Soumyaa1804 removed projects: Security-Team, Security.

I intended to create a draft proposal for GSoC and outreachy and wanted to change the visibility from public to only subscribers for the time being it's not completed but I guess that added task as a security bug. Is there a way to remove that security tag or I should change the status to 'decline'?

Aklapper renamed this task from [Proposal: WikiEduDashboard] Improve Wiki Education Dashboard javascript build pipeline and reduce bundle size [GSoC 20 & Outreachy 20] to [GSoC 20 & Outreachy 20 Proposal] Improve Wiki Education Dashboard javascript build pipeline and reduce bundle size.Mar 7 2020, 7:59 AM
Aklapper changed the visibility from "Custom Policy" to "Custom Policy".
Aklapper changed the subtype of this task from "Security Issue" to "Task".

In general, https://www.mediawiki.org/wiki/Phabricator/Help#Restricting_access_to_tasks (which won't help much in this case) :)

I set visibility to author, subscribers and admins, but it is unclear to me /why/ visibility should be restricted.

Thanks, @Aklapper! I recently got to know about this template so can I create a new task using that template and decline this one or should I continue with this one by editing its desciption?
About the visibility, I thought its okay to make task restricted so that other applicants can't see it. But as things have been in past rounds of Outreachy programs, I am totally fine with making it public. :)

Let's avoid duplicates. You can edit the task description by clicking Edit Task.

And I think this task should be public, but I'll defer that to @srishakatux. :)

Let's avoid duplicates. You can edit the task description by clicking Edit Task.

And I think this task should be public, but I'll defer that to @srishakatux. :)

Yes, totally fine.

Yes, the task should be public on Phabricator as the intention to do so is to gather feedback from Wikimedia community members and mentors :)

Aklapper changed the visibility from "Custom Policy" to "Public (No Login Required)".Mar 9 2020, 9:24 AM
Soumyaa1804 removed a subscriber: Ragesoss.

I'll subscribe to the mentor once the proposal is ready for review by the mentor.

@Soumyaa1804 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 14 students. 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 students who we did not accept in 2019 have become Wikimedia maintainers, contractors and even GSoC students and mentors this year!

If you would like a de-brief on why your proposal was not accepted, please let me know as a reply to this comment or on the ‘Feeback on Proposals’ topic of the Zulip stream #gsoc20-outreachy20. I will respond to you within a week or so. :)

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: https://www.mediawiki.org/wiki/New_Developers.

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