Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proactively publish #196

Closed
m52go opened this issue Jul 23, 2020 · 2 comments
Closed

Proactively publish #196

m52go opened this issue Jul 23, 2020 · 2 comments

Comments

@m52go
Copy link
Contributor

m52go commented Jul 23, 2020

We should make a bigger deal out of all the new software features, advancements, and insights about BIsq in general. We already do this (to an extent) with the cycle reports published monthly, as well as tweets (and lately with the wiki), but there is more we can do.

Such updates used to be done on growth calls, but views on those videos never really increased to a point that they felt worthwhile. People prefer bite-size content in a medium that's easier to share, and growth calls didn't do that well.

I suggest aiming for a frequency of twice per month to begin, although more would be better. For now, just getting started is key. We will figure out what works best as we get moving.

Recent, related events:

  • 2 particular take keen interest in sharing their insights about the ins and outs of USPS money orders
  • twitter feud about bisq listing altcoins (conclusion: bisq will publish blog post to clarify position)
  • users confused or unaware about new bisq features such as improved deposits and account signing (same name)

I've created a project board to organize ideas for publishing ideas, and will keep it updated as new ideas emerge.

For anyone interested in taking on a task on the board, please float the idea in #growth on Keybase or contact me directly.

@m52go
Copy link
Contributor Author

m52go commented Oct 23, 2020

Original publishing since last post:

Many more wiki articles have been created, but the list above only lists those that are meant to cover practical user-facing topics (i.e., no pure reference/documentation items). It's not a fine line, but one way of putting it is these articles are "tweetable" whereas others aren't.

@m52go
Copy link
Contributor Author

m52go commented Nov 26, 2020

Closing in favor of publishing as part of market-driven initiatives like #211.

I personally don't like the idea of blindly writing posts without an underlying goal, which is probably why I never got much done on this.

Can be reopened at some point if someone has another take on this.

@m52go m52go closed this as completed Nov 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant