"Hi gouthamr rdopiera tmazur ,..." <- > <@ai.naymul:matrix.org> Hi gouthamr rdopiera tmazur , > > What's your thought on this timeline for the horizan project? > > > Here it is: > > > Week 1-2: May 27th - June 9th - Orientation and Setup > > a. Get familiar with OpenStack Horizon and Glance documentation. > > b. Set up the development environment according to the system requirements. > > c. Explore the Horizon and Glance codebase, focusing on current image service implementations. > > Week 3-4: June 10th - June 23rd - Understanding and Planning > > 1. Deep dive into Glance API features not yet supported in Horizon: Image sharing, hidden images, image import, community images, and image activation/deactivation. > > 2. Draft initial design documents for UI changes and discuss them with mentors. > > 3. Identify and list necessary API calls for the new features. > > Week 5-6: June 24th - July 7th - UI Design and API Integration > > 1. Start designing UI components for the new features, focusing on user experience and integration points with the Glance API. > > 2. Begin frontend development for image sharing and hidden images features. > > 3. Conduct initial tests with mock data to ensure UI components behave as expected. > > Week 7-8: July 8th - July 21st - Feature Development Continues > > 1. Continue with frontend development, focusing now on image import and community images features. > > 2. Start integrating frontend components with the backend Glance API. > > 3. Perform integration testing to identify and fix bugs or issues. > > Week 9-10: July 22nd - August 4th - Finalizing Features and Testing > > 1. Implement image activation/deactivation features in the UI. > > 2. Conduct comprehensive testing across all new features, including user acceptance testing to gather feedback. > > 3. Refine UI based on feedback and test results. > > 4. Ensure all code is well-documented and follows project guidelines. > > Week 11-12: August 5th - August 23rd - Documentation, Demonstration, and Wrap-Up > > 1. Finalize all features and conduct a final round of testing to ensure stability. > > 2. Prepare and update project documentation to reflect new features and guide users. > > 3. Develop a demonstration of the new features to showcase their functionality. > > 4. Review the project with mentors, gather feedback, and discuss potential future improvements. > > 5. Submit a final report detailing the project process, challenges encountered, and how they were overcome. > > This timeline is flexible and may be adjusted based on progress, feedback from mentors, and any unforeseen challenges. gouthamr: should I propose this timeline?