After discussing this proposal during the Mar 01 meeting it was suggested to expand on some details. Here I will be diving into the process of each of the items above for clarity and to illustrate what work is involved during the process:
Facilitate developer outreach initiative - I am always looking for new ways to expand and reach more developers; there is value here as developers make up essential product demographics in both contribution and use. Here is the working process currently in play:
-
R//Rust has a prominent jobs posting on each new rustLang update. As this post gets updated a new Grin Jobs post is posted. This benefits project awareness in addition to eyes on from essential demographic.
-
Also in this jobs post is a section where experienced Rust devs may post work experience and contact info for recruiters to contact them. In the past Q I’ve contacted over 40 Rust developers and fwd them a friendly greeting with an invitation to join dev channels. This also benefits project awareness in key demographic. As Grin has a strong value proposition I am confident with moving forward with individual contact sourced from other channels i.e github profiles, lobste.rs contributors, etc. for more eyes on.
-
The Grin Jobs post went to twitter thanks to @future. I have a strategy to use this screencap and share across various channels. This is a clever way to use the ‘Jobs’ post as a way to push general awareness/ gets eyes on project.
-
I don’t see this job ending with the advertised jobs posts, or the individual contact outreach. When interested parties respond to outreach they don’t get ghosted. There has to be a follow up such as getting the wish-list, bounty items of interest and general on-boarding assistance in front of new developers.
I am looking to expand on this initiative through new methods and from various sources like github profiles and lobste.rs technical site. This work came into scope as the community highlighted the importance of bringing developers to Grin.
release bi-weekly grinnews newsletter - This work process looks like this:
- Research Phase: conducted by following closely development, news, research, governance, and community updates to identify item inclusion.
- Writing + Edit + Publish Phase: original content writing with brief survey of the items from the research phase. Also will include meetups, jobs into newsletter as they come-up. Edit and formatted to be published to stackexhange.
- I don’t just write the newsletter; I see this also as an asset to drive project awareness, as such I take responsibility to share, and spread this article across various channels post publish including: HackerNews, Reddit(various subs), Bitcointalk, Telegram, Keybase, Grin-Forum. I am looking for more channels to share to as this is an asset to bring eyes on the project.
Maintain, organize, and contribute to github documentation -
- Financial documentation - keep up-to-date financial github documents: spending_log.csv, quarterly transparency reports.
- Meeting notes - Community Council meetings run Bi-weekly. These notes are transcribed and published.
- During meetings there are decisions being made, I maintain these post meeting note transcription with updates to the decision_log.md
- Misc opportunity is the acknowledgment that there will be additional future updates, additions, edits, etc that may fall outside the scope of those already mentioned above. I take responsibility to make these necessary changes when needed as part of the role.
Work closely with CC,OC,IC’s, and developers to identify new campaigns and opportunities - To clarify, this is in reference to how the Groundskeeping role puts my work in close proximity to these entities; and as such I take personal responsibility to collaborate and meet the ongoing and any unforeseen new requests. I refer to these ongoing request as campaigns and opportunities as they can be various tasks asked within reason. The job title groundskeeper is a hint at this job feature- as being available to meet demands and requests as needed.
Remain flexible and available to respond to project related tasks and initiatives directed from CC/OC - I think this item is closely related to the above item but I want to make clear the emphasis of availability and to be open to meet ongoing project demands and requests. This is an emphasis on role flexibility and being open to meet these objectives as they arise without placing burden on others to get the job done.
I hope this is helpful in clarifying some of the work objectives and processes that go into fulfilling the role. I also see these job descriptions as an evolution and work in progress.