Skip to content
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

Closed
winzou opened this issue Jun 28, 2013 · 18 comments
Closed

Roadmap #209

winzou opened this issue Jun 28, 2013 · 18 comments
Labels
RFC Discussions about potential changes or new features.

Comments

@winzou
Copy link
Contributor

winzou commented Jun 28, 2013

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:

It does not mean that other non-official collaborators
cannot move forward with this implementation/concept,
and in fact it's already in progress, but slow.

To coordinate all efforts and ease the integration of Sylius, such a roadmap is vital.

Thanks.

@pjedrzejewski
Copy link
Member

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! :(

@ghost
Copy link

ghost commented Jun 28, 2013

a meeting? i wasn't aware of any meeting. i was under the impression that the meeting was going to be public?

@jjanvier
Copy link
Contributor

Hmm... I'm quite surprised too. Looking forward to see this roadmap anyway and thanks to winzou for raising again this point.

@marcospassos
Copy link
Contributor

It was one of our suggestion in the meeting call: publish the roadmap and leave developers pick up tasks as their capacity allows. IMHO we have to stabilize the core and make Sylius fully functional. Basically, we have two fronts: things we have to do and the things we would like to do (aka enhancements). I believe that the contributors can help in both fronts, as long as the enhancements had been agreed and planned. Thus, I think that agreed enhancements should be in the roadmap, leaving the contributors pick up a task and work on it according with his interest or the community interest.

@jrobeson in the meeting skype call we just clarify some points related to the project creator goal and the next steps to give to community more transparency (like public meeting) and autonomy.

Note: these are just my opinions and suggestions.

@pjedrzejewski
Copy link
Member

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!

@PaddyLock
Copy link

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

@umpirsky
Copy link
Contributor

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.

@jjanvier
Copy link
Contributor

Great news :) And congratulations to @marcospassos

@arnolanglade
Copy link
Contributor

Good news!

@arnolanglade
Copy link
Contributor

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) :
Backend, we need advanced grid system, I think it miss the following functionalities :

  • choosing the number of items you want to display in a grid.
  • executing actions on one or more than one item.
  • Managing complex filters.
  • Exporting to different formats (csv, xls)

Frontend :

  • I heard that we want to use some CMF functionalities. I think it miss to Sylius the possibility to manage static content from administration. For example you can do that with Magento, you can create pages or blocks. It can be useful for user who are not developer. Magento have interesting layout and block system, perhaps you cam do something like that.
  • We need to think about theme system. Like other CMS and E-Business system, you can install themes and decide what theme you want to enable.

Order Management :
Now, it is difficult to manage orders.

  • The user can not manage the shipment of the order item.
  • We can not manage the status of the order, I think we can remove the delete action and replace it by cancel action. If we can edit them from the backend, it will be great, some peoples have very specifics order statuses.
  • We can not export invoices in PDF.

Order process :
We can offer the possibility to manage terms and conditions from the backend and to the customer to accept them before payment.

Customer / User :

  • I think we can add some new fields, like birthday, gender, title, etc... these informations can be useful for businessman... Adding customers to one or more groups can be usefull too.
  • In the backend, we can not manage access rights to each part of administration.

I hope that my English is not so bad.

@PaddyLock
Copy link

@pjedrzejewski when can we expect the roadmap to be published please?

@ghost
Copy link

ghost commented Jul 8, 2013

any updates on the roadmap?

@Eponymi
Copy link
Contributor

Eponymi commented Jul 20, 2013

I think someone needs to work on a Roadmap for the publishing of a Roadmap.

@winzou
Copy link
Contributor Author

winzou commented Aug 29, 2013

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?

@molchanoviv
Copy link

@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?

@stloyd
Copy link
Contributor

stloyd commented Oct 15, 2013

@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...)

@pjedrzejewski
Copy link
Member

@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?

@stloyd
Copy link
Contributor

stloyd commented Oct 15, 2013

@pjedrzejewski This is one of the simplest aprroaches (display progerss bar or something like that), but anyway it's good start.

pamil pushed a commit to pamil/Sylius that referenced this issue Mar 21, 2016
[ResourceBundle] Adding new chapter which explains how the doctrine mapping works
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFC Discussions about potential changes or new features.
Projects
None yet
Development

No branches or pull requests

10 participants