TECH: Q & A SESSION 9TH OF MARCH
Q: Are you aware of current symfony/http-foundation state and if it comply with PSR-7? Are you going to support PSR-7?
A: Yes, we have checked whether “symfony/http-foundation” package is PSR-7 compliant — itself it is not, however, there is a bridge package available to add PSR-7 support to it. And, yes, we will support PSR-7.
Q: Are you going to follow semantic versioning (http://semver.org/)?
A: Absolutely — once we reach the point when framework core codebase is well defined.
Q: Would be great to keep a changelog — http://keepachangelog.com/. Will you?
A: We will — once we reach the point when framework core codebase is well defined. Otherwise, we would be stuck constantly updating changelogs for every change we make at early stage of development.
Q: If you host the code on github, would it be better to use github wiki instead of atlassian.net for initial paper work? At least until the project has it’s own website.
A: We chose Confluence because A) the documentation on project will be quite massive and Confluence makes it easy to maintain/search/organize, B) we use it for most of our documentation for other projects — we are very familiar with it. At later stages, there will most likely to be a documentation dedicated website, however, at this moment we concentrate on documenting all relevant information rather that presenting it nicely. Our GitHub repository is split into packages and it makes more sense to have package specific documentation stored there and the rest — global type of documentation — in dedicated storage — at this moment — Confluence.
Q: Would be great to have some high level architecture diagrams to understand how components will interact with each other. Will such be available?
A: Yes, such diagrams will be provided.
Q: If you want some help during the research stage, it would be great to have a spreadheet or any other source with components you are planing to implement and packages/ideas/approaches which you have already reviewed/considered/dropped. So anyone could suggest the package or share some ideas about the specific components. For example when you come to translation management you may want to implement XLIFF (http://www.opentag.com/xliff.htm) support for dedicated translation tools integration. I believe you could benefit form out collective experience.
A: Yes, we want it to be like this — developer community being actively involved in development. So, this is not a question of IF, but rather a question of HOW — how and where to keep track of all ideas, suggestions and feedback from community. We will decide on this ASAP and let you all know.
Q: An idea from a frontend standpoint, you should make it similar to wordpress themes, a folder where it houses all frontend functionality so it’s up the developer how the frontend should look and work, seeing as it’s plug and play.
A: We haven’t touched framework’s front-end part yet, as we are mainly working on creating framework’s core, so this is not something we can clearly agree on or deny. However, what drawbacks we see in this approach — modularity can suffer. If there won’t be a standard of how themes should be created, 3rd party module installations will be troublesome. Theme file conflicts will be inevitable. Expect more information on front-end architecture as we go on.
Q: From an ecommerce portion, any way to make it easier to upload products or create products and categories will be beneficial. Especially mass amount of products. I know a lot of users build API extensions for Magento based on JSON feeds. Why not have an extension that is plug in play for JSON feeds?
A: There is absolutely no reason not to have it! Such functionality will be a matter of creating new module for framework.