Difference between revisions of "Gitbackend"
Jump to navigation
Jump to search
Line 26: | Line 26: | ||
=== '''Steps to move on this project:''' === | === '''Steps to move on this project:''' === | ||
1. Code to use git as datastore | 1. Code to use git as datastore | ||
− | Datastore should provide "CRUD" functionality. | + | Datastore should provide "CRUD" functionality of program for git backend along with special features as mentioned in functional requirements. |
2. Desigin UI | 2. Desigin UI | ||
UI should allow user to perform following activies in database: | UI should allow user to perform following activies in database: | ||
* fork | * fork | ||
* clone | * clone | ||
+ | * start new program versioning | ||
+ | * see history of program | ||
* pull request | * pull request | ||
* merge | * merge | ||
− | * | + | * add new content to the versioned program |
+ | * look at difference between current state of program and versioned state of program | ||
+ | * create branche |
Revision as of 10:54, 5 April 2015
Git Backend
Overview
The project is aimed to develop a git based backend for Sugar Journal.
Functional Requirements
Users(kids) should be able to:
- Register a unique username
- Login with his/her unique username
- Start versioning their program
- Look at history of their program
- Clone others and their programs
- Save new content to versioned programs
- Look at difference between current state of program and versioned state
- Create different branches
- Merge branches
- Fork others program
- Make pull request to others program
User Work Flow
User work flow image is present at https://drive.google.com/file/d/0B-LVD_AaEDFjakw3VjExU2ZhYnM/view?usp=sharing
The dia file of above work flow is present here.
Steps to move on this project:
1. Code to use git as datastore
Datastore should provide "CRUD" functionality of program for git backend along with special features as mentioned in functional requirements.
2. Desigin UI
UI should allow user to perform following activies in database: * fork * clone * start new program versioning * see history of program * pull request * merge * add new content to the versioned program * look at difference between current state of program and versioned state of program * create branche