Creating Documentation on GitHub, review culture

+1 Jekyll. Have used that in past projects and had a good experience with it. Always used a custom build process, so it’s cool that we don’t need that. It will lower the barrier to contributing.

Makes sense to me. Perhaps this is an Initiative you can champion? I’m still a bit confused honestly as to how Initiatives work, but we should reward this in the graph somehow.

It’s funny, this made me think of a podcast I listened to recently on the importance of being transparent about OSS funding. Looked it up and it was your podcast! I think I found this when I was checking out your Twitter or something when you joined. But it’s been rattling around the back of my head when I think about these issues.

It’s a good listen, and you make some good points. Contributors should have visibility into who is funding a project (or know that the donors chose to remain anonymous (which will happen too)), in order to make an informed decision and not be blindsided by ickiness. I know we shout out @protocol as a funder of the project in multiple places.

Not sure how someone donating via sponsor button would make it into the graph…I think the idea is that we want people injecting money/value through Boosting, playing the SourceCred game (and increasing the utility/value of Grain). But how does that get surfaced? How do we reward people that contribute through outside channels. This is an open problem we’re still grappling with. But I digress…we should probably create a new post on transparency so as not to divert this convo (and more cred :innocent:)