<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi, conferences without an invitation to the list beforehand and an announcement to join are not in the spirit of cooperation. good that you talk, though ;-) next time, please invite everyone beforehand for the possibility to join. it makes stuff easier decision for trac: was discussed as best alternative to non-user-friendly bugzilla on freedesktop, see for example here and the thread around it: <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/archives/xesam/2009-June/000469.html">http://lists.freedesktop.org/archives/xesam/2009-June/000469.html</a> in the same thread: we use SVN now because it works and integrates with trac, we want to use git later. Branches/Trunk: I agree to: development on trunk and have 'stable' branches. (because we do it like this everywhere else) bugtracking: trac. about the rest (responsibilities, etc) please read the wiki before discussing things, it helps: <a class="moz-txt-link-freetext" href="https://sourceforge.net/apps/trac/oscaf/wiki/OntologyMaintenance">https://sourceforge.net/apps/trac/oscaf/wiki/OntologyMaintenance</a> this is the wiki page where everything is documented, if not, change it, its got a history. changes should, if critical, be announced on this list beforehand. keeping the wiki up-to-date helps keeping previous discussions remembered, so any decision on SVN layout must go into the wiki... best Leo It was Antoni Mylka who said at the right time 23.07.2009 18:39 the following words: <blockquote cite="mid:4A689252.6090805@gmail.com" type="cite"> <pre wrap="">Philip Van Hoof pisze: </pre> <blockquote type="cite"> <pre wrap="">We had a conference where we discussed several things. I was just checking the current status. We was me, Jürg, Sebastian Trüg, Rob Taylor, Ivan Frade (if I missed somebody, let me know. Not sure if Jos Vandenoever also discussed ontology with us). What I noticed so far: - Apparently has a project called OSCAF been setup on sourceforce. <a class="moz-txt-link-freetext" href="http://sourceforge.net/projects/oscaf/">http://sourceforge.net/projects/oscaf/</a> - Although I had the impression that at the conference most people where reluctant to opt for trac, trac is nevertheless being installed as the ticket system. I don't know how 'okay' this is for all people. My impression at least was that this isn't ok. </pre> </blockquote> <pre wrap=""> Well, it's there, it works, and people have already migrated most of the open issues from the old NEPOMUK trac, so I guess there is little use to drop it all now. </pre> <blockquote type="cite"> <pre wrap="">- I also had the impression that most people would prefer git, nonetheless is SVN being installed as repository. This is probably not a very big issue, just pointing out. </pre> </blockquote> <pre wrap=""> The SF trac doesn't have git integration (yet), so choosing git would rob us of the cool timeline, the source browser, and the ability to link to sources from wiki and ticket comments. </pre> <blockquote type="cite"> <pre wrap="">- Sebastian has starting implementing the layout changes that we discussed at the conference. This is nice, thanks! Important items that we need: o. Formal decisions on branch management. Apparently is Evgeny's opinion (discussion on IRC) that trunk should be stable, and that development happens in branches. Sebastian Trüg's (and my opinion, too) appears to be that trunk is development and we'll have stable version branches. I conclude that there's no conclusion on this, and that we should soon make a decision. This will of course matter for the projects depending on the shared ontology project. </pre> </blockquote> <pre wrap=""> Indeed. I would also rather do the development on trunk and have 'stable' branches. </pre> <blockquote type="cite"> <pre wrap="">o. A decision on the bugtracking system (this is urgent) </pre> </blockquote> <pre wrap=""> Once again, the trac is as good as any. </pre> <blockquote type="cite"> <pre wrap="">o. A product in that bugtracking system </pre> </blockquote> <pre wrap=""> That trac instance is dedicated solely to the shared ontologies, no need to have any separate products. </pre> <blockquote type="cite"> <pre wrap="">o. A component for each ontology on that product o. Each component will have a default assignee o. Some of the developers will be put in CC for all ontologies o. Patches containing Tracker's initial ontology-change requests. We have quite a few change requests already, indeed. </pre> </blockquote> <pre wrap=""> currently it looks like this: New Ontology Draft trueg ontology-nao SimonScerri ontology-nfo trueg ontology-nie leo_sauermann ontology-nmm konttori ontology-nrl simonscerri ontology-pimo leo_sauermann The list of who volunteered for what is here: <a class="moz-txt-link-freetext" href="https://sourceforge.net/apps/trac/oscaf/wiki/OntologyMaintenance">https://sourceforge.net/apps/trac/oscaf/wiki/OntologyMaintenance</a> </pre> <blockquote type="cite"> <pre wrap="">o. Structural decisions on who will maintain what </pre> </blockquote> <pre wrap=""> See above, this can change whenever there is need to. For instance, Simon Scerri (the original NAO maintainer from DERI/Ireland) hasn't confirmed his wish to be further involved. </pre> <blockquote type="cite"> <pre wrap="">o. The layout changes (but Sebastian already started this, awesome!) o. Build environment ( remember autotools being mentioned) </pre> </blockquote> <pre wrap=""> Sebastian started writing some scripts, and there is a basic doc generator and valiator from Ivan. There is some resistance against expanding on the java-based tools from nepomuk. For java projects I'd imagine a packaging system similar to the aperture-vocabulary package <a class="moz-txt-link-freetext" href="https://aperture.svn.sf.net/svnroot/aperture/aperture/trunk/core/vocabulary/core/">https://aperture.svn.sf.net/svnroot/aperture/aperture/trunk/core/vocabulary/core/</a> Though I must admit I know very little about c/c++ and I don't know what are the requirements for ontology packaing. This has probably been agreed on at GCDS. (minutes anyone????). If it's really necessary to have a java-free build environment for everyone, i'd probably hack the java packaging outside the main tree, so that the c/c++ community won't have to do anything with it. </pre> <blockquote type="cite"> <pre wrap=""> o. The TriG files and the directory layout for them </pre> </blockquote> <pre wrap=""> Already there. </pre> <blockquote type="cite"> <pre wrap=""> o. A file describing the dependency tree of the ontologies o. Documentation about custom ontology install procedure o. Tools for generating documentation (part of the build environment) </pre> </blockquote> <pre wrap=""> Right now there are two. The java one used in nepomuk, showcased at <a class="moz-txt-link-abbreviated" href="http://www.semanticdesktop.org/ontologies">www.semanticdesktop.org/ontologies</a>, and one developed by Ivan. </pre> <blockquote type="cite"> <pre wrap="">I noticed some confusion on who is doing what, how what is being done and where it is being done. Therefor I think it would be useful if people would (more clearly) point such things out on this mailing list, and use it more often to articulate decisions made at conference meetings (as these days they are happening, at a high frequency). </pre> </blockquote> <pre wrap=""> As for the discussions I couldn't agree more. Is there anything that was agreed on at GCDS that hasn't been mentioned in Sebastian's blog post? <a class="moz-txt-link-freetext" href="http://trueg.wordpress.com/2009/07/13/gran-canaria-desktop-summit-2009-the-nepomuk-perspective/">http://trueg.wordpress.com/2009/07/13/gran-canaria-desktop-summit-2009-the-nepomuk-perspective/</a> For instance, what exactly has been decided on the ontology packaging? Antoni Mylka <a class="moz-txt-link-abbreviated" href="mailto:antoni.mylka@gmail.com">antoni.mylka@gmail.com</a> _______________________________________________ Xesam mailing list <a class="moz-txt-link-abbreviated" href="mailto:Xesam@lists.freedesktop.org">Xesam@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/xesam">http://lists.freedesktop.org/mailman/listinfo/xesam</a> </pre> </blockquote> <pre class="moz-signature" cols="72">-- _____________________________________________________ Dr. Leo Sauermann <a class="moz-txt-link-freetext" href="http://www.dfki.de/~sauermann">http://www.dfki.de/~sauermann</a> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz DFKI GmbH Trippstadter Strasse 122 P.O. Box 2080 Fon: +43 6991 gnowsis D-67663 Kaiserslautern Fax: +49 631 20575-102 Germany Mail: <a class="moz-txt-link-abbreviated" href="mailto:leo.sauermann@dfki.de">leo.sauermann@dfki.de</a> Geschaeftsfuehrung: Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 _____________________________________________________ </pre> </body> </html>