-
Notifications
You must be signed in to change notification settings - Fork 6
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
Delete Old Branches #8
Comments
Hi @benhills I would like to work on this. |
Hello @saptarsi96 I am wondering how you found this repository? This is a project that was started as a group of glaciologists at the ICESat-2 Hackweek in June. Are you interested in glaciology? I am not trying to turn you away from contributing, certainly not. I just want to make sure that this is a good fit for you. This particular issue would probably be best for one of the folks who is already in communication with the rest of the group. That way, they could reach out to people to make sure that they are finished working on what I considered to be an old branch as you noted above. Definitely let me know what your goals are. If you are interested in glaciology and/or ICESat-2 we are more than happy to bring you in on the project! |
Hi @benhills I am new to GitHub and am trying to solve issues marked as "good first issue". I don't have any particular interest in glaciology but would love to know more about it. I am interested in Computer Science, if you do need any help with that I can try to help you out. |
Cool! That is great that you are so ambitious to pick up any extra projects that you can find. These two issues were marked as 'good first issue' because I see them as being that specifically for the participants of our group from the hackweek. Many, like you, are new to github and are trying to get experience with branches, etc. I would say that these two issues are not the best for you to pick up for general CS experience. Having said that, I will accept your pull request today if I can get do it. How about I explain the project, and you can decide whether you would be interested in getting more involved? A new Earth-observing satellite was launched ~2 years ago now with the primary use case being to monitor the Earth's ice sheets (Antarctica and Greenland). The onboard sensor is an altimeter that uses visible light to measure the height of whatever is below it. Glaciologists are using it to monitor how the ice sheets are shrinking/growing through time. @RGFell from our group came up with an idea to use this instrument to measure how fast the ice is moving. Essentially, we calculate the surface slope at two different satellite passes and correlate the profiles to see how far the wrinkles and bumps have moved. Ice velocity is interesting for a variety of reasons, but the main is the implications that it has for future sea-level rise. If you are interested in this project, why don't you send me an email at [email protected] so we can talk more. If this is not exactly what you are looking for, no worries. Like I said, I will accept your pull request soon. |
Great discussion - I'm so glad to see this library making forward progress! @saptarsi96, I also wanted to share with you some other groups who are always happy to have new contributors (and have plenty of opportunities for those looking to expand their skillsets). icepyx, which is a broader scale effort to build tools for ICESat-2 data users, and; the Pangeo project, which brings together a lot of great computing resources for scientific computing and is always happy to have new contributors (as are many of the component libraries it depends on, such as XArray and Pandas). Both of these groups also have open meetings (icepyx; Pangeo) if you'd like to get more involved with the teams. |
Sure @JessicaS11 I will check those out. I am pretty fascinated by your project. Would love to help you guys out sometime and learn more about how you people are doing such an incredible job to collect critical data which will save our planet. |
Some branches that I don't think we are using anymore:
Someone should double check that they are all good to be deleted and then delete from the remote repository.
The text was updated successfully, but these errors were encountered: