[xwiki-devs] [proposal] Move xwiki-plugin-invitationmanager and xwiki-plugin-spacemanager to contrib/retired.
Now that InvitationManager is replaced with the Invitation Application and XWorkspaces has been retired, the only "living" dependency on InvitationManager or SpaceManager is Curriki. I propose we: 1. Move these projects to contrib/retired. 2. Stop building them in Hudson. WDYT? Caleb
On Oct 14, 2010, at 6:20 PM, Caleb James DeLisle wrote:
Now that InvitationManager is replaced with the Invitation Application and XWorkspaces has been retired, the only "living" dependency on InvitationManager or SpaceManager is Curriki. I propose we: 1. Move these projects to contrib/retired. 2. Stop building them in Hudson.
WDYT?
+1 Thanks -Vincent
Your proposal says "move Curriki to retired" ? If yes, I would rather be against. If the invitation-manager, I guess I could be ok as long the maven builds and (some) access to source is kept. paul On 14 oct. 2010, at 18:20, Caleb James DeLisle wrote:
Now that InvitationManager is replaced with the Invitation Application and XWorkspaces has been retired, the only "living" dependency on InvitationManager or SpaceManager is Curriki. I propose we: 1. Move these projects to contrib/retired. 2. Stop building them in Hudson.
WDYT?
On 10/14/2010 12:51 PM, Paul Libbrecht wrote:
Your proposal says "move Curriki to retired" ? Oops, indeed it does. I meant move only xwiki-plugin-invitationmanager and xwiki-plugin-spacemanager. My proposal is that the historical maven builds will remain and the source will still be avainable in the contrib/retired section but no new builds will be created by hudson.
Caleb
If yes, I would rather be against. If the invitation-manager, I guess I could be ok as long the maven builds and (some) access to source is kept.
paul
On 14 oct. 2010, at 18:20, Caleb James DeLisle wrote:
Now that InvitationManager is replaced with the Invitation Application and XWorkspaces has been retired, the only "living" dependency on InvitationManager or SpaceManager is Curriki. I propose we: 1. Move these projects to contrib/retired. 2. Stop building them in Hudson.
WDYT?
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 14 oct. 2010, at 19:10, Caleb James DeLisle wrote:
Your proposal says "move Curriki to retired" ? Oops, indeed it does. I meant move only xwiki-plugin-invitationmanager and xwiki-plugin-spacemanager. My proposal is that the historical maven builds will remain and the source will still be avainable in the contrib/retired section but no new builds will be created by hudson.
But that would really mean the project curriki is retired or retiring. I think this is not correct. paul
On 10/14/2010 04:02 PM, Paul Libbrecht wrote:
On 14 oct. 2010, at 19:10, Caleb James DeLisle wrote:
Your proposal says "move Curriki to retired" ? Oops, indeed it does. I meant move only xwiki-plugin-invitationmanager and xwiki-plugin-spacemanager. My proposal is that the historical maven builds will remain and the source will still be avainable in the contrib/retired section but no new builds will be created by hudson.
But that would really mean the project curriki is retired or retiring. I think this is not correct.
If you know what I really mean then you're a better man than me ;) I just looked over my email history and I see there have been no changes to InvitationManager in over a year so continuing to build, test, and release it seems rather silly IMO. I would stress that this will not prevent Curriki from building since the existing versions will remain in maven repository. If in the future there is desire to begin maintaining the SpaceManager or InvitationManager once again, I don't see why they can't come back out of retirement. Caleb
paul _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Caleb, it must a simple interpretation story. That the spacemanager and invitationmanager plugins are retired is probably ok. I just don't curriki to be flagged behind a "retired" path-name; I find it ok that it depends on retired project. paul On 14 oct. 2010, at 22:22, Caleb James DeLisle wrote:
On 10/14/2010 04:02 PM, Paul Libbrecht wrote:
On 14 oct. 2010, at 19:10, Caleb James DeLisle wrote:
Your proposal says "move Curriki to retired" ? Oops, indeed it does. I meant move only xwiki-plugin-invitationmanager and xwiki-plugin-spacemanager. My proposal is that the historical maven builds will remain and the source will still be avainable in the contrib/retired section but no new builds will be created by hudson.
But that would really mean the project curriki is retired or retiring. I think this is not correct.
If you know what I really mean then you're a better man than me ;) I just looked over my email history and I see there have been no changes to InvitationManager in over a year so continuing to build, test, and release it seems rather silly IMO. I would stress that this will not prevent Curriki from building since the existing versions will remain in maven repository. If in the future there is desire to begin maintaining the SpaceManager or InvitationManager once again, I don't see why they can't come back out of retirement.
Caleb
paul _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 10/14/2010 10:02 PM, Paul Libbrecht wrote:
On 14 oct. 2010, at 19:10, Caleb James DeLisle wrote:
Your proposal says "move Curriki to retired" ? Oops, indeed it does. I meant move only xwiki-plugin-invitationmanager and xwiki-plugin-spacemanager. My proposal is that the historical maven builds will remain and the source will still be avainable in the contrib/retired section but no new builds will be created by hudson.
But that would really mean the project curriki is retired or retiring. I think this is not correct.
No, it means that the Curriki project is doing fine with the current versions of the plugins. And these versions are in the maven repository, and will always be there. Moving the code to the retired svn repository means just that no new development is planned for them. And, if Curriki wants to evolve, then it should upgrade to a newer version of the platform, and it should switch to components, which means new modules, not related to the plugins. -- Sergiu Dumitriu http://purl.org/net/sergiu/
On 14 oct. 2010, at 22:52, Sergiu Dumitriu wrote:
On 10/14/2010 10:02 PM, Paul Libbrecht wrote:
On 14 oct. 2010, at 19:10, Caleb James DeLisle wrote:
Your proposal says "move Curriki to retired" ? Oops, indeed it does. I meant move only xwiki-plugin-invitationmanager and xwiki-plugin-spacemanager. My proposal is that the historical maven builds will remain and the source will still be avainable in the contrib/retired section but no new builds will be created by hudson.
But that would really mean the project curriki is retired or retiring. I think this is not correct.
No, it means that the Curriki project is doing fine with the current versions of the plugins. And these versions are in the maven repository, and will always be there. Moving the code to the retired svn repository means just that no new development is planned for them. And, if Curriki wants to evolve, then it should upgrade to a newer version of the platform, and it should switch to components, which means new modules, not related to the plugins.
As I said, as long as curriki itself doesn't have paths (svn or maven) that are with retired, I'm fine. Hence here's my +1. paul
On 10/14/2010 06:20 PM, Caleb James DeLisle wrote:
Now that InvitationManager is replaced with the Invitation Application and XWorkspaces has been retired, the only "living" dependency on InvitationManager or SpaceManager is Curriki. I propose we: 1. Move these projects to contrib/retired. 2. Stop building them in Hudson.
WDYT?
+1 -- Sergiu Dumitriu http://purl.org/net/sergiu/
+1 Thanks, Marius On 10/14/2010 07:20 PM, Caleb James DeLisle wrote:
Now that InvitationManager is replaced with the Invitation Application and XWorkspaces has been retired, the only "living" dependency on InvitationManager or SpaceManager is Curriki. I propose we: 1. Move these projects to contrib/retired. 2. Stop building them in Hudson.
WDYT?
Caleb
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 On Thu, Oct 14, 2010 at 18:20, Caleb James DeLisle <[email protected]> wrote:
Now that InvitationManager is replaced with the Invitation Application and XWorkspaces has been retired, the only "living" dependency on InvitationManager or SpaceManager is Curriki. I propose we: 1. Move these projects to contrib/retired. 2. Stop building them in Hudson.
WDYT?
Caleb
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 On Thu, Oct 14, 2010 at 11:43 PM, Thomas Mortagne <[email protected]> wrote:
+1
On Thu, Oct 14, 2010 at 18:20, Caleb James DeLisle <[email protected]> wrote:
Now that InvitationManager is replaced with the Invitation Application and XWorkspaces has been retired, the only "living" dependency on InvitationManager or SpaceManager is Curriki. I propose we: 1. Move these projects to contrib/retired. 2. Stop building them in Hudson.
WDYT?
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
participants (7)
-
Caleb James DeLisle -
Jerome Velociter -
Marius Dumitru Florea -
Paul Libbrecht -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol