Hi,
as brief report of the meeting: some actions are going on (kiwi
triplestore, website, logo and so on), and no new important decisions
have been taken.
Only for today I manually send the chat log (see it attached).
MARMOTTA-15 has been solved with the help of Infra team, so for next
meetings we can use ASFBot features. Further details and documentation at:
http://www.staging.apache.org/dev/asfbot.html#meetings
The next scrum meeting is planned for tomorrow January 18th 10:00 am CET.
Cheers,
On 17/01/13 12:17, Sergio Fernández wrote:
Hi,
for those who would be interested on attend, in about 5 minutes we'll
meet all together at the #apachemarmotta irc channel of freenode.net for
the daily scrum meeting, where we'll briefly discuss the ongoing tasks.
Sorry for the slight time. Next meetings will be at 10.00 am CET.
Cheers,
--
Sergio Fernández
Salzburg Research
+43 662 2288 318
Jakob-Haringer Strasse 5/II
A-5020 Salzburg (Austria)
http://www.salzburgresearch.at
* Now talking on #apachemarmotta
* barjavel.freenode.net sets mode +n #apachemarmotta
* barjavel.freenode.net sets mode +s #apachemarmotta
* Wikier has changed the topic to: Apache Marmotta (incubating)
* wastl ([email protected]) has joined #apachemarmotta
<Wikier> I still use this every day
<Wikier> for the #swig
<Wikier> but now also for the #asfinfra
<wastl> for me it has been some time, but I always liked it, used to be the
main communication for a long time
<wastl> so let's continue here
<wastl> maybe wait for Thomas and Jakob to join at least
<Wikier> probably they are still installing a client
* Wikier gives channel operator status to wastl
<wastl> thx :)
* jakob_srfg ([email protected]) has joined
#apachemarmotta
* tkurz ([email protected]) has joined #apachemarmotta
<Wikier> good
<wastl> ah here you are :)
<wastl> freenode is funny
<Wikier> let's start?
<wastl> Thomas is in London, Jakob and Sergio in Paris, and I am in Bulgaria
<wastl> yes
<wastl> ok
<jakob_srfg> ?
<Wikier> whaqt
<Wikier> (John)
<wastl> type /whois jakob_srfg and you will see
<Wikier> current tasks?
<wastl> ok, but let's start
<Wikier> website is going, just awaiting for infra
<wastl> ok, this is very important, also wrt the EU proposals
<wastl> we need something up there
<wastl> maybe we need to check the logo with branding
<Wikier> right
<Wikier> logo is something to solve, indeed
<wastl> but I would put it and add a Jira issue
<Wikier> do we have a final draft?
<wastl> yes, the one I gave you
<Wikier> cool
<wastl> I can create a tar.gz or ZIP
<Wikier> let's ask the mentos how to proceed
<wastl> and attach it to the issue
<wastl> there is one thing maybe, we need to donate the rights on the Logo to
Apache
<wastl> but this is not so urgent
<Wikier> right
<tkurz> test
<tkurz> okay. should i ask dani for the different formats
<wastl> ok, so I will update the logo issue
<tkurz> so we can donate it
<jakob_srfg> what is the final draft?
<wastl> number 8 I think
<jakob_srfg> is it attached to the jira issue?
<wastl> no, 7
<wastl> 7 is the most recent
<wastl> yes, the PDF is attached
<Wikier> ok, good
<Wikier> what else?
<wastl> but I created different PNG versions already and sent them once to
Sergio
<wastl> what size of the logo would you need for the website?
<Wikier> yes, I'm using it at the web site
http://svn.apache.org/repos/asf/incubator/marmotta/site/trunk/content/resources/img/apache-marmotta.png
<wastl> ok
<tkurz> can you send it to me to use it on the admin page
<wastl> I will attach the ZIP file to the Jira issue
<tkurz> or commit it ;)
<tkurz> okay txs
<tkurz> thx
<Wikier> tkurz, for the code, we'll still use lmf images until v2.4, right?
<jakob_srfg> from jira the logos should then be moved into the repository
<tkurz> yes, but we should prepare a new admin interface and just change the
logos
<tkurz> so we can use the css for both LMF and Marmotta
<Wikier> ok
<wastl> @jakob: yes, they should be moved to the code repository
<wastl> maybe we need another directory in our planning for such things
<jakob_srfg> /doc ?
<wastl> is logo /doc?
<wastl> maybe /style ?
<wastl> no idea yet
<Wikier> +1 for /doc
<tkurz> +1 for /doc
<wastl> another idea would be to give Daniela access to Jira for the logo
<wastl> ok, so /doc :)
<jakob_srfg> and now we need to wait for 72h ;-)
<tkurz> :)
<Wikier> xD
<wastl> ok, but this is proceeding
<wastl> so when do you expect the website to be up?
<wastl> hey, so now all of you wait for 72h or what? :-P
<tkurz> the question was for sergio?
<Wikier> yes
<Wikier> hopefully today
<Wikier> maybe tomorrow
<Wikier> you can check out the current source
<wastl> ok great
<wastl> yes
<Wikier> http://svn.apache.org/repos/asf/incubator/marmotta/site/trunk/
<Wikier> I'm still reading about how the apache cms works
<jakob_srfg> so we are using svn for the webpage now?
<Wikier> it is the single option, yes
<jakob_srfg> and how do we sync it with the code-doc?
<wastl> there is no other way
<Wikier> current tools for the apache sites only support svn
<wastl> even if we use mvn site we have to put the result in SVN for now
<wastl> but deadline for mvn site is 8th February, so not now :)
<Wikier> since it uses maven as build system, probably we can depends on the
source artifacts for that
<Wikier> at least that's my idea
<Wikier> still not sure...
<wastl> another question Sergio, I have the website checked out, what can I do
now?
<wastl> mvn xyz?
<Wikier> good point
<Wikier> there are some tools for working with the cms
<Wikier> https://svn.apache.org/repos/infra/websites/cms
<Wikier> as soon as I get a clear picture, I'll prepare some documentation
<wastl> ok
<wastl> otherwise I have checked it out, albeit I cannot do anything :)
<Wikier> right
<wastl> let's move to the next topic
<Wikier> yes
<wastl> ok
<wastl> so I continue
<wastl> I will work on the KiWi triple store the coming weeks
<Wikier> BTW, I created MARMOTTA-15 to find a way to support these meetings
within the project
<Wikier> yes, that task is quite important
* westei ([email protected]) has joined #apachemarmotta
<wastl> I have updated the API to Sesame 2.7 beta
<Wikier> hi westei
<wastl> which has some significant changes that affect us:
<westei> hi
<wastl> (1) Sesame is now fully transactional and every connection should/needs
to be started with begin()
<wastl> (2) the RDBMS support in Sesame is deprecated, so KiWi might eventually
be the only RDBMS repository available
<wastl> the basic functionality is there (module kiwi-triplestore)
<wastl> it is a triple store working with either H2, MySQL or PostgreSQL
<wastl> the second module that is more or less finished is kiwi-transactions
<wastl> it extends the Sesame SAIL API by support for transaction logging like
in KiWi
<wastl> i.e. it keeps track of added/removed triples
<wastl> I did some work on this today, because I want to make it clean and
proper, in the style the rest of Sesame is designed
<wastl> (it worked before Christmas, but I refactored today)
<wastl> now I started on the kiwi-versioning component
<wastl> difficulty here is to make it as simple as possible and as flexible as
possible to combine with other things
<wastl> I'd like to be able to say
<wastl> Repository r = new SailRepository(new KiWiVersioningStore(new
KiWiTransactionalStore(new KiWiStore(...)));
<wastl> or
<wastl> Repository r = new SailRepository(new KiWiVersioningStore(new
KiWiReasoningStore(...)));
<wastl> or
<wastl> Repository r = new SailRepository(new KiWiReasoningStore(new
KiWiVersioningStore(...)))
<wastl> i.e. stackable in many different ways
<wastl> and this is a bit tricky to achieve :)
<wastl> currently I am trying to find a clean way for modularizing the database
dialect support
<wastl> and I expect I can finish this until tonight
<jakob_srfg> is the separate KiWiTransactionalStore necessary? As I read it,
all Stores should support transactions...
<tkurz> okay. then it is modular in porgramming sense. but what about if we use
osgi. would it be possible to configure on runtime?
<wastl> yes, but transaction support in Sesame does not mean you have a
listener for commit()
<wastl> OSGi: yes, this would then be the task of the service
<tkurz> cool
<wastl> for example, in OSGi I could imagine
<wastl> we have a configuration option saying
<wastl> "create new KiWi backend"
<jakob_srfg> ahh. but then the name is misleading...
<wastl> and there you could have checkboxes "reasoning" "versioning", etc
<wastl> @jakob: this is the Sesame terminology
<wastl> I could rename it to Sail maybe for those parts that are not stores
<Wikier> probably, yes
<jakob_srfg> sounds better, yes
<wastl> ok, so there will be only one KiWiStore
<wastl> and the rest will be called ...Sail
<Wikier> +1
<wastl> KiWiVersioningSail
<jakob_srfg> is is a Repository or a Store?
<wastl> it is a bit more complicated
<wastl> Repository in Sesame is the developer-facing API
<wastl> there can be different backends
<wastl> the generic approach for implementing a repository, however, is the
SAIL approach
<wastl> so you implement the Sail interface
<wastl> and then you create a repository with "new SailRepository(sail)"
<wastl> sails can be either
<wastl> Store
<wastl> (e.g. MemoryStore, NativeStore, KiWiStore)
<wastl> or
<wastl> StackableSails
<wastl> (i.e. wrap other sails and add additional functionality)
* ASFBot ([email protected]) has joined #apachemarmotta
* Humbedooh (~humbedooh@apache/committer/Humbedooh) has joined #apachemarmotta
<wastl> Sesame comes with some StackableSails, e.g. a notifying sail and
inferencing sail
<wastl> ah, welcome ASFBot :)
<Wikier> thx Humbedooh
<wastl> so, back to the KiWi triple store
<Wikier> for this first meeting does not matter, but for the future we'd need
to take this into account:
http://www.staging.apache.org/dev/asfbot.html#meetings
<Wikier> anyway, let's continue
<wastl> goal for today is to solve the database dialect issue cleanly and allow
creating the necessary database tables
<wastl> goal for tomorrow is to finish the versioning module
<wastl> (i.e. API, test, and Sail)
<Wikier> that would require different scripts per dialect, right?
<wastl> yes
<Humbedooh> three things before you start, please :)
<wastl> ok
<Humbedooh> 1) If you need to send a summary to somewhere via email, I'll need
to set that up with karma and such (who gets to send emails via IRC and so on)
<Wikier> ok
<Humbedooh> 2) type: ASFBot: meeting start
<Humbedooh> 3) set mode -t, but you already have that, so never mind :)
<Wikier> good
<wastl> great :)
<Wikier> thx Humbedooh
<Humbedooh> and when meeting is over, type: ASFBot: meeting end
<wastl> and the bot will now remain here?
<Humbedooh> you can use #topic bla bla bla to set a topic in the meeting
<wastl> or do we have to add him somehow
<Humbedooh> yes, it will remain for as long as you want it - but only log when
a meeting is taking place
<wastl> ok, but if we all leave, the bot will be op
<Humbedooh> yes
<Humbedooh> or, no
<Humbedooh> it will just be a regular user all the time iirc
* Wikier gives channel operator status to ASFBot
<Humbedooh> anywho, you'll figure that out - I suggest you read up on how the
bot works if you want a proper meeting summary :)
<wastl> but if the bot is the last remaining user, then a human will not be bot
next time
<Wikier> I'll register the channel, no problem
<wastl> ok
<Humbedooh> let me give you a primer for a minute
<Humbedooh> ASFBot: meeting start
<ASFBot> Record keeping is not enabled for this channel. Please contact
infrastructure.
<Humbedooh> bla bla blabla
<Humbedooh> bah
<Humbedooh> ASFBot: option allowLogging true
<ASFBot> Set option 'allowLogging' to: true
<wastl> quick tutorial :)
<Humbedooh> ASFBot: meeting start
<ASFBot> Meeting started at Thu Jan 17 12:06:13 2013
<ASFBot> Any message starting with [off] is considered off-the-record and will
not be logged.
<Humbedooh> bla bla bla
<Humbedooh> #topic some agenda we have
* ASFBot has changed the topic to: some agenda we have
<Humbedooh> bla bla bla
<Humbedooh> #info let it be resolved that a = b
<Humbedooh> #link http://www.apache.org
<Humbedooh> bla bla
* ChanServ sets mode -s #apachemarmotta
* ChanServ sets mode +t #apachemarmotta
* ChanServ sets mode +c #apachemarmotta
<Humbedooh> #action we must do this before next meeting
<Humbedooh> #topic final thoughts
* ASFBot has changed the topic to: final thoughts
<Humbedooh> blaa bla
<Humbedooh> ASFBot: meeting end
<ASFBot> Meeting ended at Thu Jan 17 12:07:05 2013
* ASFBot has changed the topic to: Apache Marmotta (incubating)
<ASFBot> Minutes available at:
http://comments.apache.org/meetings/apachemarmotta-17_01_2013-4504.html
<Humbedooh> and that's it :)
<wastl> cool :)
<Wikier> cool!
<Humbedooh> oh, one last thing ofc
<tkurz> thx
<Humbedooh> if you need to send a summary somewhere
<Humbedooh> ASFBot: meeting send [email protected]
<ASFBot> Sending meeting summary to [email protected]
<ASFBot> Meeting summary sent!
<ASFBot> Raw summary available at:
http://comments.apache.org/meetings/apachemarmotta-17_01_2013-6338.txt
<Humbedooh> but you'll need to be set up for that
<Wikier> Humbedooh, could go to dev@marmotta?
<Humbedooh> yes, it could
<wastl> doc for the bot?
<Wikier> I'll request it on the jira
<Wikier> wastl, http://www.staging.apache.org/dev/asfbot.html#meetings
<Humbedooh> ASFBot: karma add Wikier 3
<ASFBot> Looking up Wikier...
<ASFBot> Gave karma to Wikier
<Humbedooh> ASFBot: karma add wastl 3
<ASFBot> Looking up wastl...
<ASFBot> Gave karma to wastl
<wastl> :)
<Humbedooh> okay, you can now send meetings to whereever
<wastl> ok, still worried about that op thing though
<wastl> can the bot auto-op us?
<Humbedooh> no
<Humbedooh> you should get chanserv for that
<wastl> ok
<Humbedooh> and please, end a meeting before sending it, or it will send the
previous meeting :)
<Wikier> :-)
<Wikier> ok
<Wikier> thanks so much, Humbedooh!
<wastl> thanks very much
<Humbedooh> np, enjoy
<Humbedooh> bye for now :)
<wastl> bye :)
<Wikier> bye
* Humbedooh (~humbedooh@apache/committer/Humbedooh) has left #apachemarmotta
("Meh")
<wastl> so maybe before we resume the meeting
<jakob_srfg> so now we start all over again?
<wastl> we should register with chanserv
<Wikier> so... let's continue quickly
<Wikier> John wants to go for lunch
<Wikier> xD
<wastl> yes yes
<wastl> but chanserv is important
<Wikier> whatelse is open?
<Wikier> I'm registered, also the channel now
<Wikier> I'l setup the OPs later
<wastl> ok, so maybe we decide on a common password (offline)
<Wikier> no problem, everyone has each own password, and I'll give op to your
users
<wastl> ok
<Wikier> I have to remember how to do it, just that
<Wikier> ok
<Wikier> so, marmotta itself, whatelse?
<wastl> but you registered the channel, or not?
<tkurz> okay. I will restructure the admin interface, templating service and
the property definition in modules
<Wikier> I think so
<wastl> with /chanserv register #channel password description
<Wikier> I'll continue with the website, open bugs and start with LDP-C
<jakob_srfg> I'm stuck with projects. :(
<Wikier> jakob_srfg,
<Wikier> jakob_srfg continues with the scenarios, right
<tkurz> just got an email from a project partner, too ;)
<wastl> (for later: @Wikier, my nickname is already registered, so I will
choose another name)
* wastl is now known as sschaffert
<Wikier> ok
* ChanServ removes channel operator status from sschaffert
* Wikier needs to remember all irc stuff
<Wikier> ok
<Wikier> lunch?
<tkurz> yes
<sschaffert> op me again first please!
* jakob_srfg too
* Wikier gives channel operator status to sschaffert
<sschaffert> thx
* Wikier gives channel operator status to jakob_srfg tkurz
<Wikier> tomorrows meeting will be much more organized
<Wikier> I'll manually send the log later
<sschaffert> yes
<Wikier> thx all!
<sschaffert> don't forget to register your nicknames :)
<Wikier> yes
<jakob_srfg> how?
<sschaffert> to get info
<sschaffert> type /msg NickServ help
<sschaffert> http://www.irc-faq.de/nickname-registrieren.php
<Wikier> later I'll send of those details to the mailing list
<Wikier> good
<Wikier> now lunch
<sschaffert> enjoy :)
