[Workshop]: 2026-07-27 Monday Hackday at ESIP Summer Meeting

[ateucher]

Workshop Description

Theme: ‘Making Things Easier for Scientists’

Purpose: To gather anyone who’s interested and going to ESIP, and hack on “making things easier for scientists” from policy, social and technical perspectives. This in-person hackday is about how we’re supporting scientists with infrastructure. A lot of hacking is not hands-on coding. It’s hacking on decisions. It’s seeing how each other works. Asking each other questions about interoperability. It’s surfacing friction - which friction lies in the tech and which lies in the social? We know earthaccess has transformed the way people access NASA Earthdata. It’s technically possible to do this with data across agencies like NOAA, USGS. What would that look like? We want to identify what we can move forward after the hackday. What problem do you think needs solving?

Workshop Start Date

2026-07-27

Workshop End Date

No response

Workshop Start Time

1:00 PM CDT

Workshop End Time

6:00 PM CDT

Workshop URL

https://openscapes.org/events/2026-07-27-esip-hackday/

Reset Date

2026-08-03

Estimated Number of Participants

40

Compute Requirements

4GB RAM, Up to 4CPU (TBC)

Image Requirements

Default NASA-Openscapes Python image (TBC)

Storage Requirements

Default workshop home directory limits (10GB)

Checklist for workshop organizer (person planning/leading the workshop) and hub point-of-contact (PoC; Openscapes team member helping with hub setup and logistics. Usually @ateucher).

• Hub PoC: Send confirmation to organizer that the request is received and the hub is available for the workshop (a comment in this issue thread is fine).

• Organizer: Add your event in the workshop spreadsheet. Please check if there are any other workshops scheduled around the same time and if so, let the hub PoC know to make sure the hub can support multiple workshops at the same time.

• Organizer: Submit a ticket by email to 2i2c for the workshop and request a new password for the workshop, as per instructions, cc'ing hub PoC (@ateucher; andy [at] openscapes [dot] org). You will receive confirmation of the new password for the workshop from 2i2c once it is reset. Note: DO NOT include the password in this issue or any public-facing websites. You will share it with participants on the day of the workshop.

• Hub PoC: Confirm [Event] or [Support] issue opened in 2i2c-org/infrastructure in response to ticket (example)

• Hub PoC: Add new password and dates to workshop password spreadsheet.

• Organizer: Two weeks before event. I have tested the default hub images on the workshop hub or conferred with hub PoC on plan for a workshop specific image.

• Organizer: In the week before the event (or when hub PoC indicates password should be live). I tested that the workshop password works and images work.

• Organizer: After the event, open an issue in the Workshop Planning repo to report back.

• Hub PoC: After event, put in a 2i2c ticket to reset password.

• Hub PoC: After event, log in to the hub as admin, enumerate the participant directories and update the workshop spreadsheet with the actual number of participants.

• Hub PoC: After event, delete the participant directories.

• Hub PoC: Close the issue. If the workshop was completed, close as "completed". If the workshop was cancelled before being held, close as "Not Planned" and note in the comments that it was cancelled.

[ateucher]

@betolink @asteiker @jules32 I am getting things ready for the hub to be available to use on the ESIP earthaccess hackday, and was hoping to get your input into what resources we might need? I've put these in for now:

Estimated Number of Participants: 40

Compute Requirements: 4GB RAM, Up to 4CPU (The second lowest in the dropdown)

Image Requirements: Default NASA-Openscapes Python image (latest corn image)

Storage Requirements: Default workshop home directory limits (10GB)

Let me know if you think that's sufficient - thanks!

[jules32]

Thank you Andy, I think this is a good plan!

[asteiker]

Yes @ateucher This looks good to me as well. I don't expect we'll see as many as 40 participants but it's a good number to start with to be safe.

I wonder if we should consider bumping the earthaccess version in the default Python image. I recall we may be behind but haven't confirmed yet.

[ateucher]

Thanks @asteiker! The default Python image has earthaccess v0.18.0. I believe that's the latest?

[asteiker]

Thank you, I should have checked before commenting! Yes this is the latest release, thank you for confirming. I believe @betolink was interested in a new release before ESIP to merge open.virtual() so this may be something to keep in mind.

[ateucher]

2i2c support issue here: 2i2c-org/infrastructure#8722