Piwigo.org

plg · 2010-01-26 15:28:18

Hi coding team,

Let's talk about Piwigo 2.1 and planning.

I don't want to have a list of features to implement before releasing 2.1, I rather propose a date and we will have features depending on what will have been commited.

I propose:
* 2010-03-12 : 2.1.0RC1 (was released on 2010-03-28)
* 2010-03-19 : 2.1.0RC2 (was released on 2010-04-14)
* 2010-03-26 : 2.1.0RC3 (was released on 2010-04-30)
* 2010-03-31 : 2.1.0 (currently planned for 2010-05-17)

Yes, it's only 60 days in the future. As suggested by nicolas, I agree that if we say June, we'll simply postpone coding till April or May :-) I'm also OK to say that 2.2 could be released only 6 months later (instead of 12 months). 2.0 was a really big release, with a new website and a big work on internationalization. 2.1 should be much lighter.

What will be 2.1, for sure:
* support for PostgreSQL
* support for SQLite
* drag & drop to reorder photos in a category
* upload form (plg has already released an alpha version as a plugin)

What would be really appreciated for 2.1:
* improved EXIF/IPTC/XMP support (grum has already made a big part of it)
* theme manager
* template dependencies
* better way to manage user input data (to avoid security issues)
* as many usability improvement as possible in the administration panel
* gettext to manage i18n

If there is any feature you would like to add for 2.1, drop a post :-)

[2010-05-10] edited by plg: 2.1.0 postponed to 2010-05-17

plg · 2010-01-26 15:31:34

VDigital, I created a new topic compared to [Forum, topic 15174] [Roadmap] for Piwigo 2.1.x, because you turned it into a "expected features for 2.1" and I would really like to avoid this method this time, or else I'm afraid 2.1 won't be released before 2011 (without exaggeration).

VDigital · 2010-01-26 17:29:33

No problem at all.

* template dependencies (I will implement it in february)
As I told you, I will review some parts (removals and reorganisation) in template...
Consider we embed now Simple / yoga / and a new template (even if we were expecting to have Gally as well).

nicolas · 2010-01-26 20:27:20

Can you create version 2.1 so that we can affect task to that version : http://piwigo.org/bugs/roadmap_page.php
Mine tasks are :
- support for SQLite : almost finish
- gettext
- others ?

Last edited by nicolas (2010-01-26 20:27:37)

plg · 2010-01-26 20:30:08

Currently, in the bugtracker, "Colibri" = 2.1

plg · 2010-01-26 20:31:48

nicolas wrote:
- others ?

Propose a secure method to work with user data input (considering PHP 5 is required to run Piwigo), I know that's important for you :-)

nicolas · 2010-01-26 22:25:10

plg wrote:
nicolas wrote:
- others ?
Propose a secure method to work with user data input (considering PHP 5 is required to run Piwigo), I know that's important for you :-)

I know that you will say something like that ! :-) Ok for me but just after gettex. Even if that new point is very important I think internationalisation is much important. If we don't work on internationalisation, we will not ne able to make a great PiwigoCamp in London in 2011 ! :-)
I hope I can finish that new request or almost started it for 2.1.

Last edited by nicolas (2010-01-26 22:27:57)

nicolas · 2010-01-26 22:32:10

plg wrote:
Currently, in the bugtracker, "Colibri" = 2.1

Ok. There a strange version in the bugtracker : Colibri 1 !!

mathiasm · 2010-01-26 23:47:34

plg wrote:
* as many usability improvement as possible in the administration panel

Does it include modifying the admin menu (sorting, naming, etc) ?

plg · 2010-01-27 00:01:01

mathiasm wrote:
plg wrote:
* as many usability improvement as possible in the administration panel
Does it include modifying the admin menu (sorting, naming, etc) ?

Yes, it does include this kind of improvement.

plg · 2010-01-27 00:02:21

nicolas wrote:
plg wrote:
Currently, in the bugtracker, "Colibri" = 2.1
Ok. There a strange version in the bugtracker : Colibri 1 !!

Not that strange. At the right moment, this release will be renamed into 2.1.0RC1 or 2.1.0beta1. For the moment, Colibri is the code name for 2.1.

grum · 2010-01-31 10:21:42

plg wrote:
What would be really appreciated for 2.1:
* improved EXIF/IPTC/XMP support (grum has already made a big part of it)

I'm working on it, but I don't know if the dedicated plugin will be 100% functionnal at this date...

plg · 2010-01-31 11:22:09

grum wrote:
plg wrote:
What would be really appreciated for 2.1:
* improved EXIF/IPTC/XMP support (grum has already made a big part of it)
I'm working on it, but I don't know if the dedicated plugin will be 100% functionnal at this date...

Of course, that's not a problem. We will see what's functionnal and what's not on 2010-03-01 to see what can be integrated into core (it doesn't mean we can't have an AdvancedMetadataManager living in parallel).

VDigital · 2010-02-09 18:31:20

VDigital wrote:
* template dependencies (I will implement it in february)
As I told you, I will review some parts (removals and reorganisation) in template...
Consider we embed now Simple / yoga / and a new template (even if we were expecting to have Gally as well).

On my personal roadmap:
- template dependencies: renamed in template modelling (if you have a better name).
- new template: juzq.
- CSS review (without loses).
- theme extensions.
- squared function
- some useful template functions
- and if I have enough time: I hope relaunch Swift Theme Creator.

If someone is interested to do one of them, I can explain the objective, and main lines.
As well if someone is motivated to help finalizing delivery, we can split this heavy final task.

tosca · 2010-02-10 02:23:33

plg wrote:
mathiasm wrote:
plg wrote:
* as many usability improvement as possible in the administration panel
Does it include modifying the admin menu (sorting, naming, etc) ?
Yes, it does include this kind of improvement.

I've begun to work on a new admin interface.
I intend to:
- fully reorganize the access to current functionalities in a much more intuitive and user-friendly manner
- add improvements as suggested in several forum topics from the past weeks, especially 16762, 16704, 16816, 16847

As I want to cencentrate on producing something rather finalized, and not to lose time in arguing about peccadillos, I will not make anything public till I'll have some kind of models for most pages and functionalities, to use as a starting point for functional specifications to be discussed (first draft).

I hope things will get much clearer in a couple of weeks. In the meantime, I might ask questions to some of you in order to clarify some points, or get feelings about technical solutions.
Feel free to call my attention on any point you think I could have passed by.

Piwigo.org

Announcement

#1 2010-01-26 15:28:18

Piwigo 2.1 planning

#2 2010-01-26 15:31:34

Re: Piwigo 2.1 planning

#3 2010-01-26 17:29:33

Re: Piwigo 2.1 planning

#4 2010-01-26 20:27:20

Re: Piwigo 2.1 planning

#5 2010-01-26 20:30:08

Re: Piwigo 2.1 planning

#6 2010-01-26 20:31:48

Re: Piwigo 2.1 planning

nicolas wrote:

#7 2010-01-26 22:25:10

Re: Piwigo 2.1 planning

plg wrote:

nicolas wrote:

#8 2010-01-26 22:32:10

Re: Piwigo 2.1 planning

plg wrote:

#9 2010-01-26 23:47:34

Re: Piwigo 2.1 planning

plg wrote:

#10 2010-01-27 00:01:01

Re: Piwigo 2.1 planning

mathiasm wrote:

plg wrote:

#11 2010-01-27 00:02:21

Re: Piwigo 2.1 planning

nicolas wrote:

plg wrote:

#12 2010-01-31 10:21:42

Re: Piwigo 2.1 planning

plg wrote:

#13 2010-01-31 11:22:09

Re: Piwigo 2.1 planning

grum wrote:

plg wrote:

#14 2010-02-09 18:31:20

Re: Piwigo 2.1 planning

VDigital wrote:

#15 2010-02-10 02:23:33

Re: Piwigo 2.1 planning

plg wrote:

mathiasm wrote:

plg wrote:

Board footer