Contributing guideline

[herodrigues]

Hi, Ivan

I was taking a look in your project and noticed that you're the only contributor.
Going through the README I couldn't find any contributing guideline.

Your project seems to be very promise and it would be great if you provide a contributing guideline or a "what to do" guide.

[ivanproskuryakov]

Hi, unfortunately it is. Could you describe what guidelines might be useful for you, please?

[herodrigues]

Coding patterns, good practices, to-do list, etc

Or just a to-do list as I think you may follow Symfony2 coding patterns.

[ivanproskuryakov]

Hello @herodrigues,
I'm not sure that I can give you a list of good practices, basically the goal is to write highly reusable code. For this case I'm trying to decompose logical structures into bundles, like PageBundle, ProductBundle, with depends on ResourceBundle.
ResourceBundle handles controllers, repositories, traits which are common in all Bundles. It helps to write less, and refactor the code in minutes, hours..

for this case I'm optimizing doctrine entities with traits, which is described here:
http://ivanproskuryakov.github.io/publications/Optimizing-Symfony-and-Doctrine-using-Traits/

But I have a good new as well, I wrote an article which described code organisation for Angular and frontend
http://ivanproskuryakov.github.io/publications/AngularJS-app-architecture/

[herodrigues]

Thanks @ivanproskuryakov! I'll take a look.