Name: Shreyaa Sharma
Course: Civil Engineering
University: Indian Institute of Technology, Roorkee, India
Location: Roorkee - 247667, India
Timezone: UTC +5:30 India Time Zone
Gitter Handle: shreyaa-s
I am a fresher at IIT Roorkee currently pursuing BTech in Civil Engineering. I have always loved the concept of open source and wanted to contribute to the same. I have been trying to contribute in the small ways I could, by having all my projects on GitHub so that others can benefit from the same and trying to fix minor bugs. Outreachy provides a great opportunity for women to step foot into the world of open source development with the chance to work in big open-source projects with the core developers. This makes me excited and eager to participate in it.
STATEMENT OF MOTIVATION
I chose this particular project because it is very well aligned with my interests and also correlated with what I have worked on in the past. Being an avid reader myself, it's easy for me to look at the project from a user's point of view. Other than that, this project provides a good opportunity to apply my learnings on a practical scale. This is my field of interest and therefore the natural inclination to this project.
Programming Languages and Skills :
- Git VCS with knowledge of Subversion
- Sound knowledge of MySQL
- Fluent in C++, PHP
- Object-Oriented Programming, Analysis, and Design
Development Environment :
- Kubuntu 18.04 with KDE Plasma 5
- Visual Studio Code
SDSWoC, IIT Roorkee
- Spearheaded the development of an online pre-ordering system in campus canteens to reduce waiting time and increase efficiency
- Worked on the dynamic rendering of orders and order status.
GGJ, IIT Roorkee
- A 2D game made for a global game jam in Lua
- Implemented the function to keep the player within the screen
- Added image to the player
SDSLabs, IIT Roorkee
- A platform for predictive modeling and analytics competitions for the campus.
- Implemented lazy loading in the website using ReactJS.
Open Source Contributions
Public Lab Editor
Public Lab Plots2
- PR#7705 : https://github.com/publiclab/plots2/pull/7705
- PR#7768 : https://github.com/publiclab/plots2/pull/7768**
Mozilla Firefox Voice
- PR#1214 : https://github.com/mozilla/firefox-voice/pull/1214
- PR#1218 : https://github.com/mozilla/firefox-voice/pull/1218
- PR#1313 : https://github.com/mozilla/firefox-voice/pull/1313
- PR#1314 : https://github.com/mozilla/firefox-voice/pull/1314
- PR#1333 : https://github.com/mozilla/firefox-voice/pull/1333
Public Lab Editor
- Issue#422: Missing entries in .gitignore
- Issue#424: Spelling mistakes
- Issue#457: New line added with bold formatting
- Issue#458: Overlapping image and table dialog box
- Issue#459: Shifting of selected data to new line with bold formatting**
Public Lab Plots2
- Issue#7775: Spamaway check in signup is skipped
The Public Lab Editor is a WYSIWYG rich text editor which is a component of the Public Lab.org community content management system. The Editor is built on the Woofmark library which is no longer actively maintained. The aim of the project is to identify and fix bugs for improved user experience and introduce custom inserts to expand the Editor's functionality by creating simple and intuitive ways to add advanced content to posts, such as maps, tables, and lists of content from elsewhere on the Public Lab.org website.
The First Phase of the Project consists of removing the bugs present in the Editor. This consists of the bugs that I encountered as well as already documented bugs on the project repository.
The Second Phase is the part of the project that introduces general modifications to the already existing features. The first two parts of this phase are about improving the responsiveness of the mobile site and ToolBar modifications. The third part is to create a rich mapping between shortcode syntax and visible UI to introduce the features already present in the Editor in the rich text mode.
The Third Phase is to add custom inserts to the Editor. The Editor is built on a modular system, and I propose the idea to develop an extension, a new module, alongside the existing modules. The project will work on the shortcode syntax to ensure compatibility for people who use codes directly in the text, both for existing posts and in the Editor itself where current users may expect to be able to continue using this syntax. The user will be able to configure and insert their selection and make changes or tweaks to already added inserts.**
Phase I: Identifying and fixing bugs
As of right now, there are numerous issues related to the toolbar's positioning. The toolbar is only applicable and required for the text area. Public Lab's Editor provides the user with a floating toolbar so that the user doesn't have to scroll all the way till the bottom to edit a piece of text but the misplaced toolbar negatively affects the user experience. As depicted in the image below:
A potential solution to both these issues will be to have a fixed toolbar at the top of the page, below the navbar, which is visible/enabled only when the focus is set to the text area or a fixed vertical toolbar to the left.
The tables when inserted do not offer any formatting options.
- The tables do not have borders by default and the users do not have an option to add them.
- The alignment of the table rows is automatic and the user has little control over them.
I propose to add formatting options to the tables. The user can choose to add or remove borders and resize the table column.
- The spinner in 'use current location' appears every time 'Use current location' button is clicked. The number of active spinners should not exceed one. Also, the action should cancel on the second consecutive click if the user had clicked on the button by mistake.
2. Clicking on the 'Add a location' button which should expand a menu containing the options to enter location using place name, coordinates or using existing location.
Responsiveness & Space Efficiency
- The Editor becomes space inefficient when used from a mobile device. I propose to reduce the numbered heading size and move them to the left of the concerned box.
- The 'Extras' bar at the bottom of the page is not center-aligned in the mobile site due to the shifting of the heading to the top of the bar.
3. The third part of the Editor ie. the 'Add a location' takes up a lot of space. It could be shrunk down into a single button and the menu would expand only when the button is clicked.
4. Fixing the 'Publish' button to the bottom of the web page to make it more space-efficient.
5. Fixing the misplaced toolbar.
- Highlighting Bold and Italics icon when in use.
- Collapse 'Add table' pop up menu on adding table to text area.
Adding Tools for shortcode syntax
Some of the features of Editor, like adding activity grids, are present in shortcode syntax in the markdown mode but can't be used in the rich text mode. A solution to this would be to develop a rich mapping between shortcode syntax and visible UI. A column would be added in the 'More' drop-down menu in the 'Extras' tab. This would open up a drop-down list of additional features that are, as of now, present in markdown mode but not in rich text mode. I propose to introduce a visible UI for the following inline features:
The options 2-5 can be added in the form of both lists and grids. The option will be given to the user to choose between the two.**
Phase III: Adding Custom Inserts
Adding functionalities to the 'Extras' tab
- Invite Responses
Clicking this button would open up a dialog box with a search bar and suggestions of top writers of the topic. Clicking on the name of a user would send an invite for a response to the user and a green tick in front of the user's username. A list item would be added to the plots repository with the title 'Invitations' in the drop-down menu shown below. Also, a list item would be added to the notification settings that would give the user option to receive email notifications.
Clicking on this button would open up a dialog box with a calendar, a search bar and a list of suggested users. The person creating the event could choose to send invites to specific users or simply schedule an event. The notifications would work similarly to the one explained above.
A user could choose to include maps in the editor. For example, a person writing a research note on the varying water quality from city to city or the history of natural disasters could be highly benefited by displaying a map and marking important locations of the study. It would work similar to 'Add a location feature' and a person could choose to mark(pinpoint) several locations in a map like shown below.
The Editor has always been a platform to share knowledge. One of the charts' functionality's many uses would be in research notes based on surveys. The target audience and the researcher could opt for a chart based representation. In the dialog box, the writer would select the type of chart, enter no of constituents of the charts and can select custom colors for each from the research palette. On clicking 'Prepare Chart' he would see a prepared chart in his text area.
- Social Icons
A developer could choose to add reference to his GitHub profile or a blogger to his Instagram post. For rich text editing experience, a user could add the social icon for relevant sites at the bottom and add the link to the concerned profile or post.
- Additional ToolBar
An interface for already present functions that were previously used in markdown mode with shortcodes.
Additions to ToolBar :
- Left and Right Align : Along with center alignment, the user would also get an option to left-align or right-align the data. It would be done at the Woofmark level.
- Audio: The user would get an option to embed an audio clip in the text area.
- Video: Along with youtube video links, the user could also add a video which would be added using an iframe. If time permits, the feature would be made compatible with google drive, dropbox, along with uploading from the device. A maximum limit would be set on video upload.
- Underline: Introduce an underline icon in the toolbar.
- Calendar: The author would be able to add widgets such as a calendar in the text area.
Project Outline :
Media Features :
|Features||Currently Available||In this module|
|File Upload|| ✓
|Youtube Video|| ✓
| Geotagging (maps)
| Social Icons
Formatting and Extra Features :
|Features||Currently Available||In this module|
|Center Align|| ✓
|Left, Right Align|| ✕
|Table Formatting|| ✕
|Create Event|| ✕
|Invite a Response|| ✕
Other Features :
- Space efficient design in mobile site
- 'Add a location' drop-down menu.
- Controlling notifications of the new custom inserts.
- Adding tools in visible UI for shortcode syntax.
Official Coding Period (19 May - 18 Aug)
Phase I: Identifying Bugs and fixing them
Week 1 - 3 (19 May- 9 June)
- Work on the aforementioned bugs
- Sort through the issues on Github labeled as bug and fix them in order of priority.
- Prepare for initial feedback
- Test the current code base to document other existing issues and create first-timer issues.
Phase II: General Modifications
Week 3 - 4 (9 June - 16 June)
- Complete the first part of modifications
- Open up new issues on the encountered bugs especially for first-timers.
- Testing the modifications
Week 4 - 6 (16 June - 30 June)
- Complete second part and third part of modifications
- Summarize rules and add comments wherever necessary.
- Will require rigorous manual testing, henceforth will take the most time.
- Clean up of redundant code.
- Prepare for mid-term evaluation
Phase III: Adding custom Inserts
Week 6-9 (1 July - 22 July)
- Work on adding the functionalities to extras tab (first part)
- Regular testing to find bugs and fixing them along with opening minor issues to welcome newcomers to the community.
Week 9 - 11 (23 July - 13 August)
- Adding functionalities to the ToolBar(second part)
- Specify unit tests for possible test cases.
- Finding and documenting bugs and opening relevant issues.
- This requires manual testing.
Week 12 (13 August - 18 August)
- Complete minor tasks.
- General code cleanup and state proper contribution documentation for manual testing.
- Any work left shall be completed here including writing tests and documentation.
- Prepare for Final Submission.
My vacations were supposed to start on 5 May and end on 15 July. I have yet to receive any update about the change in timetable due to COVID-19 pandemic. The official Outreachy period is from 19 May to 18 August. I can easily devote 45-50 hours a week until my college reopens and 40-45 hours per week after that. Although there are no exams scheduled in this period as of now, in case they are pushed back to this duration owing to Covid-19, I would require a 5 days long break for the same. I'm also free on the weekends and I intend to complete most of the work before my college reopens.
Other than this project, I have no commitments/vacations planned for the summer. I shall keep my status posted to all the community members on a weekly basis and maintain transparency in the project.
I have learned a lot and was introduced to a completely new ecosystem by contributing to the Public Lab and even after the Outreachy period ends, I plan on contributing to this organization, by adding to my past projects and working on open issues.
The aforementioned project that I will be working on is not only going to help developers with a better rich text editing experience but also a generated agreement for the not so technical people and newcomers. By integrating the short code syntax and visible UI in the text Editor itself, it will improve the user experience.
The highlight of my experience so far with Public Lab has been the fast-planned development and the active involvement of the mentors. With the community growing continuously, I feel responsible for all the projects I'm a part of. Having picked up a lot of development skills, my major focus would be to help the project and the community grow.