+1 for (a)
Regards,
Torsten
Andreas Hartmann schrieb:
Hi Lenya devs,
we have to come to a decision about the repository question.
People stated their opinions, it looks like there are two
general directions.
If you think it's too early for a vote, please request cancelling.
Vote:
(a) Lenya should focus on JCR only. It is OK to implement core
functionality which absolutely relies on JCR features.
+1
----
(b) Lenya should support other repository implementations as well,
without implementing custom JCR content repositories.
This means we need a Lenya-specific repository abstraction layer.
----
(c) That should be deferred, let's release 1.4 with the current
repository implementation. I'm aware that this could imply
bigger migration efforts from 1.4 to 1.6.
Some advantages of (a):
- We can leverage the full power of JCR.
- We don't have to care about designing another repo layer (which is quite
complex).
- We don't have to care about compliance between several repo
implementations.
- We don't have to mimic JCR functionality in other repo implementations.
- Testing efforts are reduced. (we don't have automated tests yet, that's
not good but it is the truth and we have to face it)
- Overall: faster, cleaner, simpler.
Some advantages of (b):
- Assuming that the Lenya repo API is not as complex as JCR, it is
easier to implement back-ends (content repositories, e.g. SVN-backed).
- We don't rely on external code.
- Overall: more flexible, more independent.
----
A note about doco etc.:
There will always be the need for other repositories.
But IMO we should differentiate between
- using a repo as a Lenya repository and
- allowing to export / import content to / from a repo
In the case of doco, IIUC there's no need for using the SVN versioning
for CMS versioning, is there? Maybe an (automated) export to an SVN
repository would be sufficient.
-- Andreas
---------------------------------------------------------------------
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]
