-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap #209
Comments
We're few days after a meeting where we defined approximate release dates and important milestones. The roadmap is ready to be published... but there are few things which need to be solved before I do this, be sure it will be ASAP! I know people have been asking for this many times - and I'm sorry for the delay! :( |
a meeting? i wasn't aware of any meeting. i was under the impression that the meeting was going to be public? |
Hmm... I'm quite surprised too. Looking forward to see this roadmap anyway and thanks to winzou for raising again this point. |
It was one of our suggestion in the @jrobeson in the Note: these are just my opinions and suggestions. |
I used wrong word perhaps, we did 30 minutes skype call where I presented my idea for roadmap and release dates, when @umpirsky and @marcospassos gave me some thoughts and ideas. Everything will be public and I hope to make a real meeting of all interested users and contributors where we discuss if my idea is realistic / interesting / good. :) And YES, one of things we discussed was that I should be 100% transparent with all plans and start public discussions! |
This is fantastic news! there are some items such as https://github.com/Sylius/SyliusAssortmentBundle/issues/74 https://github.com/Sylius/SyliusAssortmentBundle/issues/68 and https://github.com/Sylius/SyliusShippingBundle/issues/18 which may not be in the current feature set but to me seem like fundamental features of which any e-commerce site with a large amount of configurable products could not do without. I wouldn't consider my use cases exceptional. If feedback on these and other features in the roadmap is transparent, this would be very useful indeed! thanks |
The conclusion is: stay tuned untill @pjedrzejewski publishs the roadmap (hope to see it soon). Then we can iterate on it together FTW. @winzou Thanks for raising this. |
Great news :) And congratulations to @marcospassos |
Good news! |
Some idea we can add to the roadmap : We have to choose a javascript framework, firstly we have to define what we want... One page application? What ui component we need? etc... We have to improve the user interface (back and front), Pawel said us he finds a designer (this is not sure, I hope it will be ok) :
Frontend :
Order Management :
Order process : Customer / User :
I hope that my English is not so bad. |
@pjedrzejewski when can we expect the roadmap to be published please? |
any updates on the roadmap? |
I think someone needs to work on a Roadmap for the publishing of a Roadmap. |
Thanks @pjedrzejewski for having published this wanted roadmap. Now, like I said in the comments (but not the best place for it), we need a mean to know who is working on what. Indeed I saw in the comments that people already have their preferences on what they want to work on, let's make these choices visible to anyone. So that 2 guys won't do the same thing at the same time, but work together in a more effective way. What do you think? What would be the best method to achive it? |
@winzou For this purpose I offered Pawel to set up Redmine or Bugzilla for project. But he didn't answered. What do you think guys about this idea? |
@pjedrzejewski I think we can close this as you have published: http://sylius.org/blog/the-roadmap and we use milestones at Github (maybe some better integration between webpage and GH issues, could help, but that's just some off many ideas I was mentioning you in mails...) |
@stloyd Thinking about some progress bar for BETA milestone, on website? I already query gh api for some stuff so it should be pretty easy to add. What do you think? |
@pjedrzejewski This is one of the simplest aprroaches (display progerss bar or something like that), but anyway it's good start. |
[ResourceBundle] Adding new chapter which explains how the doctrine mapping works
Hi,
Despite its early state, Sylius is already used in many projects.
We do really need a roadmap of what is being coded, postponed, etc. It is currently very hard to ancitipate, you guys are not telling that much here and we don't know exactly what is going on about many features.
I think this is quite important, especially after seing a message from @marcospassos:
To coordinate all efforts and ease the integration of Sylius, such a roadmap is vital.
Thanks.
The text was updated successfully, but these errors were encountered: