[Sugar-devel] Git Backend Architecture | GSoC'15

[Shaifali Agrawal]

Here <http://wiki.sugarlabs.org/go/Gitbackend> I have listed functional
requirements and put user work flow. Please let me know if any neat is
needed.

Thanks!!!
Shaifali Agrawal
about.me/shaifaliagrawal
  [image: Shaifali Agrawal on about.me]
    <http://about.me/shaifaliagrawal>

On Mon, Mar 23, 2015 at 1:25 PM, James Cameron <quozl at laptop.org> wrote:

> Most if not all of the git size increase is caused by the checked out
> working copy.  That would not happen though.  A backend would use a bare
> repository.  A working copy of an entry would only exist for the duration
> of an activity.
>
> If it did become a problem, it should be possible to turn off this feature
> for systems with limited space, like XO-1.  I don't think the XO-1 is
> sufficient reason to avoid git altogether.  We have XO-4 now.  Sugar must
> move on, and not be held back by an installed base of XO-1.  Let the user
> decide how to use the space available.
>
> If the datastore (which is used to store the journal) were to use the same
> method as it does now for most entries, then there would be no size
> increase.
>
> Then, the user might select an entry in the journal for which a git
> backend is to be used.  Once this is done, a history of changes to this
> entry can be kept.
>
> On the other hand, this all seems premature.  Before the implementation
> details are debated, describe the user work flow.
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20150405/b7c56313/attachment.html>