Background
Open Austin is moving from a casual meetup toward a more mature volunteer organization while keeping its grassroots, flexible, open-source character.
One lightweight process we need is a consistent way to give volunteers credit for their work. This operationalizes the contributor policy across three surfaces:
- Website / Lab page
- Open Austin repositories
- Social media shoutouts
Contributor policy: https://open-austin.odoo.com/contributor-policy
Lab page: https://open-austin.odoo.com/lab
Scope boundary
This is a starter infrastructure / operations task, not a forever-role.
The goal is to produce a practical audit and recommendation, not to personally fix every contributor-credit problem across the whole org. If implementation work grows, split follow-up issues for Communications, Product Teams, or project champions.
Keep the first pass small enough that a new Infrastructure contributor can complete it without becoming the long-term owner of contributor recognition.
Method 1: Website / Lab page audit
Audit the people listed on the Open Austin Lab page.
Tasks:
- Identify who appears to need to be added or removed.
- For each product/project, check the relevant Slack project channel history (
#p-...) for active contributors.
- For people who likely need to be added, find the Slack profile-photo URL if available.
- Record uncertain cases separately instead of guessing.
Definition of done:
- Short list of likely additions, removals, and uncertain cases.
- Each recommendation includes project/source context.
- No direct website changes are required in this issue unless separately assigned.
Method 2: Repository contributor credit
Data Research Hub
Tasks:
- Confer with Beto and Nicola Rowe about how Data Research Hub contributors should receive credit.
- Capture their view on how open-source data work differs from software-engineering repo credit.
- Summarize their feedback into a recommendation.
Cross-functional product repos
Tasks:
- Identify how three well-known open-source projects credit contributors in code repos.
- Identify current Open Austin project repositories that may need contributor-credit standards.
- Recommend a lightweight repo-credit convention Open Austin can reuse.
Definition of done:
- One short recommendation for Data Research Hub.
- One short recommendation for software/product repos.
- Follow-up implementation issues created if repo changes are needed.
Method 3: Social media shoutouts
Canva template: https://www.canva.com/design/DAGn77O97eg/n1HV6mhpNljF_Y6loqESYw/edit
Project champions sync notes: https://docs.google.com/document/d/1QibMDrHCg_SwUtMFShJJOGLALCshf17Oors0s1CYES4/edit?tab=t.0
Tasks:
- Review the contributor spotlight template status.
- Gather contributor names from the March 8 entry in the project champions sync notes.
- Identify what information is missing before shoutouts can be drafted.
- Do not make the new Infrastructure contributor responsible for full social media production unless they explicitly want that work.
Definition of done:
- Template status noted.
- Candidate contributor names gathered.
- Missing info / follow-up asks listed.
- Follow-up Communications issue created if content production is needed.
Recommended first pass
For a new contributor, start with discovery and a compact written recommendation:
- Website / Lab page audit list.
- Repository-credit recommendation.
- Social shoutout readiness check.
- Follow-up issues for implementation work that should live outside this starter task.
Notes
This touches Infrastructure because it involves repeatable systems, repositories, website surfaces, and contributor records. It also overlaps with Communications and project operations, so keep handoffs explicit.
Background
Open Austin is moving from a casual meetup toward a more mature volunteer organization while keeping its grassroots, flexible, open-source character.
One lightweight process we need is a consistent way to give volunteers credit for their work. This operationalizes the contributor policy across three surfaces:
Contributor policy: https://open-austin.odoo.com/contributor-policy
Lab page: https://open-austin.odoo.com/lab
Scope boundary
This is a starter infrastructure / operations task, not a forever-role.
The goal is to produce a practical audit and recommendation, not to personally fix every contributor-credit problem across the whole org. If implementation work grows, split follow-up issues for Communications, Product Teams, or project champions.
Keep the first pass small enough that a new Infrastructure contributor can complete it without becoming the long-term owner of contributor recognition.
Method 1: Website / Lab page audit
Audit the people listed on the Open Austin Lab page.
Tasks:
#p-...) for active contributors.Definition of done:
Method 2: Repository contributor credit
Data Research Hub
Tasks:
Cross-functional product repos
Tasks:
Definition of done:
Method 3: Social media shoutouts
Canva template: https://www.canva.com/design/DAGn77O97eg/n1HV6mhpNljF_Y6loqESYw/edit
Project champions sync notes: https://docs.google.com/document/d/1QibMDrHCg_SwUtMFShJJOGLALCshf17Oors0s1CYES4/edit?tab=t.0
Tasks:
Definition of done:
Recommended first pass
For a new contributor, start with discovery and a compact written recommendation:
Notes
This touches Infrastructure because it involves repeatable systems, repositories, website surfaces, and contributor records. It also overlaps with Communications and project operations, so keep handoffs explicit.