Thoughts about contributing & WB releases

[Yetiie]

Ok ... slowly it became more clear. Thx.
And great reactions up to now


----
Just to make especially the idea of the theme and the css elements for modules clear:

The new backend theme could be prepare to 2.8.4 without affecting core and without dev team.
Only the defintive starting point is needed and this ist at least clear when the version is published.
In this case there is nothind to forbid. That's the charme of the project

With the very little mentioned requirement it would be possible to AND would make sense to develop html/css elements for module development without affection core or further work of dev team. And just to avoid misunterstandings:
- the actual modules stays as they are (their look does not change)!
- the elements don't need be used for module development (of course every developer is able to do his own thing)!
- if someone does not like the styling it would be easier to change it because the css could be changed ... of course!

In this case there is nothing to forbid too ... but not to do the little requirment would prevent it by dev team as this work does not make sense


So: if you like it --> maintain/support it and vote for so the dev team includes this litle requirement to 2.8.4  
Your chance or better: the chance of the comunity  
And other and more ideas are welcome ... as well !!!

[Yetiie]

@Stefek

Do you want WebsiteBaker to be a community developed project ...

The idea has charme ... but I am not quite sure if this ist not too much and a step to far ... for the moment.
We will see

So let's have a look to things too we can do without affecting the dev team.
Preparing the Bootstrap elements to WB ... could be another theme ... if there are some interessted in ...

[Stefek]

@Stefek

Do you want WebsiteBaker to be a community developed project ...

The idea has charme ... but I am not quite sure if this ist not too much and a step to far ...

Yes, I have already obseved that you look at the things from your perspective. From what you are interested in (i.e. the Backend Theme). The same is the case for the Dev - she thinks only her perspective and speed of work is the one correct. And that's why WB ain't a community project anymore.

People like Tez, Boudi, Michael and many many many others with some experience regarding the bureaucracy of WB management already know how annoying contribution to this project has been in the past. You are yet to find it out, my friend

When nothing changes, well... nothing changes.

[Yetiie]

Yes, I have already obseved that you look at the things from your perspective. From what you are interested in (i.e. the Backend Theme).

Oh ... no, no, no 
To be honest I am not interessted in special things not even the backend theme. The backend theme ... you know from the german forum how it grew up ... I am interested in improvemtent of WB itself does not matter what item !!! And I am EXACTLY on your side ... !!! Your idea of branch development is the right way I believe. But indeed I am affraid it is a step to far way ... with the actual organizing structure and of cause the actual leadership.


Indeed I think:

Activating people to engage themselve ...
Activating the community to tell what they would like have ...
... could be more successfull even if there are more reachable (concrete and limmited) projects which could be realized without the dev team! (And there are a lot of possivilities. And this could make change the complicated mind of the dev team ... if they see it works. This is what I would like to do.


This could (but don't must) be (just spinning):
- Backend theme with standardizing CSS module elements ...
- Bootstrap ...
- A group which would like to organize the rest of the modules on a plattform if the team don't like to improve the module plattform themselve ... (you know we had this and the people for it but no support but icy silnce of the leaders which prevent this)
... or any other idea people would like to to



[ So additional ideas and signals of engagment are welcome. ]



Indeed our ideas are not far away. You wonna work in separted teams on parts of the official project and improve it ... I wonna work in little separated teams on concrete possibilities to improve WB too without need to affect the official project to activate the process.

The best: both works 
And both works together.



-----------------------
And as I see it. The last days hope grows to the people here. I hope the dev team does not destroy it once more as they did in the past to any project or attempt which they could not understand or which they did not like ... better way would to be to lead the trend than to play the big boss nobody accept and even dont take serously anymore. Well, maybe the comming meeting will be a change ...

[Stefek]

Yes, I have already obseved that you look at the things from your perspective. From what you are interested in (i.e. the Backend Theme).

Oh ... no, no, no 
To be honest I am not interessted in special things not even the backend theme. The backend theme ... you know from the german forum how it grew up ... I am interested in improvemtent of WB itself does not matter what item !!! And I am EXACTLY on your side ... !!! Your idea of branch development is the right way I believe. But indeed I am affraid it is a step to far way ... with the actual organizing structure and of cause the actual leadership.

So, that's what I am talking about.

Of course the first step is, to have the Verein see a need for change of its past structures and patterns.
If the main developer has a veto right on anything regarding development, it's not a Community Project.

I want WebsiteBaker to be a community project, developed and created by the community.
I want DarkViper to be a team player, not what she is currently presenting herself as.

There is actually nothing wrong with that.

[Stefek]

Indeed our ideas are not far away. You wonna work in separted teams on parts of the official project and improve it ... I wonna work in little separated teams on concrete possibilities to improve WB too without need to affect the official project to activate the process.

The best: both works  
And both works together.

I am sure we have parallels in our ideas.

Primarly I want that WB is developed by the community on a branch system(like GitHub or even better, BitBucket).

[Yetiie]

@Stefek
... so we are trying the same ... but with different sub-targets and little similar steps

Yeah, a little change of working of the leadership would be very good for the project. It is allways the same (not a special wb systematic): a big boss prevents ... people go and boss fails and with him the project ... the leaders coordinate ... and get all they want and even more

Have hope

[Stefek]

Have hope

Hope?  

OK, if you say so  

Yeah, a little change of working of the leadership would be very good for the project. It is allways the same (not a special wb systematic): a big boss prevents ... people go and boss fails and with him the project ... the leaders coordinate ... and get all they want and even more

Yeah, full ack on that.

Let's end for now and let others speak, my friend.

Kind regards,
Stefek

[Tez Oner]

Eeey,

kinda flabbergasted by the optimistic response   and as there
definitly some key-issue / wishes we need to structure the issues
to 'framed' sections like; backend (functionality / theme / methodics
/ consistency), frontend (functionality / consistency / functions /
templates).

From there look if there some tool for collabration, to add bugs / features
etc etc. And what maybe more interresting are the additions / forks that
are already made by community members (e.g. the fact that Stefek modded
the backend for 80% with new code, that are awesome things would (if you
ask me) speeds up the development dramatically!

And I would love to hear from the WB Dev team what they think of the thoughts!


Cheerz,

Tez Oner