as far as I understand your code is at the moment completely separated from the Slide project.
IMO it would be a good idea to integrate the jcrri into the Slide project as this would give you some more feedback on your work. There are lots of people out there using Slide.
As we plan to introduce a completely new api in the Slide 3.0 release, it might of interest to see if the jsr-170 api would be a choice. Have a look at this thread:
http://www.mail-archive.com/slide-dev%40jakarta.apache.org/msg10230.html
So, to see if the 170-api suits our needs it would be great to have an implementation that talks to the Slide server via WebDAV using the webdavclient library. The upcoming Slide 2.1 release has some nice new features as remote long term transactions and notifications, that are also available via the client lib.
Regards,
Daniel
Stefan Guggisberg schrieb:
dear colleagues
i followed the poll regarding removal of @author tags in the slide source code with great interest. i didn't cast my vote though for 2 reasons:
- i didn't want to interfere because i do not work on the slide code base.
- as committer of the code in proposals/jcrri i consider myself a guest in the slide community as i am not (yet)
actively involved in the development of slide.
i agree that removing the @author tags makes sense for code that a lot of people have been working on, that is
evolving over a longer period of time, where the author(s) can not be identified properly or where the individual contributions are not apparent.
but i wasn't aware though that @author tags would also be removed from the JCR Reference Implementation (proposals/jcrri):
1. the future/role of this proposal within slide is still
unclear and has to be decided upon by the community. the JCR RI is currently not an official part of the slide
project. 2. i am currently the sole committer working on this proposal.
3. the initial idea/hope was that a community would evolve
around this proposal. this was unfortunately not realistic, as the reference implementation is trying to implement an api that is still quite volatile and that (current version) is not publicly disclosed yet. the current code itself is subject to major changes. things will change hopefully when the final proposal draft is available.
4. the jcrri proposal is currently attracting a lot of interest
from people from outside of the slide community. i am taking
the full responsibility for this code: bugs, bad coding style
and/or design, other shortcomings... i am the one to blame as i am the author of this code and i should be identifiable
as such.
the reasons for removing the @author tags were:
<quoting_oliver>
- author tags hardly and rarely indicate the person to talk to.
- the whole community is in charge of code, not just the person(s) indicated by author tags
</quoting_oliver>
those clearly do not apply for the jcrri proposal (at least not for the time being).
i therefore kindly ask for undoing the @author tag removal in proposals/jcrri for the above stated reasons.
should the jcr ri become official part of slide sometime (in whatever form ever) and should a community develop around this code base i would gladly remove all @author tags.
cheers stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
