[xwiki-devs] Location, release cycle and distribution of non core macros 2.0
Hello devs, This week we created a new "xwiki-macros" module under platform/core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro. Possibilities I see : 1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core I am for solution 1 right now, but maybe there are better alternatives to this, too. We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE) Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1. Jerome.
On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter <[email protected]> wrote:
Hello devs,
This week we created a new "xwiki-macros" module under platform/core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro.
Possibilities I see :
1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core
I am for solution 1 right now, but maybe there are better alternatives to this, too.
We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE)
Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1.
+1 for 2. especially if we plan to distribute them with XE. Anyway having them in core/xwiki-macros does not means it is automatically in the "basic working wiki" and all the macros we officially support should be in the same place IMO.
Jerome. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Thomas Mortagne wrote:
On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter <[email protected]> wrote:
Hello devs,
This week we created a new "xwiki-macros" module under platform/core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro.
Possibilities I see :
1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core
I am for solution 1 right now, but maybe there are better alternatives to this, too.
We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE)
Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1.
+1 for 2. especially if we plan to distribute them with XE. Anyway having them in core/xwiki-macros does not means it is automatically in the "basic working wiki" and all the macros we officially support should be in the same place IMO.
I gave it more thoughts, and I think I agree with Thomas. I think it's better to have the macros we plan to officially support in one place. Plus, if we bundle them by default with XE, having them in core together with the other macros would prevent us of having to state the dependency explicitly at XE level, as we have to do for plugins that are in platform/plugins/ for example. Jerome.
Jerome. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Nov 25, 2008, at 10:43 AM, Jerome Velociter wrote:
Thomas Mortagne wrote:
On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter <[email protected]> wrote:
Hello devs,
This week we created a new "xwiki-macros" module under platform/ core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro.
Possibilities I see :
1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core
I am for solution 1 right now, but maybe there are better alternatives to this, too.
We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE)
Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1.
+1 for 2. especially if we plan to distribute them with XE. Anyway having them in core/xwiki-macros does not means it is automatically in the "basic working wiki" and all the macros we officially support should be in the same place IMO.
I gave it more thoughts, and I think I agree with Thomas. I think it's better to have the macros we plan to officially support in one place. Plus, if we bundle them by default with XE, having them in core together with the other macros would prevent us of having to state the dependency explicitly at XE level, as we have to do for plugins that are in platform/plugins/ for example.
I'm not sure if this is right. It might be ok for now since we don't have a lot. But very soon we'll have some macro that are not ready to be released or that are a bit "exotic" (I'm not sure for the map macro) or that have a different release cycle (it's a pain to have to wait 3 months to release a macro that is ready for consumption for ex). For me this is exactly similar to plugins. We don't release them all when we do a XE release. -Vincent
Vincent Massol wrote:
On Nov 25, 2008, at 10:43 AM, Jerome Velociter wrote:
Thomas Mortagne wrote:
On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter <[email protected]> wrote:
Hello devs,
This week we created a new "xwiki-macros" module under platform/ core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro.
Possibilities I see :
1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core
I am for solution 1 right now, but maybe there are better alternatives to this, too.
We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE)
Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1. +1 for 2. especially if we plan to distribute them with XE. Anyway having them in core/xwiki-macros does not means it is automatically in the "basic working wiki" and all the macros we officially support should be in the same place IMO. I gave it more thoughts, and I think I agree with Thomas. I think it's better to have the macros we plan to officially support in one place. Plus, if we bundle them by default with XE, having them in core together with the other macros would prevent us of having to state the dependency explicitly at XE level, as we have to do for plugins that are in platform/plugins/ for example.
I'm not sure if this is right. It might be ok for now since we don't have a lot. But very soon we'll have some macro that are not ready to be released or that are a bit "exotic" (I'm not sure for the map macro) or that have a different release cycle (it's a pain to have to wait 3 months to release a macro that is ready for consumption for ex). For me this is exactly similar to plugins. We don't release them all when we do a XE release.
Yes, I agree we will need an other macro repository at some point anyway. I propose I commit the map macro in platform/core/macros/ for now, and move it to this new repo when we start feeling the need, WDYT ? Jerome.
-Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Nov 25, 2008, at 11:08 AM, Jerome Velociter wrote:
Vincent Massol wrote:
On Nov 25, 2008, at 10:43 AM, Jerome Velociter wrote:
Thomas Mortagne wrote:
On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter <[email protected]> wrote:
Hello devs,
This week we created a new "xwiki-macros" module under platform/ core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro.
Possibilities I see :
1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core
I am for solution 1 right now, but maybe there are better alternatives to this, too.
We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE)
Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1. +1 for 2. especially if we plan to distribute them with XE. Anyway having them in core/xwiki-macros does not means it is automatically in the "basic working wiki" and all the macros we officially support should be in the same place IMO. I gave it more thoughts, and I think I agree with Thomas. I think it's better to have the macros we plan to officially support in one place. Plus, if we bundle them by default with XE, having them in core together with the other macros would prevent us of having to state the dependency explicitly at XE level, as we have to do for plugins that are in platform/plugins/ for example.
I'm not sure if this is right. It might be ok for now since we don't have a lot. But very soon we'll have some macro that are not ready to be released or that are a bit "exotic" (I'm not sure for the map macro) or that have a different release cycle (it's a pain to have to wait 3 months to release a macro that is ready for consumption for ex). For me this is exactly similar to plugins. We don't release them all when we do a XE release.
Yes, I agree we will need an other macro repository at some point anyway. I propose I commit the map macro in platform/core/macros/ for now, and move it to this new repo when we start feeling the need, WDYT ?
ok for me, but provided the macro is fully working for 1.7 final (with tests). Thanks -Vincent
On Tue, Nov 25, 2008 at 10:51 AM, Vincent Massol <[email protected]> wrote:
On Nov 25, 2008, at 10:43 AM, Jerome Velociter wrote:
Thomas Mortagne wrote:
On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter <[email protected]> wrote:
Hello devs,
This week we created a new "xwiki-macros" module under platform/ core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro.
Possibilities I see :
1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core
I am for solution 1 right now, but maybe there are better alternatives to this, too.
We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE)
Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1.
+1 for 2. especially if we plan to distribute them with XE. Anyway having them in core/xwiki-macros does not means it is automatically in the "basic working wiki" and all the macros we officially support should be in the same place IMO.
I gave it more thoughts, and I think I agree with Thomas. I think it's better to have the macros we plan to officially support in one place. Plus, if we bundle them by default with XE, having them in core together with the other macros would prevent us of having to state the dependency explicitly at XE level, as we have to do for plugins that are in platform/plugins/ for example.
I'm not sure if this is right. It might be ok for now since we don't have a lot. But very soon we'll have some macro that are not ready to be released or that are a bit "exotic" (I'm not sure for the map macro) or that have a different release cycle (it's a pain to have to wait 3 months to release a macro that is ready for consumption for ex). For me this is exactly similar to plugins. We don't release them all when we do a XE release.
This is not describing a macro we officially support IMO. Such macro should always work or we consider this as a contrib even if it has been done by us at first and it will goes with other contrib macros.
-Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Nov 25, 2008, at 12:07 PM, Thomas Mortagne wrote:
On Tue, Nov 25, 2008 at 10:51 AM, Vincent Massol <[email protected]> wrote:
On Nov 25, 2008, at 10:43 AM, Jerome Velociter wrote:
Thomas Mortagne wrote:
On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter <[email protected]> wrote:
Hello devs,
This week we created a new "xwiki-macros" module under platform/ core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro.
Possibilities I see :
1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core
I am for solution 1 right now, but maybe there are better alternatives to this, too.
We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE)
Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1.
+1 for 2. especially if we plan to distribute them with XE. Anyway having them in core/xwiki-macros does not means it is automatically in the "basic working wiki" and all the macros we officially support should be in the same place IMO.
I gave it more thoughts, and I think I agree with Thomas. I think it's better to have the macros we plan to officially support in one place. Plus, if we bundle them by default with XE, having them in core together with the other macros would prevent us of having to state the dependency explicitly at XE level, as we have to do for plugins that are in platform/plugins/ for example.
I'm not sure if this is right. It might be ok for now since we don't have a lot. But very soon we'll have some macro that are not ready to be released or that are a bit "exotic" (I'm not sure for the map macro) or that have a different release cycle (it's a pain to have to wait 3 months to release a macro that is ready for consumption for ex). For me this is exactly similar to plugins. We don't release them all when we do a XE release.
This is not describing a macro we officially support IMO. Such macro should always work or we consider this as a contrib even if it has been done by us at first and it will goes with other contrib macros.
Again why are we not releasing all plugins at the same time then? Thanks -Vincent
On Tue, Nov 25, 2008 at 12:13 PM, Vincent Massol <[email protected]> wrote:
On Nov 25, 2008, at 12:07 PM, Thomas Mortagne wrote:
On Tue, Nov 25, 2008 at 10:51 AM, Vincent Massol <[email protected]> wrote:
On Nov 25, 2008, at 10:43 AM, Jerome Velociter wrote:
Thomas Mortagne wrote:
On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter <[email protected]> wrote:
Hello devs,
This week we created a new "xwiki-macros" module under platform/ core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro.
Possibilities I see :
1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core
I am for solution 1 right now, but maybe there are better alternatives to this, too.
We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE)
Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1.
+1 for 2. especially if we plan to distribute them with XE. Anyway having them in core/xwiki-macros does not means it is automatically in the "basic working wiki" and all the macros we officially support should be in the same place IMO.
I gave it more thoughts, and I think I agree with Thomas. I think it's better to have the macros we plan to officially support in one place. Plus, if we bundle them by default with XE, having them in core together with the other macros would prevent us of having to state the dependency explicitly at XE level, as we have to do for plugins that are in platform/plugins/ for example.
I'm not sure if this is right. It might be ok for now since we don't have a lot. But very soon we'll have some macro that are not ready to be released or that are a bit "exotic" (I'm not sure for the map macro) or that have a different release cycle (it's a pain to have to wait 3 months to release a macro that is ready for consumption for ex). For me this is exactly similar to plugins. We don't release them all when we do a XE release.
This is not describing a macro we officially support IMO. Such macro should always work or we consider this as a contrib even if it has been done by us at first and it will goes with other contrib macros.
Again why are we not releasing all plugins at the same time then?
We planned to replace all plugins with core component actually...
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Nov 25, 2008, at 12:16 PM, Thomas Mortagne wrote:
On Tue, Nov 25, 2008 at 12:13 PM, Vincent Massol <[email protected]> wrote:
On Nov 25, 2008, at 12:07 PM, Thomas Mortagne wrote:
On Tue, Nov 25, 2008 at 10:51 AM, Vincent Massol <[email protected]> wrote:
On Nov 25, 2008, at 10:43 AM, Jerome Velociter wrote:
Thomas Mortagne wrote:
On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter <[email protected]> wrote: > Hello devs, > > This week we created a new "xwiki-macros" module under platform/ > core/ > for macros of the XWiki Syntax 2.0. Another question now is what > do we > do for macros that are not "core macros" (i.e. not indispensable > for > what we consider being the basic working wiki, unlike the TOC > macro, or > the velocity macro). Development of such macros already started, > for > example the instant messenger status macro, and the map macro. > > Possibilities I see : > > 1. having them at the same level we have applications/ plugins/ > under > platform : adding a macros/ directory. > 2. having them in the xwiki-macros core submodule, despite the > fact they > are not core > > I am for solution 1 right now, but maybe there are better > alternatives > to this, too. > > We also have to decide how we do release and distribute them, > for > example do we pack them with XE, or do we release them > separately, > and > let users install them themselves as it is the case for most of > the > applications already. (For me the answer to this latest question > seems > obvious : we _should_ send them together with XE) > > Let me know what you think, I'd like if still possible having > the > map > macro in 1.7 RC1.
+1 for 2. especially if we plan to distribute them with XE. Anyway having them in core/xwiki-macros does not means it is automatically in the "basic working wiki" and all the macros we officially support should be in the same place IMO.
I gave it more thoughts, and I think I agree with Thomas. I think it's better to have the macros we plan to officially support in one place. Plus, if we bundle them by default with XE, having them in core together with the other macros would prevent us of having to state the dependency explicitly at XE level, as we have to do for plugins that are in platform/plugins/ for example.
I'm not sure if this is right. It might be ok for now since we don't have a lot. But very soon we'll have some macro that are not ready to be released or that are a bit "exotic" (I'm not sure for the map macro) or that have a different release cycle (it's a pain to have to wait 3 months to release a macro that is ready for consumption for ex). For me this is exactly similar to plugins. We don't release them all when we do a XE release.
This is not describing a macro we officially support IMO. Such macro should always work or we consider this as a contrib even if it has been done by us at first and it will goes with other contrib macros.
Again why are we not releasing all plugins at the same time then?
We planned to replace all plugins with core component actually...
Yes and the question will be the same. I think there'll be core components and non core components and some components will have their own release lifecycle IMO. -Vincent
Vincent Massol wrote:
On Nov 25, 2008, at 12:16 PM, Thomas Mortagne wrote:
On Tue, Nov 25, 2008 at 12:13 PM, Vincent Massol <[email protected]> wrote:
On Nov 25, 2008, at 12:07 PM, Thomas Mortagne wrote:
On Tue, Nov 25, 2008 at 10:51 AM, Vincent Massol <[email protected]> wrote:
On Nov 25, 2008, at 10:43 AM, Jerome Velociter wrote:
Thomas Mortagne wrote: > On Tue, Nov 18, 2008 at 10:50 PM, Jerome Velociter > <[email protected]> wrote: >> Hello devs, >> >> This week we created a new "xwiki-macros" module under platform/ >> core/ >> for macros of the XWiki Syntax 2.0. Another question now is what >> do we >> do for macros that are not "core macros" (i.e. not indispensable >> for >> what we consider being the basic working wiki, unlike the TOC >> macro, or >> the velocity macro). Development of such macros already started, >> for >> example the instant messenger status macro, and the map macro. >> >> Possibilities I see : >> >> 1. having them at the same level we have applications/ plugins/ >> under >> platform : adding a macros/ directory. >> 2. having them in the xwiki-macros core submodule, despite the >> fact they >> are not core >> >> I am for solution 1 right now, but maybe there are better >> alternatives >> to this, too. >> >> We also have to decide how we do release and distribute them, >> for >> example do we pack them with XE, or do we release them >> separately, >> and >> let users install them themselves as it is the case for most of >> the >> applications already. (For me the answer to this latest question >> seems >> obvious : we _should_ send them together with XE) >> >> Let me know what you think, I'd like if still possible having >> the >> map >> macro in 1.7 RC1. > +1 for 2. especially if we plan to distribute them with XE. > Anyway > having them in core/xwiki-macros does not means it is > automatically > in > the "basic working wiki" and all the macros we officially support > should be in the same place IMO. I gave it more thoughts, and I think I agree with Thomas. I think it's better to have the macros we plan to officially support in one place. Plus, if we bundle them by default with XE, having them in core together with the other macros would prevent us of having to state the dependency explicitly at XE level, as we have to do for plugins that are in platform/plugins/ for example. I'm not sure if this is right. It might be ok for now since we don't have a lot. But very soon we'll have some macro that are not ready to be released or that are a bit "exotic" (I'm not sure for the map macro) or that have a different release cycle (it's a pain to have to wait 3 months to release a macro that is ready for consumption for ex). For me this is exactly similar to plugins. We don't release them all when we do a XE release. This is not describing a macro we officially support IMO. Such macro should always work or we consider this as a contrib even if it has been done by us at first and it will goes with other contrib macros. Again why are we not releasing all plugins at the same time then? We planned to replace all plugins with core component actually...
Yes and the question will be the same. I think there'll be core components and non core components and some components will have their own release lifecycle IMO.
And in the far far away future, each component will be released when it's ready, and be automatically picked by the awesome AutoUpdater XWiki application. We will only do product releases every once in a while when we gather enough changes. -- Sergiu Dumitriu http://purl.org/net/sergiu/
On Nov 18, 2008, at 10:50 PM, Jerome Velociter wrote:
Hello devs,
This week we created a new "xwiki-macros" module under platform/core/ for macros of the XWiki Syntax 2.0. Another question now is what do we do for macros that are not "core macros" (i.e. not indispensable for what we consider being the basic working wiki, unlike the TOC macro, or the velocity macro). Development of such macros already started, for example the instant messenger status macro, and the map macro.
Possibilities I see :
1. having them at the same level we have applications/ plugins/ under platform : adding a macros/ directory. 2. having them in the xwiki-macros core submodule, despite the fact they are not core
I am for solution 1 right now, but maybe there are better alternatives to this, too.
+1 for 1 I think (but I need to think more about it). The important part is the release cycle. Right now we handle this differentiating platform from core and core is released as a single block. Thanks -Vincent
We also have to decide how we do release and distribute them, for example do we pack them with XE, or do we release them separately, and let users install them themselves as it is the case for most of the applications already. (For me the answer to this latest question seems obvious : we _should_ send them together with XE)
Let me know what you think, I'd like if still possible having the map macro in 1.7 RC1.
Jerome.
participants (4)
-
Jerome Velociter -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol