[xwiki-devs] [Discussion] Granularity of applications?
Hi, I'd like to discuss the granularity we want to have for our applications. This discussion was prompted by the recent password- reset application. There are some pros and cons I think of having small applications. Pros: - better compartimentation - different release cycle Cons: - heaviness of release (separate XAR; etc) - different release cycle - fragmentation My personal take is that this application should go under the administration application so that it's released together with it (it could be a sub module that is aggregated in the final XAR for the admin app.). WDYT? Thanks -Vincent
+1 for bundling the password reset application with the Administration one (people have been waiting for it for so long, let's just give it to them ;-) ) Guillaume On Tue, Aug 26, 2008 at 9:26 AM, Vincent Massol <vincent@massol.net> wrote:
Hi,
I'd like to discuss the granularity we want to have for our applications. This discussion was prompted by the recent password- reset application. There are some pros and cons I think of having small applications.
Pros: - better compartimentation - different release cycle
Cons: - heaviness of release (separate XAR; etc) - different release cycle - fragmentation
My personal take is that this application should go under the administration application so that it's released together with it (it could be a sub module that is aggregated in the final XAR for the admin app.).
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Guillaume Lerouge Product Manager - XWiki Skype ID : wikibc http://blog.xwiki.com/
Vincent Massol wrote:
Hi,
I'd like to discuss the granularity we want to have for our applications. This discussion was prompted by the recent password- reset application. There are some pros and cons I think of having small applications.
Pros: - better compartimentation - different release cycle
Cons: - heaviness of release (separate XAR; etc) - different release cycle - fragmentation
My personal take is that this application should go under the administration application so that it's released together with it (it could be a sub module that is aggregated in the final XAR for the admin app.).
WDYT?
I was thinking about this myself. For me, it isn't exactly Administration, as it isn't something admins can do, that's why I created a different application. We could rename the administration application to something more generic, and which should have submodules (administration, coreClasses, passwordReset). -- Sergiu Dumitriu http://purl.org/net/sergiu/
On Aug 26, 2008, at 11:11 AM, Sergiu Dumitriu wrote:
Vincent Massol wrote:
Hi,
I'd like to discuss the granularity we want to have for our applications. This discussion was prompted by the recent password- reset application. There are some pros and cons I think of having small applications.
Pros: - better compartimentation - different release cycle
Cons: - heaviness of release (separate XAR; etc) - different release cycle - fragmentation
My personal take is that this application should go under the administration application so that it's released together with it (it could be a sub module that is aggregated in the final XAR for the admin app.).
WDYT?
I was thinking about this myself. For me, it isn't exactly Administration, as it isn't something admins can do, that's why I created a different application.
We could rename the administration application to something more generic, and which should have submodules (administration, coreClasses, passwordReset).
For me this is definitely an Administrative feature. Administration doesn't mean it's only for administrators. It means anything that is an administrative feature. I don't have any better idea on the name right now. Thanks -Vincent
Vincent Massol wrote:
Hi,
I'd like to discuss the granularity we want to have for our applications. This discussion was prompted by the recent password- reset application. There are some pros and cons I think of having small applications.
Pros: - better compartimentation - different release cycle
Cons: - heaviness of release (separate XAR; etc) - different release cycle - fragmentation
My personal take is that this application should go under the administration application so that it's released together with it (it could be a sub module that is aggregated in the final XAR for the admin app.).
WDYT?
+1 for bundling the password reset application with the Administration one -- Artem Melentyev
participants (4)
-
Artem Melentyev -
Guillaume Lerouge -
Sergiu Dumitriu -
Vincent Massol