Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ROADMAP: Moving PyAEDT Extensions to a separate repository #5516

Open
Samuelopez-ansys opened this issue Dec 3, 2024 · 0 comments
Open

ROADMAP: Moving PyAEDT Extensions to a separate repository #5516

Samuelopez-ansys opened this issue Dec 3, 2024 · 0 comments
Milestone

Comments

@Samuelopez-ansys
Copy link
Member

The decision to move PyAEDT extensions to a dedicated repository introduces several key advantages for the development and maintenance of the project:

Focused Development: Separating extensions from the core PyAEDT codebase allows for targeted enhancements and updates to the extensions without impacting the primary functionality of PyAEDT.

Improved Modularity: A standalone repository enables better organization and a more modular structure, making it easier to manage and scale the extensions as independent components.

Simplified Maintenance: Issues related to extensions can be tracked and resolved within their own repository, leading to a more streamlined debugging and testing process.

Enhanced Collaboration: Contributors can work on extensions independently, fostering specialized development efforts and reducing complexity in the main PyAEDT repository.

Reusability and Versatility: A separate repository allows for the extensions to be reused in other projects or adapted for broader purposes outside of PyAEDT.

This move represents a strategic step toward improving the structure, maintainability, and scalability of the PyAEDT ecosystem.

@Samuelopez-ansys Samuelopez-ansys converted this from a draft issue Dec 3, 2024
@Samuelopez-ansys Samuelopez-ansys added this to the v2.0 milestone Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Q2 2025 - Apr-Jun
Development

No branches or pull requests

1 participant