-
Notifications
You must be signed in to change notification settings - Fork 6
RFC: peer-star vs. peer-base #56
Comments
@pgte are you considering these names in a marketing sense, as in "I'm building my app on peer-base" or in terms of a github structure, as in "the code is at https://github.com/peer-base/peer-chess"? Before I knew what peer-star was I had some trouble finding it, because when referring to the projects in a marketing sense, some people would write peer-* and some would write peer-star. So then when searching for the projects on github I wasn't sure what to search for. |
@dirkmc so far the marketing plans on a nutshell are:
@dirkmc thoughts on this? |
Ah I see, that makes sense, I think peer-base is a clearer name for newcomers 👍 My point of confusion is |
I agree with building the branding around "peer-base" ... if people only learn one word, it should be that. Internally, we can still use "peer-*" when we need a glob for conversation. :-) |
Now that we've migrated peer-star-app into peer-base, we need to understand what to make of peer-star.
Here is the way that I see this:
peer-base is a library
Peer-base is a library that helps you create DApps on top of IPFS. It will contain a main library (peer-base) and can contain libraries that peer-base depend on (like peer-base-discovery, for instance).
peer-star are DApp blueprints
"peer-star" stands for "peer-*" (peer-pad, peer-chess, etc.) and depends on peer-base.
Peer-star is where the blueprints for how to build DApps live. This should be the place for peer-pad, Discussify, the peer-base to-do list, etc.
Please tell me your thoughts on this.
The text was updated successfully, but these errors were encountered: