Another direction

[Daniel Leech]

Hi all,

So, I really want to build a decoupled CMS and I want to invest my time
over the coming months to that purpose (providing I can actually find a
stable place to stay and work!).

As such, the first difficulty was how to do this rapidly in this
organization. As David has already mentioned he and Lukas are currently
further away from the organization and Wouter and I have been working on
the "new" things which I have introduced.

But all progress is painfully slow, even if this slowness often leads to
positive gains in code quality.

As such I have been considering the development of a new organization in
which I can rapidly develop the things that I "need" to create the
decoupled CMS.

The organization itself has the following features:

- One repository per library.
- Documentation contained within the library repository.
- One repository per "driver" (e.g. description-phpcr-odm,
content-type-doctrine-orm).
- Dedicated documentation site (readthedocs).
- Automated meta files via. Ansible (README, LICENSE, .gitignore, etc).
- Starts on PHP7 and Symfony 3.0.

Current components:

- resource-browser (no UI just model).
- description
- description-phpcr-odm
- content-type (I would transfer it from the Symfony CMF)
- meta (org management repository with ansible playbook)

The organization would be driven by the development of an actual CMS (in
a separate org), which may or may not be my experiment with SyCMS[1] but
the overall aim of the actual "new" organization would be to encourage
users to build their own CMS implementations, and the DX would be a
primary consideration.

So it is amazingly similar to the Symfony CMF but at the same time
running on a different track.

It is possible that it would not use any existing Symfony CMF
components other than Routing/Auto[2]. This means that if the new
components were developed in the current organization, it would mean
either branching efforts between this "new" stuff and the "current"
stuff, or deprecating all the "current" stuff[3].

Then there is the fact that I would be able to drive the organization
and take responsibility for it in order to produce the result that I
(we?) want.

As you can see I have already gone a long way down this decision path
and I actually cannot see a way to do what I want to do without this
"branching" of organizations. But maybe there is a way and I cannot see
it, hence this email.

It would not surprise me if if this all falls on its face. Perhaps again
more reason why it should be done in a separate organization as, as has
been mentioned numerous times, this organization does not have the
resources to maintain these things, more so I imagine when they are dead
ducks.

So I am interested in what you think,

Peace,

Dan

[1] https://github.com/sycms (note this is *not* the new org).
[2] And it is conceivable that even RoutingAuto could be replaced by a
more generalized system.
[3] Here I am not indicating that the "current" stuff is bad, but that
it could be handled differently in the new organization.

[David Buchmann]

Hi Dan,

Thank you for this open email. And thanks for all your contributions to
the Symfony CMF so far - I hope you stay in the loop and when there are
things that should go into the base cmf repositories, you still contribute.

I agree with you that the CMF progress is rather slow. This is not
necessarily a bad thing - we have a lot of things to maintain and care
about BC. But I can understand that you want to get a fresh start for
new ideas. I also think the API oriented approach to CMS is different
enough to the approach that we have taken so far to warrant a separate
organization. While the two things are not mutually exclusive by any
means, they can sometimes be competing approaches. Also, if we would
provide alternate solutions for the same problem within the same
organization, we risk confusion.

So i wish you good luck and a lot of fun with this "relaunch" and lets
see where the future leads. Who knows, we might be able to merge the
efforts together again at some point in the future.

cheers,
david

--
Liip AG // Agile Web Development // T +41 43 500 39 80
CH-8005 Zurich // PGP 0xA581808B // www.liip.ch

[Daniel Leech]

On Thu, Sep 15, 2016 at 09:30:02AM +0200, David Buchmann wrote:
> Hi Dan,
>
> Thank you for this open email. And thanks for all your contributions to
> the Symfony CMF so far - I hope you stay in the loop and when there are
> things that should go into the base cmf repositories, you still contribute.

Indeed I will still be here and contributing.

> I agree with you that the CMF progress is rather slow. This is not
> necessarily a bad thing - we have a lot of things to maintain and care
> about BC. But I can understand that you want to get a fresh start for
> new ideas. I also think the API oriented approach to CMS is different
> enough to the approach that we have taken so far to warrant a separate
> organization. While the two things are not mutually exclusive by any
> means, they can sometimes be competing approaches. Also, if we would
> provide alternate solutions for the same problem within the same
> organization, we risk confusion.
>
> So i wish you good luck and a lot of fun with this "relaunch" and lets
> see where the future leads. Who knows, we might be able to merge the
> efforts together again at some point in the future.

Yeah, I certainly don't want the two efforts to be in ignorance of
each-other and if it proves to be a success it would be great if we could
recombine efforts somehow.

> --
> You received this message because you are subscribed to the Google Groups "symfony-cmf-devs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-de...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.