Forming Module team - Who wants to participate?

[DarkViper]

don't worry Ruud.... Tez and others are talking about orphaned modules only. not about these still being in active maintenance.

manuela

[Ruud]

for the MOD modules it's maybe an idea to add an Git Rep
for every module. So other can also contribute.

In my opinion this can only be done for mod's that are no longer actively maintained by their original author.
I would not like my work to end up in some public repo when I am still maintaining them.

[Tez Oner]

Eeey,

for the MOD modules it's maybe an idea to add an Git Rep
for every module. So other can also contribute.

Cheerz,

Tez Oner

[Stefek]

Is there a place where we can make suggestions for "module standards"?
A thread or Sub-Forum?

I have one, two simple suggestions that are useful (in connection to the old, non-oop based modules).

Kind regards,
Stefek

[Boudi]

Where should we put the new finished mods down? I prefer one central topic for that.

I got my first small contribution: http://forum.websitebaker.org/index.php/topic,1733.msg197761.html#msg197761

I upgraded the Bookmarks mod.

[Martin Hecht]

for the modules I'm already maintaining, yes, I'll update them according to the new standards and use the API once it is there...

[easyuser]

Hello all together,

as discussed and decided in the community meeting last week, WebsiteBaker wants to form a module team.

- The module team is independent from the development team, but the team leader stands in contact with the development team. The development team gives guidelines to the module team.
- The module team divided into two sub teams, one of the team leaders is the "module team leader":
--- "Module care team": This team looks for modules, updates and maintaining. It fills and maintains the add-ons repository, and also makes modules more modern / up-to-date. It also should merge modules, so there are more focused modules, e.g. 1-2 image galleries instead of 15.
--- "Module API team": This subteam cares about some kind of API or functions which the modules can call, e.g. functions for uploading / resizing images.
- The team should set some kind of guidelines, how modules should be written they fit well into the "WB world", e.g. templates.
- There should be no overorganization / bureaucracy, so the team goals can change dynamic.

If you like to participate, just write here or contact Boudi or me.