General Community > Off-Topic
Unofficial WebsiteBaker community & developer meeting
Tez Oner:
Eey,
it was nice and good to have a meeting like this and the German / English went well right ;)
Cheerz,
Tez Oner
crnogorac081:
thumbs up ! These are good news !
I am inpatient to read the report.
I would also add a feature to remove phisical php pages as it is deprecated in current modern development. I already have some medium size projects with 0 access pages in FE.
Martin Hecht:
Hi,
I agree, it was a nice and constructive discussion. I maintain/contribute to a few modules and use some which have not received an update for a long time.
Once the direction is clear, I'm willing to contribute to the effort to modernize the modules. The "direction" may be defined by guidelines (e.g. no tables in the frontend ;-) ) and maybe one or some templates which can be used as a starting point. But I don't want to anticipate to the process for which the meeting of yesterday was just the kickoff.
Stefek:
--- Quote from: crnogorac081 on April 24, 2015, 10:01:04 PM ---thumbs up ! These are good news !
I am inpatient to read the report.
--- End quote ---
Yes, agree. Would also like to see some kind of report.
--- Quote from: Martin Hecht on April 24, 2015, 10:03:20 PM ---
But I don't want to anticipate to the process for which the meeting of yesterday was just the kickoff.
--- End quote ---
It's not easy for me to follow you (maybe because I didn't take part in the meeting). Would you elaborate on that a little bit, Martin?
--- Quote from: easyuser on April 23, 2015, 08:17:56 PM ---4.5) Building teams / working at the project; Crazy idea: Splitting WB core development in two teams for 2.8.x and and 2.9.x?
--- End quote ---
Yes Michael, this sounds radical, but when nothing happens again, what should be the consequences? After all this is a community project. Isn't it?
In a nutshell, what crazy means is: "Doing the same thing over and over again and expecting a different result" (Albert Einstein). :wink:
It was nice to see how many people took part in the meeting. Carry on.
I'll be back with a new module once the 2.8.4. is released to the public (hopefully soon).
Kind regards,
Stefek
Martin Hecht:
Hi Stefek,
--- Quote from: Stefek on April 25, 2015, 09:30:31 AM ---
--- Quote from: Martin Hecht on April 24, 2015, 10:03:20 PM ---
But I don't want to anticipate to the process for which the meeting of yesterday was just the kickoff.
--- End quote ---
It's not easy for me to follow you (maybe because I didn't take part in the meeting). Would you elaborate on that a little bit, Martin?
--- End quote ---
I'm referring to item 2 on the agenda. I didn't take notes during the meeting, so I can just write a summary what I remember (I believe someone took some notes and wanted to distribute them).
So, just to elaborate on this point: We agreed that there are many modules, some of them are unfortunately not maintained any more. Ruud manages the Add-ons repository and he uploads modules which are tested. Some others got stuck during the development and were never finished and/or are written in an old style with hard-coded css formatting or tables which cause trouble with modern div-based templates. The Core Development team has not the time to put much effort into maintaining/modernizing modules nor for coordinating this work.
However, for web designers the templates and modules are as important as the core itself, so we agreed that there should also be a modules development team. (actually, the idea is not new. I believe Manuela has announced such a plan mentioning you as one of the coordinators already some time ago). Another task which came up for the module development was that there should some kind of API or functions which the modules can call, some set of default variables and some kind of guidelines how modules should be written so that it fits well together with any template. Once, there is such an API, or however you would call it, we can take old modules and simplify them. One example is that many modules come with their own upload mechanism - and if there was a framework which provides ready-to use dialogs for such standard tasks, one can replace the module's own mechanism by this framework, which is then maintained (e.g. receives security patches in a central place).
All in all, there are a lot of ideas and there is a lot of work - enough for two teams: one for developing an API and another team which looks for modules, updates and maintains them (probably not all of them if there are many different modules for the same task e.g. many image galleries...). And after talking quite a long time about modules, templates and other ideas, we decided that the next Skype call should be dedicated to the module development and we should proceed in the agenda.
Martin
Disclaimer: I didn't take notes during the call... so forgive me if I remember something not correctly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version