Skip to content
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

Workshop in ADASS #236

Open
pllim opened this issue Feb 13, 2024 · 1 comment
Open

Workshop in ADASS #236

pllim opened this issue Feb 13, 2024 · 1 comment

Comments

@pllim
Copy link
Member

pllim commented Feb 13, 2024

We have done quite a few in AAS but those are introductory and aimed at users. According to https://astropy-report.orgmycology.com/sections/community_recommendations#workshops , there might be a need for workshop that targets new potential contributors in ADASS.

I think we could hold contributor workshops or Github workshops at more technical meetings like ADASS.

@jduckles
Copy link

A couple of related things:

Deconstructed workshops - I wonder if some of these GitHub contributor workshops could be "deconstructed" and taken online. Maybe 4 1-hour sessions over four weeks, would be equivalent to a half-day workshop. With a recording and some "exercises" making commits to a "learning" repository could be helpful to let the workshop have legs for a few months afterwards as well.

Supporting First PRs - If community members haven't done PRs before, I have taught the GitHub pull request model to those who haven't experinced it with a "demo" repository. It contanis content that most people can find something to commit to it (trivia about all the countries in the world). This can demystify the process of a pull request for those who have never gone through that process before. I'm not sure if this level of support is a need or not in this community though.

Contribute to Documentation First - To learn the contributor "ways of Astropy" perhaps we can find ways to encourage their first-commit target to be improving documentation, before committing software PRs to the core packages. Small documentation PRs are likely needed, and helpful, and demystify the mechanisms of contribution for people who are keen to find ways to contribute. A culture of documentation improement can be kicked off with a bug BBQ event as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants