here is conclusion of the meeting:From easyuser:
- Updating modules
- Starting right now, updating modules for 2.8.3 SP4
- Coding standards from http://wiki.WebsiteBaker.org/doku.php/dev/all/psr
; SQL standards
- In 2.8.4 there will be an abstract Module class, in WB 2.9 there will be a new Module API, but the module team waits using them until the WB versions are public
- The module team should write some security guidelines down
- The module team should take care of the IPO model: http://en.wikipedia.org/wiki/IPO_model
- Module upgrades should look more modern, but should be as easy as possible; HTML5 structured format
- Everybody makes a list of his most used modules -> Open forum thread where everybody can take part, the most voted modules will be updated; but not current maintained modules (and if current maintained modules - only after contacting the maintainer / author)
- "Module team members" (member are just participants, not fixed members) right now: easyuser, Martin Hecht, Boudi, Tez ownerFrom Martin Hecht:
- Modul Team: Interface between developers and community
- pick out old modules and bring up-to-date
- API probably later
- collect in the forum old modules and fixes and snippets...
- focus on a few modules, popular ones, the ones *we* use
- In 2.8.4 the modules still running, that run in 2.8.3 and down
- coding standard for modules: http://wiki.WebsiteBaker.org/doku.php/dev/all/psr
- discussion about relation core<->(f)ckeditor:
there will be an abstraction layer (in 2.8.4)
- start changing modules according to standard, later on switch
to the engine
- first bring the modules to 2.8.3 sp4 / 2.8.4 is a good start http://wiki.WebsiteBaker.org/doku.php/dev/all/examples/sql
- there should probably be some standard how the modules
should create the html code for the frondend
- in the future (2.9...) there will be templates for the modules,
a page can have one or more blocks, and a block can have
one or more sections, and a section will not correspond
anymore to one module. It will be a container and modules
are linked to the sections (somehow like the section picker):
more flexible. Modules can be moved between the pages...
- first find a number of modules. Focus on the security.
Take care about best practices. One important thing:
- get rid of tables and hard-coded css/attributes, focus on
- make the backend maybe a little bit look more modern -
with TWIG this will be more flexible in the backend...
- Discussion about media folder and possible alternatives, e.g.
elfinder, supports drag&drop - but current media folder has
good functionality, like uploading zip files