Gitcoin Forum Improvement Project

This is a fantastic initiative. Iā€™m looking forward to participate in the workshop next week!

2 Likes

Starting now: meet.google.com/jgj-uudo-ppt

1 Like

Vision and categorization

A forum is an organized, easy-to-navigate active community space where people post their well-thought ideas to get feedback and build a consensus that lasts over time.

Based on your responses, this is a vision statement, and our whole project will be heading to accomplish that vision.

As the most significant problem, we have defined the categorization of the Gitcoin forum; therefore, the first step in our Forum improvement project is to focus on that.

Categorization approach

There are a few possible approaches to it. Discourse enables the creation of categories, subcategories, and tags. But that doesnā€™t mean that we need to use all those options. Many forums do not heavily use subcategories. And I think the reason is that there are not that many categories where you need to break them down and create a structure around them. In other words, if I have 100 categories, it will be hard to find something; therefore, it would make sense to create 10 top categories and 10 subcategories per each for more straightforward navigation. But If I have 10-20 categories overall, why I would make the system more complex.

Thatā€™s why I have excluded subcategories from the design considerations.

What about tags? I love tags, and as I saw on other forums, itā€™s a very nice and casual approach to flag something across categories to ā€œnotify specific stakeholdersā€.

One example of a stakeholder who needs to be notified across categories is the steward. But there is no such a thing as this is steward only topic. One example can be Partnerships. Stewards need to comment on those topics and eventually vote, but it doesnā€™t mean that those topics are Steward only.

Another use case where flags can be used rather than categories is to support cross-workstream collaboration. We currently have many workstream silos, which we have identified as one of the key issues during our all-team session in Denver. And if we create categories for each workstream, we would create another silo.

I propose to use Tags to identify the right stakeholder.

Identification of the stakeholder should be part of the post creation; the creator should be able to identify their audience, and they should be able to know who they are targeting and who they want feedback from.

Here are some examples of tags:

  1. Gitcoin Community
  2. Stewards
  3. Holdings
  4. Newbies
  5. MMM
  6. Moonshot
  7. Technical
  8. Product

The full list can be found here, please review.

Why are we tagging the potential reader?

By tagging the reader, we introduce a new easy way to keep track of all the items the reader should be involved in, which will introduce three new behaviors:

  1. The reader will be able to target better the post they need to be involved in; therefore, those topics get more attention.
  2. The readers will be more willing to participate in the forum as it will be a better experience and require less time to find stuff.
  3. The readers might ignore topics that they are not tagged in, but previously they have randomly visited those and contributed.

Those are predominantly positive behaviors, but itā€™s important to be aware of those negatives and closely monitor them.

If you are following closely, you know how we will be using tags and that we are not going to use subcategories.

In terms of categories, letā€™s be rather unrestrictive and let the community decide. When you look at another popular forum such as Reddit, the most popular categories are at the top and then the less popular. In the same way, we should manage our forum:

  • Step n.1 - Suggest categories - open to everyone; put any category you have in mind on the list here and help to prioritize it.

  • Step n. 2 - Poll - Letā€™s run a quick poll of what categories people want and pick the top 15-20.

  • Step n. 3 - based on the n. of votes, create categories at Discourse.

  • Step n. 4 - actively manage the hierarchy of the categories based on the importance and activity.

And by that, we should be able to solve a most important issue - categorization.

In the next iteration, we will explore the self-hosting of the platform, sign-in with the wallet, and how to attract people from different communities to provide insight.

Please, if you have any questions or feedback, leave your comment below.

Also please review our current set of categories and tags and help me finalize it.

CC: @Pop ; @Fred ; @krrisis ; @Hammad ; @Fishbiscuit ; @0xRachael

3 Likes

For collective curation and prioritization processes like this, I can highly recommend a Pol.is conversation followed by a quadratic vote.

Happy to facilitate these if you like, Puncar.

1 Like

Great idea @erich , thank you, yes it will be great to set it up. Currently, I am tracking it in Google Sheets, and itā€™s not perfect.

1 Like

Awesome ā€” hereā€™s a Pol.is conversation around this issue: Polis. Please feel free to circulate the poll in GitcoinDAO and the wider community.

Let me know if youā€™d like to make edits to the descriptions I used.

In any case, Iā€™m looking forward to see what categories will get the most plural community support. Let me know when to close the poll and generate the full report with the results.

Thanks for the writeup Puncar. I appreciate the methodology you are using to solve this problem.

2 Likes

Thanks for the write up, this feels like a great step in the right direction. Iā€™ve added some comments in the google sheet with my thoughts regarding categories and tags.

The Pol.is results are here, @puncar: https://pol.is/report/r7bjuaeufyws8mcjapxkn.

2 Likes

Thanks, @erich, I will combine that with the outcome of yesterdayā€™s Workshop and prepare a report to post here.

2 Likes

The next steps for the forum, which I am suggesting implementing for Season 14.

Create standard categories that moderators will actively manage:

  • DAO Governance and Metagovernance (to be merged with the Metagovernance category)
  • Vision, goals, roadmaps, and partnerships (to be merged with the Proposal category)
  • Budgets and financial matters
  • Ideas and open discussion ( to be merged with the Workstream discussion category)
  • User and Community Experience (how to / tooling)
  • Grants
  • Products
  • Newsletter, Digest, and Daily thread (to be merged with the Community hangout category)

Create tags to notify appropriate stakeholders about the new post;
That enables any stakeholder to set up the notifications based on those tags or search for the tag within the forum and target only relevant posts.

There will be three categories of Tags - standard, technical, and vibes. The community will manage those tags to ensure that we are not excluding any stakeholders.

Additional material to be created:
How to write new post and determine what category and tag to use.

Sources:
Miro Board
Forum categories and tags spreadsheet

Please let me know if you have any questions or comments on the suggested changes and approach.

2 Likes


@Fred @seedphrase could MMM help me with some visuals for the Forum? as you can see I am not a designer :slight_smile:

3 Likes

Thanks for writing this up Puncar!
I think the tags are OK but I think we need shorter category names, eg if you look at forum.giveth.io you see why.

Plus, also some things missing when I look at recent posts + how we are evolving as a DAO. We have the following priorities for the coming 18 months (to be ratified tmrw)

  • Grants Protocol
  • Financial Sustainability
  • DAO Organization
  • Grants Program Mission

ā€¦ and would propose to align the categories to this as much as possible/relevant.

Wdyt of the following:

  • DAO Governance & Vision
    ā†’ how we coordinate within our DAO + where we are going

  • Grants
    ā†’ where we talk about the Grants 2.0 protocol & roadmap + grants program mission

  • Budget Proposals & Partnerships
    ā†’ where workstreams & other interested parties post their proposals for budget & partnerships

  • News & Community
    ā†’ where we share our weekly newsletter & other dao-wide recordings

  • Ideas and Open Discussion
    ā†’ where anyone can join in

On the others:

  • User and Community Experience (how to / tooling) ā†’ I think this fits under dao governance, other how-toā€™s should live on notion?

  • Products ā†’ I donā€™t think we need this, our product = grants

Apart from this I think ALL previous posts need to be evaluated after merging old categories IF they are actually in the right category & reassigned if needed. Would be great if you could reserve enough time for this + also add a timing for doing these things.

Let me know what you think & thx for all the follow-up!
Note: I will also mention these thoughts for an updated categorization during CSDO (if time allows) but will tweak if I get your feedback in time.

cc @Pop

I would like to wait until we ratify in the CSDO call today vs putting this out and front-running any comments or amendments. It avoids any double work or confusion - both in the broader community and internallyā€¦

2 Likes

I like that point; we should definitely follow our main goals / northstar

Both topics are pretty substantial.

  1. how are we coordinating - DAO Governance
  2. where are we heading - Roadmap, vision

When we have done voting, each of these categories received many votes from the community, and we would be basically merging the top 2 categories. Because of those reasons, I would like to keep those 2 categories separate.

I think the primary purpose of the partnership should not be budget requests. It should be about synergies and supporting the overall vision. Putting it into the budget category would imply that our partnerships are only financial.

Therefore, I want to separate financial matters like budget proposals from business partnerships as originally proposed

I know that our main product is Grants, but we have some other products coming from different teams, and I believe it will be great to have product discussions on the forum, to get community feedback on those products and shape their development.

Thank you very much for all your suggestions; I have updated the categories based on that; here is the updated list in the order of priority based on community feedback:

  • DAO Governance
  • Vision, roadmaps, and partnerships
  • Budgets and financial matters
  • Ideas and open discussion
  • Grants
  • Products
  • News & Community

Additionally, I would like to add that when those changes get implemented, the main page will have categories on the left side and the latest on the right side as the default view. It will look very similar to Giveth; see the screenshot below:

@Pop, has CSDO ratified the approach, and can I implement this new category & tag structure on Friday, May 27?

Hey Puncar,

Thanks for the feedback & suggestions!

So I also discussed with @Pop just now. Iā€™ll be bringing this as a proposal to CSDO tmrw to ratify, unless there is strong input on the purpose and intents during the Stewards Council call that makes us go back to the drawing table. And your further thoughts are ofc also still very much welcome.

Some comments on your comments:

We donā€™t really see the difference between those two. It makes sense that people have voted up those two high, because they were two separate categories to vote on, but we donā€™t see the distinction between both, so I would want to push back here. If we keep them separately here Iā€™d go for

  • DAO Governance
  • Vision & Mission

but Iā€™d prefer to stick with just one

  • DAO Governance & Vision

ā€¦ because these topics are very much overlapping.

If you look through partnership proposals you will see that 99% of them are actually financial, that is how the world currently works. (one day weā€™ll change that :slight_smile: )

The advantage of separating them is that we keep our budget proposals separate from partnership proposals, so possibly open to that.

So here as well I want to give CSDO the option, either

  • Budget Proposals & Partnerships
    or

  • Budget proposals
    &

  • Partnerships

Notes:

  • Partnerships can definitely not stay with vision & mission / governance, because partnership proposals will start getting mixed up with our own DAO plans and this is confusing to people
  • ā€˜Financial mattersā€™ Iā€™d propose to leave out as well as this is again a bit vague. If itā€™s treasury diversification updates it can end up in news & community, if it is a strategic plan on financial matters it should end up in mission & vision.

Yeah, so here both Simona and I disagree strongly.
We have only one product for the foreseeable future and that is Grants.

Others will either be spun out, stay with holdings or cease to exist.
If new ideas pop up they can be shared in ideas & open discussion and can at some point become budget proposals.

So tl;dr I will be proposing the following categories:

  • DAO Governance & Vision
    Alt:
    DAO Governance
    &
    Vision & Mission

  • Budget Proposals & Partnerships
    Alt :
    Budget Proposals
    &
    Partnerships

  • Ideas and Open Discussion

  • Grants

  • News & Community

Let me know if this makes sense and if youā€™d like to add anything else for the proposal, same for you @pop!

2 Likes

Ok, letā€™s try that for now and see.

as discussed on the call, for this one, I would prefer to separate budget requests from partnerships, as I would like to encourage to have partnerships that are not starting with the budget request or token swaps.

I may see the future with multiple products as moonshot and other workstreams are building it, but for now, we probably focus mostly/only on grats and we donā€™t need that category.

Overall the new list is:

  • DAO Governance & Vision
  • Budget Proposals
  • Partnerships
  • Ideas and Open Discussion
  • Grants
  • News & Community
1 Like

Sounds good!
Final note for now, I would move up Grants, as being at the core of what we do.
This would bring us to

  • DAO Governance & Vision
  • Grants
  • Budget Proposals
  • Partnerships
  • Ideas and Open Discussion
  • News & Community

Will present during CSDO & report back!

1 Like

Hey @puncar this was ratified during CSDO, feel free to implement!

1 Like

Thank you - I will implement it on Friday/Saturday when the Forum is more quiet

1 Like