Hi Evgeny<br><br><div class="gmail_quote">On Sat, Jun 6, 2009 at 11:55 PM, Evgeny Egorochkin <span dir="ltr"><<a href="mailto:phreedom.stdin@gmail.com">phreedom.stdin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 6 ÉÀÎÑ 2009 23:52:24 Ivan Frade wrote:<br>
> > > Herewith I'd like to volunteer to assist in maintaining the NFO. Over<br>
> > > the last three years I have been working on a project that focuses on<br>
> > > efficient attribute based file management for storage abstraction in<br>
> > > Semantic Desktops. The results of this project will be published in<br>
> > > October this year and I'd like to propose the developed Ontology for<br>
> > > integration into NEPOMUK.<br>
><br>
> Sounds great. Something we can know in advance? Is it a deep modification<br>
> of NFO? extensions? I want to propose some (minor) modifications in NFO and<br>
> have some extensions, so i am really curious about your changes.<br>
<br>
</div>I'd like to clarify that it's not necessary to be a maintainer of an ontology<br>
to propose changes ;)<br>
</blockquote><div><br>Yes, of course.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Moreover I think it would make sense to introduce a "no ticket - šno commit"<br>
policy. That is, all but trivial changes should first be first discussed in<br>
the issue tracker and even if the changes are good and wanted there must be a<br>
decision making documentation somewhere and the best place for this is the<br>
issue tracker.<br>
</blockquote></div><br>Agree, and we can use the usual format of the Changelog in the git commits:<br>Fixes #1111111. Add property X to class Y for Z.<br>It works really nice for us in tracker.<br><br>Regards,<br><br>Ivan<br>
<br>