Description

The idea is to have technical resources translate the Bitcoin Lightning BOLTs into an easier to understand document, explaining what each BOLT and its components do.

The goal of this is to make it easier for Bitcoin lightning network builders to get onboarded so they can more quickly ship products which help address customer needs.

Resources:

N/A

NOTE:
Issue originally submitted by jackronaldi on hellonext

Description

1. Interview exchanges to see what their motivations are, what they would need to implement it, and what specific deliverable would be helpful for them. (Do they want a white paper? Code? Tool recommendations? etc.)
2. Consult with technical subject matter experts to see how to implement it.
3. Execute and market the solution.
4. I imagine this project would take a while but would definitely be high impact

Resources:

Include links to resources that will help the community understand your project idea.

NOTE:
Issue originally submitted by Bitcoin Product Contributor on hellonext

Description of Proposal

Since we launched the group on March 20, 2023, one of the initiatives we've been working on has been to connect contributors to foss bitcoin projects (#8).

Since then we've been manually interviewing both foss projects and contributors to get a feel for what exactly is the "secret sauce" of connecting the two groups. Here's our product requirements document(PRD) that explains our methodology.

You can find the results of our interviews and market research in this slide deck. You can also listen to the high level overview of the results of the initiative in this video.

We are now ready to move on to the next phase of creating an MVP which is the Bitcoin FOSS Opportunity Board. This board will be a repo under our Github organization that FOSS projects can submit an issue with the following template. Once they create an issue, it will automatically get put in a github project titled: Bitcoin FOSS Opportunity Board. This is the place contributors can peruse to see which opportunity and project they are interested in getting involved with.

We decided to use github for several reasons. It's free and easy to set up which is great for an MVP. But most importantly this is the tool most FOSS Bitcoin projects use. It is also great for skill development for contributors as they get familiar with github.

If we have no objections, we should create this repo + github project then start marketing it to Bitcoin FOSS projects who might need some help.

Here is the project folder which contains all the interviews we did, the templates, the PRD, and the data.

Deadline for Rough Consensus

5/11/23

Notes for the community::

• Please feel free to leave comments on the issue for any questions or concerns.
• Vote with Emojis on the issue proposal.
  • 👍 in support,
  • 👎 not in support

Description

Persona: People who want to be product managers

For folks who want to develop skills in product management who might not know the value or steps to becoming one. How might we provide them with a path to embark on?

Possible Solutions
Create a list of useful articles, links, videos and other materials that someone can consume in order to become a open source product/project manager.

Resources:

N/A

NOTE:
Issue originally submitted by Johns Beharry on hellonext

Description of Proposal

Let’s find a domain name for our community. Please do both of the below, or at least #2:

Submit your proposals for the domain name of the Bitcoin Product Community in the comments below.

Give a thumbs up for the name which you like best

The domain name with the most upvotes by our next meeting, March 2nd, wins!

May the odds be ever in your favor.

Deadline for Rough Consensus

Notes for the community::

• Please feel free to leave comments on the issue for any questions or concerns.
• Vote with Emojis on the issue proposal.
  • 👍 in support,
  • 👎 not in support

Description:

Gather UX/UI feedback and other insights from customer interactions into one shared repository for all Bitcoin PMs to benefit from.

NOTE:
Issue originally submitted by jackronaldi on hellonext

Description of Proposal

One of the requirements we wanted when we first chose a website was to have a tool to collect emails and host blogs.

Notion has the ability to host blogs but doesn’t have a tool for email integration.

I propose that we use substack as the platform to host our blogs and collect email subscriptions.

Deadline for Rough Consensus

Due date for feedback: 2/15/23

Notes for the community::

• Please feel free to leave comments on the issue for any questions or concerns.
• Vote with Emojis on the issue proposal.
  • 👍 in support,
  • 👎 not in support

BPC Speaker Series Proposal

Proposal

BPC hosts a ten episode speaker series interviewing Bitcoin Product Managers, Project Managers and FOSS contributors. The series will be the main communications outlet that drives people to the Bitcoin Product Community socials and Discord.

Thesis

One of the content pieces suggested by leading Bitcoin Product PMs is interview-style conversations that outline a PMs journey into Bitcoin contribution.

This journey can showcase where they got started, how they navigated the FOSS ecosystem, and provide advice for people looking to do the same. Completely educational.

This content exists to drive people who are interested in contributing to Bitcoin to the BPC social pages, which could then lead them to joining the Discord and converting to a BPC community member.

The thesis driving this proposal is that people absorb audio content that helps them progress in their Bitcoin journey. BPC can be a supplier of niche content around the FOSS space.

Logistics

For this plan to go into action, we would:

• Show format
• Need to schedule 10 initial guests for a season 1 of the series
• Confirm who can host conversations
• Create repeatable preparation documents
• Ensure comms persons can attend conversations
• This is for time stamps, clipping and social media content purposes

Other logistical items would include:

• Confirming if conversation, hosted on Twitter spaces, could be streamed to other mediums
• Determine how we want to scale comms efforts around the show

I recommend that we host 8 of the series’ episodes on Twitter spaces and focus the majority of communications efforts there. We can host 2 episodes on Nostr to experiment with that environment and see if it is worth more attention for a second season. After this season is complete, we can explore using other mediums, like podcast sites.

Description of Proposal

Deadline for Rough Consensus

Notes for the community::

• Please feel free to leave comments on the issue for any questions or concerns.
• Vote with Emojis on the issue proposal.
  • 👍 in support,
  • 👎 not in support

Description of Proposal

Bolt.fun and Fedi is hosting a bitcoin + AI hackathon. This is a great opportunity for people aspiring to be a bitcoin PM to get experience and come out with a project.

We can host weekly meetings for people participating in the hackathon so that we can support each other.

We will need to discuss what a good timezone is but I propose Thursdays at 9:30AM PT. But comment below if you think of a better time slot for you.

Here is a link to the hackathon with more details: https://bolt.fun/tournaments/ai4all/overview

Deadline for Rough Consensus

7/3/23 Short timeline because the hackathon already started. Also their first kickoff call is that day at 8am PT: https://www.youtube.com/watch?v=I9RMay6ZKL8

Notes for the community::

• Please feel free to leave comments on the issue for any questions or concerns.
• Vote with Emojis on the issue proposal.
  • 👍 in support,
  • 👎 not in support

Description

1. Generate list of potential contributors and their skills sets
2. Generate list of FOSS projects and their needs
3. Match skills with needs and provide a “speed-date” type event for FOSS people to

This could tie into another idea we discussed which is to maintain a list of FOSS projects and their needs which people can view and see if we can participate. Kinda like a job board for FOSS projects.

Resources:

N/A

NOTE:
Issue originally submitted by Bitcoin Product Contributor on hellonext

Description of Proposal

Bitcoin Product Community is an open source product community that runs on Discord as of April 2023. This proposal is to migrate from Discord to a FOSS tool in Mattermost. Reasoning is laid below.

As Jeff Booth lays out in The Price of Tomorrow (and in his talks such as BTC Van 4/20/23) the inevitable outcome of the fiat system will tend towards total control on communication. This means that BPC may eventually become pressured, and/or deplatformed. Discord is after all a platform, where imperfect people make decisions.

In contrast to using a platform, one of the most successful FOSS projects in BTCPayServer run by luminaries such as Pavlenex, Rockstar, and Dorier utilize a FOSS communication solution in Mattermost.

A FOSS solution is aligned with the values & principles of the FOSS BTC Product Community (BPC). Mattermost extends access to those who do not want to expose, or those without phone numbers, removes the friction of requiring a phone number, blocking basic privacy protection tools in email forwarders & VPNs. BTCPayServer is proof that a FOSS communication solution scales over thousands of users, and is fit for purpose in accommodating the growing BPC.

Pros of the current setup:
-Discord is well known, and widely distributed
-The BPC community is already using Discord, and it seems to work for most
-There is zero effort in continuing to use the same tool (and there is no additional effort in setting up a new tool)

Cons:
-Discord is not an open source project
-Risk of deplatforming: Discord has investors, and may eventually IPO. This means that Discord is beholden to external interests, and is run by imperfect people.
-Discord discourages user privacy by requiring a phone number, and by not allowing email forwarders, VPNs
-VPN friction breaks discord for some users
-Phone number requirements may dissuade some from joining

Deadline for Rough Consensus

June 1st, 2023

Notes for the community::

• Please feel free to leave comments on the issue for any questions or concerns.
• Vote with Emojis on the issue proposal.
  • 👍 in support,
  • 👎 not in support

Description of Proposal

Hi Bitcoin Product Community (BPC),

I’m writing this proposal to outline a potential communications plan for the next four months. The proposal will cover an opportunity and potential solution for BPC’s social media brands. I will also highlight my background and why I might be a good fit for managing this.

If the BPC community approves of this proposal, I could start working on a communications strategy in the coming weeks.

Opportunity

Bitcoin Product Community does not have a established communications or marketing plan for the calendar year.

Solution

Content Mix

BPC initially creates a standardized communications plan that focuses on a “consistent content mix” for the next 4 months. The reasons for a this are:

• Low lift
• Continuous posts support engagement for the account(s)
• Consistent content, that amplifies BPC work, shows the branded properties are making progress
  • This is key for potential followers when they look at the account for the first time
• Laying a foundation that supports future growth strategies
  • Comms mixes usually contain consistent content that maintain engagement + audience retention, while having other content that focuses on growth
    • I.e. Newsletters are used to maintain engagement, Twitter spaces are used to attract new followers
    • Having the “retention” content mix in place, immediately, can help account stay top of mind for new followers

I mentioned a potential comms mix in the #product-showcase channel’s “Comms Ideas” thread on Discord.

After this 4 month period, the team could shift focus to including growth-centric social media content into this mix.

Amplification

A simple piece, but having someone amplify BPC associated accounts helps align contributors with the brand on social media.

Process

I’ve found that planning out this type of content, and creating templates, reduces the amount of time needed to manage this process. I recommend creating the following:

• Style Guide
  • Creating a style guide template keeps content consistent across the branded accounts
  • An example could be, having a newsletter announcement template that shows how that specific post looks stylistically (punctuation, emoji use, sentence length, etc.)
• Calendar + Post documentation working document
  • Helps comms person manage their week and know when they need to be ready to publish content
  • Depending on workflow, this could let a comms person know what content they need to draft for the week
  • Post documentation shows broader team why certain posts went out (not necessary, but helps provide insight into strategy)

Having both of these processes in place helps BPC comms by 1) reducing time spent planning content 2) enable multiple contributors to manage the brand properties while maintaining a consistent style + message.

I have pre-built templates for all of the items mentioned above.

Time commitment

I believe I could build out all workflows, and managed the processes mentioned above, in 8-10 hours a week. I’d be happy to allocate this amount of time specifically to BPC comms management, and also help onboard new contributors who want to work on this stuff. It’s really fun!

My Background

As mentioned, I’d enjoy working on this for BPC. I’ve posted my background below:

• Managed comms (mainly Twitter), for one year, at an org in a similar industry
  • Grew audience 8%, engagements 9% and engagement per impression 83%
    • Audience was 98k followers
• Experience writing on privacy and cryptography
  • Have been featured in CoinDesk
• Additional experience in startups sales and marketing
  • Namely the founder of an educational non-profit

I’m happy to provide a reference to confirm the information above is truthful.

Outro

If you’ve made it this far, thanks for reading! If you have any questions or feedback around this, please let me know.

-Cli5y

Issue submitted by Matty Cli5y on Hello Next

Deadline for Rough Consensus

Notes for the community::

• Please feel free to leave comments on the issue for any questions or concerns.
• Vote with Emojis on the issue proposal.
  • 👍 in support,
  • 👎 not in support

Description

FOSS projects should list what qualities they’re looking for and can be a central repository.
Contributors should browse and see if the needs of project and if they can assist the project.

One potential format this could take is a job board.

Another one is an extensive list of FOSS projects.

Resources:

N/A

NOTE:
Issue originally submitted by Bitcoin Product Contributor on hellonext