The future of the cod

[may17]

Dear cod folks,

Seems like there are some people who will work on a cod v2 and i will stop investigating any work on the cod. Time to talk about the future of the project and involve everyone who's intrested.

Organization
I will stop any work on this project in 2022. This means we need a new project lead. How about you @sascha-mueller, would be still part of the cod team?

Current Maintaining
Currently only @cliffparnitzky is an active maintainer. @cliffparnitzky am i right that you only like to maintain and won't bei part of the creation of a new demo?

Anyone else please comment here If you like to be part of the team and being ntrested to work on a new CoD version.

Todos:

• Find new project lead / leads
• clarify if @sascha-mueller will stay in the project
• clarify the future role of @cliffparnitzky in the project
• Add new members to the GitHub repo and kick ex members.

[sascha-mueller]

@may17 As far as foreseeable I will stay in the project. In a future version I would see myself responsible for the SCSS again.

[fkaminski]

I will follow the further development (v2) in the future. Should I then be able to contribute something (not as maintainer) I will try to do so with pleasure.

[fkaminski]

First of all, I would like to thank Joe for his work so far.
As mentioned, there should be a leader here who can make final decisions.
Otherwise, one will surely hang unnecessarily on various issues.

Optimally, this person should be familiar with GitHub in terms of maintenance/merging, etc..
Would @cliffparnitzky continue to fill this role?

[fkaminski]

Furthermore, the next step should be to first agree on basic questions regarding v2
and then respond accordingly.

I had tried, from my point of view, to put these up for discussion in #103.
This is primarily about:

• How to maintain most effectively (regarding Contao version/installation).
• This depends on: Fundamental task of COD
• Together then appropriate implementations (content/layout).

Maybe it would be better to split them into separate issues?

[fkaminski]

@sascha-mueller Bist du über Slack erreichbar?

[may17]

Any news @fkaminski @sascha-mueller ?

[sascha-mueller]

@may17
Cliff has not yet commented. Franko is out for now, because he is busy with other projects for Contao.
Franko and I decided to leave the content as it is and only change the layout.
Currently no one has been found for the creation of a design. Therefore it is a consideration to orientate on the current camp page.

[fkaminski]

Therefore it is a consideration to orientate on the current camp page.

As discussed on Slack, I think a layout implementation based on the current camp layout (https://2022.camp.contao.org/) is good, as long as no one else presents a different layout concept.

[may17]

You reconized that the camp page is based on a theme from Contao-Themes.net? So creating a copy of an existing theme is maybe not a good approach for an official demo?

[sascha-mueller]

@may17 Yes, I know that it is a theme. It's also not about copying, but just a general inspiration.

Currently I'm also talking with my employer to see what he wants to contribute to the theme.

[fkaminski]

So creating a copy of an existing theme is maybe not a good approach for an official demo?

As Sascha mentioned it was intended more as a layout inspiration in this regard.

[may17]

Ok thats up to you. As mentioned in the issue i will not be longer responsible for the CoD. I started an internal discussion on the slack now to figure out how to move on cause there was no clear response who will take the project lead in future.

[Tastaturberuf]

yesterday i was thinking about the demo when it came to test the 4.13. i think the demo is too complicated to install and maintain. i would like to test the possibilities of https://github.com/richardhj/contao-theme-framework and maybe we will find a new solution here. @richardhj can you see any chance we can use your framework for easier maintain the demo?

[richardhj]

The charm of the Theme Framework is that it standardizes themes, in the sense of where you find the templates, CSS files, etc. pp., and that it comes with Encore that IMHO will be the new standard since it comes from the Symfony Ecosystem.

The framework is a CAN but not a MUST for the Contao demo.
To be honest, I would wait for any progress in contao/contao#2781 before making a decision. Also, to have the best forward compatibility.

However, the Contao demo is highly dependent on the database. I don't know what an official strategy might look like, but using the official database commands from contao/contao#3631 for the Contao demo would be a great benefit already.

[fkaminski]

@richardhj :-)
But: First things first.
I would favor it if we first internally agree on a layout (for the purpose of representative representation) that @sascha-mueller could implement.
Subsequently, then accompanied by possible further deployment options...

[may17]

Could we please stay focused on the main concerns of this issue please ;)

[sascha-mueller]

To finally move Joe's cause forward:
If no one wants, I will take over the further organization of the COD for the time being. However, help is welcome.
Cliff remains in the team and primarily takes care of the change from one version to the next.

[may17]

Nice to read about your decision @sascha-mueller :) @leofeyer could you please add @sascha-mueller to the team? I already removed myself. I also created a pull request to update the README.md.