Improve developer experience in GitHub and GitLab platforms
Within the GitHub and GitLab platforms, we currently have long-standing processes that enforce ECA compliance within our projects. As technology and platforms grow and evolve, so too should our processes to better support our user base. To this end, we are launching an initiative to improve the developer experience on our supported platforms with a focus on how users can interact with the ECA.
The goal of these updates is two-fold. The first is to update any systems that have the potential to prevent users from interacting with Eclipse Foundation projects to better enable collaboration. The second is to reduce the burden on our existing committers and project leads by helping new users in resolving their ECA status when needed.
To get there, we are planning the following updates:
1. Launch the auto-comment system within GitHub to help users to resolve invalid ECA states without direct involvement from project leadership.
2. Update the GitLab ECA validation process to be an asynchronous check similar to GitHub, replacing the current commit-time validation process.
3. Update the auto-comment system for GitHub to also function within GitLab.
4. Provide an easier method on both platforms to trigger a revalidation without having to leave the platform or make a code update.
Throughout this process, we will be accepting feedback from Eclipse Foundation users to help refine our goals and to best support our community.
epic