Change Details

===Profile Information=== **Name**: Mahfuza Humayra Mohona **IRC nickname on Zulip**: mhmohona [[ https://drive.google.com/file/d/1Vm7iklgBpia-mLB6bx0FYk3-O0JdXhJL/view | Resume ]] | [[ https://github.com/mhmohona | GIthub ]] | [[ https://www.linkedin.com/mhmohona | LinkedIn ]] **Location** - Bangladesh (GMT +6) ===Introduction=== The MediaWiki documentation hosted across Meta-Wiki and MediaWiki.org has become fragmented and difficult to navigate for both users and contributors. While MediaWiki.org was established as the central repository for MediaWiki documentation, there are still numerous pages on Meta-Wiki that contain relevant MediaWiki information. This duplication creates challenges in maintaining consistent and up-to-date documentation. The goal of [[ https://www.mediawiki.org/wiki/Season_of_Docs/2024/Proposal# | this project ]] is to consolidate MediaWiki's help documentation by identifying duplicate content between MediaWiki.org and Meta-Wiki, and migrating relevant content from Meta-Wiki to MediaWiki.org. This involves auditing each Meta page to find its MediaWiki.org equivalent, identifying any information that needs to be added to the MediaWiki.org page, and any information that is specific to Wikimedia and needs to stay on Meta. The primary goal is to improve the accessibility and usability of MediaWiki's documentation for both new and existing users. ===Deliverables=== - **Audit Report**: A comprehensive [[ https://docs.google.com/spreadsheets/d/1P2OKBg68hixEZkDEjl-XKTIY9UKt8nHaVvnlBljlSUM/edit?usp=sharing | report]] detailing the audit of each Meta page, including its MediaWiki.org equivalent, any additional information that needs to be added to MediaWiki.org, and any information that is specific to Wikimedia and needs to stay on Meta. - **Migrated Content**: Content migrated from Meta-Wiki to MediaWiki.org, ensuring that MediaWiki.org has a comprehensive and up-to-date documentation base, correctly connected pages and all the links. - **Feedback and Revision Documentation**: Documentation of the feedback received during the project, including any revisions made to the migrated content based on this feedback. - **Finalized Documentation**: The finalized version of the documentation on MediaWiki.org, reflecting all migrated content and any necessary adjustments based on feedback. ===Stretch Goal=== Develop a sustainable process for maintaining and updating the consolidated MediaWiki documentation on MediaWiki.org, ensuring that the information remains current and accessible. ===Mentors=== Alex Paskulin ===Participation=== **Communication Medium**: Zullip **Communication Frequency**: Attending Community meeting, 1:1 call with mentors --- === Discussion=== This project is going to have 3 phases - - Phase 1: De-duplication - Phase 2: New content - Phase 3: Organize =====Phase 1: Addressing Pages with MediaWiki.org Equivalents===== 1. **Comprehensive Review of Pages**: - Review each page listed under the "Has MediaWiki.org equivalent" section on the "Project:MediaWiki_documentation_on_Meta-Wiki/List" page. - For each page, identify the corresponding MediaWiki.org page that serves as the equivalent. 2. **Content Comparison and Migration**: - Conduct a detailed comparison of the content between the Meta-Wiki page and the MediaWiki.org equivalent page. - Identify any information on the Meta-Wiki page that is missing from or needs to be added to the MediaWiki.org page. - Migrate the relevant content from the Meta-Wiki page to the MediaWiki.org page, ensuring the information is accurate and up-to-date. 3. **Licensing Considerations**: - Verify that the content being migrated from Meta-Wiki to MediaWiki.org is properly licensed under the MIT license, as required by MediaWiki.org. - If necessary, work with the Wikimedia community to relicense the content from the CC-BY-SA license used on Meta-Wiki. 4. **Redirects and Cross-linking**: - Set up appropriate redirects from the Meta-Wiki page to the corresponding MediaWiki.org page. - Ensure there are clear cross-links between the two pages to maintain the seamless flow of information for users. 5. **Community Feedback and Validation**: - Engage with the Wikimedia community to gather feedback on the proposed content migrations and changes. - Incorporate the community's suggestions and validate the changes to ensure they meet the users' needs. 6. **Documentation Maintenance**: - Establish a sustainable process for the ongoing maintenance and update of the consolidated MediaWiki documentation on MediaWiki.org. - Identify and train a team of contributors responsible for maintaining the documentation in the long term. =====Phase 2: Addressing Pages with No MediaWiki.org Equivalents===== 1. **Create MediaWiki.org Pages**: - For each page listed under Project:MediaWiki_documentation_on_Meta-Wiki/List#No_MediaWiki.org_equivalent, create a corresponding MediaWiki.org page that covers the content on the Meta page. 2. **Review and Group Pages**: - Review the newly created pages and group them into subject areas for better organization and navigation. 3. **Audit Pages in Subject Areas**: - Audit pages in each subject area and identify: - Any information that needs to be added to MediaWiki.org. - Where the information should be added in the context of the related MediaWiki.org documentation. - Any information that is specific to Wikimedia and needs to stay on Meta. 4. **Transferral of Images**: - Images located on Wikimedia Commons do not need any changes and can be used directly in MediaWiki.org pages. - Images on Meta that are used solely within pages that will be exported can be transferred to MediaWiki.org. In this case, tag them appropriately. - Images that are used in pages to be transferred but also in other pages on Meta should be moved to Commons, as well as other images allowed by Commons' guidelines. 5. **Licensing Considerations**: - Most content on MediaWiki.org is licensed under the GFDL, allowing direct movement of content from Meta to MediaWiki.org. However, be cautious with the 'PD Help' project, as the licenses are not compatible. - When transferring pages, ensure to follow 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 ]], including not moving any page that has not been displaying the 'MoveToMediaWiki' template for at least 2 weeks and not moving pages into the Help: namespace due to license incompatibility. 6. **Write Content and Get Feedback**: - Write the necessary content for each new page on MediaWiki.org, ensuring it is original and not copied from Meta without proper consideration of copyright and licensing issues. - Seek feedback from the community on the new content. This could involve posting drafts on the MediaWiki.org talk pages or seeking input from other contributors. 7. **Publish**: - Once the content has been reviewed and approved, publish the updates on MediaWiki.org. ===Phase 3: Organizing Wikimedia-Specific Content=== 1. **Review Wikimedia-Specific Content on Meta** - Review the content on Meta, including the content in the "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific" category identified during Phases 1 and 2 - Carefully examine this Wikimedia-specific content to understand its purpose and relevance 2. **Design an Information Architecture** - Based on the review, design an information architecture for the Wikimedia-specific content on Meta - Organize the content into logical, user-friendly categories and subcategories - Ensure the structure makes it easy for users to navigate and discover the information they need 3. **Get Feedback** - Share the proposed information architecture with the Wikimedia community and gather feedback - Incorporate the community's suggestions to refine the design and ensure it meets their needs 4. **Implement Changes to meta:Help** - For the pages listed under "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific": - Review the pages for usability and identify areas for improvement - Design and implement an organization structure to make these pages easy to discover and maintain - Publish the updated meta:Help pages with the new organizational structure 5. **Ongoing Maintenance** - Establish a process for regularly reviewing and updating the Wikimedia-specific content on Meta - Identify a team of contributors responsible for maintaining the content and information architecture over time - Monitor user feedback and adjust the organization as needed to ensure the content remains accessible and relevant ===Tentative timeline=== **Project kickoff and onboarding (May 20 - June 1)** - Analyze the project in detail with mentor and finalize the project scope. - Discuss about: - How often the tasks should be reviewed. - Share schedules and decide on a weekly/daily workflow. - Bi-weekly and daily project reports. - Create the required tasks and subtasks on Phabricator. **Week 1 (June 2 - June 8)** 1. **Comprehensive Review of Pages**: - Review the 20 pages listed under the "Has MediaWiki.org equivalent" section on the "Project:MediaWiki_documentation_on_Meta-Wiki/List" page. - Identify the corresponding MediaWiki.org page that serves as the equivalent for each page. 2. **Licensing Considerations**: - Verify that the content being migrated from all 20 Meta-Wiki pages is properly licensed under the MIT license, as required by MediaWiki.org. - Identify any content that needs to be relicensed from the CC-BY-SA license used on Meta-Wiki. 3. **Community Engagement**: - Inform the Wikimedia community about the project and gather initial feedback. - Address any concerns or questions raised by the community. **Week 2 (June 9 - June 15)** 1. **Licensing Considerations (continued)**: - Work with the Wikimedia community to relicense any content that needs to be relicensed from CC-BY-SA to MIT. 2. **Content Comparison and Migration**: - Conduct a detailed comparison of the content between the first 4-5 Meta-Wiki pages and their MediaWiki.org equivalents. - Identify and migrate any relevant information from the Meta-Wiki pages to the MediaWiki.org pages, ensuring accuracy and up-to-dateness. 3. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the project and the initial set of pages. **Week 3 (June 16 - June 22)** 1. **Content Comparison and Migration (continued)**: - Conduct a detailed comparison of the content between the next 4-5 Meta-Wiki pages and their MediaWiki.org equivalents. - Identify and migrate any relevant information from the Meta-Wiki pages to the MediaWiki.org pages, ensuring accuracy and up-to-dateness. 2. **Redirects and Cross-linking**: - Set up appropriate redirects from the Meta-Wiki pages to the corresponding MediaWiki.org pages for the completed set of pages. - Ensure there are clear cross-links between the two pages to maintain the seamless flow of information for users. - Gather community feedback on the proposed redirects and cross-links. 3. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the content migration and redirects/cross-links for the completed set of pages. **Week 4 (June 23 - June 29)** 1. **Content Comparison and Migration (continued)**: - Conduct a detailed comparison of the content between the remaining Meta-Wiki pages and their MediaWiki.org equivalents. - Identify and migrate any relevant information from the Meta-Wiki pages to the MediaWiki.org pages, ensuring accuracy and up-to-dateness. 2. **Testing and Quality Assurance**: - Thoroughly review the migrated content, redirects, and cross-links for all 20 pages. - Involve the project team and select community members to ensure the migrated documentation meets the required standards and user expectations. 3. **Address Backlog and Blockers**: - Address any remaining tasks, feedback, or blockers related to the content migration for the 20 pages. 4. **Documentation Maintenance**: - Establish a sustainable process for the ongoing maintenance and update of the consolidated MediaWiki documentation on MediaWiki.org. - Identify and train a team of contributors responsible for maintaining the documentation in the long term. 5. **Buffer Time**: - Allocate buffer time to accommodate any unforeseen delays or additional tasks that may arise during the project. **Week 5 (June 30 - July 6)** 1. **Create MediaWiki.org Pages**: - For each page listed under Project:MediaWiki_documentation_on_Meta-Wiki/List#No_MediaWiki.org_equivalent, create a corresponding MediaWiki.org page. - These new pages should cover the content from the Meta pages. 2. **Review and Group Pages**: - Review the newly created MediaWiki.org pages. - Group them into subject areas for better organization and navigation. **Week 6 (July 7 - July 13)** 1. **Audit Pages in Subject Areas**: - Audit pages in each subject area and identify: - Any information that needs to be added to MediaWiki.org. - Where the information should be added in the context of the related MediaWiki.org documentation. - Any information that is specific to Wikimedia and needs to stay on Meta. 2. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the newly created MediaWiki.org pages and subject area grouping. **Week 7 (July 14 - July 20)** 1. **Transferral of Images**: - Identify images located on Wikimedia Commons that can be used directly in the new MediaWiki.org pages. - Identify images on Meta that are used solely within pages being exported and tag them appropriately for transfer to MediaWiki.org. - Move images that are used in pages being transferred but also in other Meta pages to Wikimedia Commons, following the guidelines. 2. **Licensing Considerations**: - Ensure that the content being transferred from Meta to MediaWiki.org is properly licensed under the GFDL. - Be cautious with the 'PD Help' project, as the licenses are not compatible. - Follow 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 ]], including not moving any page that has not been displaying the 'MoveToMediaWiki' template for at least 2 weeks and not moving pages into the Help: namespace due to license incompatibility. **Week 8 (July 21 - July 27)** 1. **Write Content and Get Feedback**: - Write the necessary content for each new page on MediaWiki.org, ensuring it is original and not copied from Meta without proper consideration of copyright and licensing issues. - Seek feedback from the community on the new content by posting drafts on the MediaWiki.org talk pages or seeking input from other contributors. 2. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the new content written for the MediaWiki.org pages. **Week 9 (July 28 - August 3)** 1. **Write Content and Get Feedback (continued)**: - Continue writing and seeking feedback on the remaining new content for the MediaWiki.org pages. 2. **Feedback Review and Incorporation (continued)**: - Review and incorporate community feedback related to the remaining new content. **Week 10 (August 4 - August 10)** 1. **Publish**: - Once the content has been reviewed and approved, publish the updates on MediaWiki.org. 2. **Testing and Quality Assurance**: - Thoroughly review the published content, including links, formatting, and overall quality. - Involve the project team and select community members to ensure the documentation meets the required standards and user expectations. **Week 11 (August 11 - August 17)** 1. **Address Backlog and Blockers**: - Address any remaining tasks, feedback, or blockers related to the content migration for the pages with no MediaWiki.org equivalents. 2. **Buffer Time**: - Allocate buffer time to accommodate any unforeseen delays or additional tasks that may arise during the project. **Week 12 (August 18 - August 24)** 1. **Documentation Maintenance**: - Establish a sustainable process for the ongoing maintenance and update of the newly added MediaWiki documentation. - Identify and train a team of contributors responsible for maintaining the documentation in the long term. **Week 13 (August 25 - August 31)** 1. **Buffer Week**: - Allocate this week as a buffer to address any remaining tasks or issues that may arise during the project. **Week 14 (September 1 - September 7)** 1. **Review Wikimedia-Specific Content on Meta**: - Review the content on Meta, including the content in the "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific" category identified during Phases 1 and 2. - Carefully examine this Wikimedia-specific content to understand its purpose and relevance. 2. **Design an Information Architecture**: - Based on the review, design an information architecture for the Wikimedia-specific content on Meta. - Organize the content into logical, user-friendly categories and subcategories. - Ensure the structure makes it easy for users to navigate and discover the information they need. **Week 15 (September 8 - September 14)** 1. **Get Feedback**: - Share the proposed information architecture with the Wikimedia community and gather feedback. - Incorporate the community's suggestions to refine the design and ensure it meets their needs. 2. **Implement Changes to meta:Help**: - For the pages listed under "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific": - Review the pages for usability and identify areas for improvement. - Design and implement an organization structure to make these pages easy to discover and maintain. **Week 16 (September 15 - September 21)** 1. **Implement Changes to meta:Help (continued)**: - Continue implementing the organization structure for the meta:Help pages. 2. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the proposed changes to meta:Help. **Week 17 (September 22 - September 28)** 1. **Publish Updated meta:Help Pages**: - Once the changes have been reviewed and approved, publish the updated meta:Help pages with the new organizational structure. 2. **Testing and Quality Assurance**: - Thoroughly review the published changes to meta:Help, including navigation, links, and overall user experience. - Involve the project team and select community members to ensure the changes meet the required standards and user expectations. 3. **Ongoing Maintenance**: - Establish a process for regularly reviewing and updating the Wikimedia-specific content on Meta. - Identify a team of contributors responsible for maintaining the content and information architecture over time. **Week 18 (September 29 - October 5)** 1. **Ongoing Maintenance (continued)**: - Continue setting up the ongoing maintenance process for the Wikimedia-specific content on Meta. 2. **Monitor User Feedback**: - Monitor user feedback on the updated meta:Help pages and the new organizational structure. - Adjust the organization as needed to ensure the content remains accessible and relevant. 3. **Address Backlog and Blockers**: - Address any remaining tasks, feedback, or blockers related to the organization of Wikimedia-specific content on Meta. 4. **Buffer Time**: - Allocate buffer time to accommodate any unforeseen delays or additional tasks that may arise during the project. **Week 19 - 21 (October 6 - October 26)** 1. **Identify Cleanup Tasks**: - Conduct a thorough review of the project to identify any remaining cleanup tasks that need to be completed. - Examples of cleanup tasks may include: - Resolving any outstanding issues or bugs - Updating documentation or guides - Addressing any remaining feedback or concerns from the community 2. **Identify Follow-up Work**: - Identify any follow-up work that may be required after the completion of the project. - Examples of follow-up work may include: - Ongoing maintenance and updates to the documentation - Future enhancements or improvements to the documentation 3. **Prioritize and Plan Follow-up Work**: - Prioritize the identified follow-up work based on its importance and urgency. - Develop a plan or schedule for addressing the follow-up work in the future. 2. **Write Project Report**: - Write a comprehensive project report describing the outcomes, learning, best practices, and recommendations for future projects. - The report will cover the following areas: - Project overview and objectives - Key milestones and achievements - Challenges faced and how they were addressed - Lessons learned and best practices - Recommendations for future projects or improvements - Next steps and follow-up work 3. **Review and Finalize Project Report**: - Review the project report with the project team and other stakeholders. - Incorporate any feedback or additional input. - Finalize the report and distribute it to relevant parties. --- ===Past Experience **Writing Portfolio** - [[ https://github.com/mhmohona/writing-portfolio | github/mhmohona/writing-portfolio ]] ====Google Season of Doc -2023 =====AsyncAPI Initiative **Documentation** * [Adding channel](https://github.com/asyncapi/website/pull/2408) * [Dynamic channel](https://github.com/asyncapi/website/pull/2409) * [Extending Specification](https://github.com/asyncapi/website/pull/2407) * [Adding Messages](https://github.com/asyncapi/website/pull/2410) * [Reuse with traits](https://github.com/asyncapi/website/pull/2411) * [Adding binding](https://github.com/asyncapi/website/pull/2042) **Killercoda Tutorial** * [AsyncAPI Specification Basic](https://github.com/asyncapi/learning-paths/pull/5) * [Create & Validate Document](https://github.com/asyncapi/learning-paths/pull/4) =====WasmEdge Runtime * [Plugin - Developer guide](https://github.com/WasmEdge/docs/pull/102) * [Plugin - User guide](https://github.com/WasmEdge/docs/pull/146) * [Plugin Details](https://github.com/WasmEdge/docs/pull/200) * [Plugin - Best Practice](https://github.com/WasmEdge/docs/pull/191) * [Troubleshooting Guide](https://github.com/WasmEdge/docs/pull/192) * [FAQ & Style Guide](https://github.com/WasmEdge/docs/pull/193) * [Community Page](https://github.com/WasmEdge/docs/pull/153) ====Season Of KDE - 2024 =====Labplot **Newly Created pages** * [Data Analysis : Curve Fitting](https://userbase.kde.org/LabPlot/DataAnalysis/CurveFitting) * [Data Analysis : Fourier Transform](https://userbase.kde.org/LabPlot/DataAnalysis/FourierTransfromation) * [CAS Computing](https://userbase.kde.org/LabPlot/CASComputing) * [LaTeX Typesetting](https://userbase.kde.org/LabPlot/LaTeXTypesetting) * [Tools : FITS Metadata Editor](https://userbase.kde.org/LabPlot/FITSMetadataEditor)

===Profile Information=== **Name**: Mahfuza Humayra Mohona **IRC nickname on Zulip**: mhmohona [[ https://drive.google.com/file/d/1iHwWRU9pp16H0vyJrgPVqiZD0MHtEFFB/view?usp=sharing | Resume ]] | [[ https://github.com/mhmohona | GIthub ]] | [[ https://www.linkedin.com/mhmohona | LinkedIn ]] **Location**: Bangladesh (GMT +6) **Availability**: 20-25 hours per week ===Introduction=== The MediaWiki documentation hosted across Meta-Wiki and MediaWiki.org has become fragmented and difficult to navigate for both users and contributors. While MediaWiki.org was established as the central repository for MediaWiki documentation, there are still numerous pages on Meta-Wiki that contain relevant MediaWiki information. This duplication creates challenges in maintaining consistent and up-to-date documentation. The goal of [[ https://www.mediawiki.org/wiki/Season_of_Docs/2024/Proposal# | this project ]] is to consolidate MediaWiki's help documentation by identifying duplicate content between MediaWiki.org and Meta-Wiki, and migrating relevant content from Meta-Wiki to MediaWiki.org. This involves auditing each Meta page to find its MediaWiki.org equivalent, identifying any information that needs to be added to the MediaWiki.org page, and any information that is specific to Wikimedia and needs to stay on Meta. The primary goal is to improve the accessibility and usability of MediaWiki's documentation for both new and existing users. ===Deliverables=== - **Audit Report**: A comprehensive [[ https://docs.google.com/spreadsheets/d/1P2OKBg68hixEZkDEjl-XKTIY9UKt8nHaVvnlBljlSUM/edit?usp=sharing | report]] detailing the audit of each Meta page, including its MediaWiki.org equivalent, any additional information that needs to be added to MediaWiki.org, and any information that is specific to Wikimedia and needs to stay on Meta. - **Migrated Content**: Content migrated from Meta-Wiki to MediaWiki.org, ensuring that MediaWiki.org has a comprehensive and up-to-date documentation base, correctly connected pages and all the links. - **Feedback and Revision Documentation**: Documentation of the feedback received during the project, including any revisions made to the migrated content based on this feedback. - **Finalized Documentation**: The finalized version of the documentation on MediaWiki.org, reflecting all migrated content and any necessary adjustments based on feedback. ===Stretch Goal=== Develop a sustainable process for maintaining and updating the consolidated MediaWiki documentation on MediaWiki.org, ensuring that the information remains current and accessible. ===Mentors=== Alex Paskulin ===Participation=== **Communication Medium**: Zullip **Communication Frequency**: Attending Community meeting, 1:1 call with mentors --- === Project Details=== This project is going to have 3 phases - - Phase 1: De-duplication - Phase 2: New content - Phase 3: Organize =====Phase 1: Addressing Pages with MediaWiki.org Equivalents===== 1. **Comprehensive Review of Pages**: - Review each page listed under the "Has MediaWiki.org equivalent" section on the "Project:MediaWiki_documentation_on_Meta-Wiki/List" page. - For each page, identify the corresponding MediaWiki.org page that serves as the equivalent. 2. **Content Comparison and Migration**: - Conduct a detailed comparison of the content between the Meta-Wiki page and the MediaWiki.org equivalent page. - Identify any information on the Meta-Wiki page that is missing from or needs to be added to the MediaWiki.org page. - Migrate the relevant content from the Meta-Wiki page to the MediaWiki.org page, ensuring the information is accurate and up-to-date. 3. **Licensing Considerations**: - Verify that the content being migrated from Meta-Wiki to MediaWiki.org is properly licensed under the MIT license, as required by MediaWiki.org. - If necessary, work with the Wikimedia community to relicense the content from the CC-BY-SA license used on Meta-Wiki. 4. **Redirects and Cross-linking**: - Set up appropriate redirects from the Meta-Wiki page to the corresponding MediaWiki.org page. - Ensure there are clear cross-links between the two pages to maintain the seamless flow of information for users. 5. **Community Feedback and Validation**: - Engage with the Wikimedia community to gather feedback on the proposed content migrations and changes. - Incorporate the community's suggestions and validate the changes to ensure they meet the users' needs. 6. **Documentation Maintenance**: - Establish a sustainable process for the ongoing maintenance and update of the consolidated MediaWiki documentation on MediaWiki.org. - Identify and train a team of contributors responsible for maintaining the documentation in the long term. =====Phase 2: Addressing Pages with No MediaWiki.org Equivalents===== 1. **Create MediaWiki.org Pages**: - For each page listed under Project:MediaWiki_documentation_on_Meta-Wiki/List#No_MediaWiki.org_equivalent, create a corresponding MediaWiki.org page that covers the content on the Meta page. 2. **Review and Group Pages**: - Review the newly created pages and group them into subject areas for better organization and navigation. 3. **Audit Pages in Subject Areas**: - Audit pages in each subject area and identify: - Any information that needs to be added to MediaWiki.org. - Where the information should be added in the context of the related MediaWiki.org documentation. - Any information that is specific to Wikimedia and needs to stay on Meta. 4. **Transferral of Images**: - Images located on Wikimedia Commons do not need any changes and can be used directly in MediaWiki.org pages. - Images on Meta that are used solely within pages that will be exported can be transferred to MediaWiki.org. In this case, tag them appropriately. - Images that are used in pages to be transferred but also in other pages on Meta should be moved to Commons, as well as other images allowed by Commons' guidelines. 5. **Licensing Considerations**: - Most content on MediaWiki.org is licensed under the GFDL, allowing direct movement of content from Meta to MediaWiki.org. However, be cautious with the 'PD Help' project, as the licenses are not compatible. - When transferring pages, ensure to follow 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 ]], including not moving any page that has not been displaying the 'MoveToMediaWiki' template for at least 2 weeks and not moving pages into the Help: namespace due to license incompatibility. 6. **Write Content and Get Feedback**: - Write the necessary content for each new page on MediaWiki.org, ensuring it is original and not copied from Meta without proper consideration of copyright and licensing issues. - Seek feedback from the community on the new content. This could involve posting drafts on the MediaWiki.org talk pages or seeking input from other contributors. 7. **Publish**: - Once the content has been reviewed and approved, publish the updates on MediaWiki.org. ===Phase 3: Organizing Wikimedia-Specific Content=== 1. **Review Wikimedia-Specific Content on Meta** - Review the content on Meta, including the content in the "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific" category identified during Phases 1 and 2 - Carefully examine this Wikimedia-specific content to understand its purpose and relevance 2. **Design an Information Architecture** - Based on the review, design an information architecture for the Wikimedia-specific content on Meta - Organize the content into logical, user-friendly categories and subcategories - Ensure the structure makes it easy for users to navigate and discover the information they need 3. **Get Feedback** - Share the proposed information architecture with the Wikimedia community and gather feedback - Incorporate the community's suggestions to refine the design and ensure it meets their needs 4. **Implement Changes to meta:Help** - For the pages listed under "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific": - Review the pages for usability and identify areas for improvement - Design and implement an organization structure to make these pages easy to discover and maintain - Publish the updated meta:Help pages with the new organizational structure 5. **Ongoing Maintenance** - Establish a process for regularly reviewing and updating the Wikimedia-specific content on Meta - Identify a team of contributors responsible for maintaining the content and information architecture over time - Monitor user feedback and adjust the organization as needed to ensure the content remains accessible and relevant ===Tentative timeline=== **Project kickoff and onboarding (May 20 - June 1)** - Analyze the project in detail with mentor and finalize the project scope. - Discuss about: - How often the tasks should be reviewed. - Share schedules and decide on a weekly/daily workflow. - Bi-weekly and daily project reports. - Create the required tasks and subtasks on Phabricator. **Week 1 (June 2 - June 8)** 1. **Comprehensive Review of Pages**: - Review the 20 pages listed under the "Has MediaWiki.org equivalent" section on the "Project:MediaWiki_documentation_on_Meta-Wiki/List" page. - Identify the corresponding MediaWiki.org page that serves as the equivalent for each page. 2. **Licensing Considerations**: - Verify that the content being migrated from all 20 Meta-Wiki pages is properly licensed under the MIT license, as required by MediaWiki.org. - Identify any content that needs to be relicensed from the CC-BY-SA license used on Meta-Wiki. 3. **Community Engagement**: - Inform the Wikimedia community about the project and gather initial feedback. - Address any concerns or questions raised by the community. **Week 2 (June 9 - June 15)** 1. **Licensing Considerations (continued)**: - Work with the Wikimedia community to relicense any content that needs to be relicensed from CC-BY-SA to MIT. 2. **Content Comparison and Migration**: - Conduct a detailed comparison of the content between the first 4-5 Meta-Wiki pages and their MediaWiki.org equivalents. - Identify and migrate any relevant information from the Meta-Wiki pages to the MediaWiki.org pages, ensuring accuracy and up-to-dateness. 3. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the project and the initial set of pages. **Week 3 (June 16 - June 22)** 1. **Content Comparison and Migration (continued)**: - Conduct a detailed comparison of the content between the next 4-5 Meta-Wiki pages and their MediaWiki.org equivalents. - Identify and migrate any relevant information from the Meta-Wiki pages to the MediaWiki.org pages, ensuring accuracy and up-to-dateness. 2. **Redirects and Cross-linking**: - Set up appropriate redirects from the Meta-Wiki pages to the corresponding MediaWiki.org pages for the completed set of pages. - Ensure there are clear cross-links between the two pages to maintain the seamless flow of information for users. - Gather community feedback on the proposed redirects and cross-links. 3. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the content migration and redirects/cross-links for the completed set of pages. **Week 4 (June 23 - June 29)** 1. **Content Comparison and Migration (continued)**: - Conduct a detailed comparison of the content between the remaining Meta-Wiki pages and their MediaWiki.org equivalents. - Identify and migrate any relevant information from the Meta-Wiki pages to the MediaWiki.org pages, ensuring accuracy and up-to-dateness. 2. **Testing and Quality Assurance**: - Thoroughly review the migrated content, redirects, and cross-links for all 20 pages. - Involve the project team and select community members to ensure the migrated documentation meets the required standards and user expectations. 3. **Address Backlog and Blockers**: - Address any remaining tasks, feedback, or blockers related to the content migration for the 20 pages. 4. **Documentation Maintenance**: - Establish a sustainable process for the ongoing maintenance and update of the consolidated MediaWiki documentation on MediaWiki.org. - Identify and train a team of contributors responsible for maintaining the documentation in the long term. 5. **Buffer Time**: - Allocate buffer time to accommodate any unforeseen delays or additional tasks that may arise during the project. **Week 5 (June 30 - July 6)** 1. **Create MediaWiki.org Pages**: - For each page listed under Project:MediaWiki_documentation_on_Meta-Wiki/List#No_MediaWiki.org_equivalent, create a corresponding MediaWiki.org page. - These new pages should cover the content from the Meta pages. 2. **Review and Group Pages**: - Review the newly created MediaWiki.org pages. - Group them into subject areas for better organization and navigation. **Week 6 (July 7 - July 13)** 1. **Audit Pages in Subject Areas**: - Audit pages in each subject area and identify: - Any information that needs to be added to MediaWiki.org. - Where the information should be added in the context of the related MediaWiki.org documentation. - Any information that is specific to Wikimedia and needs to stay on Meta. 2. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the newly created MediaWiki.org pages and subject area grouping. **Week 7 (July 14 - July 20)** 1. **Transferral of Images**: - Identify images located on Wikimedia Commons that can be used directly in the new MediaWiki.org pages. - Identify images on Meta that are used solely within pages being exported and tag them appropriately for transfer to MediaWiki.org. - Move images that are used in pages being transferred but also in other Meta pages to Wikimedia Commons, following the guidelines. 2. **Licensing Considerations**: - Ensure that the content being transferred from Meta to MediaWiki.org is properly licensed under the GFDL. - Be cautious with the 'PD Help' project, as the licenses are not compatible. - Follow 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 ]], including not moving any page that has not been displaying the 'MoveToMediaWiki' template for at least 2 weeks and not moving pages into the Help: namespace due to license incompatibility. **Week 8 (July 21 - July 27)** 1. **Write Content and Get Feedback**: - Write the necessary content for each new page on MediaWiki.org, ensuring it is original and not copied from Meta without proper consideration of copyright and licensing issues. - Seek feedback from the community on the new content by posting drafts on the MediaWiki.org talk pages or seeking input from other contributors. 2. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the new content written for the MediaWiki.org pages. **Week 9 (July 28 - August 3)** 1. **Write Content and Get Feedback (continued)**: - Continue writing and seeking feedback on the remaining new content for the MediaWiki.org pages. 2. **Feedback Review and Incorporation (continued)**: - Review and incorporate community feedback related to the remaining new content. **Week 10 (August 4 - August 10)** 1. **Publish**: - Once the content has been reviewed and approved, publish the updates on MediaWiki.org. 2. **Testing and Quality Assurance**: - Thoroughly review the published content, including links, formatting, and overall quality. - Involve the project team and select community members to ensure the documentation meets the required standards and user expectations. **Week 11 (August 11 - August 17)** 1. **Address Backlog and Blockers**: - Address any remaining tasks, feedback, or blockers related to the content migration for the pages with no MediaWiki.org equivalents. 2. **Buffer Time**: - Allocate buffer time to accommodate any unforeseen delays or additional tasks that may arise during the project. **Week 12 (August 18 - August 24)** 1. **Documentation Maintenance**: - Establish a sustainable process for the ongoing maintenance and update of the newly added MediaWiki documentation. - Identify and train a team of contributors responsible for maintaining the documentation in the long term. **Week 13 (August 25 - August 31)** 1. **Buffer Week**: - Allocate this week as a buffer to address any remaining tasks or issues that may arise during the project. **Week 14 (September 1 - September 7)** 1. **Review Wikimedia-Specific Content on Meta**: - Review the content on Meta, including the content in the "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific" category identified during Phases 1 and 2. - Carefully examine this Wikimedia-specific content to understand its purpose and relevance. 2. **Design an Information Architecture**: - Based on the review, design an information architecture for the Wikimedia-specific content on Meta. - Organize the content into logical, user-friendly categories and subcategories. - Ensure the structure makes it easy for users to navigate and discover the information they need. **Week 15 (September 8 - September 14)** 1. **Get Feedback**: - Share the proposed information architecture with the Wikimedia community and gather feedback. - Incorporate the community's suggestions to refine the design and ensure it meets their needs. 2. **Implement Changes to meta:Help**: - For the pages listed under "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific": - Review the pages for usability and identify areas for improvement. - Design and implement an organization structure to make these pages easy to discover and maintain. **Week 16 (September 15 - September 21)** 1. **Implement Changes to meta:Help (continued)**: - Continue implementing the organization structure for the meta:Help pages. 2. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the proposed changes to meta:Help. **Week 17 (September 22 - September 28)** 1. **Publish Updated meta:Help Pages**: - Once the changes have been reviewed and approved, publish the updated meta:Help pages with the new organizational structure. 2. **Testing and Quality Assurance**: - Thoroughly review the published changes to meta:Help, including navigation, links, and overall user experience. - Involve the project team and select community members to ensure the changes meet the required standards and user expectations. 3. **Ongoing Maintenance**: - Establish a process for regularly reviewing and updating the Wikimedia-specific content on Meta. - Identify a team of contributors responsible for maintaining the content and information architecture over time. **Week 18 (September 29 - October 5)** 1. **Ongoing Maintenance (continued)**: - Continue setting up the ongoing maintenance process for the Wikimedia-specific content on Meta. 2. **Monitor User Feedback**: - Monitor user feedback on the updated meta:Help pages and the new organizational structure. - Adjust the organization as needed to ensure the content remains accessible and relevant. 3. **Address Backlog and Blockers**: - Address any remaining tasks, feedback, or blockers related to the organization of Wikimedia-specific content on Meta. 4. **Buffer Time**: - Allocate buffer time to accommodate any unforeseen delays or additional tasks that may arise during the project. **Week 19 - 21 (October 6 - October 26)** 1. **Identify Cleanup Tasks**: - Conduct a thorough review of the project to identify any remaining cleanup tasks that need to be completed. - Examples of cleanup tasks may include: - Resolving any outstanding issues or bugs - Updating documentation or guides - Addressing any remaining feedback or concerns from the community 2. **Identify Follow-up Work**: - Identify any follow-up work that may be required after the completion of the project. - Examples of follow-up work may include: - Ongoing maintenance and updates to the documentation - Future enhancements or improvements to the documentation 3. **Prioritize and Plan Follow-up Work**: - Prioritize the identified follow-up work based on its importance and urgency. - Develop a plan or schedule for addressing the follow-up work in the future. 2. **Write Project Report**: - Write a comprehensive project report describing the outcomes, learning, best practices, and recommendations for future projects. - The report will cover the following areas: - Project overview and objectives - Key milestones and achievements - Challenges faced and how they were addressed - Lessons learned and best practices - Recommendations for future projects or improvements - Next steps and follow-up work 3. **Review and Finalize Project Report**: - Review the project report with the project team and other stakeholders. - Incorporate any feedback or additional input. - Finalize the report and distribute it to relevant parties. --- ===Past Experience=== **Writing Portfolio** - [[ https://github.com/mhmohona/writing-portfolio | github/mhmohona/writing-portfolio ]] ====Google Season of Doc -2023==== =====AsyncAPI Initiative===== **Documentation** * [Adding channel](https://github.com/asyncapi/website/pull/2408) * [Dynamic channel](https://github.com/asyncapi/website/pull/2409) * [Extending Specification](https://github.com/asyncapi/website/pull/2407) * [Adding Messages](https://github.com/asyncapi/website/pull/2410) * [Reuse with traits](https://github.com/asyncapi/website/pull/2411) * [Adding binding](https://github.com/asyncapi/website/pull/2042) **Killercoda Tutorial** * [AsyncAPI Specification Basic](https://github.com/asyncapi/learning-paths/pull/5) * [Create & Validate Document](https://github.com/asyncapi/learning-paths/pull/4) =====WasmEdge Runtime===== * [Plugin - Developer guide](https://github.com/WasmEdge/docs/pull/102) * [Plugin - User guide](https://github.com/WasmEdge/docs/pull/146) * [Plugin Details](https://github.com/WasmEdge/docs/pull/200) * [Plugin - Best Practice](https://github.com/WasmEdge/docs/pull/191) * [Troubleshooting Guide](https://github.com/WasmEdge/docs/pull/192) * [FAQ & Style Guide](https://github.com/WasmEdge/docs/pull/193) * [Community Page](https://github.com/WasmEdge/docs/pull/153) ====Season Of KDE - 2024==== =====Labplot Documentation===== **Newly Created pages** * [Data Analysis : Curve Fitting](https://userbase.kde.org/LabPlot/DataAnalysis/CurveFitting) * [Data Analysis : Fourier Transform](https://userbase.kde.org/LabPlot/DataAnalysis/FourierTransfromation) * [CAS Computing](https://userbase.kde.org/LabPlot/CASComputing) * [LaTeX Typesetting](https://userbase.kde.org/LabPlot/LaTeXTypesetting) * [Tools : FITS Metadata Editor](https://userbase.kde.org/LabPlot/FITSMetadataEditor)

===Profile Information=== **Name**: Mahfuza Humayra Mohona **IRC nickname on Zulip**: mhmohona [[ https://drive.google.com/file/d/1Vm7iklgBpia-mLB6bx0FYk3-O0JdXhJLiHwWRU9pp16H0vyJrgPVqiZD0MHtEFFB/view?usp=sharing | Resume ]] | [[ https://github.com/mhmohona | GIthub ]] | [[ https://www.linkedin.com/mhmohona | LinkedIn ]] **Location** -: Bangladesh (GMT +6) **Availability**: 20-25 hours per week ===Introduction=== The MediaWiki documentation hosted across Meta-Wiki and MediaWiki.org has become fragmented and difficult to navigate for both users and contributors. While MediaWiki.org was established as the central repository for MediaWiki documentation, there are still numerous pages on Meta-Wiki that contain relevant MediaWiki information. This duplication creates challenges in maintaining consistent and up-to-date documentation. The goal of [[ https://www.mediawiki.org/wiki/Season_of_Docs/2024/Proposal# | this project ]] is to consolidate MediaWiki's help documentation by identifying duplicate content between MediaWiki.org and Meta-Wiki, and migrating relevant content from Meta-Wiki to MediaWiki.org. This involves auditing each Meta page to find its MediaWiki.org equivalent, identifying any information that needs to be added to the MediaWiki.org page, and any information that is specific to Wikimedia and needs to stay on Meta. The primary goal is to improve the accessibility and usability of MediaWiki's documentation for both new and existing users. ===Deliverables=== - **Audit Report**: A comprehensive [[ https://docs.google.com/spreadsheets/d/1P2OKBg68hixEZkDEjl-XKTIY9UKt8nHaVvnlBljlSUM/edit?usp=sharing | report]] detailing the audit of each Meta page, including its MediaWiki.org equivalent, any additional information that needs to be added to MediaWiki.org, and any information that is specific to Wikimedia and needs to stay on Meta. - **Migrated Content**: Content migrated from Meta-Wiki to MediaWiki.org, ensuring that MediaWiki.org has a comprehensive and up-to-date documentation base, correctly connected pages and all the links. - **Feedback and Revision Documentation**: Documentation of the feedback received during the project, including any revisions made to the migrated content based on this feedback. - **Finalized Documentation**: The finalized version of the documentation on MediaWiki.org, reflecting all migrated content and any necessary adjustments based on feedback. ===Stretch Goal=== Develop a sustainable process for maintaining and updating the consolidated MediaWiki documentation on MediaWiki.org, ensuring that the information remains current and accessible. ===Mentors=== Alex Paskulin ===Participation=== **Communication Medium**: Zullip **Communication Frequency**: Attending Community meeting, 1:1 call with mentors --- === Discussion===Project Details=== This project is going to have 3 phases - - Phase 1: De-duplication - Phase 2: New content - Phase 3: Organize =====Phase 1: Addressing Pages with MediaWiki.org Equivalents===== 1. **Comprehensive Review of Pages**: - Review each page listed under the "Has MediaWiki.org equivalent" section on the "Project:MediaWiki_documentation_on_Meta-Wiki/List" page. - For each page, identify the corresponding MediaWiki.org page that serves as the equivalent. 2. **Content Comparison and Migration**: - Conduct a detailed comparison of the content between the Meta-Wiki page and the MediaWiki.org equivalent page. - Identify any information on the Meta-Wiki page that is missing from or needs to be added to the MediaWiki.org page. - Migrate the relevant content from the Meta-Wiki page to the MediaWiki.org page, ensuring the information is accurate and up-to-date. 3. **Licensing Considerations**: - Verify that the content being migrated from Meta-Wiki to MediaWiki.org is properly licensed under the MIT license, as required by MediaWiki.org. - If necessary, work with the Wikimedia community to relicense the content from the CC-BY-SA license used on Meta-Wiki. 4. **Redirects and Cross-linking**: - Set up appropriate redirects from the Meta-Wiki page to the corresponding MediaWiki.org page. - Ensure there are clear cross-links between the two pages to maintain the seamless flow of information for users. 5. **Community Feedback and Validation**: - Engage with the Wikimedia community to gather feedback on the proposed content migrations and changes. - Incorporate the community's suggestions and validate the changes to ensure they meet the users' needs. 6. **Documentation Maintenance**: - Establish a sustainable process for the ongoing maintenance and update of the consolidated MediaWiki documentation on MediaWiki.org. - Identify and train a team of contributors responsible for maintaining the documentation in the long term. =====Phase 2: Addressing Pages with No MediaWiki.org Equivalents===== 1. **Create MediaWiki.org Pages**: - For each page listed under Project:MediaWiki_documentation_on_Meta-Wiki/List#No_MediaWiki.org_equivalent, create a corresponding MediaWiki.org page that covers the content on the Meta page. 2. **Review and Group Pages**: - Review the newly created pages and group them into subject areas for better organization and navigation. 3. **Audit Pages in Subject Areas**: - Audit pages in each subject area and identify: - Any information that needs to be added to MediaWiki.org. - Where the information should be added in the context of the related MediaWiki.org documentation. - Any information that is specific to Wikimedia and needs to stay on Meta. 4. **Transferral of Images**: - Images located on Wikimedia Commons do not need any changes and can be used directly in MediaWiki.org pages. - Images on Meta that are used solely within pages that will be exported can be transferred to MediaWiki.org. In this case, tag them appropriately. - Images that are used in pages to be transferred but also in other pages on Meta should be moved to Commons, as well as other images allowed by Commons' guidelines. 5. **Licensing Considerations**: - Most content on MediaWiki.org is licensed under the GFDL, allowing direct movement of content from Meta to MediaWiki.org. However, be cautious with the 'PD Help' project, as the licenses are not compatible. - When transferring pages, ensure to follow 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 ]], including not moving any page that has not been displaying the 'MoveToMediaWiki' template for at least 2 weeks and not moving pages into the Help: namespace due to license incompatibility. 6. **Write Content and Get Feedback**: - Write the necessary content for each new page on MediaWiki.org, ensuring it is original and not copied from Meta without proper consideration of copyright and licensing issues. - Seek feedback from the community on the new content. This could involve posting drafts on the MediaWiki.org talk pages or seeking input from other contributors. 7. **Publish**: - Once the content has been reviewed and approved, publish the updates on MediaWiki.org. ===Phase 3: Organizing Wikimedia-Specific Content=== 1. **Review Wikimedia-Specific Content on Meta** - Review the content on Meta, including the content in the "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific" category identified during Phases 1 and 2 - Carefully examine this Wikimedia-specific content to understand its purpose and relevance 2. **Design an Information Architecture** - Based on the review, design an information architecture for the Wikimedia-specific content on Meta - Organize the content into logical, user-friendly categories and subcategories - Ensure the structure makes it easy for users to navigate and discover the information they need 3. **Get Feedback** - Share the proposed information architecture with the Wikimedia community and gather feedback - Incorporate the community's suggestions to refine the design and ensure it meets their needs 4. **Implement Changes to meta:Help** - For the pages listed under "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific": - Review the pages for usability and identify areas for improvement - Design and implement an organization structure to make these pages easy to discover and maintain - Publish the updated meta:Help pages with the new organizational structure 5. **Ongoing Maintenance** - Establish a process for regularly reviewing and updating the Wikimedia-specific content on Meta - Identify a team of contributors responsible for maintaining the content and information architecture over time - Monitor user feedback and adjust the organization as needed to ensure the content remains accessible and relevant ===Tentative timeline=== **Project kickoff and onboarding (May 20 - June 1)** - Analyze the project in detail with mentor and finalize the project scope. - Discuss about: - How often the tasks should be reviewed. - Share schedules and decide on a weekly/daily workflow. - Bi-weekly and daily project reports. - Create the required tasks and subtasks on Phabricator. **Week 1 (June 2 - June 8)** 1. **Comprehensive Review of Pages**: - Review the 20 pages listed under the "Has MediaWiki.org equivalent" section on the "Project:MediaWiki_documentation_on_Meta-Wiki/List" page. - Identify the corresponding MediaWiki.org page that serves as the equivalent for each page. 2. **Licensing Considerations**: - Verify that the content being migrated from all 20 Meta-Wiki pages is properly licensed under the MIT license, as required by MediaWiki.org. - Identify any content that needs to be relicensed from the CC-BY-SA license used on Meta-Wiki. 3. **Community Engagement**: - Inform the Wikimedia community about the project and gather initial feedback. - Address any concerns or questions raised by the community. **Week 2 (June 9 - June 15)** 1. **Licensing Considerations (continued)**: - Work with the Wikimedia community to relicense any content that needs to be relicensed from CC-BY-SA to MIT. 2. **Content Comparison and Migration**: - Conduct a detailed comparison of the content between the first 4-5 Meta-Wiki pages and their MediaWiki.org equivalents. - Identify and migrate any relevant information from the Meta-Wiki pages to the MediaWiki.org pages, ensuring accuracy and up-to-dateness. 3. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the project and the initial set of pages. **Week 3 (June 16 - June 22)** 1. **Content Comparison and Migration (continued)**: - Conduct a detailed comparison of the content between the next 4-5 Meta-Wiki pages and their MediaWiki.org equivalents. - Identify and migrate any relevant information from the Meta-Wiki pages to the MediaWiki.org pages, ensuring accuracy and up-to-dateness. 2. **Redirects and Cross-linking**: - Set up appropriate redirects from the Meta-Wiki pages to the corresponding MediaWiki.org pages for the completed set of pages. - Ensure there are clear cross-links between the two pages to maintain the seamless flow of information for users. - Gather community feedback on the proposed redirects and cross-links. 3. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the content migration and redirects/cross-links for the completed set of pages. **Week 4 (June 23 - June 29)** 1. **Content Comparison and Migration (continued)**: - Conduct a detailed comparison of the content between the remaining Meta-Wiki pages and their MediaWiki.org equivalents. - Identify and migrate any relevant information from the Meta-Wiki pages to the MediaWiki.org pages, ensuring accuracy and up-to-dateness. 2. **Testing and Quality Assurance**: - Thoroughly review the migrated content, redirects, and cross-links for all 20 pages. - Involve the project team and select community members to ensure the migrated documentation meets the required standards and user expectations. 3. **Address Backlog and Blockers**: - Address any remaining tasks, feedback, or blockers related to the content migration for the 20 pages. 4. **Documentation Maintenance**: - Establish a sustainable process for the ongoing maintenance and update of the consolidated MediaWiki documentation on MediaWiki.org. - Identify and train a team of contributors responsible for maintaining the documentation in the long term. 5. **Buffer Time**: - Allocate buffer time to accommodate any unforeseen delays or additional tasks that may arise during the project. **Week 5 (June 30 - July 6)** 1. **Create MediaWiki.org Pages**: - For each page listed under Project:MediaWiki_documentation_on_Meta-Wiki/List#No_MediaWiki.org_equivalent, create a corresponding MediaWiki.org page. - These new pages should cover the content from the Meta pages. 2. **Review and Group Pages**: - Review the newly created MediaWiki.org pages. - Group them into subject areas for better organization and navigation. **Week 6 (July 7 - July 13)** 1. **Audit Pages in Subject Areas**: - Audit pages in each subject area and identify: - Any information that needs to be added to MediaWiki.org. - Where the information should be added in the context of the related MediaWiki.org documentation. - Any information that is specific to Wikimedia and needs to stay on Meta. 2. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the newly created MediaWiki.org pages and subject area grouping. **Week 7 (July 14 - July 20)** 1. **Transferral of Images**: - Identify images located on Wikimedia Commons that can be used directly in the new MediaWiki.org pages. - Identify images on Meta that are used solely within pages being exported and tag them appropriately for transfer to MediaWiki.org. - Move images that are used in pages being transferred but also in other Meta pages to Wikimedia Commons, following the guidelines. 2. **Licensing Considerations**: - Ensure that the content being transferred from Meta to MediaWiki.org is properly licensed under the GFDL. - Be cautious with the 'PD Help' project, as the licenses are not compatible. - Follow 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 ]], including not moving any page that has not been displaying the 'MoveToMediaWiki' template for at least 2 weeks and not moving pages into the Help: namespace due to license incompatibility. **Week 8 (July 21 - July 27)** 1. **Write Content and Get Feedback**: - Write the necessary content for each new page on MediaWiki.org, ensuring it is original and not copied from Meta without proper consideration of copyright and licensing issues. - Seek feedback from the community on the new content by posting drafts on the MediaWiki.org talk pages or seeking input from other contributors. 2. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the new content written for the MediaWiki.org pages. **Week 9 (July 28 - August 3)** 1. **Write Content and Get Feedback (continued)**: - Continue writing and seeking feedback on the remaining new content for the MediaWiki.org pages. 2. **Feedback Review and Incorporation (continued)**: - Review and incorporate community feedback related to the remaining new content. **Week 10 (August 4 - August 10)** 1. **Publish**: - Once the content has been reviewed and approved, publish the updates on MediaWiki.org. 2. **Testing and Quality Assurance**: - Thoroughly review the published content, including links, formatting, and overall quality. - Involve the project team and select community members to ensure the documentation meets the required standards and user expectations. **Week 11 (August 11 - August 17)** 1. **Address Backlog and Blockers**: - Address any remaining tasks, feedback, or blockers related to the content migration for the pages with no MediaWiki.org equivalents. 2. **Buffer Time**: - Allocate buffer time to accommodate any unforeseen delays or additional tasks that may arise during the project. **Week 12 (August 18 - August 24)** 1. **Documentation Maintenance**: - Establish a sustainable process for the ongoing maintenance and update of the newly added MediaWiki documentation. - Identify and train a team of contributors responsible for maintaining the documentation in the long term. **Week 13 (August 25 - August 31)** 1. **Buffer Week**: - Allocate this week as a buffer to address any remaining tasks or issues that may arise during the project. **Week 14 (September 1 - September 7)** 1. **Review Wikimedia-Specific Content on Meta**: - Review the content on Meta, including the content in the "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific" category identified during Phases 1 and 2. - Carefully examine this Wikimedia-specific content to understand its purpose and relevance. 2. **Design an Information Architecture**: - Based on the review, design an information architecture for the Wikimedia-specific content on Meta. - Organize the content into logical, user-friendly categories and subcategories. - Ensure the structure makes it easy for users to navigate and discover the information they need. **Week 15 (September 8 - September 14)** 1. **Get Feedback**: - Share the proposed information architecture with the Wikimedia community and gather feedback. - Incorporate the community's suggestions to refine the design and ensure it meets their needs. 2. **Implement Changes to meta:Help**: - For the pages listed under "Project:MediaWiki documentation on Meta-Wiki/List#Actually WMF-specific": - Review the pages for usability and identify areas for improvement. - Design and implement an organization structure to make these pages easy to discover and maintain. **Week 16 (September 15 - September 21)** 1. **Implement Changes to meta:Help (continued)**: - Continue implementing the organization structure for the meta:Help pages. 2. **Feedback Review and Incorporation**: - Review and incorporate community feedback related to the proposed changes to meta:Help. **Week 17 (September 22 - September 28)** 1. **Publish Updated meta:Help Pages**: - Once the changes have been reviewed and approved, publish the updated meta:Help pages with the new organizational structure. 2. **Testing and Quality Assurance**: - Thoroughly review the published changes to meta:Help, including navigation, links, and overall user experience. - Involve the project team and select community members to ensure the changes meet the required standards and user expectations. 3. **Ongoing Maintenance**: - Establish a process for regularly reviewing and updating the Wikimedia-specific content on Meta. - Identify a team of contributors responsible for maintaining the content and information architecture over time. **Week 18 (September 29 - October 5)** 1. **Ongoing Maintenance (continued)**: - Continue setting up the ongoing maintenance process for the Wikimedia-specific content on Meta. 2. **Monitor User Feedback**: - Monitor user feedback on the updated meta:Help pages and the new organizational structure. - Adjust the organization as needed to ensure the content remains accessible and relevant. 3. **Address Backlog and Blockers**: - Address any remaining tasks, feedback, or blockers related to the organization of Wikimedia-specific content on Meta. 4. **Buffer Time**: - Allocate buffer time to accommodate any unforeseen delays or additional tasks that may arise during the project. **Week 19 - 21 (October 6 - October 26)** 1. **Identify Cleanup Tasks**: - Conduct a thorough review of the project to identify any remaining cleanup tasks that need to be completed. - Examples of cleanup tasks may include: - Resolving any outstanding issues or bugs - Updating documentation or guides - Addressing any remaining feedback or concerns from the community 2. **Identify Follow-up Work**: - Identify any follow-up work that may be required after the completion of the project. - Examples of follow-up work may include: - Ongoing maintenance and updates to the documentation - Future enhancements or improvements to the documentation 3. **Prioritize and Plan Follow-up Work**: - Prioritize the identified follow-up work based on its importance and urgency. - Develop a plan or schedule for addressing the follow-up work in the future. 2. **Write Project Report**: - Write a comprehensive project report describing the outcomes, learning, best practices, and recommendations for future projects. - The report will cover the following areas: - Project overview and objectives - Key milestones and achievements - Challenges faced and how they were addressed - Lessons learned and best practices - Recommendations for future projects or improvements - Next steps and follow-up work 3. **Review and Finalize Project Report**: - Review the project report with the project team and other stakeholders. - Incorporate any feedback or additional input. - Finalize the report and distribute it to relevant parties. --- ===Past Experience=== **Writing Portfolio** - [[ https://github.com/mhmohona/writing-portfolio | github/mhmohona/writing-portfolio ]] ====Google Season of Doc -2023==== =====AsyncAPI Initiative===== =====AsyncAPI Initiative **Documentation** * [Adding channel](https://github.com/asyncapi/website/pull/2408) * [Dynamic channel](https://github.com/asyncapi/website/pull/2409) * [Extending Specification](https://github.com/asyncapi/website/pull/2407) * [Adding Messages](https://github.com/asyncapi/website/pull/2410) * [Reuse with traits](https://github.com/asyncapi/website/pull/2411) * [Adding binding](https://github.com/asyncapi/website/pull/2042) **Killercoda Tutorial** * [AsyncAPI Specification Basic](https://github.com/asyncapi/learning-paths/pull/5) * [Create & Validate Document](https://github.com/asyncapi/learning-paths/pull/4) =====WasmEdge Runtime===== * [Plugin - Developer guide](https://github.com/WasmEdge/docs/pull/102) * [Plugin - User guide](https://github.com/WasmEdge/docs/pull/146) * [Plugin Details](https://github.com/WasmEdge/docs/pull/200) * [Plugin - Best Practice](https://github.com/WasmEdge/docs/pull/191) * [Troubleshooting Guide](https://github.com/WasmEdge/docs/pull/192) * [FAQ & Style Guide](https://github.com/WasmEdge/docs/pull/193) * [Community Page](https://github.com/WasmEdge/docs/pull/153) ====Season Of KDE - 2024==== =====Labplot Documentation===== **Newly Created pages** * [Data Analysis : Curve Fitting](https://userbase.kde.org/LabPlot/DataAnalysis/CurveFitting) * [Data Analysis : Fourier Transform](https://userbase.kde.org/LabPlot/DataAnalysis/FourierTransfromation) * [CAS Computing](https://userbase.kde.org/LabPlot/CASComputing) * [LaTeX Typesetting](https://userbase.kde.org/LabPlot/LaTeXTypesetting) * [Tools : FITS Metadata Editor](https://userbase.kde.org/LabPlot/FITSMetadataEditor)