Changes

m
fix camelcase links
Line 13: Line 13:  
* Work hours: about 12h to 00h local time, i.e. 10h to 22h UTC
 
* Work hours: about 12h to 00h local time, i.e. 10h to 22h UTC
 
* Open source projects (with other developers beside me) I participated in: [http://husky.sourceforge.net/ Husky (Fidonet on Linux)] (many years ago, co-founded the project; my profile on that page is rather outdated), [http://www.openstreetmap.org OSM], contributed bug reports and patches to a large number of projects. Try a web search on my name, it's unique (AFAIK at least).
 
* Open source projects (with other developers beside me) I participated in: [http://husky.sourceforge.net/ Husky (Fidonet on Linux)] (many years ago, co-founded the project; my profile on that page is rather outdated), [http://www.openstreetmap.org OSM], contributed bug reports and patches to a large number of projects. Try a web search on my name, it's unique (AFAIK at least).
* Current affiliation with SugarLabs: maintainer of the [[DevelopmentTeam/Buildbot|build infrastructure]]
+
* Current affiliation with SugarLabs: maintainer of the [[Development Team/Buildbot|build infrastructure]]
    
==About my project==
 
==About my project==
   −
* Name of project: Version support for [[DevelopmentTeam/DatastoreRewrite|data store]] / [[Design_Team/Designs/Journal|Journal]]
+
* Name of project: Version support for [[Development Team/DatastoreRewrite|data store]] / [[Design_Team/Designs/Journal|Journal]]
 
* Technologies used: The ones currently in use by the data store / journal. The bonus part might introduce additional ones (e.g. sqlite) for indexing.
 
* Technologies used: The ones currently in use by the data store / journal. The bonus part might introduce additional ones (e.g. sqlite) for indexing.
   Line 34: Line 34:  
[http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines/The_Laptop_Experience#Implicit_Versioning_System was part of] the  
 
[http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines/The_Laptop_Experience#Implicit_Versioning_System was part of] the  
 
[http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines/The_Laptop_Experience#The_Journal original design concept]
 
[http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines/The_Laptop_Experience#The_Journal original design concept]
for the Journal, but [[DevelopmentTeam/DatastoreRewrite#Versioned_entries_.28not_fulfilled_yet.29|hasn't been finished yet]].  
+
for the Journal, but [[Development Team/DatastoreRewrite#Versioned_entries_.28not_fulfilled_yet.29|hasn't been finished yet]].  
    
There are several prototypes ([http://wiki.laptop.org/go/Olpcfs Olpcfs], [http://dev.laptop.org/git/users/cscott/olpcfs2/ olpcfs2])
 
There are several prototypes ([http://wiki.laptop.org/go/Olpcfs Olpcfs], [http://dev.laptop.org/git/users/cscott/olpcfs2/ olpcfs2])
Line 46: Line 46:  
For this reason, I don't believe that any of these prototypes will mature enough to get integrated
 
For this reason, I don't believe that any of these prototypes will mature enough to get integrated
 
in Sugar even mid-term. My project focusses on the version support instead, enhancing the
 
in Sugar even mid-term. My project focusses on the version support instead, enhancing the
[[DevelopmentTeam/DatastoreRewrite|current data store]] instead of replacing it, with the Journal as the only
+
[[Development Team/DatastoreRewrite|current data store]] instead of replacing it, with the Journal as the only
 
intended user of the versioning API (though, at least in theory, regular activities could access it as well).
 
intended user of the versioning API (though, at least in theory, regular activities could access it as well).
   Line 112: Line 112:     
I'm skipping the screenshot of the simple text replacement task for time reasons. I guess being the maintainer of the  
 
I'm skipping the screenshot of the simple text replacement task for time reasons. I guess being the maintainer of the  
[[DevelopmentTeam/Buildbot|build infrastructure]] and having committed several patches on the bugtracker should be  
+
[[Development Team/Buildbot|build infrastructure]] and having committed several patches on the bugtracker should be  
 
sufficient substitute. :)
 
sufficient substitute. :)
  
2,751

edits