Summer of Code/2015/git backend shaifali: Difference between revisions

(One intermediate revision by the same user not shown)

Line 23:

* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

'''Brief Explanation''':

The project is aimed to facilitate versioning, cloning, forking, merging, pull requests from Journal, to the end users. Basically Journal database(sugar-datastore) will be rebuild to be a database based on git, so that the features that are needed to improve(versioning, forking etc) can be achieved easily. All the users who practice/learn development using Sugar(turtle blocks)will get benefit from this. For developing git based backend I have two choices:

Using some API that provide similar functionality like github provide [git data](https://developer.github.com/v3/git/) but this will create dependency of database on the API and will force to develop the database in the way API wants. Also we have to bear certain limitations if API have, like the git API limits the support of blobs up to 100 megabytes in size[https://developer.github.com/v3/git/blobs/], number of requests per hour are limited(60 requests for unauthenticated requests[https://developer.github.com/v3/#rate-limiting]. So it is better to opt option 2.

Line 102:

Line 103:

| Testing, Bug fixing || 13 || 6-13 Aug

|-

| Documenting on sugar wiki - how to fork, merge, look history of Journal and its datastore.

|

Preparing a demo || 14 || 14-20 Aug

# Documenting on sugar wiki - how to fork, merge, look history of Journal and its datastore.

# Preparing a demo

|| 14 || 14-20 Aug

|-

| Final Evaluation || 15 || 21-27 Aug

Line 114:

Line 117:

I already have an experience of similar program - Outreachy(mentioned above) where I worked on a project with running my college in parallel, it was “winter of code” for me. So being committed to the project(and timeline) and working hard for it is what am aware about very well.

I have build a web app in 4 days NGO Locator(mentioned above) for a hackathon. So again committing with time and working hard for project is what I am well aware of.Thus for Sugar Labs also I will able to work without hassle.

I have been working as Python Developer and Analyst at [Development Center](http://iips.edu.in/dc) along with my college studies.

My Interest

I have been working as Python Developer and Analyst at [Development Center](http://iips.edu.in/dc) along with my college studies.

'''My Interest'''

Apart from all these facts the concrete reason for me to work on this project is it is based on "git" which is something that always excites me! I am a big git fan, have mentioned about my curiocity to learn about internals of git in my blog post too [https://shaifaliagrawal.wordpress.com/2015/01/17/two-merge-so-far/] so working on git based project will be lots of fun!

Line 125:

Line 131:

The impact of this project on end users will be great, as mentioned above in application users will get benefit of versioning, forking, merging, cloning from Journal, their learning experience will improve. Since it will recreate the sugar-datastore, it will impact on Sugar developers too.

Walter Bender

'''Walter Bender:'''

I think there are 2 benefits: a technical one and a user-experience one

The technical benefit is that we are able to leverage a well supported, well understood backend that alleviates the need to keep a custom backend supported

The user experience benefit is that we can provide mobility of the datastore; versioning of projects; cloning of projects; etc. all of which means it is easier to collaborate and evolve as a learner.

'''Quozl`'''

'''Quozl`:'''

The impact may be greater collaboration between sugar users who have not collaborated before.

@@ Line 23: / Line 23: @@
 * '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''
 '''Brief Explanation''':
 The project is aimed to facilitate versioning, cloning, forking, merging, pull requests from Journal, to the end users. Basically Journal database(sugar-datastore) will be rebuild to be a database based on git, so that the features that are needed to improve(versioning, forking etc) can be achieved easily. All the users who practice/learn development using Sugar(turtle blocks)will get benefit from this. For developing git based backend I have two choices:
 Using some API that provide similar functionality like github provide [git data](https://developer.github.com/v3/git/) but this will create dependency of database on the API and will force to develop the database in the way API wants. Also we have to bear certain limitations if API have, like the git API limits the support of blobs up to 100 megabytes in size[https://developer.github.com/v3/git/blobs/], number of requests per hour are limited(60 requests for unauthenticated requests[https://developer.github.com/v3/#rate-limiting]. So it is better to opt option 2.
@@ Line 102: / Line 103: @@
 | Testing, Bug fixing || 13 || 6-13 Aug
 |-
-| Documenting on sugar wiki - how to fork, merge, look history of Journal and its datastore.
+|
-Preparing a demo  || 14 || 14-20 Aug
+# Documenting on sugar wiki - how to fork, merge, look history of Journal and its datastore.
+# Preparing a demo
+|| 14 || 14-20 Aug
 |-
 | Final Evaluation || 15 || 21-27 Aug
@@ Line 114: / Line 117: @@
 I already have an experience of similar program - Outreachy(mentioned above) where I worked on a project with running my college in parallel, it was “winter of code” for me. So being committed to the project(and timeline) and working hard for it is what am aware about very well.
 I have build a web app in 4 days NGO Locator(mentioned above) for a hackathon. So again committing with time and working hard for project is what I am well aware of.Thus for Sugar Labs also I will able to work without hassle.
-I have been working as Python Developer and Analyst at [Development Center](http://iips.edu.in/dc) along with my college studies.
-My Interest
+I have been working as Python Developer and Analyst at [Development Center](http://iips.edu.in/dc) along with my college studies.
+'''My Interest'''
 Apart from all these facts the concrete reason for me to work on this project is it is based on "git" which is something that always excites me! I am a big git fan, have mentioned about my curiocity to learn about internals of git in my blog post too [https://shaifaliagrawal.wordpress.com/2015/01/17/two-merge-so-far/] so working on git based project will be lots of fun!
@@ Line 125: / Line 131: @@
 The impact of this project on end users will be great, as mentioned above in application users will get benefit of versioning, forking, merging, cloning from Journal, their learning experience will improve. Since it will recreate the sugar-datastore, it will impact on Sugar developers too.
- Walter Bender
+'''Walter Bender:'''
- I think there are 2 benefits: a technical one and a user-experience one
+I think there are 2 benefits: a technical one and a user-experience one
 The technical benefit is that we are able to leverage a well supported, well understood backend that alleviates the need to keep a custom backend supported
 The user experience benefit is that we can provide mobility of the datastore; versioning of projects; cloning of projects; etc. all of which means it is easier to collaborate and evolve as a learner.
-'''Quozl`'''
+'''Quozl`:'''
 The impact may be greater collaboration between sugar users who have not collaborated before.