ref: Refactor the main branch to be a basic documentation #151
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request has conflicts ☹ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
With the new branch-out movement that we're doing (creation of v0.0.x and v0.1.x), the
mainbranch doesn't have much use. Bearing this in mind, we though of making it just a basic documentation with a pointer to a more complete documentation that lays on the proper branch that one might be interested in.This new readme will only have documentation on plugin build and development, and also explain that correspondence between SDK version and BBB-core version.
Motivation
Just give some use to this branch
mainMore
We're open to discussions, since this is a big change, contribute down bellow.
One other thing: there is one last PR targeting this branch
main(this PR), I am going to left this PR as a draft only until that one is merged, and after that, we shall mergemainin bothv0.0.xandv0.1.x, then, we will proceed with separate strategies for each one.