John Porter

I have a design pattern I wanted to implement a while back, but my lack of knowledge around how it would affect the current JS meant I left it alone.

> Maybe it's a good idea to also create a list of business objectives for Symphony Next with priorities so any decisions can be made with those very much in...

I agree. I have my opinion, but until it is discussed with the project leads and owner, I can't dictate it. I think this will come down to a decision...

OH GOD.

PS, don't get me wrong about all this, I really like Laravel. Really. I just want the best for the project, but I think the majority is leaning toward Laravel,...

@ijy I'm really happy to hear you've done that, that makes me very happy indeed. It's good to hear that people are out there spreading the word. It would be...

I wouldn't have thought so, it's just a matter of ensuring we follow a standard of coding, and keep the separation of dependencies correct.

Yeah, we just need to specify that it needs configuration injecting into it, and show an example of that configuration.

Can you add this as a wiki page instead to limit the writing of the list to actual team members.

The tutorial tried to allow you to limit the amount of Symphony's history that's stored in your project by limiting the commit depth in each fetch/pull. It also limits the...