Thoughts about contributing & WB releases

[Stefek]

>>> Standardizse the css for modules ... this has to to with the backend theme ... the idea is a modular css with defined elements which should be used for modules. Standardizing elements means: defne html- und css-structure (classes). On this way it would be possible to have en even look for the modules and to be able to change the look to another design by styling the same elements only with css.

Yetiie,

this is rather easy. But it begins with the backend-theme itself.

Once you have the backend-modules (like settings, page-settings etc.) and some of the packaged modules (like news, form-module etc.) reworked you end up with the necessary HTML structure for way over 80% of all modules. This HTML structure and its CSS definitions then can be easily applied in the modules developed by the community.

So yes. Doable. And long overdue.

>>> a mulitchanger-module ...

What do you mean by that?

Stefek

[pcwacht]

+1 for the standardization of modules

This will give faster development - simular look etc.

Hmm, not just +1, I'll give it a +100

John

[Yetiie]

And one other information:

The last two or three days in a thread one of the development team mentioned, for a wb project he would open a place on the resporitory (as I hd understood that) ... could be a good place to collect and coordinate ...

[Yetiie]

Very good idea.

Just my two cents: to create a goal for whole websitbaker project will be alittle bit complicated ... because the development team has their own planning and as I learned over the last years ...

But the way to improve WB by realising concrete and limited single projects in little teams could be very effective.



######## To be concrete:

My most done suggestion at the moment is a WB-Bootstrap project.
The theme grows up here on WB too.
Means: Making the elements of bootstrap easy accessable to WB.
Done as best-practise-demonstration and/or as starter-template.


Other ideas are:

>>> Standardizse the css for modules ... this has to to with the backend theme ... the idea is a modular css with defined elements which should be used for modules. Standardizing elements means: defne html- und css-structure (classes). On this way it would be possible to have en even look for the modules and to be able to change the look to another design by styling the same elements only with css.

>>> a mulitchanger-module ... not as easy, but multichangers become more and more popular and replaces the picture changers and it would kick the possibilities of WB forward.


-----------
... just as some ideas!

[easyuser]

Until this or some similar concept is realized and set up, I need no meetings.
Too much time wasted already.

Well, there were wasted 5-7 years and endless hours in four-eyes-meetings and forum posts, I don't think an unofficial meeting is that bad, I think it's a better discussion platform than the forum. But of course nobody has to take part.

[easyuser]

Just saw the post about the Skype meeting, its sunday (well see this as an addition)

For now most people have time Thursday or Sunday next week. I spoke with Luisehahne about it, he will be there and perhaps DarkViper (?), so there are also some official persons taking part. 

[Stefek]

Hello Tez

... it's a fact that there's some let's call em 'new generation' who would love to take WB to another level, make it even better as it is, more transparent and more 'open' source, which would if you ask me speed up the development.

Agree with you one hundred percent.

But for that it's needed to have a shared goal - and not individual issues or whatever.
There's 1000 ways to have contact / contribute on WB these days, but the development process at the moment
is to unstructured to actually contribute anything.
What's needed is to have some structure like any software development should have, and maybe new methodics.

That's the main issue.
WB is developed without any transparency at all, let alone having ways to contribute to the core.

The core has become the property of one person.
Only she decides what is good or bad and what comes in or not.

In the german forum it was even said that NO branching system will be set up for the community.
In my opinion it's a waste of potential.

Maybe there will change something (or has already changed) in this philosophy, but till now I have seen no signs of it.

As long as WB is developed behind closed doors instead of in the open, with more contributors involved, there will be no real progress.

Let people work on separate branches, use GitHub or BitBucket (which is even better suited as it costs nothing for OS projects and grants you closed space for experimental Branches), let them work on prototypes and show their results to the community, so the community can decide whether or not it is something worthwhile and should go into the core or if it is only something that is nice but too specific and better be used as a  patch.

Until this or some similar concept is realized and set up, I need no meetings.
Too much time wasted already.

Thanks for the consideration.

Stefek

[Tez Oner]

Just saw the post about the Skype meeting, its sunday (well see this as an addition)

[Tez Oner]

Eeey,

as the previous thread is been closed on request of Stefek (can imagine' a lil why   )
it had some very constructive thoughts from e.g. Nibz, Stefek, Argos and me (as I can say that).
That whole language **** is clear - period, but - it's a fact that there's some let's call em 'new generation'
who would love to take WB to another level, make it even better as it is, more transparent
and more 'open' source, which would if you ask me speed up the development.

But for that it's needed to have a shared goal - and not individual issues or whatever. There's 1000
ways to have contact / contribute on WB these days, but the development process at the moment
is to unstructured to actually contribute anything. What's needed is to have some structure like any
software development should have, and maybe new methodics.

Just some thoughts.

Cheerz,

Tez Oner