===Personal Information===
**Name:**Shriya Kamat Tarcar
**Email ID:**shriyakt08@gmail.com
**Location:**India
**Available Working Hours/Week=**40+ hours(flexible)
**LINKS TO MY RESUME AND PROFILES:**
[[ https://drive.google.com/file/d/1l1ccwsIUl6EC1SO7v9DOiGDSuSwUJMRe/view?usp=sharing | RESUME ]]
[[ https://twitter.com/Shriya1002 | TWITTER ]]
[[ https://www.linkedin.com/in/shriyacktarcar/ | LINKEDIN ]]
[[ https://github.com/shri3016 | GITHUB ]]
[[ https://medium.com/@kamattarcarshriya | MEDIUM ]]
[[ https://meta.wikimedia.org/wiki/User:ShriyaKT | METAWIKI ]]
[[ https://warwick.ac.uk/research/data-science/warwick-data/dssgx/dssgx2022/2022-fellows-mentors/ | DATA SCIENCE FOR SOCIAL GOOD FELLOWSHIP,UNIVERSITY OF WARWICK,UK ]]
[[ https://www.outreachy.org/alums/2023-12/ | OUTREACHY WEBSITE ]]
[[ https://www.mediawiki.org/wiki/Outreachy/Round_27| WIKIMEDIA FOUNDATION ]]
[[ https://www.youtube.com/watch?v=Tb4zFB5XENI&t=680s | OUTREACHY YOUTUBE PODCAST(SETTING YOUR CAREER THROUGH OPEN-SOURCE)
]]
**ACADEMICS
**Passionate about leveraging technology for positive societal impact, I am Shriya Kamat Tarcar, a Computer Science Engineer from Goa,India. I possess a diverse skill set spanning from technical documentation,research, data science, software development to open-source development.During my academic tenure at Goa University, I have honed my technical writing skills while maintaining a strong academic record, including achieving a CGPA of 8.53/10.
**EXPERIENCE**===Professional Experience===
From crafting college articles to contributing to poetry, magazines, and newspapers, my writing journey has been diverse and enriching. Through projects like DSSG Fellowship's user guide, final year project reports, and technical documentation for Wikimedia's Outreachy internship, I've honed my ability to communicate complex concepts effectively across various mediums.
**I]OUTREACHY-WIKIMEDIA FOUNDATION(OPEN-SOURCE INTERNSHIP)**:
1)[[ https://drive.google.com/file/d/1XC04PEeTDTQBDWMVO3ixfqqGK3RyQgWA/view?usp=sharing | INTERNSHIP CERTIFICATE ]]
2)[[ https://phabricator.wikimedia.org/T346374 | OPEN SOURCE CONTRIBUTION PHASE ]]
**3)PROJECT PHASE:**
A][[ https://docs.google.com/document/d/1yPso5iWCjPQapLvDEanFYNpbaofLdTQ8mbjHrC22y54/edit?usp=sharing | SURVEY DOCUMENT ]]
B][[ https://docs.google.com/document/d/1hAHkDJyaZwkD_71WvzIhThyF8HZ8SNuYQw5OTgl8xRQ/edit?usp=sharing | TASKS DOCUMENT ]]
I have experience of working independently as well as with international and cross-functional teams.
I was selected as **1 of the 7 Outreachy Interns with the Wikimedia Foundation** which afforded me the opportunity to engage in **qualitative and quantitative analysis**, along with **technical documentation**, for the **"Multilingual Wikipedia Editor Survey"** project under the mentorship of **Mike Raish(Lead Design Researcher at Wikimedia Foundation)**.This opportunity marked a turning point in my journey toward technical writing. From this experience, I've embarked on a focused path of skill acquisition and experiential learning aimed at mastering the craft. Along this path, I've **immersed myself in diverse technological domains**, **actively engaged with the Wikimedia Foundation community**, and **made significant contributions to the "Multilingual Wikipedia Editor Survey" project**.I have gained **experience of working on wikis, Meta-Wiki, and using wikitext during this internship**.
A]**A]****Experience with WikiText **
1. [[ https://en.wikipedia.org/wiki/Amboli,_Sindhudurg | Amboli, Sindhudurg Article Enhancements ]]
**Task:** Added a "Natural Wonders" section and a sunset photo.
**Wikitext Skills Demonstrated:** Utilized **wikitext** to embed images, create sections, and format text** to enhance the visual and informational quality of the article.**
**Task:** **Impact: ** Improved article quality and visitor engagement by providing detailed and visually appealing content.
2. [[ https://en.wikipedia.org/wiki/Global_Climate_and_Energy_Project | Global Climate and Energy Project Article Description ]]
**Task:** Composed and integrated a concise project description.
** **Wikitext Skills Demonstrated**: **Applied** wikitext** t**o to succinctly summarize complex information**, making it quickly accessible and understandable for readers.
**Impact: ** Streamlined user experience by clearly defining the article’s focus at the outset.
3. [[ https://en.wikipedia.org/wiki/Ashan_Priyanjan | Ashan Priyanjan Article Translation ]]
**Task:** Translated the article to Hindi, enhancing accessibility for Hindi-speaking readers.
**Wikitext Skills Demonstrated:** Employed **wikitext in multilingual settings**, demonstrating flexibility and adaptability in content presentation across languages.
** **Impact:** ** Broadened the reach of the article, making it accessible to a non-English-speaking audience.
**B]Experience with WikiText and Meta-Wiki **
- Showcasing My **Wikitext and Meta-Wiki Skills** Through Blogging ([[ https://meta.wikimedia.org/wiki/User:ShriyaKT | My Page ]])
- During my Outreachy internship with the Wikimedia Foundation, I authored a s**Series of blog posts on Meta-Wiki**, demonstrating my ability to effectively **use wikitext **and engage with **complex content management systems.
1**.
**1. Wikitext Proficiency: **Each blog post required advanced** wikitext formatting **to structure content, embed links, and ensure proper layout which demonstrates my fluency in handling MediaWiki's markup language.
**2. Engaging Content Creation: **My blogs, such as "Introduction," "Struggle," "Think About Your Audience," and "Career Goals," showcase my **skill in creating engaging and well-structured content** that resonates with the community. These posts are not only informative but also formatted to enhance readability and accessibility.
**3. Community Interaction: **Writing these posts on Meta-Wiki allowed me to **interact directly with the Wikimedia community**, **receiving feedback** and **participating in discussions**, furthering my **understanding of the community’s needs** and how best to **address them**.
**4. Technical Documentation: My **My **experience mirrors the tasks required in Google Season of Docs**, particularly in **documenting complex systems in an accessible manner**, making me **well-prepared to contribute effectively to the MediaWiki documentation efforts.**
Links To **My BlogPosts:
https://meta.wikimedia.org/wiki/User:ShriyaKT/Introductionsts:**
[[ https://meta.wikimedia.org/wiki/User:ShriyaKT/Struggle
Introduction | Introduction ]]
[[ https://meta.wikimedia.org/wiki/User:ShriyaKT/Think_About_Your_AudienceStruggle | Struggle ]]
[[ https://meta.wikimedia.org/wiki/User:ShriyaKT/Think_About_Your_Audience | Think_About_Your_Audience ]]
[[ https://meta.wikimedia.org/wiki/User:ShriyaKT/Career_Goals | Career Goals ]]
Eager to master MediaWiki's architecture, my background with Meta equips me with the **skills necessary to fully grasp and contribute to the breadth of this projec**t.
Eager to master MediaWiki's architecture, my background with Meta equips me with the skills necessary to fully grasp and contribute to the breadth of this project.
2**II]DATA SCIENCE FOR SOCIAL GOOD FELLOWSHIP:,UNIVERSITY OF WARWICK,UNITED KINGDOM:**
CERTIFICATE:1][[ https://drive.google.com/file/d/1ClZ9Ne_VotLKND3ga4zK6KdcUk5pHhFK/view?usp=drive_link | INTERNSHIP CERTIFICATE ]]
2][[ https://github.com/DSSGxUK/s22_wmca| OPEN-SOURCE CODE FOR PROJECT ]]
WEBSITE:3][[ https://warwick.ac.uk/research/data-science/warwick-data/dssgx/dssgx2022/2022-fellows-mentors/drive.google.com/file/d/18QiqJfCY6FDbTP1r-_OLHoG9SQph_z-T/view?usp=sharing | POSTER ]]
OPEN-SOURCE CODE FOR PROJECT: https://github.com/DSSGxUK/s22_wmca4][[ https://warwick.ac.uk/research/data-science/warwick-data/news/events/poster-entries/ | AI SUPERPOWER SHOWCASE 2022,UNITED KINGDOM ]]
Notably,I got** selected as 1 of the 15 fellows globally** for the **Data Science for Social Good Fellowship at the University of Warwick,UK** where I collaborated with **West Midlands Combined Authority** and **Pure Leapfrog** to **predict energy efficiencies**, contributing to regional **carbon neutrality goals** in the West Midlands.
My **proficiency in technical documentation** is demonstrated through this project. I adeptly **utilized markdown** to craft **clear and organized README files** for the project as well as each folder, facilitating **easy understanding and replication of project methodologies and data processes**. This helped to enhance **accessibility and usability for fellow collaborators and future users**.I crafted **user guides** and **manual instruction documents** by **distilling complex technical information** into **clear and accessible language tailored to stakeholder needs**. I **organized the documentation logically, provided step-by-step instructions, and incorporated stakeholder feedback to ensure usability**.
AI SUPERPOWER SHOWCASE 2022,UNITED KINGDOM:Presented this project in various **international data science conferences** namely:“**DataFest 2022,Shard,London,UK**”,“**Learning and Doing Data For Good Conference 2022,USA”** and **“How Might We Target UK Homes, To Make Them More Energy Efficient?,Geovation.” **
https://warwick.ac.uk/research/data-science/warwick-data/news/events/poster-entries/
I**II]TIMBLE LAW ASSOCIATES**
POSTER:[[ https://drive.google.com/file/d/18QiqJfCY6FDbTP1r-_OLHoG9SQph_z-TGvUCOm5cNmZVqL2KwjpYAHh62FzgMgwP/view?usp=sharingdrive_link | WORK REPORT ]]
Notably,I got selected as 1 of the 15 fellows globally for the Data Science for Social Good Fellowship at the University of Warwick,UK where I collaborated with West Midlands Combined Authority and Pure Leapfrog to predict energy efficienciesDuring my work as a **Developer Intern** at Timble Law Associates, I took charge of **website development**, **feature implementation**, and **chat flow optimization** using **HubSpot**. However, a pivotal aspect of my role revolved around **creating technical documentation**. This entailed meticulously **documenting processes** and **functionalities**, contributthereby **streamlining to regional carbon neutrality goals in the West Midlandsoperations** and **enhancing efficiency** within the team.
My proficiency in technical documentation is demonstrated through this project.At Timble Law Associates, I adeptly utilized markdownI **created and maintained critical documentation** to craft clearsupport **website development and organized README files,chatflow optimization**. facilitating easy understandingI skillfully **documented the firm’s legal services** and replication of project methodologies and data processes.**developed comprehensive software design documentation**, Addi**functionally requirements**, I authored concise and informative README files for each folder within the project repository,**feature-oriented guides**. enhancing accessibility and usability for fellow collaborators and future users.
I crafted user guides and manual instruction documents by distilling complex technical information into clear and accessible language tailored to stakeholder needs.My work provided clear, essential insights to project managers and developers, I organized the documentation logically,ensuring effective project execution. provided step-by-step instructionsCollaborating closely with engineering leaders, and incorporated stakeholder feedback to ensure usability and replicability ofI **produced detailed guides** that became **key resources** for the project's methodologiesdevelopment team, ultimately contributing to the**enhancing project's success in driving regional carbon neutrality goals in the West Midlands clarity** and **coherence** throughout its lifecycle.
Presented this project in various data science conferences namely:**IV]SAWO LABS**
“DataFest 2022,Shard,London,UK”,“Learning and Doing Data For Good Conference 2022,USA” and “How Might We Target UK Homes, To Make Them More Energy Efficient?,Geovation.”
3]TIMBLE LAW ASSOCIATES1)[[ https://drive.google.com/file/d/1AblSQ7JNDKVoYNHzksjEXGGIKAiCVbfM/view | Internship Certificate ]]
WORK REPORT:https://drive.google.com/file/d/1GvUCOm5cNmZVqL2KwjpYAHh62FzgMgwP/view?usp=drive_link
During my work as a Developer Intern at Timble Law Associates, I took charge of website development, feature implementation, and chat flow optimization using HubSpot. However, a pivotal aspect of my role revolved around creating technical documentation. This entailed meticulously documenting processes and functionalities, thereby streamlining operations and enhancing efficiency within the team.
I worked there to create and maintain new and existing documentation to support the website development process along with chatflow optimization of the firm.I've adeptly documented the legal services offered by the firm, along with crafting comprehensive software design documentation, functional requirements, and feature-oriented guides. These efforts have been instrumental in enabling project managers and software developers to gain a thorough understanding of project expectations and requirements.2)[[ https://www.linkedin.com/feed/update/urn:li:activity:6901493233965182978/ | Social Media Shoutout ]]
In my capacity as a technical writer,3)[[ https://twitter.com/Shriya1002/status/1499104431476187138?t=UcA7ZNbqOmeN3Z-3gk5BVQ&s=19 | Twitter(Emerged among Top 4 champs of the week) ]]
During my internship at SAWO Labs, I excelled as a **Developer Champ**, demonstrating **prowess **in **technical documentation**, **integration**, **bug reporting**, and **community engagement**. With a focus on **developer documentation**, I **crafted tutorials**, **how-to guides**, and **API documentation**, ensuring **clarity and usability** across diverse platforms. I've delivered succinct and lucid documentation for the firm's legal servicesLeveraging **Docs-as-Code principles**, while also taking the lead in documenI played a vital role in seamlessly** integrating website functionalities.the SAWO API** into **frameworks like Gatsby, Collaborating closely with the head of engineering and the technical leadNext.js, I've produced comprehensive guides that serve as invaluable references for the development teamNuxt.js, ensuring clarity and alignment throughout the project lifecycle.
4]SAWO LABSand WordPress**, while consistently providing **valuable feedback to enhance user experience**.
Certificate:https://drive.google.com/file/d/1AblSQ7JNDKVoYNHzksjEXGGIKAiCVbfM/view**V]FINAL YEAR THESIS & RESEARCH PUBLICATION**
Social Media Shoutout:1)[[ https://www.linkedingithub.com/feed/update/urn:li:activity:6901493233965182978/shri3016/FaceRecognitionForStudentAttendance | Github ]]
Twitter(Emerged among Top 4 champs of the week) : https://twitter.com/Shriya1002/status/1499104431476187138?t=UcA7ZNbqOmeN3Z-3gk5BVQ&s=19
During my internship at SAWO Labs, I excelled as a Developer Champ, demonstrating prowess in technical documentation, integration, bug reporting, and community engagement. With a focus on developer documentation, I crafted tutorials, how-to guides, and API documentation, ensuring clarity and usability across diverse platforms. Leveraging Docs-as-Code principles, I played a vital role in seamlessly integrating the SAWO API into2)[[ https://drive.google.com/file/d/1tfHwz027vm4-bM-epdRJgZsEC4DGoJHP/view?usp=sharing | Report ]]
3)[[ https://drive.google.com/file/d/1H_bq-f33PtM4eyhIn9bS4qamHA8QUiP0/view?usp=sharing | Paper ]]
frameworks like Gatsby, Next.js, Nuxt.js, and WordPress, while consistently providing valuable feedback to enhance user experience.4)[[ https://drive.google.com/file/d/1wy8XCJB4McRWJICAT--fJgJObQAuD5Cp/view?usp=sharing | Instruction Manual ]]
My dedication to technical excellence at SAWO Labs was recognized as I secured a spot among the top four champs of the weekFor my **final year thesis in Computer Engineering**, I developed a **face recognition system** that utilized **advanced algorithms** like **Haar Cascade** and **MTCNN** for **precise detection** and **PCA for analyzing facial embeddings**. I crafted **comprehensive documentation**, including a **detailed project report**, an **instruction manual **with s**tep-by-step guidance** and** troubleshooting tips**, and a **research paper** that highlighted the latest developments in facial recognition technology. This **documentation enhanced the system's usability** in various settings and fostered further research, refleffecting my proactive engagement and skill in addressing developer needs with precision in documentvely bridging the gap between sophisticated technology and practical application and supportn.
5]FINAL YEAR THESIS & RESEARCH PUBLICATION**VI]PROJECTS**
In my capacity as a technical writer, I meticulously crafted detailed README files for multiple projects like:
Github:1)[[ https://github.com/shri3016/FaceRecognitionForStudentAttendanceshri3016| My Profile README ]]
Report:2)[[ https://drive.googlegithub.com/file/d/1tfHwz027vm4-bM-epdRJgZsEC4DGoJHP/view?usp=sharingshri3016/Happify-Me-For-PCCE | Happify-Me-For-PCCE ]]
Paper:3)[[ https://drive.googlegithub.com/file/d/1H_bq-f33PtM4eyhIn9bS4qamHA8QUiP0/view?usp=sharing/shri3016/NewsNinja | NewsNinja ]]
Instruction Manual: https://drive.google.com/file/d/1wy8XCJB4McRWJICAT--fJgJObQAuD5Cp/view?usp=sharing4)[[ https://github.com/shri3016/The-New-Normal | The-New-Normal ]]
5)[[ https://github.com/shri3016/PinkSafe | PinkSafe ]]
These project documentations were meticulously structured to provide clear and concise guidance, exemplifying my expertise in documentation. They stand as a testament to my proficiency in conveying complex technical information effectively.
My final year thesis, face recognition system integrates cutting-edge algorithms like Haar Cascade and MTCNN for accurate face detection, coupled with advanced visualization techniques such as PCA for insightful analysis of facial embeddings, empowering seamless implementation and facilitating further research in the field.**VII]ACE OF COMPUTER ENGINEERS MAGAZINE,ETHOS MAGAZINE AND THE GOAN DAILY NEWSPAPER**
[[ https://drive.google.com/file/d/1_Gu4nMMTnADC95XyGogHBU3u-Np4wWMA/view?usp=sharing | Link To My Writings ]]
As a tech writer, I excelled in crafting comprehensive documentation for a cutting-edge face recognition project,my final year thesis in my computer engineering. Leveraging my expertiseI have a **strong background** in **technical writing**, I meticulously compiled a project report, instruction manualdemonstrated through my work on **open-source technology,radio communication, and research paper that elucidated the intricacies of the endeavor.
Central to my documentation approach was a user-centric focus.cloud computing, I crafted an instruction manual that offered step-by-step guidance, troubleshooting tips,user engagement,SAWO-One Tap Authentication Service and my journey as a Developer Champ at SAWO Labs** for **notable publications** like the **Association of Computer Engineers Magazine** and **Ethos Magazine**. and best practices, ensuring seamless implementation and usage of the facial recognition systemMy experience also includes writing for the** Navhind Times,the goan news daily **on a variety of topics from **cultural insights to technological innovations like Goa's DISHTAVO system**. This meticulous attention to detail facilitated smooth integrI'm eager to **apply these skills to the MediaWiki documentation into diverse environmentsproject at Wikimedia**, from educaiming to make informational institutions to corporate settings **accessible** and **comprehensive** for all users.
Furthermore, my research paper was characterized by thorough exploration and citation of relevant sources, reflecting my commitment to staying abreast of the latest developments in facial recognition technology.**VIII]MICROSOFT LEARN STUDENT AMBASSADOR**
1][[ https://drive.google.com/file/d/1zvE9iIxbCa7IBf5InihrkRp1p8LLd1IA/view | Certificate ]]
2][[ https://drive.google.com/file/d/1PnB1h3PavwEF1CuBHSISOnlA9zX5VhQM/view?usp=sharing | Poster ]]
3][[ https://drive.google.com/file/d/1WLKo3Ysau1yKdxOjdB_4TfPQp7GYYXTO/view?usp=sharing | Event ]]
In essenceDuring my tenure as a** Microsoft Learn Student Ambassador**, I led **workshops on Git and GitHub**, creating **visually engaging PowerPoint presentations** and soliciting feedback to refine content. I **mentored peers**, **designed interactive forms**, and **facilitated collaborative learning sessions**, showcasing **my ability to distill complex concepts into accessible content.** My commitment to continuous learning is evidenced by my **completion of Microsoft Learn Courses** and a **comprehensive portfolio**, my documentation not only provided clarity and guidance but also served as a catalyst for further research and innovation in facial recognition technology**demonstrating proficiency in diverse Microsoft Technologies**. With a keen eye for detail and a passion for effective communicationEager to contribute to **GSOD at Wikimedia**, I played a pivotal role in bridging the gap between complex algorithms and real-world applications.aim to** leverage my technical expertise** and **passion for knowledge sharing to produce impactful documentation.**
**IX]Medium:**
6]PROJECTS[[ https://medium.com/@kamattarcarshriya | My Medium Account ]]
In my capacity as a technical writerMy portfolio of published articles on Medium **demonstrates my versatility and depth** in **technical communication**. Covering topics from **Google Developer Student Clubs-WOW Event Highlights** to **Google Cloud innovations** and** one-tap authentication services**, I meticulously crafted detailed README files for multiple projects like:these pieces reflect **my capacity to break down complex technological subjects and present them engagingly and informatively**.
https://github.com/shri3016/shri3016**Links to my published articles:
**1)[[ https://githubmedium.com/shri3016/Happify-Me-For-PCCE@kamattarcarshriya/precious-moments-dsc-wow-3ef7e56b3d02 | Precious-Moments-DSC-WOW ]]
2)[[ https://githubmedium.com/shri3016/NewsNinja@kamattarcarshriya/the-radio-d56d8778d2e9| The Radio ]]
3)[[ https://githubmedium.com/@kamattarcarshri3016/The-New-Normalya/30-days-of-google-cloud-f770ed6b0089 | 30 Days Of Google Cloud ]]
https://github.com/shri3016/PinkSafe
These project documentations were meticulously structured to provide clear and concise guidance, exemplifying my expertise in documentation. They stand as a testament to my proficiency in conveying complex technical information effectively.
7]ACE OF COMPUTER ENGINEERS MAGAZINE,ETHOS MAGAZINE AND THE GOAN DAILY NEWSPAPER
https://drive.google.com/file/d/1_Gu4nMMTnADC95XyGogHBU3u-Np4wWMA/view?usp=sharing
I am passionate about open-source technology and have a strong background in technical writing, demonstrated through my written articles on radio communication, cloud computing and 30 Days Of Google Cloud for the Association Of Computer Engineers Magazine, and on SAWO-One Tap Authentication Service and my journey as a Developer Champ at SAWO Labs for the Ethos Magazine. My experience has equipped me with a deep understanding of technical documentation and user engagement. I am eager to apply these skills to the MediaWiki documentation project at Wikimedia, ensuring information is both accessible and comprehensive for all users.
In addition to my technical writing contributions on cloud computing and radio technologies, I have also engaged with broader audiences through the Navhind Times, Goa’s leading news daily. My pieces there have ranged from seasonal cultural reflections to critical analysis of pioneering educational technologies like Goa's DISHTAVO system. These experiences have honed my ability to adapt complex information for diverse audiences, a skill I am excited to bring to the Wikimedia Foundation's MediaWiki documentation project.
**8]MICROSOFT LEARN STUDENT AMBASSADOR**4)[[ https://medium.com/@kamattarcarshriya/sawo-one-tap-authentication-service-4228052e322c| SAWO-One Tap Authentication Service ]]
Certificate Of Completion: https://drive.google.com/file/d/1zvE9iIxbCa7IBf5InihrkRp1p8LLd1IA/view**X]REDDIT,STACKOVERFLOW,QUORA:**
Poster:https://drive.google.com/file/d/1PnB1h3PavwEF1CuBHSISOnlA9zX5VhQM/view?usp=sharingI **actively engaged** with the **wider developer community** by **participating in discussions on platforms like Quora, Stack Overflow, and Reddit**, providing **insightful answers, troubleshooting tips, and fostering a collaborative knowledge-sharing environment**.
Event:https://drive.google.com/file/d/1WLKo3Ysau1yKdxOjdB_4TfPQp7GYYXTO/view?usp=sharingMy presence on Quora, Stack Overflow, and Reddit allowed me to **contribute to technical dialogues**, **offer solutions to complex queries**, and **share my expertise**, thereby **strengthening community support** and **driving the collective learning journey**.
During my tenure as a Microsoft Learn Student Ambassador, I led workshops on Git and GitHub, creating visually engaging PowerPoint presentations and soliciting feedback to refine content. I mentored peers, designed interactive forms, and facilitated collaborative learning sessions, showcasing my ability to distill complex concepts into accessible content. My commitment to continuous learning is evidenced by my completion of Microsoft Learn Courses and a comprehensive portfolio, demonstrating proficiency in diverse Microsoft Technologies. Eager to contribute to GSOD at Wikimedia, I aim to leverage my technical expertise and passion for knowledge sharing to produce impactful documentation.
**9]Medium:**
https://medium.com/@kamattarcarshriya
My portfolio of published articles on Medium demonstrates my versatility and depth in technical communication. Covering topics from Google Developer Student Clubs-WOW Event Highlights to Google Cloud innovations and one-tap authentication services, these pieces reflect my capacity to break down complex technological subjects and present them engagingly and informatively.
https://medium.com/@kamattarcarshriya/precious-moments-dsc-wow-3ef7e56b3d02**XI]OPEN-SOURCE **
https://medium.com/@kamattarcarshriya/the-radio-d56d8778d2e9Participated in **Outreachy Open-Source Contribution Period(Oct 23-Nov 23)** where I contributed to **open-source projects** of **Wikimedia Foundation,Oppia and HOTOSM**.Also participated in **Open-Source Programmes** like **Girlscript Summer Of Code**, **Hacktoberfest(every year since 2020)**, **OpenForce **and contributed to **various open-source projects**.
[[ https://github.com/DSSGxUK/s22_wmca| **1]DATA SCIENCE FOR SOCIAL GOOD FELLOWSHIP,UNIVERSITY OF WARWICK,UK
https://medium.com/@kamattarcarshriya/30-days-of-google-cloud-f770ed6b0089OPEN-SOURCE CODE FOR OUR PROJECT:** ]]
[[ https://mediumgithub.com/@kamattarcarshriya/sawo-one-tap-authentication-service-4228052e322coppia/oppia/pull/19082#issuecomment-1817450937 | 2]OPPIA(MERGED PULL REQUEST) ]]
REDDIT,STACKOVERFLOW,QUORA:
I actively engaged with the wider developer community by participating in discussions on platforms like Quora, Stack Overflow, and Reddit, providing insightful answers, troubleshooting tips, and fostering a collaborative knowledge-sharing environment.3][[ https://github.com/hotosm/fmtm/issues/863#issuecomment-1779575126 | HOTOSM (OPEN SOURCE CONTRIBUTION PHASE) ]]
My presence on Quora, Stack Overflow, and Reddit allowed me to contribute to technical dialogues, offer solutions to complex queries, and share my expertise, thereby strengthening community support and driving the collective learning journey.
**SKILLS**All of these experiences have been instrumental in sculpting and amplifying my skills as a technical writ
===Skills===
**A]Technical:**
**1)Technical Writing:**Markdown,Latex,MkDocs,SphinxSwagger,Overleaf,Hashnode,Dev.to,GitHub gist,Postman,Confluence,Google Docs,Notion,Medium,
Langauges:Python, SQL, C/C++
**2)Web Development:**HTML, CSS, and JavaScript,Hugo, Gatsby,React.js, Bootstrap
**3)Data Science:**Jupyter Notebook,Google Collab,Statistics, EDA, Data Analysis & Visualization, Numpy, Pandas, MatPlotlib, Seaborn, Pytorch, Tensorflow, Scikit-Learn, Machine Learning, Predictive Modelling, Deep Learning, Pattern Recognition,Artifical Intelligence
**4)Software Tools:Git**Git,Github,Jira,Monday.com,Power BI, Tableau, StreamLit, MS Excel, MySQL, PostgreSQL, Figma, Adobe XD,GitLab, Visual Studio Code,Google Cloud,Google Analytics
**5)Operating Systems:**Windows,Linux,MAC OS
**6)CS Fundamentals:**Engineering Mathematics,Digital Logic and Design,Computer Organization and Architecture,Programming and Data Structures, Algorithms,Theory of Computation,Compiler Design, Operating System,Databases,Computer Networks
****B]Soft Skills:**
Technical Writing & Editing,Report Writing,Instruction Manual Writing ,Communication, Problem-Solving, Presentation, Critical Thinking,Teamwork, Analytical Thinking, Leadership,Search Engine Optimization(like Google Scholar) ,Adaptibility,Detail-Oriented
****C]Languaauges:**
English,Hindi,Konkani,Marathi,Sanskrit
**OPEN-SOURCE**
Participated in Outreachy Open-Source Contribution Period(Oct 23-Nov 23) where I contributed to open-source projects of Wikimedia Foundation,Oppia and HOTOSM.Also participated in Open-Source Programmes like Girlscript Summer Of Code, Hacktoberfest(every year since 2020), OpenForce and contributed to various open-source projects.
1]DATA SCIENCE FOR SOCIAL GOOD FELLOWSHIP,UNIVERSITY OF WARWICK,UK===Achievements===
OPEN-SOURCE CODE FOR OUR PROJECT:1)[[ https://drive.google.com/file/d/187Lh9tJ5XQ5fGn4_x9MCZ33vt9RxyFPG/view) | Machine Learning Quiz Winner, DevFest India 2021 ]]
https://github.com/DSSGxUK/s22_wmca
2]OPPIA:
MERGED PULL REQUEST:2)[[ https://drive.google.com/file/d/1GQl9jNC9fpyoj6c7W1O7HJTBPB4XYmtn/view | Top 13 Teams Shortlisted, Hack4She National Level Hackathon (Project: PinkSafe) ]]
https://github.com/oppia/oppia/pull/19082#issuecomment-1817450937
3]HOTOSM:
OPEN SOURCE CONTRIBUTION PHASE:
https://github.com/hotosm/fmtm/issues/863#issuecomment-1779575126
All of these experiences have been instrumental in sculpting and amplifying my skills as a technical writer.
ACHIEVEMENTS:
Machine Learning Quiz Winner, DevFest India 2021(3)[[ https://drive.google.com/file/d/187Lh9tJ5XQ5fGn4_x9MCZ33vt9RxyFPG/view)
Top 13 Teams Shortlisted, Hack4She National Level Hackathon (Project: PinkSafe).(https://drive.google.com/file/d/1GQl9jNC9fpyoj6c7W1O7HJTBPB4XYmtn/view)LD2fc6eu3hZNyxRU7915m7SZzvAuMxGz/view?usp=sharing | Topper,Scaler Edge Apex(National Coding Contest) ]]
Topper,Scaler Edge Apex(National Coding Contest)(https://drive.google.com/file/d/1LD2fc6eu3hZNyxRU7915m7SZzvAuMxGz/view?usp=sharing)4)[[ https://www.linkedin.com/feed/update/urn:li:activity:7110237983244492800?updateEntityUrn=urn%3Ali%3Afs_feedUpdate%3A%28V2%2Curn%3Ali%3Aactivity%3A7110237983244492800%29 | Web3 Conference Goa 2023 ]]
Web3 Conference Goa 2023(https://www.linkedin.com/feed/update/urn:li:activity:7110237983244492800?updateEntityUrn=urn%3Ali%3Afs_feedUpdate%3A%28V2%2Curn%3Ali%3Aactivity%3A7110237983244492800%29)5)[[ https://drive.google.com/file/d/1s55tJzjBSKvmcQdGgQ54JcbLOATGQDHf/view?usp=sharing | Dan Kohn Scholarship Recipient for KubeCon+CloudNativeCon Europe 2023 due to my contributions in cloud-native computing ]]
Dan Kohn Scholarship Recipient for KubeCon+CloudNativeCon Europe 2023 due to my contributions in cloud-native computing (6)[[ https://drive.google.com/file/d/1s55tJzjBSKvmcQdGgQ54JcbLOATGQDHfeHdrvqQVhFeR2KIGFsWA8l1P10i4zv0j/view?usp=sharing)drive_link | Winner,Best Landing Page Competition,Hexcoderz,Techyon,PCCE,Goa ]]
Winner,Best Landing Page Competition,Hexcoderz,Techyon,PCCE,Goa(https://drive.google.com/file/d/1eHdrvqQVhFeR2KIGFsWA8l1P10i4zv0j/view?usp=drive_link)
Awarded National Programme on Technology Enhanced Learning(NPTEL) Star twice (NPTEL Believer and NPTEL Enthusiast)(7)[[ https://drive.google.com/file/d/1dHk8uY5T9nVlBJDroQPxmGYAZ46Ffxi7/view?usp=sharing)
Selected as a Scholar for the UI/UX Design Course in Education Outreach Program Batch 11 powered by Girlscript Foundation( | Awarded National Programme on Technology Enhanced Learning(NPTEL) Star twice (NPTEL Believer and NPTEL Enthusiast) ]]
8)[[ https://drive.google.com/file/d/1sB7PFdSSxFK2ArBlOw1UicigR2ylDah6/view?usp=sharing)
Completed the "30 Days Of Google Cloud" in Cloud Engineering Track and Data Science and Machine Learning Track .( | Selected as a Scholar for the UI/UX Design Course in Education Outreach Program Batch 11 powered by Girlscript Foundation ]]
9)[[ https://drive.google.com/file/d/1gIwE1POVTyot8KdL0Mh_Jg5MiSdLu7Im/view?usp=sharing)
Winner,Financial Literacy Quiz by Girlscript Foundation.( | Completed the "30 Days Of Google Cloud" in Cloud Engineering Track and Data Science and Machine Learning Track ]]
10)[[ https://drive.google.com/file/d/1KfZP93AvciZWxi8MqYTgpcwKxtlK04FG/view?usp=sharing)
Got my Spark AR effect approved and accepted | Winner,Financial Literacy Quiz by Reskilll X Spark AR Initiative (Girlscript Foundation ]]
11)[[ https://www.linkedin.com/posts/activity-6904878613745713152-oIEB?utm_source=share&utm_medium=member_desktop)
| Got my Spark AR effect approved and accepted by Reskilll X Spark AR Initiative ]]
12)Idea Presentation Competition 2022 Winner,World Water Day,PCCE,Goa
OTHERS
I love participating in hackathons,coding competitions and community program initiatives(I have been a Microsoft Learn Student Ambassador[Beta])Beyond the realms of technology, my enthusiasm extends to diverse interests, like acting on national television,being a radio jockey on All India Radio and 92.7 BIG FM,taking part in debate,fancy-dress,dance,drawing and sanskrit shloka competitions.I'm on a journey to make an impact both in and outside the tech sphere.,there are links on side of each achievements
In conclusion===Extra-Curricular Activities===
I **love participating in hackathons**,**coding competitions** and **community program initiatives**(I have been a **Microsoft Learn Student Ambassador[Beta]**)Beyond the realms of technology, I am confident that my blend of technical writing skillsmy enthusiasm extends to diverse interests, academic background, and hands-on experience make me a strong candidate for the Technical Writer role with the Mediawiki project. I am excited about the prospect of contributing to this dynamic project and playing a role in advancing MediaWiki through clear and comprehensive documentation.
WHY BEST?like **acting on national television**,**being a radio jockey on All India Radio** and **92.7 BIG FM**,taking part in **debate,fancy-dress,dance,drawing and sanskrit shloka competitions**.I'm on a journey to make an **impact both in and outside the tech sphere**.
Based on my expertise in user-analysis research and data gatheringIn conclusion, I am confident that my blend of technical writing skills, academic background, I am well-equipped to enhance the user experience onand hands-on experience make me a strong candidate for the Technical Writer role with the MediaWwiki documentationproject. My ability to gather feedback from the community and create comprehensive user-persona case studies enables me to tailor documentation effectivelyI am excited about the prospect of **contributing to this dynamic project** and playing a role in **advancing MediaWiki through clear and comprehensive documentation**.
Moreover, my proficiency in various flavors of Markdown showcases my adaptability and willingness to learn new technologies, including Wikitext.===Why I am the suitable candidate for this role?===
Based on my expertise in **user-analysis research and data gathering**, I am eagerwell-equipped to leverage my skills and**enhance the user experience to contribute to the MediaWiki project,on MediaWiki documentation**. collaborating with the team and community to achieve our shared goalsMy ability to **gather feedback from the community** and **create comprehensive user-persona case studies** enables me to **tailor documentation effectively**.
Moreover, **my proficiency in various flavors of Markdown** showcases **my adaptability and willingness to learn new technologies**, including **Wikitext**. I am eager to **leverage my skills and experience** to contribute to the MediaWiki project, collaborating with the **team and community** to achieve our shared goals.
In addition, **my unique combination of technical writing skills, familiarity with Wikitext, and experience in open-source environments**, **particularly with Wikimedia Projects**s, makes me an ideal candidate for this role. I am **committed to addressing duplication issues, streamlining content, and implementing efficient organization practices to ensure a seamless migration of MediaWiki documentation**.
**As a technical writer dedicated to enhancing user experiences through clear and concise documentation**, I am enthusiastic about the opportunity to contribute to the **complete migration of MediaWiki documentation**. I look forward to **collaborating with the team and achieving our shared goals.** I've made **valuable edits to the MediaWiki documentation utilizing wikitext**.
I have successfully set up MediaWiki on a virtual server hosted by a leading cloud service provider. Additionally, I've made valuable edits to the MediaWiki documentation utilizing wikitext.
Project Statement===Project Statement==
**Project Title:Enhancing MediaWiki Documentation: Consolidation and Organization**
Project Title:Enhancing MediaWiki Documentation: Consolidation and Organization**Introduction**
In the vast landscape of online documentation, **MediaWiki stands out as a pivotal platform**, **powering sites like Wikipedia and serving various organizations worldwide with its robust, open-source wiki software**. Despite its extensive use, the **documentation for MediaWiki is currently split between Meta-Wiki and MediaWiki.org**, leading to fragmented and **occasionally outdated information**. This split not only **complicates the user and contributor experience **but also **impedes the maintenance and updating of the documentation.**
Introduction**Problem**
In the vast landscape of online documentation, MediaWiki stands out as a pivotal platform, powering sites like Wikipedia and serving various organizations worldwide with its robust, open-source wiki software. Despite its extensive use,The essential function of documentation within MediaWiki has been **hampered by the historical division of its content across two distinct platforms: Meta-Wiki and MediaWiki.org**. the documentation for MediaWiki is currently split between Meta-Wiki and MediaWiki.orgWhile MediaWiki.org was designated as the** primary site** for** hosting comprehensive documentation, leading to fragmented and occasionally outdated informationa significant portion of material remains scattered on Meta-Wiki**. This split not only complicates the user and contributor experience but also impedes the maintenance and updating of the documentation.dispersal presents several challenges:
Problem
The essential function of documentation within MediaWiki has been hampered by the historical division of its content across two distinct platforms:**1. Redundancy and Overlap**: There exists **considerable overlap between the pages **on Meta-Wiki and MediaWiki.org. However, **because of licensing constraints and the presence of corresponding pages** that already exist on MediaWiki.org, **direct importation of content from Meta-Wiki is not feasible**. This redundancy complicates the process for** users seeking specific information** and **burdens documentation maintainers with inconsistent and duplicated content**.
**2. Outdated Information:** Many of the MediaWiki documentation pages still hosted on Meta-Wiki have become **outdated**. While MediaWiki.org was designated as the primary site for hosting comprehensive documentation**Without a systematic process for updates and review**, these pages fail to provide the **most current and relevant information to users**, a significant portion of material remains scattered on Meta-Wikithereby **diminishing the utility and reliability of the documentation** as a whole.
**3. This dispersal presents several challenges:
1.Specificity to Wikimedia Projects: **Some of the documentation on Meta-Wiki is **uniquely tailored to how MediaWiki is used within Wikimedia projects**. This specificity means that while certain content is crucial for Wikimedia project contexts and should remain on Meta, Redundancy and Overlap: There exists considerable overlap between the pages on Meta-Wiki and MediaWiki.org.it **unnecessarily clutters** general MediaWiki documentation for broader audiences.
**4. Contributor Engagement and Strategy:** Historically, However,the migration and maintenance of documentation have suffered from a **lack of sustained contributor engagement**. because of licensing constraints and the presence of corresponding pages that already exist on MediaWiki.org,Volunteers and contributors often initiate documentation projects but may not see them through to completion, leading to stalled or incomplete content migration. direct importation of content from Meta-Wiki is not feasible.Additionally, This redundancy complicates the process for users seeking specific information and burdens documentation maintainers with inconsistent and duplicated content.there is a **noted absence of a cohesive strategy** to **manage and expedite** this migration process efficiently as mentioned by **Benoît Evellin** in **T181380**
2. Outdated Information: Many of the MediaWiki documentation pages still hosted on Meta-Wiki have become outdated. Without a systematic process for updates and review, these pages fail to provide the most current and relevant information to users, thereby diminishing the utility and reliability of the documentation as a whole.**My Approach**
3. Specificity to Wikimedia Projects: Some of the documentation on Meta-Wiki is uniquely tailored to how MediaWiki is used within Wikimedia projects. This specificity means that while certain content is crucial for Wikimedia project contexts and should remain on Meta, it unnecessarily clutters general MediaWiki documentation for broader audiences.**Phase 1: Integrate and Update Existing Documentation
Objective: Efficiently integrate and update existing documentation listed under MediaWiki_documentation_on_Meta-Wiki/List#Has_MediaWiki.org_equivalent.**
4. Contributor Engagement and Strategy: Historically, the migration and maintenance of documentation have suffered from a lack of sustained contributor engagement. Volunteers and contributors often initiate documentation projects but may not see them through to completion, leading to stalled or incomplete content migration. Additionally, there is a noted absence of a cohesive strategy to manage and expedite this migration process efficiently as mentioned by Benoît Evellin in T181380**Actions:
My Approach1.Performing in-depth content assessment:**
Part 1: Integrate and Update Existing DocumentationFrom my research, it has become clear that **maintaining documentation has been challenging due to the presence of corresponding pages**.
Objective: Efficiently integrate and update existing documentation listed under MediaWiki_documentation_on_Meta-Wiki/List#Has_MediaWiki.org_equivalent.
Actions:**Page-by-Page Content Comparison:**Conduct a thorough **comparison of each Meta-Wiki page that has a corresponding page on MediaWiki.org**.
1.Performing in-depth content assessment:**Review Of Content:**Utilize a **comparison tool like MediaWiki diff along with a manual side-by-side review** to identify **discrepancies, missing information, or content redundancy**.
From my research,**2. it has become clear that maintaining documentation has been challenging due to the presence of corresponding pages.Strategic Content Integration:**
Page-by-Page Content Comparison:Conduct a thorough comparison of each Meta-Wiki page that has a corresponding page on MediaWiki.org **Missing Information:** Integrate **any missing or outdated information from Meta-Wik**i into the corresponding MediaWiki.org page**. Ensure** accuracy, consistency, and completeness **of the consolidated content.
Review Of Content:Utilize a comparison tool like MediaWiki diff along with a manual side-by-side review to identify discrepancies, missing information, or content redundancy.
2. Strategic Content Integration:**Elimination of Duplicate Content: ** Identify and **remove redundant sections** **from either platform to **streamline the documentation and avoid user confusion**.
Missing Information: Integrate any missing or outdated information from Meta-Wiki into the corresponding**Content Enhancement:** Adapt the Meta-Wiki content to **fit the style and format standards of MediaWiki.org page.**, Ensure accuracyincluding **adjusting language tone, consistencytechnical terms, and completeness of the consolidated contentpresentation formats**.
Elimination of Duplicate Content: Identify and remove redundant sections from either platform to streamline the documentation and avoid user confusion.**3. Validation Of Content and Legal Compliance:**
Content Enh**Licensing Compliancement: Adapt the Meta-Wiki Verification:**Check all content to fitfor **compliance with the style and format standards oflicensing requirements** specific to MediaWiki.org, including adjusting language tone, technical terms, and presentation formats.
3. Validation Of Censuring all integrated content and Ldheres to legal Compliance:standards.
Licensing Compliance Verification:Check all content for compliance with the licensing requirements specific to MediaWiki.org**Licensing Adaptation and Community Collaboration:** I will **work closely with MediaWiki's technical writers and community** to **address and resolve GFDL and CC-BY-SA licensing issues**. Our goal will be to **create legally compliant solutions** for** adapting** and **migrating content from MetaWiki to MediaWiki**.I am also dedicated to** refining the content management approach**, **ensuring all integrated content adheres to legalnew MediaWiki pages comply with Creative Commons and GNU Free Documentation License standards**.
Licensing Adaptation and Community Collaboration:I will work closely with MediaWiki's technical writers and community to address and resolve GFDL and CC-BY-SA licensing issues.**Content Rewriting:** For content with restrictive licensing, Our goal will be**rewrite sections to create legally compliant soluonvey the same informations for adapt while adhering and migrating content from MetaWiki to MediaWiki.to MediaWiki.org's licensing guidelines.**
I am also dedicated to refining the content management approach,**4. ensuring new MediaWiki pages comply with Creative CommonsCollaboration and GNU Free Documentation License standards.Feedback:**
Content Rewriting: For content with restrictive licensing, rewrite sections to convey the same information while adhering to MediaWiki.org's licensing guidelines.
4. Collaboration and Feedback:**Establishment of Community Feedback Mechanism:** Establish a feedback mechanism so that the **technical writers and community members review and comment** on the updated documentation before final publication.
-Establishment of Community Feedback Mechanism:Establish a feedback mechanism so that the technical writers and community members review and comment on the updated documentation before final publication**Incorporation of Community Insights**:Incorporate the **technical writers’ and community’s feedback**** to **refine documentation, enhancing its accuracy and relevance**. **Implement final edits **based on this feedback.
- Incorporation of Community Insights:Incorporate the technical writers’ and community’s feedback to refine documentation, enhancing its accuracy and relevance. Implement final edits based on this feedback.
**5. Documentation Redirection and Tracking:**
**Setup of Redirections: Set**Set up appropriate redirects from Meta-Wiki to the updated pages on MediaWiki.org, ensuring a seamless transition for users.
**Migration Documentation: **Maintain a log or tracking system to document the migration process, including migrated content, resolved licensing issues, and any redirects implemented.
**Enhancements Through Cross-Linking:** Implement strategic cross-links between related pages on MediaWiki.org and Meta-Wiki. This effort aims to improve information accessibility and enrich the user's learning path.
**Phase 2: Creation of Missing Documentation
Objective: Create and establish new pages on MediaWiki.org for topics identified under MediaWiki_documentation_on_Meta-Wiki/List#No_MediaWiki.org_equivalent that currently lack adequate documentation.**
**Actions:**
**1. Gap Analysis and Content Planning:**
-** Identifying topics from Meta-Wiki:**Identify topics** from Meta-Wiki that** require new documentation **on MediaWiki.org.
-Planning content structure and layout:Plan content structure and layout in advance,** Planning content structure and layout:**Plan **content structure and layout** in advance, considering the best practices for **readability and user engagement**.
**Content Evaluation: **Assess the **relevance and importance of the content** on these Meta-Wiki pages for the MediaWiki user base. considering the best practices for readability and user engagement.Prioritize content that addresses significant gaps in the existing MediaWiki.org documentation
Content Evaluation: Assess the relevance and importance of the content on these Meta-Wiki pages for the MediaWiki user base. Prioritize content that addresses significant gaps in the existing MediaWiki.org documentation
2. Engaging and Informative Content Creation:
**Content Creation: ** **Develop new pages** on MediaWiki.org that comprehensively **cover the information from the selected Meta-Wiki pages**.Make sure that the** new pages are both informative and engaging**, ensuring the **content provides value to both new users and experienced practitioners.
Image Management for Comprehensive Documentation:Image management is vital for enhancing the comprehensiveness and visual appeal of the documentation on MediaWiki.org. Considerations include:**
Ensuring visual consistency by transferring relevant images from Meta-Wiki to MediaWiki.org, contributing to a seamless user experience.Along with addressing legal and licensing considerations when transferring images to maintain compliance and prevent copyright violations.For Eg:Utilizing images from Wikimedia Commons, which typically have appropriate licensing,**Image Management for Comprehensive Documentation**:Image management is vital for enhancing the **comprehensiveness and visual appeal **of the documentation on MediaWiki.org. can streamline the process and mitigate legal risks associated with image usage.[I have done this in my previous work with MediaWiki during the Outreachy Internship-you can check out my blog posts for the same]Considerations include:
Formatting and Style: Adhere to established MediaWiki.org documentation standards and formatting guidelines for consistency and user experience.**Ensuring visual consistency by transferring relevant images from Meta-Wiki to MediaWiki.org**, contributing to a seamless user experience.Along with **addressing legal and licensing considerations when transferring images** to maintain compliance and prevent copyright violations.For Eg:U**tilizing images from Wikimedia Commons**, which typically have appropriate licensing, can **streamline the process and mitigate legal risks associated with image usage.[I have done this in my previous work with MediaWiki during the Outreachy Internship-you can check out my blog posts for the same]**
Clarity and Comprehensiveness: Present the information clearly, logically, and in a user-friendly manner, including relevant examples and usage instructions.Use rich media, such as diagrams, code snippets, and screenshots, to enhance textual content and aid comprehension.
3.Licensing Considerations in Content Creation**Formatting and Style:** **Adhere** to established **MediaWiki.org documentation standards and formatting guidelines** for consistency and user experience.
Verification of Licensing Compliance:Me along with the technical writers and community members should verify that all newly created content adheres to the guidelines and licensing requirements of MediaWiki.org and any content transferred from Meta-Wiki is thoroughly checked to ensure it complies with MediaWiki.org's licensing standards.Adherence to the protocol outlined in Meta:MetaProject_to_transfer_content_to_MediaWiki.org/si,should be ensured to maintain consistency and follow established procedures.
Incorporation of External Content:If external sources are referenced or incorporated into the new documentation**Clarity and Comprehensiveness:** **Present the information clearly, logically, and in a user-friendly manner**, we have to ensure that they meet the appropriate licensing standards of MediaWiki.org.
Help Page Consideration:Special attention is given to pages intended for the "Help" namespace as stated in the project proposalincluding **relevant examples and usage instructions**.Use **rich media, such as diagrams, as they may have specific licensing requirements.
4.code snippets, and screenshots**, Community Collaboration for Content Review:to enhance textual content and aid comprehension.
Internal Review: Involve technical writers,MediaWiki experts and community members in reviewing the newly created pages for practical**3.Licensing Considerations in Content Creation**
**Verification of Licensing Compliance:**Me along with the technical writers and community members should **verify that all newly created content adheres to the guidelines and licensing requirements of MediaWiki.org** and **any content transferred from Meta-Wiki is thoroughly checked to ensure it complies with MediaWiki.org's licensing standards**.Adherence to the protocol outlined in[[ https://meta.wikimedia.org/wiki/Meta:MetaProject_to_transfer_content_to_MediaWiki.org/si | Meta:MetaProject_to_transfer_content_to_MediaWiki.org/si ]] , should be ensured to maintain consistency and follow established procedures.
**Incorporation of External Content:**If **external sources are referenced or incorporated** into the new documentation, we have to ensure that** they meet the appropriate licensing standards of MediaWiki.org.**
**Help Page Consideration:**S**pecial attention** is given to pages intended for the** "Help" namespace as stated in the project proposal**, as they **may have specific licensing requirements.**
**4. Community Collaboration for Content Review:**
**Internal Review:** Involve **technical writers,MediaWiki experts and community members in reviewing the newly created pages** for **practical needs,accuracy, clarity, and completeness.During this review,**During this review, **group the newly created pages into subject areas for better organization and navigation**. This will **help users easily find relevant information on specific topics.**
**Assessment of Pages Within Subject Areas:**During the **audit of newly created pages within each subject area**, the **focus will lie on identifying missing information** crucial for **enhancing the completeness and relevance of MediaWiki.org documentation**. group the newly created pages into subject areas for better organization and navigationDetermining the **optimal placement of supplementary details** within the **existing documentation structure** is **crucial for coherence. This will help users easily find relevant information on specific topics.
Assessment of Pages Within Subject Areas:During the audit of newly created pages within each subject area**
**Community Feedback:** Seek **feedback from the broader MediaWiki community** on the **new content through established communication channels**.
**Iterative Improvement:** Based on feedback, the focus will lie on identifying missing information crucial for enhancing the completeness and relevance of MediaWiki.org documentation.**revise and refine the new pages **based on **assessment findings to ensure they meet user needs** and **effectively address knowledge gaps**.Implementation of necessary changes will ensure comprehensive, relevant, Determining the optimal placement of supplementary details within the existingand gap-free documentation structure is crucial for coherencetion.
Community Feedback: Seek feedback from the broader MediaWiki community on the new content through established communication channels.**5. Usability Testing ,Optimization and Publish:**
Iterative Improvement: Based on feedback, revise and refine the new pages based on assessment findings to ensure they meet user needs and effectively address knowledge gaps.Implementation of necessary changes will ensure comprehensive, relevant, and gap-free documentation.
5. Usability Testing ,Optimization and Publish:**Usability testing with a subset of end-users:** Usability testing with a** subset of end-users** to **evaluate the ease of navigation and information retrieval** within the new documentation.
Usability testing with a subset of end-users: Usability testing with a subset of end-users to evaluate the ease of navigation and information retrieval within the new documentation**Refining and optimizing content based on testing outcomes**:**Refine and optimize content** based on testing outcomes to ensure superior user experience.
Refining and optimizing content based on testing outcomes:Refine and optimize content based on testing outcomes to ensure superior user experience**Publishing:**Upon completion of the content review and approval process, proceed to **publish the updates on MediaWiki.or**g, ensuring that the revised documentation is **readily accessible to users.
Publishing:Upon completion of the content review and approval process, proceed to publish the updates on MediaWiki.org, ensuring that the revised documentation is readily accessible to users.
#### **
**Phase 3: Organization and Usability Enhancement
Objective: Enhance the organization and usability of WMF-specific content listed under Project:MediaWiki_documentation_on_Meta-Wiki/List#Actually_WMF-specific.**
This phase encompasses an** array of pages tailored to support the WMF community (contributors, researchers, editors, etc.)** in various tasks such as user management, logins etc.
**Challenges:
Discoverability:** Due to their location on Meta-Wiki, **these pages might not be easily discovered** by users primarily focused on MediaWiki documentation.
**Maintainability: ** **Scattered content can be challenging to update and maintain** over time.
Actions:
**1. Content Review and User Research:**
**Content Review**:Conduct a **detailed review of all WMF-specific content to **to **determine current usage patterns and areas **needing improvement.Identify **outdated or irrelevant content for revision or removal**.
**User Research: **Understand how**how users currently find and utilize WMF-specific documentation**. This could **involve user interviews, surveys, or analyzing access logs.[I have conducted many informational interviews during my Outreachy project “Multilingual Wikipedia Editor Survey,so that experience would be helpful]
2.Information Architecture Design:**
Structure Optimization: Based on the content review and user research, design an improved information architecture for WMF-specific content.**2.Information Architecture Design:**
Consideration Points: This could involve:**Structure Optimization:** Based on the content review and user research, **design an improved information architecture for WMF-specific content.**
**Categorization: ****Organize pages into clear,well-defined,intuitive and user-friendly categories **based on topic or project.
**Tagging:** Implement a **tagging and metadata system **to allow for easier **discovery** based on relevant keywords.
**Navigation: **Design a **clear navigation structure** within Meta-Wiki or** link prominently **from MediaWiki.org for easy access.
3. Implementation and User/Stakeholder Feedback Integration:
Implementation: Apply the chosen information architecture to organize WMF-specific content on Meta-Wiki. This may involve moving pages, creating category structures, and implementing tagging systems. Roll out the new organizational structure in stages,**3. allowing users to adapt to changes gradually.Implementation and User/Stakeholder Feedback Integration:**
User Feedback Integration:Collect and integrate user and stakeholders feedback to refine the organizational tweaks, ensuring the new system meets the needs of a diverse user base.
4. Maintenance Strategy:.
Maintenance Plan: Develop a clear plan for ongoing maintenance of WMF-specific content. This includes establishing regular reviews and forming guidelines for updating information, managing contributor access,**Implementation: **Apply the **chosen information architecture** to organize WMF-specific content on Meta-Wiki. and version control.This will also include rolesThis may involve m**oving pages, procedcreating category structures, and schedules to ensure the coimplementinuous upkeep of MediaWiki documentation,g tagging systems**. guaranteeing its relevance and accuracy over time.Introduce versioning systems to monitor alterations and updates systematicallyRoll out the **new organizational structure in stages, fosterallowing transparency and responsibility within the content.
5.Communication and Collaboration:users to adapt to changes gradually.**
Community Volunteer Engagement:Engage with a dedicated team of community volunteers and take their assistance with the ongoing maintenance and updating of the documentation.
Community Engagement: Engage with the MediaWiki community and WMF teams to gather feedback on the work and usability of the WMF-specific content.** User Feedback Integration:**Collect and integrate user and stakeholders feedback to r**efine the organizational tweaks**, ensuring the** new system meets the needs of a diverse user base.**
Collaboration: Encourage WMF-specific content contributions from relevant stakeholders.
Through my approach we will be able to achieve this goals:**4. Maintenance Strategy:**
Reduce Pages Requiring Migration: Aim to reduce the number of pages requiring migration to MediaWiki.org from 91 to 0**Maintenance Plan: **Develop a clear plan for ongoing maintenance of WMF-specific content. This includes **establishing regular reviews and forming guidelines for updating information, managing contributor access, and version control**.This will also include **roles, procedures, and schedules** to ensure the** continuous upkeep of MediaWiki documentation**, **guaranteeing its relevance and accuracy over time.**Introduce **versioning systems to monitor alterations** and **updates systematically**, ensu**fostering comprehensive coveragetransparency and accesresponsibility of documentation.within the content.**
Enhance Organization and Usability: Improve the organization and usability of Meta-Wiki pages related to MediaWiki, making them easier to use and maintain for community members and contributors.**5.Communication and Collaboration:**
Foster Collaboration: Foster a collaborative and inclusive documentation ecosystem within the MediaWiki community, ensuring that documentation remains relevant and valuable to users and contributors alike**Community Volunteer Engagement:**Engage with a **dedicated team of community volunteers and take their assistance with the ongoing maintenance and updating** of the documentation.
Encouraging Contributor Efforts: Foster a supportive environment by recognizing and celebrating contributors' efforts, encouraging active participation in documentation updates**Community Engagement: **Engage with the MediaWiki community and WMF teams to** gather feedback on the work ****and usability** of the WMF-specific content.
Providing Daily Logs:Share daily progress logs with the mentors to keep them informed about project developments and encourage transparency in the documentation process.**Collaboration: ****Encourage WMF-specific content contributions from relevant stakeholders.**
**Through my approach we will be able to achieve this goals:**
Final Report Prepa**Reduce Pages Requiring Migration:Compile a comprehensive final report detail **Aim to **reduce the number of pages requiring project outcomes, achievements, and key learningsmigration to MediaWiki.org from 91 to 0**, providensuring stakeholders with a clear understandingcomprehensive coverage and accessibility of the project's impactdocumentation.
**Enhance Organization and Usability:** **Improve the organization and usability of Meta-Wiki pages related to MediaWiki**, Checkpoint Calls:Schedule regular checkpoint calls with team members to review progressmaking them easier to use and maintain for community members and contributors.
**Foster Collaboration:** Foster a **collaborative and inclusive documentation ecosystem within the MediaWiki community**, address challengesensuring that documentation remains relevant and valuable to users and contributors alike.
**Encouraging Contributor Efforts:** Foster a **supportive environment by recognizing and celebrating contributors' efforts**, and adjust strategies as needed, fostering a collaborative and adaptive project environmentencouraging **active participation** in documentation updates.
** Providing Daily Logs:**Share** **daily progress logs** with the mentors** to keep them informed about **project developments and encourage transparency** in the documentation process.
Continuous Learning and Adaptation:Embrace a **Final Report Preparation:**Compile a **comprehensive final report detailing project outcomes, achievements, and key learnings**, providing stakeholders with a clear understanding of the project's impact.
** Checkpoint Calls:**Schedule r**egular checkpoint calls with team members to review progress, address challenges, and adjust strategies** as needed, fostering a collaborative and adaptive project environment.
**Continuous Learning and Adaptation:**Embrace a **culture of continuous learning and adaptation **by staying updated with the latest documentation strategies and technologies.
TIMELINE
**Timeline**
**Before May 20:**
- Continue making contributions to the organization by actively participating in relevant discussions, contributing edits, and engaging with the community.
- Dive deeper into user documentation, familiarizing yourself with the structure, content, and style of existing documentation on Meta-Wiki and MediaWiki.org.
**May 20 - June 1: Project Kickoff and Onboarding (2 weeks)**
- Establish clear communication channels with mentors, project members, and stakeholders to ensure effective collaboration throughout the project.
- Review your compiled list of unconsolidated pages on Meta-Wiki and identify potential areas for improvement or consolidation.
- Conduct detailed discussions with mentors to analyze project goals, scope, and requirements, refining your understanding of the project objectives.
- Set up accounts, access necessary tools, and familiarize yourself with the project plan, goals, and timelines.
- Develop a comprehensive plan for project execution, outlining specific tasks, timelines, and responsibilities.
- Determine the frequency and format of project updates and check-ins with mentors and project members.
**June 2 - June 29: Phase 1: De-duplication (4 weeks)**
- Utilize your compiled list of duplicated pages on Meta-Wiki to systematically identify duplicate content and corresponding MediaWiki.org equivalents.
- Engage in thorough content audits, comparing Meta-Wiki pages with their counterparts on MediaWiki.org to identify redundant or overlapping information.
- Prioritize pages for consolidation based on relevance, usage, and community feedback.
- Begin the process of removing duplicate content from Meta-Wiki and updating MediaWiki.org pages with any missing information.
- Work closely with mentors and project members to ensure accuracy, completeness, and consistency across documentation platforms.
- Regularly update progress reports and seek feedback on de-duplication efforts to address any challenges or discrepancies promptly.
**June 30 - August 31: Phase 2: New Content (9 weeks)**
- Review Meta-Wiki pages listed under "No MediaWiki.org equivalent" and identify areas requiring new content creation or enhancement on MediaWiki.org.
- Develop a structured approach for writing new documentation for MediaWiki.org, focusing on clarity, accuracy, and relevance to users.
- Collaborate with mentors and project members to create detailed outlines for new content, ensuring alignment with project goals and community needs.
- Engage in a feedback loop with stakeholders, incorporating their input into the development process to improve the quality and usability of the documentation.
- Regularly review and update progress reports, tracking the completion status of each documentation page and addressing any bottlenecks or challenges proactively.
- Finalize and publish new content on MediaWiki.org, ensuring proper attribution, formatting, and integration with existing documentation.
**September 1 - September 29: Phase 3: Organization (4 weeks)**
- Conduct a comprehensive review of Wikimedia-specific content on Meta-Wiki, identifying opportunities to improve information architecture and organization.
- Collaborate with mentors and stakeholders to develop a structured plan for reorganizing Meta-Wiki content, focusing on usability, discoverability, and maintenance.
- Implement changes to Meta-Wiki pages based on the revised information architecture, ensuring logical categorization and clear navigation paths for users.
- Gather feedback from the community on the proposed organizational changes, incorporating their suggestions and addressing any concerns or usability issues.
- Conduct thorough testing of the updated Meta-Wiki pages to ensure a seamless user experience and effective dissemination of information.
- Document the process of organization and information architecture design, outlining best practices and lessons learned for future reference and knowledge sharing.
**
September 30 - October 12: Phase 4: User Feedback (2 weeks)**
Conduct Q&A sessions and surveys with community members and users to gather feedback on the updated Meta-Wiki pages and information architecture.
Analyze feedback received from the community, identifying trends, common issues, and areas for improvement.
Collaborate with mentors and project members to prioritize and address feedback, making necessary revisions to enhance usability and user satisfaction.
Communicate with stakeholders to share insights from user feedback sessions and solicit additional input or suggestions for further improvements.
**October 13 - October 26: Project Wrap-Up (2 weeks)**
Implement user feedback by making final revisions and adjustments to the Meta-Wiki pages and information architecture as needed.
Complete any remaining cleanup tasks, such as reviewing and revising outdated or obsolete documentation.
Identify any follow-up work, additional tasks, and potential areas for improvement required to ensure the long-term sustainability of the documentation consolidation efforts.
Write a comprehensive project report detailing the outcomes, learnings, best practices, and recommendations for future projects.
Finalize and publish the project report for stakeholders and the wider community, summarizing the project journey and highlighting key achievements and insights.
I am **flexible and willing to adjust the timeline as needed to accommodate project requirements** and ensure optimal outcomes.
**Proposed Budget:$10,500 **