On 4 February 2013 20:19, ASF IRC Services <[email protected]> wrote:
> Members present: wikier
>
> ----------------
> Meeting summary:
> ----------------
>
> 1. Preface
>
> 2. versioning
>
> 3. reasoning
>
> 4. stanbol integration
>
> 5. stackable sails
>
> 6. admin ui
>
> 7. ldp
>
> 8. branding
>
> 9. client library
>   a. check the different implementations (wikier, 9)
>
> 10. logo
>
> 11. aob
>
>
> --------
> Actions:
> --------
> - check the different implementations (wikier, 09:43:50)
>
> IRC log follows:
>
>
> # 1. Preface #
> 09:19:44 [wikier]: we are f2f at srfg today
> 09:20:12 [wikier]: we discussed to setup f2f meetings every monday, to 
> discuss the tasks for the current week sprint
> 09:20:27 [wikier]: but I'll write here all important things
>
>
> # 2. versioning #
> 09:21:12 [wikier]: status: implemented
> 09:21:27 [wikier]: awaiting for a proper user interfaces and testing
> 09:21:51 [wikier]: #reasoning
>
>
> # 3. reasoning #
> 09:22:11 [wikier]: hopefully to be ready by this week
>
>
> # 4. stanbol integration  #
> 09:22:36 [wikier]: westei is working on cleanning the bundle list
> 09:22:42 [wikier]: to make i much simpler
> 09:22:49 [wikier]: s/i/it
> 09:23:57 [wikier]: enhancement engines still not released, Fabian is working 
> on it
>
>
> # 5. stackable sails #
> 09:24:51 [wikier]: wastl reports is done
> 09:25:04 [wikier]: which allows to move to different sesame-based backends
> 09:25:27 [wikier]: i.e., virtuoso and so on

The last time I checked Virtuoso implemented the Repository interface
in their sesame adapter, not the Sail interface.

> 09:26:12 [wikier]: for the future, jena wrapper based on this stuff
> 09:31:35 [wikier]: this comes to the discussion about sparql 1.1 
> implementation over relational DBs
> 09:32:12 [wikier]: wastl guests that sesame deprecated that because property 
> paths feature
>
>
> # 6. admin ui #
> 09:34:27 [wikier]: thomas reports is done
>
>
> # 7. ldp #
> 09:36:42 [wikier]: ongoing work...
> 09:37:57 [wikier]: today w3c weekly telco
> 09:41:19 [wikier]: makes sense to suggest to the wg to invite Roy Fielding as 
> expert?
>
>
> # 8. branding #
> 09:41:49 [wikier]: website still awaiting for infra...
> 09:41:57 [wikier]: wiki online
>
>
> # 9. client library #
> 09:43:50 [wikier]: #action check the different implementations
> 09:45:19 [wikier]: Mihai explains his façading mechanism, to be contributed 
> to Marmotta
>
>
> # 10. logo #
> 09:45:42 [wikier]: sizes?
> 09:47:14 [wikier]: marmotta-5
> 09:48:04 [wikier]: so, icon:
> 09:52:21 [wikier]: icon (without text), both colored and monochrome: 16x16 
> (favicon), 32x32, 64x64, 128x128
> 09:54:12 [wikier]: normal logo as svg and xcf/psd
> 09:57:34 [wikier]: buttons with, with text, with "power by" 128x48 with 
> different color schemes, transparent and monochrome
> 09:57:44 [wikier]: drupal is a good example: 
> http://drupal.org/drupal-media-kit
> 09:58:34 [wikier]: web colors and print colors
> 09:59:21 [wikier]: I'll ad all this stuff to marmotta-5
> 10:05:49 [wikier]: wastl actually will add those requirements
>
>
> # 11. aob #
> 10:07:06 [wikier]: aob?
> 10:07:50 [wikier]: jira workflow: we all agree
> 10:09:04 [wikier]: sling is a good example, as Nandana commented
> 10:11:12 [wikier]: releases: all components will keep same version, even if a 
> component has not single change
> 10:11:42 [wikier]: many we don't like the way done in osgi projects (sling, 
> stanbol and so on)
> 10:17:27 [wikier]: let's await to get complex scenarios where a more complex 
> lifecycle would be required
>

Reply via email to