Roadmap » History » Version 6

Version 5 (Max Milbers, 03/08/2013 02:20 PM) → Version 6/14 (Rolland Vaughan, 03/12/2013 05:51 PM)

h1. March 2013 Roadmap:
For a

long time I have avoided writing we avoid to write down a roadmap, the roadmap. The problem with a classic roadmap is the perception and expectations of by the reader.

A normal roadmap implies that there are deadlines, deadlines and that tasks are resolved sorted and completed at a specific time with community contributors following that all members follow this map and working on each roadmap task do the tasks one by one, however, this is not always the case; one. Of course some tasks can be done in parallel, whilst other tasks and objectives have to wait until previous tasks are completed, before they start. parallel while others not.

But in our case it’s completely different, when it is completly different. When I started with VirtueMart with Sören as leader, the team expectations were based differently, expected this. But in the moment we tried to do todo it the conventional that way, the enthusiasm and motivation of all involved quickly dropped to the detriment of the project, the very soon. The reason for this is that VirtueMart this is a free project, and people project. People want to work on their own ideas, idea, which motivates them (or pays for their time).

However when
them). So it happened quite often, that we hoped to complete a task at a specific point, meant, yes we found should do this is not always possible as contributors and members needs and goals change, and this in turn results in community demands soon. But then people demanded for another feature, that feature so we are were not yet working on, doing it. 3rd party developers cannot always did not jump into the breach, because they thought, we will anyway add it soon to the core soon, and then on core. On the other hand, hand we have tasks scheduled had sometimes plans to implement a feature in the future, when some future and suddenly someone posted the snippet to the forum.

Whilst it is excellent that It works right, when the community people solve problems and create features a problem for their customer and then distribute it to the core, this makes core. There is no need to force the roadmap very fluid and hard people to be specific to dates, also this means people are not following the roadmap, as their contributions are inspired for other reasons and when contributed, change the roadmap constantly, so a roadmap must be considered more of an estimation, much like training a family pet, you hope they are house trained within a few weeks, but might take a few weeks longer that you wanted, but follow some roadmap. But it does happen.

In conclusion it
is right that people understand VirtueMart to have a fluid kind of roadmap which lets may help the people know to estimate, what is coming and a rough estimation of time and what they can expect in the future.

next year. 3rd party developers should also know that we usually do not implement plugins and features things which already exist exists as an extension, and is extension for a reasonable priced. This helps the community in a number of ways, firstly by allowing us to develop other areas of the core and secondly, we take care that we do not destroy the business of our partners and contributing developers. If you have a question about this please contact us to find out price. You can also just ask us, if we developing something you are working on.

*Already started and in
actually develop it.

Already started/ In
the pipeline pipe for vm2.2;*

- rewriting of customfields
- reduced sql for customfields ( drops by 80%).
- order editing
- enhanced pdf creation (selection of font, always the same header/footer)
- rework of the cart, lesser redirects, lesser session memory, more secure
- help button on every view, pointing to
- enhanced userfields, remove of the tos checkbox, exchange against new userfield (required in cart)

for vm2.2 - vm2... (yeh we could need help here), the lower the more unlikely. Be aware this is a kind of wishlist.* wishlist.
- separate seperate shopperfield language keys in an own file
- Product pattern examples (sell your T-shirt, sell your mp3, sell your book, ...)
- more layouts to choose for example multiadd of childs
- FE product editing / creating new
- fixed stocking (when shopper buy simultan)
- merge of the stockable plugin and the dynamic childs.
- ACL of j2.5 for vm2.2
*- - List of VirtueMart virtuemart extensions in the AIO component for installation/updating/3rd party licenses.* licenses.
- rewrite of the calculator using rules as objects
- Fallback for multilingual store to the main language
- joomla 3.5
- Auto resizing Autoresizing main image, with watermark
- enhanced image chooser (multi upload)
- option to display a sign for a minus or not