-
Notifications
You must be signed in to change notification settings - Fork 19
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
Peer review and branching model #1
Comments
They all seem good. I am willing to push the code but since you suggested the branching model, I will have to look at it or find another alternative. As for Gerrit, it's a great tool for pull requests, I will make sure this project adopts it. The UI part in the README was an initial one and is just used for quick presentation, it has changed and there will be up to 6 different types of items (each with their own layout) when we list the data. Everything will be Material. Please be aware that this will be a boilerplate for a single endpoint only and will be using up-to-date libraries and good documentation for anyone willing to adopt its structure or help simplify it. I am willing to use the name |
@AdeebNqo added the source code |
I saw that, thanks. I am going to go over it when I get the chance. Please just create a |
created. |
Hello,
I have a few suggestions.
Branching model
The status on the
README
file currently () says:There is currently no code in the master branch. I would to suggest the adoption of a branching model. Specifically,
I suggest the one described int this article
Peer review
Can we also use a peer review system. I suggest gerrit since it allows github sign in.
UI
I do not understand what is going on with the Wireframes on the
README
. Can we please re-do them, and aim usematerial design
The text was updated successfully, but these errors were encountered: