Proposal: LBRY Protocol

Do you have any tips on how we can improve the questions for the LBRY Protocol?

I know we should be objective and specific, but are there some methods which will really draw the attention of the viewer?

Thank you for all answers!

up vote 5 down vote accepted

Yes, I think I can help you (and anybody trying to start a healthy proposal) identify where these early efforts often get off to a poor start.

A proposal is not an introduction to the subject

A proposal is a pitch to show (hopefully) that there is an avid, engaged community with a definite need for a site about their subject. A proposal should demonstrate a community's best examples to show how they intend to intrigue like-minded colleagues to use this site every day.

If a proposal becomes an introduction to the material, or a collection of questions one might answer simply by reading through a pamphlet-sized document on the subject, this site simply is not going to be interesting and sustainable long term.

Stack Exchange hosts detailed problem statements with practical solutions

Stack Exchange works really well for helping users with very detailed, technical support-style problems which can be definitely resolved in the space of a post. But all too often when folks are asked to post the questions they would like to ask on this site, folks will instead create an introduction to the subject.

A proposal should (predominantly) appeal to a community actually working in this space. If you have a lot of curiosity-seekers looking for an introduction to the subject (or someone evangelizing some sort of educational outreach on their behalf), the proposal starts to look something like this:

  • What is {subject}?
  • Where can I learn more about {subject}?
  • What is the difference between {subject} and {competitor}?
  • Where can I find the documentation?
  • What does this {basic terminology} mean?
  • How do you do {rudimentary task 1}
  • How do you do {rudimentary task 2}
  • How do you do {rudimentary task 3}, etc…

Now go back and see how many questions similar to these⤴ are in your proposal. And how many of them attracted broad support (up-votes) as "top example questions"? Unfortunately, these bike-shed examples are NOT making a strong case for actually creating this site.

Folks will sometimes translate this expert advice into an all out moratorium against asking "simple or beginner questions"; but that is not correct. Beginner questions are certainly welcome on the actual site, but this site is not being designed or targeted (← read those words again) at folks not already familiar with this subject.

A proposal is the blueprint to justify creating a site for your community. Make those questions count.

Here is a practical example

If you were proposing a site for a professional plumbers' association (for example), you wouldn't expect to see a lot of questions like "How do I become a plumber?" "How many plumbers are there?" "How do I unclog a drain?" Instead you hope to see questions like, "If you run 2.5 GPM through 50 feet of 1/2" galv pipe, how many psi will be lost to friction loss?"

See the difference?

Also, keep in mind that the Stack Exchange Q&A engine is designed to host practical, detailed questions which can be answered definitively in the space of a post. Questions which would likely need broad, open-ended discussion or debate are better suited to a threaded discussion forum which is not supported in our Q&A format.

  • Thank you so much for your extensive answer! This REALLY helps! – Rouse Jun 2 at 10:17

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .