ORGANIZATION: WIKIMEDIA Project Title: Capacity Exchange Timeline: Date Range Task Details & Deliverables Dec 4st - Dec 10th Project breakdown and structuring Clearly defined project outline, project onboarding, and deliverables Dec 12th - Dec 13th Initial documentation Well-documented project scope on required documentation platform Dec 14th - Dec 17th (Approx. 1 week) Database Setup Models and Key constraints for the test. Key constraints Dec 18th - Dec 23th (2 weeks) File system Setup file system to store user data Alignment check with team and superiors Dec 27th - Dec 29th Receiving API API route to receive data from users Jan 3rd to Jan 7th Testing Testing and bug fixes for the receiving route Jan 8th to Jan 14th Detailed Documentation Documenting details on the data received method and its mechanism Jan 15th to Jan 24th File management Uploading processing of a file Jan 25th to Feb 4th Distribution Sending messages and resources to the recipient 6th to 18th Feb Building of UI Implement complete UI 19th to 27th Feb Testing features Testing UI features and bug-fixing 27th Feb to 1st March Documentation and Bug Fixing Bug Fixing, Documenting the mechanism of the source code

Project Idea: It has been analyzed that the future platform would best be served by a newly developed infrastructure and code language. The language switch from Java to Python enables the Capacity Exchange's online longevity and sustainability. The aim is to leverage the larger Python community within the Wiki movement. As a result, a larger pool of developers can contribute to and maintain future additions – whether features or bug fixes. Analyzing data from Toolforge further strengthens the case for Python, as it demonstrates widespread language usage within the hosting platform. Out of the hosted tools, 43 mentions "python" as one of their tags, compared to only one tool mentioning "java". Additionally, focusing on the two Python frameworks under consideration – Django and Flask – their presence on Toolforge is substantial, with 6 and 15 apps tagged, respectively. This reinforces Python language familiarity. It also highlights the advantage of selecting a framework with a strong presence among community developers. Transitioning to Python is a strategic action that aligns with the Wikimedia Movement. It takes advantage of the language's widespread adoption and robust frameworks. By doing so, CapX would benefit from increased contributions, a larger pool of potential developers, and an increased likelihood of long-term maintenance and success. Moreover, embracing Python will empower us to craft screens, user interfaces, and experiences that would otherwise be challenging. This is while building upon the current Java prototype. It will allow us to create a better peer-to-peer connection experience for all users

Usecase Diagram:

Implementation: Capacity Exchange aims for an agile and participatory methodology, which includes planning activities, as observed in the present document. ● Migration of functionalities that already exist, even partially. These are sections of code that already exist and would have to be rewritten in Python specifically with the framework Django. These are the ones we will focus on in this section.

● Development tasks are those pertaining to functionalities that don't exist in the current prototype. This will be done on the current prototype which will be realised using Django.

Detail documentation will done on every implementation of features and revised functionalities.