npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@boardroom/ideation

v0.1.5

Published

signal weighted ideation ranking

Downloads

15

Readme

RFC - 006 Ideation Forum

  • Status: proposed
  • Submission Date: 2021 - 02 - 03
  • Author(s): YJ Kim

Synopsis

The ideation forum package is an IDX package that should extend the basic comments functionality (RFC 001) such that all discussion leading up to eventual proposal submission is traceable to the the source and attributable to the original contributors (for retroactive treasury payouts, tips, etc.).

Motivation / Objectives

The flow of the Boardroom Hub should mirror the decision making process from ideation to proposal creation to execution and post-mortem/disclosures. This feature is focused on the first step of that pipeline: Ideation.

The current process is for stakeholders to post an idea on Discourse, bake the proposal through discussions with other forum members, and eventually either table the idea or submit a formal proposal onchain or as a Snapshot.

The problem with this setup is that the full line of reasoning gets lost between each stage of the pipeline. The ideation forum package is an IDX package that should extend the basic comments functionality such that all discussion leading up to eventual proposal submission is traceable to the the source and attributable to the original contributors (for retroactive treasury payouts, tips, etc.).

We may also want to enforce a time boundary during which an ideation thread can live, at then end of which and proposal is drawn up and submitted automatically to the appropriate snapshot space. The only problem with this is that the proposal author would always be a Boardroom account as opposed to those that actually participated in it. A easier middle ground may simply be to close further discussions on the thread after a certain time boundary, and the only action is to export the thread as the body of the Proposal Creation page for easy editting.

KPIs (for post-mortem & future iterations)

  • Participation in ideation threads
    • Number of new ideation threads initiated
    • Depth of discussions of the threads
  • Number of ideation threads that make it to proposal creation
  • Number of ideation threads that make it to execution

Specs / Implementation Plan

More or less the same idea as Proposal Comments, except we'll change the schema up a bit.

And we'll change up the seed, so for each space, we create a new seed hash from boardroom-${spacename}-ideation as opposed to a single boardroomideation space (as we did for proposal comments initially).

Post

| Property | Type | | |---------------|-------------|----------------------------------------------------------------------------------------------------| | id | ceramicDID | Ceramic Document Id | | author | string | Ethereum address of the submitter. | | signature | string | ECDSA signature of the post by author. | | space | string | The name of the Snapshot space. | | title | string | The name of the new ideation thread. | | body | string | The body of the new proposal in Markdown format. | | start | number | A start date/time expressed in Unix time format. | | end | number | An end date/time expressed in Unix time format. | | votes |Vote[] | Array of Votes | | replies |Reply[] | Array of Replys

Vote

| Property | Type | | |---------------|-------------|----------------------------------------------------------------------------------------------------| | id | ceramicDID | Ceramic Document Id | | author | string | Ethereum address of the submitter. | | direction | up | down | Upvote or Downvote. | | score | string | BigNumber-ish snapshot score. | | postID | ceramicDID | DocID as foreign key for the Post. | | signature | string | ECDSA signature of the post by author. |

Reply

| Property | Type | | |---------------|-------------|----------------------------------------------------------------------------------------------------| | id | ceramicDID | Ceramic Document Id | | author | string | Ethereum address of the submitter. | | score | string | BigNumber-ish snapshot score. | | postID | ceramicDID | DocID as foreign key for the Post. | | signature | string | ECDSA signature of the post by author. | | votes |Vote[] | Array of Votes | | replies |Reply[] | Array of Replys