Key Generation, management, knowledge

[amanjeev]

This task has one goal: Make the barrier to join OpenRelay lower

Task is multi-fold:

Documentation

Create neat documentation for this part (keys) of OpenRelay which is currently the toughest part to realize. If the bar is lowered here then a lot of interested folks can easily enter and install this software. This can include:

• What is this thing?
• Why does OpenRelay need this?
• Where to get it from for different OSs?
• How can it be installed?
• Where to get help?

  Ease the debugging of this feature

• I think the current information Unable to sign file error is not sufficient. Still have to see what more can be given as an error/feedback to the user.

What do you all think about this? I know I have not touched OpenRelay in a while and this morning I got the same error as above which made me realize that if I, being a programmer [not matter how clumsy :)], cannot easily debug this thing then the bar should be lowered. [In fact, I have been thinking that usability must be improved in Open Source software altogether].

Please throw in your comments. I know that there are features we need to take care of at this point but if we can improve the usability side of this product, things are more likely to pick up. After a bunch of comments, I will start looking for how to approach this (of course, with your help - looking at you @rosarior :-))

[ghost]

:) Yes the terminology for example is unique to this project so for starters a glossary of terms could help. An introduction about how OpenRelay works and the different elements by themselves would also help would-be developers realize that this is not just a Bittorrent/Freenet/TOR clone and spark further interest.

[amanjeev]

I was thinking of making one of those "Minute videos" about OpenRelay. The "product demo" type, which explain the concept in simple animation. Does someone already have any material? What are your views?