isce-framework
Accepting public contributions?
For quite a while the following notice has been in the 'about' section of the repository. Would it be possible to share an approximate timeline or prerequisites for acceptable pull requests?
NOTICE - This repository is currently a mirror of an internally hosted project and is in the process of migrating the development to this public repository. In near future we will accept external pull requests.
I'm interested in particular in helping with user-facing documentation, but I'm sure there are others out there who could be making contributions if permitted!
Dear @scottyhq thank you for reaching out and for your interest in contributing to ISCE3. We truly appreciate your patience and support as we work through this transition.
Due to factors beyond our control, progress on fully opening up the repository and accepting pull requests has been slower than we had hoped. We understand how this delay may be frustrating, especially for community members like you who are eager to contribute.
The good news is that most of the issues we've faced have been resolved, and we’re now focused on addressing one final bureaucratic step. We’re optimistic this will be resolved within the next month. If so, we’ll be able to start accepting pull requests soon after. If there will be further delays, we’ll explore alternative approaches and will update you and the community with a more precise timeline.
In any case, we commit to providing a clearer update by the end of February 2025, if not sooner.
Thank you again for your patience and your interest to contribute to ISCE3.
@scottyhq I wanted to provide an update to you and other potential contributors regarding our progress on transitioning development to this repository and accepting pull requests. Our final hurdle is setting up the CI system. While we have a robust CI system in place internally, enabling PRs on this repository requires us to establish a similar system here. After careful consideration, we've identified GitHub Actions as the best option for our needs. Given that ISCE3 includes CUDA code, we require a GitHub Actions plan that supports building and running GPU code. We're currently in the process of securing the necessary plan for this repository. Unfortunately, this process has taken longer than anticipated for reasons beyond our control. We’ll continue to keep you updated as we make progress.
Thanks for the update! Definitely having GitHub actions would be great. In case it helps, scikit-learn documented their CI setup with GPUs a while back. My guess is you'd want to follow their pattern of only running on GPUs when a maintainer adds a label https://blog.scientific-python.org/scikit-learn/gpu-ci/ https://github.com/scikit-learn/scikit-learn/blob/main/.github/workflows/cuda-ci.yml
I'm pleased to give an update on this topic. We have successfully passed all bureaucratic burdens to setup our CI/CD system using GitHub Actions. The organization is upgraded to GitHub's team plan already. Next steps for us is:
- Configure Actions and confirm that GPU runners are in place so we are all set to run all our unit tests on PRs (Expected to complete on week of May 12)
- The team has been working on reviving documentations for ISCE3. With the configured CI, the updated documentation will be live. It will include Contribution Guide as you would expect. Once that is all in place, I'm happy to hear your thoughts @scottyhq @piyushrpt @jhkennedy and others on missing documentations and contributions from everyone to improve.
- Once we receive green light that CI system is working, we will start transitioning our internal developments to this repository. You should soon see PRs and review process on this repository.
We are very excited about this big step towards engaging with the community. Thank you very much for everyone's patience.
Fantastic! Thank you for you're hard work to make this happen @hfattahi ; I think this will be a huge win for the SAR and broader science communities!
This is great !! I will be happy to contribute as well. Currently I am using ISCE3 via conda and stumbling through the source to make things work.
