On Tue, May 11, 2010 at 00:34, Caleb James DeLisle <[email protected] > wrote:
> In http://www.mail-archive.com/[email protected]/msg14717.html > Ludovic said "We need to be as compatible as possible with how the > current invitation manager stores it's configuration and state > (current invitation and requests)" > I think this concept is worthy of it's own discussion thread. > > When I approached this project, I hadn't considered a need for an > upgrade path from the Invitation Manager (I assume that's what this > is for.) The application as it stands is quite dependent on a > different configuration/storage model and changing will take a long > time. > > Do we really want to use the same configuration/storage as the > Invitation Manager? > > * The Invitation Manager plug-in uses configuration parameters > defined in the now deprecated xwiki.cfg file while Invitation > Application uses a custom configuration class through the > XWiki.ConfigurableClass system. > > * Invitation Manager and Invitation Application both store message > status as a number, Invitation Application uses additional codes for > "sending failed", "reported as spam", and "reported and investigated". > > * Invitation Manager has an additional field "space" which will make > no sense without Space Manager plug-in in the invitation application > setup and will have to be replaced by "groups". > > * To copy Invitation Manager setup will block further feature > addition such as invitations which expire after a given amount of > time (for mailing lists). > > * Invitation Manager templates are coded in a format similar to > XWiki/1.0 syntax (but not exactly the same) Invitation Application > templates are (currently) to be coded in XWiki/2.0 syntax. > > Options: > > We could continue the Invitation Application as is and if an upgrade > path is needed, add a script for upgrading legacy data later on. > +1 > > Drop the current work and get the Invitation Manager plugin to build > (It would be a shame to dump so much work over one requirement.) > -10 > > Rewrite the current work to be compatible with the old Invitation > Manager, accept using depricated configuration and sacrifice > features (this will take the most time.) > -1 > > What are your thoughts? > Invitation Manager is pretty old style and it would be a shame to not follow new clean standards. It's not like invitation manager was part of standard XE... > > Caleb > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
