Community meeting about Module Team today at 20.30!

Stefek

Quote from: Martin Hecht on June 25, 2015, 10:18:32 PM
Hi Stefek,

the task of modernizing the modules depends on the release of 2.8.4 which will be the version which is compatible up- and downwards.

Hi Martin. Thanks for keeping me informed.

In my estimation some 2 years ago I already decided that there is no point of really working on modules before 2.8.4. is released.

The odd thing is that the project collapses or stucks any time the release is announced soon to come.  :wink:

Keep up the high hopes and your work, Martin.

Kind regards,
Christian

[i]"Gemeinsam schafft man mehr."[/i]

[b][url=http://duden.de/rechtschreibung/gemeinsam#Bedeutung1]gemeinsam[/url][/b]
1. mehreren Personen oder Dingen in gleicher Weise gehörend, eigen
2. in Gemeinschaft [unternommen, zu bewältigen]; zusammen, miteinander
#Duden

Martin Hecht

Hi Stefek,

the task of modernizing the modules depends on the release of 2.8.4 which will be the version which is compatible up- and downwards. We have collected a list of modules which we should focus on. I think there are not many decisions made - but anyhow, SP4 has been released in the meantime and we are hoping on 2.8.4 to go further down the road with the modules. The core team is working on it, and the original plan was to have a release in the next weeks. However, as you have probably noticed, there was an incident on the production server which requires a lot of effort. Anyhow, this was only one part of the activities. The plan is also, to create a new web-page (unfortunately the attack on the server forced the core team to take down the old web page earlier than planned). Also the documentation shall be updated and replaced by the wiki - that's a field where I'm engaged. Large parts of the documentation for the upcoming 2.8.4 was in German only, and when I find the time I'm translating it step by step to English. Another activity is the plan to upgrade the forum software, which is announced for next weekend. So, there are things happening, even if it isn't very visible at the moment.

best regards,
Martin

Stefek

Just out of curiosity, are you guys making any progress with this promising project?

Kind regards,
Stefek
[i]"Gemeinsam schafft man mehr."[/i]

[b][url=http://duden.de/rechtschreibung/gemeinsam#Bedeutung1]gemeinsam[/url][/b]
1. mehreren Personen oder Dingen in gleicher Weise gehörend, eigen
2. in Gemeinschaft [unternommen, zu bewältigen]; zusammen, miteinander
#Duden

Stefek

+1

agree.

It's refreshing to see some community work in the making.

Thanks for the notes.

Kind regards,
Christian
[i]"Gemeinsam schafft man mehr."[/i]

[b][url=http://duden.de/rechtschreibung/gemeinsam#Bedeutung1]gemeinsam[/url][/b]
1. mehreren Personen oder Dingen in gleicher Weise gehörend, eigen
2. in Gemeinschaft [unternommen, zu bewältigen]; zusammen, miteinander
#Duden

Boudi

Indeed again a constructive second meeting and a huge thnx to Michael and Martin for taking notes and sharing them here for everyone. And off course DV, Luisehahe and Tez for contributing within this meeting.

Regards,

Boudi

...:: Bake the Unbakable ::...

hgs

LG Harald

"Fange nie an, aufzuhören - höre nie auf, anzufangen." Marcus Tullius Cicero (106-43 v.Chr.)

easyuser

#3
Hello alltogether,

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 owner

From 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:
 Input-Process-Output https://www.owasp.org/index.php/PHP_Security_Cheat_Sheet
- get rid of tables and hard-coded css/attributes, focus on
 the frontend.
- 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

easyuser

Hello all together,

here is the agenda for the WebsiteBaker module team meeting:

1.) Opening: Greetings and introduction in the meeting

2.) Module team
2.1) About the team:
2.1.1) What is the goal of the module team?
2.1.2) How should it be structured ("how open")?
2.1.3.) Communication with development team?
2.2) Depending on 2.1: How to form the the module team; in previous community meeting module team should be divided in two segments:
2.2.1.) "Normal Module Team / Maintaining Team"
2.2.2.) "Module API Team": Does it make sense to form an API for 2.8.3 or wait for 2.8.4?
2.3) Which guidelines should be the base of reworking / updating modules?
2.4) Which modules should be reworked / updated and who will do it?

3.) Other matters

4.) Next meeting, Conclusion of the meeting, Summary of to-dos; Saying Goodbye

The last meeting took too long (3 hours), we except this meeting should last 60-90 minutes

easyuser

Hello together,

today we'll have another community meeting - I know, quite soon, but we don't want to wait too long.

It's today at 20.30 MeZ (German summertime, 18.30h UTC +2 ), via Skype.

The agenda will follow, the main agenda is about how to form the Module team and what it should do.

If there are any questions - just post it here.

See you,

Michael