General Community > Off-Topic

Thoughts about contributing & WB releases

<< < (3/7) > >>

Stefek:
Yetiie,

all what you say and are asking for is on my schedule (and work in progress on my personal derivat/fork).

That's why I am asking (for some years already) for branched community development.

I have reworked almost 80-90% of the backend to make it ready for TWIG.

Having done it, you have no more problems with hardcoded php spaghetti code and such thing anymore. You only concentrate on the template.

Of course the way I have worked on the code is different then the way Luisehahne would do. Or DarkViper.
But the resulting TWIG Templaes and its variables would stay more or less the same - giving the possibility to work upon the backend theme without colliding with other parts of the core.

As I said in my first post in this thread:

--- Quote ---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.
--- End quote ---

And when I say "too much" I really mean it.

Stefek

Yetiie:
@Stefek

I am not quite sure if I understand you right.
You are working on a new backend theme?
That would be great  :-) :-) :-)


For what version?
So we don't have to adapt the new theme to 2.8.4?

With Twig?
So did you change the code output of the core or doe you write about working on the core yourself?

? ? ? ? ? ? ? ?

nibz:
Hi Yetii and Stefek,

I agree with you both, we need to work together, lets be a T.E.A.M. (Together Everyone Achieves More).

Stefek, i though would like to have the meeting to discuss the possibility to make this happen.
I claimed the WebsiteBaker github name, and made a repo: https://github.com/WebsiteBaker/WebsiteBaker

I also made a github for templates: https://github.com/WebsiteBaker-templates (possibility to have 1 repo per template).
And i also made a github for modules: https://github.com/WebsiteBaker-modules where i put all the modules which are active on the addons repo and am adding more.

I think it's not a problem to work on github because we could make branches and i for one don't mind that everyone can see the development (also nightly builds or even not yet approved codes which maybe will never see daylight). WE as a TEAM are a Open Source community and i think even the development can be opensourced, any- and everyone should be able to contribute with the understanding that the CORE crew will need to approve the pull requests etc.

I hope you would reconsider not joining the community meet and open discussion about WebsiteBaker and probobly it's future. The more people that are for the "TEAM" idea the more the more probable it is the idea will see daylight sooner.

If it's to me everyone is welcome to pull requests at my WebsiteBaker github's, and if someone of the CORE DEV team needs access they only need to ask and they will get it!.

Hope we can move WebsiteBaker to 2015!

And don't forget: "Together Everyone Achieves More".

Kind regards,

Robin (Nibz)

Stefek:
@Yetiie
It's all written there.

It's my personal branch.

Version does not matter. If you understand something about branching, you will see that it does not matter.

2.8.4. will come with whatever is scheduled by the Dev Team. But it looks like they will pull out yet another phpLib based Backend Theme. Exactly the technology that gives you the pain in the ass:

--- Quote ---Yetiie: Based on the experience with the new backend theme this IMHO only really makes sense with(!) little support of the development team sad The problem to style this special page on the backend is, that the code is hard coded by php (very old code from the beginning of the cms, someone reported from about the 80th).
--- End quote ---

And exactly the same reasons why Argos stoped his development on his Backend Theme.

If you still don't understand:
I am working on getting rid of phpLib and on a implementation of TWIG.
Yes, I am doing the php myself in order to make the /admin ready for TWIG.

When the work is done, no more pain in the ass for you, as you will have all the freedom you need in order to design the backend theme as you see fit.

Last year DarkViper wrote (sorry for german here):
"Schon mit der Umstellung des ACP auf Twig wird(hoffentlich immer noch huh) Stefek in diesen Spezialbereich mit einsteigen. Wir werden das erste Modul, die Prototypen, zusammen erarbeiten und sobald er 'es geschluckt' hat, wird er den Rest in Abstimmung mit mir durchziehen. Auch ist abgesprochen, dass er dann für diesen Bereich sein eigenes, kleines Team zusammenstellen kann und ich selbst hier nur noch als Kontroll- und Koordinationsinstan z eingreifen werde."
source: http://forum.WebsiteBaker.org/index.php?topic=27237.0

Quick Translation (google):

--- Quote ---"With the change in the ACP to twig  Stefek (hopefully still ) will join me in this special area. We will develop the first module, the prototypes together and as soon as he has 'swallowed it', he will do the rest, in coordination with run through me. it is also agreed that he can put together his own small team in this area and I myself  would intervene here only as a control and coordinations entity. "
--- End quote ---

But it just takes too long.
You see. One year has gone by just like that.

That's why I am doing it now on myself now.
It will take for the Devs some years (in the speed the development goes) until she is ready to start with what I have already accomplished.

That's why I am pushing for branched community development. (See my first post in this thread)
Everybody benefits and WBs development is faster.

Yetiie:
@all: [OT]  Aaah ... I remember. NIBZ: You have been the one who offered the resporitory ... really thought to remember the suggestion came from the dev team. As I reported wrong I apologize for this bad memory.[/OT]

@nibz: In general a good idea. But let's do one step after another ... first theme and supporter who would like to engage on a concrete project. Than how they like to work and organize ... your repository could be a possibility :-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page