Merge pull request #5755 from Ashparshp/updateLFXFall

Update LFX Fall Term.

src/collections/programs/lfx-2024/lfx-2024.mdx

@@ -233,6 +233,86 @@ Understand that your challenges will be promoted through CNCF channels, reviewed
 - LFX URL: https://mentorship.lfx.linuxfoundation.org/project/1a620529-f2be-4a6f-8b4d-0562731cb840
 
 
+## LFX Mentorship 2024 Fall Projects
+<br />
+
+### CNCF TAG Network
+<br/>
+
+#### Interrelating Kubernetes Resources: Identifying relationships between all standard and custom resources
+- Description: The OpenAPI specifications for Kubernetes provides taxonomy, but augmenting a graph data model with formalized ontologies enables any number of capabilities, one of the more straightforward is the inferencing requisite for natural language processing, and consequently, a human-centric query / response interaction becomes becomes possible. More importantly, more advanced systems can be built when a graph data model of connected systems is upgraded to be a knowledge semantic graph.
+- Expected Outcome: 
+  - YAML-formatted definition of one or more relationships per Kubernetes resource.
+  - Documentation of each relationship - per component.
+  - Development of new types of genealogies - new types of ways in which resources relate to one another and how these relationships might be visualized.
+  - Verification of functional relationships
+
+- Recommended Skills: DevOps, Kubernetes Administration, Light familiarity with all of the CNCF projects and a desire to study each project and their operators/resources.
+- Mentor(s): <Link to="/community/members/uzair-shaikh">Uzair Shaikh</Link>, <Link to="/community/members/lee-calcote">Lee Calcote</Link>
+- Upstream Issue: https://github.com/cncf/tag-network/issues/43
+
+#### CNCF Challenges: Technical Content Creation
+- Description: On a periodic basis, the CNCF would like to present a public challenge to those that are interested in participating (e.g. “Challenge: Distributed Tracing with Jaeger”). 
+
+Your mission in this internship is technical content creation of said challenges through use of markdown, Meshery, and any number of other CNCF projects. Challenges will be created using the Meshery Playground and published (in what is potentially the CNCF Hub). They will be similar too, but slightly different from these [example tutorials](https://docs.meshery.io/guides/tutorials/).
+
+Understand that your challenges will be promoted through CNCF channels, reviewed by various project maintainers, and that each challenger (participant) will receive a certain number of points, depending upon whether or not they successfully complete the challenges that you create and in what timeframe they complete those challenges (the faster, the more points). Your challenges will need to vary in level of difficulty. 
+
+- Expected Outcome: 
+  - 5+ new challenges published 
+  - Challenges can contain more than one objective. Points are earned for each objective completed.
+  - Bonus: Extend one or more of Meshery’s Learning Paths.
+
+- Recommended Skills: written English, Kubernetes, DevOps, and familiarity with any number of other CNCF projects, like Prometheus, CoreDNS, Istio, Jaeger, Helm, Harbor, OPA, Rook, SPIFEE, Flux, Argo, Flux, Falco, etc., Jekyll, strong organizational skills
+- Mentor(s): <Link to="/community/members/lee-calcote">Lee Calcote</Link>, <Link to="/community/members/nic-jackson">Nic Jackson</Link>
+- Upstream Issue: https://github.com/cncf/tag-network/issues/44
+
+### Meshery
+<br/>
+#### Meshery: End-to-End Testing with Playwright (Round 2)
+
+- Description: Meshery integrates with many other CNCF projects and technologies. Sustaining those integrations is only possible through automation. End-to-end testing with Playwright, GitHub Workflows, and self-documenting test reports is the means to the end of maintaining a healthy state of each of these [Meshery integrations](https://meshery.io/integrations).
+- Expected Outcome: 
+  - Successful migration of E2E tests from Cypress to the Playwright test library within the Meshery project.
+  - Implementation of robust and reliable test cases using Playwright to cover a wide range of Meshery's E2E scenarios.
+  - Documentation detailing the migration process, and guidelines for future contributions to maintain test quality.
+  - Integration of Playwright test suite into the Meshery CI/CD pipeline to ensure continuous testing and reliability of the platform.
+- Recommended Skills: JavaScript, Playwright, GitHub Workflows, Jekyll, Markdown, familiarity with React or Nextjs would be helpful, CI/CD
+
+- Mentor(s): <Link to = "/community/members/aabid-sofi">Aabid Sofi</Link>, <Link to="/community/members/lee-calcote">Lee Calcote</Link>
+- Upstream Issue: https://github.com/meshery/meshery/issues/11494
+
+#### Meshery: Migrate APIs to be schema-driven
+
+- Description: Enhance Meshery’s APIs capability by migrating to a schema-driven approach, which will ensure consistency, validation, and easier integration. It involves versioning and defining API schemas using OpenAPI/Swagger at https://github.com/meshery/schemas and auto generating structs. You will be ensuring all Meshery APIs aligns with defined schemas and are consistent.
+- Expected Outcome: Identifying APIs and updating them to conform these schemas. Enhance API documentation to reflect the schema-driven approach. Updating APIs to ensure they are consistent and doing validation against defined schemas.
+- Recommended Skills: Golang, Kubernetes, Swagger, JSON schemas, familiarity with React, Nextjs would be helpful
+
+- Mentor(s): <Link to="/community/members/yash-sharma">Yash Sharma</Link>, <Link to="/community/members/lee-calcote">Lee Calcote</Link>
+- Upstream Issue: https://github.com/meshery/meshery/issues/11495
+
+#### Meshery: UI Migration from MUI v4 to MUI v5 and Sistent
+
+- Description: Meshery's UI is powerful and utilizes frameworks like Next.js and Material-UI. However, it relies on outdated technology stacks, resulting in performance inefficiencies and increased maintenance overhead.
+- Expected Outcome: Migrate from MUI v4 to MUI v5 and fully utilize features of Nextjs v13 and Sistent. Migrate all class based components to function based components. Reduced code complexity and improved maintainability for long-term sustainability. Responsive and accessible UI that adapts to diverse devices and user needs.
+- Recommended Skills: ReactJs, NextJs, familiarity with Material UI, Redux and Redux Toolkit
+- Mentor(s): <Link to="/community/members/lee-calcote">Lee Calcote</Link>, <Link to="/community/members/antonette-caldwell">Antonette Caldwell</Link>
+
+- Upstream Issue: https://github.com/meshery/meshery/issues/11493
+
+### Service Mesh Performance
+<br/>
+
+#### CNCF Project Performance Test Dashboard
+- Description: In coordination with CNCF TAG Network, the current performance dashboard at https://smp-spec.io/dashboard is proposed to be incorporated into CNCF project level-moving criteria in that each CNCF project will be encouraged (mandated?) to incorporate ongoing performance tests into their build and release processes, resulting in ongoing performance analysis of each project.
+- Expected Outcome: 
+Dashboard Enhancement: Expand the existing performance dashboard to capture and visualize performance test results for non-service mesh projects. This will involve integrating with various data sources, designing user-friendly interfaces, and implementing robust data analysis pipelines.
+GitHub Workflow Integration: Collaborate with other CNCF projects to configure their GitHub workflows to automatically run load tests using the Meshery GitHub Action. This will streamline the performance testing process and ensure that results are consistently collected and published to the dashboard.	
+- Recommended Skills: Golang, familiarity with HTTP/HTTPS performance testing tools, Service Mesh, grpc, familiarity with containerization technologies, like Docker would be helpful.
+
+- Mentor(s): <Link to="/community/members/lee-calcote">Lee Calcote</Link>, <Link to="/community/members/xin-huang">Xin Huang</Link>
+- Upstream Issue: https://github.com/service-mesh-performance/service-mesh-performance/issues/432
+
 ## Additional information
 <br />