Design Matters 2025

[Tofuswang]

Here’s a synthesized version of the meeting notes from the sticky notes and the proposal sketch you provided:

---

Meeting Notes: Toban (Open Source Contribution Tool)

Context

• Open Source Software (OSS) project owners often want to give back to the community and maintain contributor motivation.
• Contributions are logged on GitHub and other platforms, but recognition and reward mechanisms are inconsistent.

---

Proposal

• Toban helps track contributions across projects.
• When projects receive funding (e.g., grants, donations, sponsorships), Toban redistributes funds to contributors using crypto.
• Goal: reinforce contributor motivation and reward participation.

---

Feedback & Concerns

• Money as a language: Funding (¥, $) may not translate into meaningful “thanks.”
• Risk: Volunteers may not contribute for money. Pure monetary incentives may undermine intrinsic or social motivations.
• Observation: ¥ might be worse than social recognition if not framed well.

---

What People Appreciate as Thanks

• Small gifts.
• Having issues fixed (“They solved my problem!”).
• Seeing the tangible effect of their contribution.
• Social connections and satisfaction.

---

User Value

• Social satisfaction and community connections are more important than financial gain.
• Recognition of both quantitative results (commits, fixes) and qualitative impact (relationships, mentorship).

---

Questions to Explore

1. What do people truly appreciate as thanks?
2. If someone contributes, do they want more responsibility or a different role?
3. What are other effective forms of motivation beyond money?
4. How do we balance event organizers’ needs and OSS project sustainability?

---

Current Use Cases

• Community park/forest stewardship.
• Community markets.
• OSS software projects.

---

Challenges Identified

• Owners struggle with giving back to contributors in a meaningful way.
• Projects don’t always make money; many rely on grants.
• Users expect high impact with low investment (e.g., “100% results with 10% input”).

---

Next Steps

• Talk to current OSS contributors and community members.
• Explore alternative models of motivation (non-monetary, hybrid).
• Prototype Toban as both a tracking tool and a recognition system (not just financial redistribution).

---

This turns the scattered sticky note insights into a coherent meeting summary.
Would you like me to also draft a visual 1-page summary (like a diagram or concept map) so it mirrors the style of your proposal sketch?

[r-itagaki-boop]

Hiii, Im runa.