GitHub user xuang7 created a discussion: Unifying Project-Specific Code in a Single Repository
Today, project-specific code often lives outside the main repository, leading to duplication, divergence, and additional maintenance overhead. The goal is to move toward a single unified repository that combines shared application code with project-specific configuration, rather than maintaining these pieces separately. The challenge is that this code appears in several forms: - Third-party code: external code brought directly into a project with little or no modification. - Locally modified third-party code: code patched primarily to access data from our platform; these changes may prevent the use of the original published images and may not be suitable for upstream contribution - Standalone microservices: project-specific services deployed alongside the main platform Currently, these integrations are implemented independently for each project. Many of the resulting changes are highly project-specific and may not be needed by other deployments. One question is whether we should define a standard, documented API for external code to access platform-managed data, rather than relying on ad hoc integrations for each project. Feedback on how to unify and manage these different types of project-specific code would be very helpful. Please feel free to share any thoughts, concerns, or suggestions. Thank you! GitHub link: https://github.com/apache/texera/discussions/6727 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
