[PAP23] PM resident for Public Assembly | 2nd term

Status: Live
Context: [[Proposal to serve PA as a PM // 2nd term ]
Votes: Onchain
Authors: verymehari


Hey all,

submitting a prop to renew my term as pm for public assembly.

I want to check-in with you to see if there was any feedback to give on the proposal beforehand.


This proposal is to request funding to serve Public Assembly as a community resident // project manager for the next 3 months. The goal is to facilitate communication both internally and externally within the community, as well as to guide current and future PA members in their projects. Based on the feedback given in my post-mortem (View here). In this second term, I’ll be focusing on creating community spaces for members to collaborate with each other, assist in ongoing projects (website redesign, assembly press, grant submissions, etc) as well as hosting our monthly townhalls.


For the past few months, I have been involved in the PA community (thanks to 0xtranqui for being a steward in that process) and I definitely see the potential for this organization to grow as a sanctuary for developers and builders in the Web 3 space. It was mentioned in the last town hall that for Public Assembly to grow, we need to be more organized and establish a baseline for communication channels and contribution guidelines. This proposal offers my time as a project manager to help build bridges between the community and PA as onchain infrastructure.

Proposal details:

Documentation Standardization: Establish documentation for future town hall meetings, and ensure that their documentation is available for the next three town hall meetings (October, November, and December). Additionally, act as a point of contact for members seeking key information within Public Assembly. As part of the deliverables for this section, transcribe meetings and present key takeaways to make the content more digestible for the community.

Project management: Assisting PA members in facilitating the 4 steps of project development (setup, planning, delivery and close). This would also involve reaching out to both old and new token holders and providing a progress report on what they need for the project to reach completion. To begin with, I would start with the following initiatives:

  • Website redesign
  • Open blog
  • Assembly Press

Communication channels:
The focus here is on sharing community highlights within Public Assembly through Twitter, with the goal of providing at least bi-weekly updates.

External funding:

I would explore grants and other funding models that could benefit PA in the long term. In this role, I would allocate my time to sharing grants in the forum and ensuring that we meet deadlines for grant applications, if necessary.


This would help improve collaboration among PA members and provide context to others who would like to be involved.


  • Month 1 (October 2023): Townhall #7, website redesign
  • Month 2 (November 2023): Townhall #8, Assembly Press.
  • Month 3 (December 2023): Townhall #9, Open Blog, end of mandate report.


Total funds requested: 2 eth (a slight increase here since I found that the role took more of my time than expected.)

1 Like

timeline going thru the end of the year feels right. in terms of general focus I would say figuring out what shared spaces exist outside of the forum that can be more participatory / focused on ppls expression / work (ex: demoView, Open blog, things like that) feels like the most meaningful angle atm

theres a whole discussion about assembly press that we need to have since earlier plans to kickoff broader community dev are on hold (in my opinion) until:

  1. me jawn salief free up again in terms of capacity (as we have been leading the direction + execution of the framework up until now)
  2. we develop a new mental model for what AP is being developed for (is it just public goods r&d that we report on?), how much we should try to engage external contributors on it depending on what its purpose is, as well as many other questions
1 Like

Agreed! Timeline for AP shouldn’t be rushed. We’ll touch base when our schedules align.

@projectmehari It looks like the “Onchain” link at the top is going to an old prop from January.

Here’s a link to the current prop for whomever needs it.


1 Like

good catch, thanks kev !

Revisiting this after our last town hall :

Items that imo are crucial for PA get organized over the next two months of @projectmehari’s PM term (in order of importance)

  • Migration of Discourse to Discord before November 30th deadline
  • Gathering of all previous documentation and organizing it to be migrated to the new doc site
  • Repository (google table, notion table, etc) of historic PA proposal applications, with links for future proposals to apply to

IMO all of this is crucial before focusing on more outreach -foundational stuff the org will benefit from and will get us ready for outreach at the start of 2024. And there are likely items that we can help Kiru with once he digs into it (like docs stuff)

(cc @0xTranqui @salief )


Wholeheartedly agree. I can definitely help with the transition from Discourse to Discord. Happy to figuring out what bundling up the data here looks like and saving it a safe place :slight_smile:

1 Like

github would be great for this imo!

Valid! Haha I feel like the use cases for github are literally endless. bless it. and that would work well if we’re moving all our docs there too.

Could you point us towards any kind of tut or docs on how to get that started in github?

Started this repo for grants last week

1 Like

im gonna make aloom rn . catch me in 5

Also started this thread here Platform Migration - Discourse to Discord, with a breakdown of the tasks at hand.

1 Like

ok boom Loom | Free Screen & Video Recording Software | Loom


1 Like

loom king bless