[xwiki-devs] Adding MS Office integration project to jira
Hi devs, We need to create a jira project for the MS Office integration. Jerome has proposed to put in "XWiki Core & Products" section, with the "*XOFFICE*" key. WDYT? The first Add-in in the suite will be the Word Add-in and is currently named *XWriter*( XWord is another option). I target the first milestone release on November 19th, and a first final version somewhere around XE 1.8 final release date. The solution also contains a project named *XWikiLib*. This is an assembly that will contain most logic for the server connection and other utilities. It might be useful for other members of the community that may want to connect to XWiki from a .NET client. Regards, Florin Ciubotaru
Hello, Florin Ciubotaru wrote:
Hi devs,
We need to create a jira project for the MS Office integration. Jerome has proposed to put in "XWiki Core & Products" section, with the "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ?
The first Add-in in the suite will be the Word Add-in and is currently named *XWriter*( XWord is another option).
I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration.
I target the first milestone release on November 19th, and a first final version somewhere around XE 1.8 final release date. FYI, the features targeted for the first final versions are described here : http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio.... Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project.
The solution also contains a project named *XWikiLib*. This is an assembly that will contain most logic for the server connection and other utilities. It might be useful for other members of the community that may want to connect to XWiki from a .NET client.
This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in). Regards, Jerome.
Regards, Florin Ciubotaru
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Hi, On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Hello,
Florin Ciubotaru wrote:
Hi devs,
We need to create a jira project for the MS Office integration. Jerome has proposed to put in "XWiki Core & Products" section, with the "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ?
I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me.
The first Add-in in the suite will be the Word Add-in and is currently named *XWriter*( XWord is another option).
I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration.
+1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
I target the first milestone release on November 19th, and a first final version somewhere around XE 1.8 final release date. FYI, the features targeted for the first final versions are described here :
http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio... . Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project.
The solution also contains a project named *XWikiLib*. This is an assembly that will contain most logic for the server connection and other utilities. It might be useful for other members of the community that may want to connect to XWiki from a .NET client.
This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in).
Regards, Jerome.
Regards, Florin Ciubotaru
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ 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/
On Oct 30, 2008, at 12:47 PM, Guillaume Lerouge wrote:
Hi,
On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Hello,
Florin Ciubotaru wrote:
Hi devs,
We need to create a jira project for the MS Office integration. Jerome has proposed to put in "XWiki Core & Products" section, with the "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ?
I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me.
No. that's not possible and not the way to do it in JIRA. Remember that one jira project = same version = same release. Thanks -Vincent
The first Add-in in the suite will be the Word Add-in and is currently named *XWriter*( XWord is another option).
I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration.
+1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
I target the first milestone release on November 19th, and a first final version somewhere around XE 1.8 final release date. FYI, the features targeted for the first final versions are described here :
http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio... . Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project.
The solution also contains a project named *XWikiLib*. This is an assembly that will contain most logic for the server connection and other utilities. It might be useful for other members of the community that may want to connect to XWiki from a .NET client.
This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in).
Regards, Jerome.
Regards, Florin Ciubotaru
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ 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/ _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Vincent Massol wrote:
On Oct 30, 2008, at 12:47 PM, Guillaume Lerouge wrote:
Hi,
On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Hello,
Florin Ciubotaru wrote:
Hi devs,
We need to create a jira project for the MS Office integration. Jerome has proposed to put in "XWiki Core & Products" section, with the "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ?
I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me.
No. that's not possible and not the way to do it in JIRA.
Remember that one jira project = same version = same release. Ah, right. And releasing them as a whole will not be really possible I guess. As well we will surely have distinct releases for word integration and eventual outlook or other MS office integration. Thus we should have separated JIRA project for each product of the suite.
What do you think about the following : * XWORD => MS Word integration * XPOFFICE => Office importer plugin Concerning the XWiki .net assembly, I don't have much idea. XDOTNET ? Jerome.
Thanks -Vincent
The first Add-in in the suite will be the Word Add-in and is currently named *XWriter*( XWord is another option). I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration.
+1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
I target the first milestone release on November 19th, and a first final version somewhere around XE 1.8 final release date. FYI, the features targeted for the first final versions are described here :
http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio... . Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project.
The solution also contains a project named *XWikiLib*. This is an assembly that will contain most logic for the server connection and other utilities. It might be useful for other members of the community that may want to connect to XWiki from a .NET client. This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in).
Regards, Jerome.
Regards, Florin Ciubotaru
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
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/ _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Jerome Velociter wrote:
Vincent Massol wrote:
On Oct 30, 2008, at 12:47 PM, Guillaume Lerouge wrote:
Hi,
On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Hello,
Florin Ciubotaru wrote:
Hi devs,
We need to create a jira project for the MS Office integration. Jerome has proposed to put in "XWiki Core & Products" section, with the "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ? I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me. No. that's not possible and not the way to do it in JIRA.
Remember that one jira project = same version = same release. Ah, right. And releasing them as a whole will not be really possible I guess. As well we will surely have distinct releases for word integration and eventual outlook or other MS office integration. Thus we should have separated JIRA project for each product of the suite.
What do you think about the following :
* XWORD => MS Word integration * XPOFFICE => Office importer plugin
No screams ? Is it ok we create the XWORD project in JIRA ? (the key cannot be changed once the project is created...) Jerome.
Concerning the XWiki .net assembly, I don't have much idea. XDOTNET ?
Jerome.
Thanks -Vincent
The first Add-in in the suite will be the Word Add-in and is currently named *XWriter*( XWord is another option). I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration. +1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
I target the first milestone release on November 19th, and a first final version somewhere around XE 1.8 final release date. FYI, the features targeted for the first final versions are described here :
http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio... . Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project.
The solution also contains a project named *XWikiLib*. This is an assembly that will contain most logic for the server connection and other utilities. It might be useful for other members of the community that may want to connect to XWiki from a .NET client. This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in).
Regards, Jerome.
Regards, Florin Ciubotaru
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
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/ _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Jerome Velociter wrote:
Jerome Velociter wrote:
Vincent Massol wrote:
On Oct 30, 2008, at 12:47 PM, Guillaume Lerouge wrote:
Hi,
On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Hello,
Florin Ciubotaru wrote:
Hi devs,
We need to create a jira project for the MS Office integration. Jerome has proposed to put in "XWiki Core & Products" section, with the "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ? I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me. No. that's not possible and not the way to do it in JIRA.
Remember that one jira project = same version = same release. Ah, right. And releasing them as a whole will not be really possible I guess. As well we will surely have distinct releases for word integration and eventual outlook or other MS office integration. Thus we should have separated JIRA project for each product of the suite.
What do you think about the following :
* XWORD => MS Word integration * XPOFFICE => Office importer plugin
No screams ? Is it ok we create the XWORD project in JIRA ? (the key cannot be changed once the project is created...)
Jerome.
But the option remains to delete the whole project, right? ;) Maybe a name that would suggest the fact that it's an addin suite? Right now, I wouldn't know how to differentiate between the two and they are, in fact different things (afaiu). So, I'd go for XMSADDINS (or XWORDADDIN), as a project and all inside as components. I think that could be good enough as the main feature would be the various addins (just msword for the moment) which heavily depends on the XDotNetLib API, so development and release will be done together anyway. Otherwise, we might be creating a too elaborate structure for it. Of course, when releasing we might make the XDotNetLib available for download separately someway, for developers (which are advanced users) to get it and use it. We need to analyze a bit the download / usage use-cases: 1/ if we do all these for the msword addin then one proj with components is well enough (I'd say) 2/ if we do it for the .NET api / lib, then 2 projects sound better. 3/ we do it to have a whole ms suite of addins. I think 1/ is the case (but it's not my call) so I'd go for a single project. In the case of 3/ we could think about a single project, with single download and single install, with options for each if its features (the xwiki ms office addins suite). Happy coding, regardless of the platform, Anca
Concerning the XWiki .net assembly, I don't have much idea. XDOTNET ?
Jerome.
Thanks -Vincent
The first Add-in in the suite will be the Word Add-in and is currently named *XWriter*( XWord is another option). I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration. +1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
I target the first milestone release on November 19th, and a first final version somewhere around XE 1.8 final release date. FYI, the features targeted for the first final versions are described here :
http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio... . Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project.
The solution also contains a project named *XWikiLib*. This is an assembly that will contain most logic for the server connection and other utilities. It might be useful for other members of the community that may want to connect to XWiki from a .NET client. This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in).
Regards, Jerome.
Regards, Florin Ciubotaru
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
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/ _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Anca Paula Luca wrote:
Jerome Velociter wrote:
Jerome Velociter wrote:
Vincent Massol wrote:
On Oct 30, 2008, at 12:47 PM, Guillaume Lerouge wrote:
Hi,
On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Hello,
Florin Ciubotaru wrote: > Hi devs, > > We need to create a jira project for the MS Office integration. > Jerome > has proposed to put in "XWiki Core & Products" section, with the > "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ? I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me. No. that's not possible and not the way to do it in JIRA.
Remember that one jira project = same version = same release. Ah, right. And releasing them as a whole will not be really possible I guess. As well we will surely have distinct releases for word integration and eventual outlook or other MS office integration. Thus we should have separated JIRA project for each product of the suite.
What do you think about the following :
* XWORD => MS Word integration * XPOFFICE => Office importer plugin No screams ? Is it ok we create the XWORD project in JIRA ? (the key cannot be changed once the project is created...)
Jerome.
But the option remains to delete the whole project, right? ;)
Maybe a name that would suggest the fact that it's an addin suite? Right now, I wouldn't know how to differentiate between the two and they are, in fact different things (afaiu). So, I'd go for XMSADDINS (or XWORDADDIN), as a project and all inside as components. I think that could be good enough as the main feature would be the various addins (just msword for the moment) which heavily depends on the XDotNetLib API, so development and release will be done together anyway.
Probably not once any longer at the moment there is more than one add-in. Anyway I agree for now the API could go in the same project as the Word add-in, and we'll extract it to its own the day we need/want to release it separately (when we have another add-in for example). I would still go for XWORD. XWORDADDIN or XMSWORD work as well, but are less easy to rememnber. We could thinko of a prefix for extensions as well, as we have XP for plugins, XS for skins and XA for applications. It could be XI, for "XWiki Integration". (But it is too late for XEclipse anyway). Right now, I'm +1 for XWORD. Jerome.
Otherwise, we might be creating a too elaborate structure for it. Of course, when releasing we might make the XDotNetLib available for download separately someway, for developers (which are advanced users) to get it and use it. We need to analyze a bit the download / usage use-cases: 1/ if we do all these for the msword addin then one proj with components is well enough (I'd say) 2/ if we do it for the .NET api / lib, then 2 projects sound better. 3/ we do it to have a whole ms suite of addins.
I think 1/ is the case (but it's not my call) so I'd go for a single project.
In the case of 3/ we could think about a single project, with single download and single install, with options for each if its features (the xwiki ms office addins suite).
Happy coding, regardless of the platform, Anca
Concerning the XWiki .net assembly, I don't have much idea. XDOTNET ?
Jerome.
Thanks -Vincent
> The first Add-in in the suite will be the Word Add-in and is > currently > named *XWriter*( XWord is another option). I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration. +1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
> I target the first milestone > release on November 19th, and a first final version somewhere > around XE > 1.8 final release date. FYI, the features targeted for the first final versions are described here :
http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio... . Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project. > The solution also contains a project named *XWikiLib*. This is an > assembly that will contain most logic for the server connection and > other utilities. It might be useful for other members of the > community > that may want to connect to XWiki from a .NET client. This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in).
Regards, Jerome. > Regards, > Florin Ciubotaru > > > _______________________________________________ > devs mailing list > devs@xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ 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/ _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Jerome Velociter wrote:
Anca Paula Luca wrote:
Jerome Velociter wrote:
Jerome Velociter wrote:
Vincent Massol wrote:
On Oct 30, 2008, at 12:47 PM, Guillaume Lerouge wrote:
Hi,
On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
> Hello, > > Florin Ciubotaru wrote: >> Hi devs, >> >> We need to create a jira project for the MS Office integration. >> Jerome >> has proposed to put in "XWiki Core & Products" section, with the >> "*XOFFICE*" key. WDYT? > I'm thinking about the Office integration as we have today the > Eclipse > integration, thus the idea of the XOffice key. > > A question remain : should the office importer project also be part > of > the Office integration JIRA project ? I think it's ok for now, it > could > be a component of the project, as the microsoft addin would be. If > it's > not ok, then XOFFICE might not be the best name, it should then > reflect > the MS Office suite. XMSOFFICE ? I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me. No. that's not possible and not the way to do it in JIRA.
Remember that one jira project = same version = same release. Ah, right. And releasing them as a whole will not be really possible I guess. As well we will surely have distinct releases for word integration and eventual outlook or other MS office integration. Thus we should have separated JIRA project for each product of the suite.
What do you think about the following :
* XWORD => MS Word integration * XPOFFICE => Office importer plugin No screams ? Is it ok we create the XWORD project in JIRA ? (the key cannot be changed once the project is created...)
Jerome. But the option remains to delete the whole project, right? ;)
Maybe a name that would suggest the fact that it's an addin suite? Right now, I wouldn't know how to differentiate between the two and they are, in fact different things (afaiu). So, I'd go for XMSADDINS (or XWORDADDIN), as a project and all inside as components. I think that could be good enough as the main feature would be the various addins (just msword for the moment) which heavily depends on the XDotNetLib API, so development and release will be done together anyway.
Probably not once any longer at the moment there is more than one add-in. Anyway I agree for now the API could go in the same project as the Word add-in, and we'll extract it to its own the day we need/want to release it separately (when we have another add-in for example).
I would still go for XWORD. XWORDADDIN or XMSWORD work as well, but are less easy to rememnber.
We could thinko of a prefix for extensions as well, as we have XP for plugins, XS for skins and XA for applications. It could be XI, for "XWiki Integration". (But it is too late for XEclipse anyway).
Right now, I'm +1 for XWORD.
I created http://jira.xwiki.org/jira/browse/XWORD Florin will add the components, first version with target date, and initial issue(s) Jerome.
Jerome.
Otherwise, we might be creating a too elaborate structure for it. Of course, when releasing we might make the XDotNetLib available for download separately someway, for developers (which are advanced users) to get it and use it. We need to analyze a bit the download / usage use-cases: 1/ if we do all these for the msword addin then one proj with components is well enough (I'd say) 2/ if we do it for the .NET api / lib, then 2 projects sound better. 3/ we do it to have a whole ms suite of addins.
I think 1/ is the case (but it's not my call) so I'd go for a single project.
In the case of 3/ we could think about a single project, with single download and single install, with options for each if its features (the xwiki ms office addins suite).
Happy coding, regardless of the platform, Anca
Concerning the XWiki .net assembly, I don't have much idea. XDOTNET ?
Jerome.
Thanks -Vincent
>> The first Add-in in the suite will be the Word Add-in and is >> currently >> named *XWriter*( XWord is another option). > I think XWord is a better name, it let us the possibility to have > XWriter for a future possible OOo integration. +1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
>> I target the first milestone >> release on November 19th, and a first final version somewhere >> around XE >> 1.8 final release date. > FYI, the features targeted for the first final versions are described > here : > > http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio... > . > Namely : > " > * Users will be able to create a new wiki page from Office(Word > works as an WYSIWYG using WebView to directly create HTML) > * Users can upload a local document to the wiki, as an attachment > * Users can export a local file as a wiki page. > " > > XE 1.8 should happen somewhere around the end of February 2009. Now > you > should propose a breakdown of the features in this roadmap for the > 1.0 > version in several milestones. I think 3 milestones of 3/4 weeks > each is > good for the 1.0 cycle - keeping in mind we want to be able to ship > it > with XE 1.8 (this way, remains 3/4 weeks for debugging in releases > candidates phases) and keeping in mind too that you are working > only 50% > of your time on this project. >> The solution also contains a project named *XWikiLib*. This is an >> assembly that will contain most logic for the server connection and >> other utilities. It might be useful for other members of the >> community >> that may want to connect to XWiki from a .NET client. > This assembly should live in its own project, right ? It source code > should also be separated from the actual office integration (the > add-in). > > Regards, > Jerome. >> Regards, >> Florin Ciubotaru >> >> >> _______________________________________________ >> devs mailing list >> devs@xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ > 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/ _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
On Thu, Oct 30, 2008 at 5:55 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Vincent Massol wrote:
On Oct 30, 2008, at 12:47 PM, Guillaume Lerouge wrote:
Hi,
On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Hello,
Florin Ciubotaru wrote:
Hi devs,
We need to create a jira project for the MS Office integration. Jerome has proposed to put in "XWiki Core & Products" section, with the "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ?
I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me.
No. that's not possible and not the way to do it in JIRA.
Remember that one jira project = same version = same release. Ah, right. And releasing them as a whole will not be really possible I guess. As well we will surely have distinct releases for word integration and eventual outlook or other MS office integration. Thus we should have separated JIRA project for each product of the suite.
What do you think about the following :
* XWORD => MS Word integration * XPOFFICE => Office importer plugin
I think office importer should have the XOFFICE code name. Because office-importer surpasses all office suits (MsOffice, OpenOffice, StarOffice) and formats. Thanks. - Asiri
Concerning the XWiki .net assembly, I don't have much idea. XDOTNET ?
Jerome.
Thanks -Vincent
The first Add-in in the suite will be the Word Add-in and is currently named *XWriter*( XWord is another option). I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration.
+1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
I target the first milestone release on November 19th, and a first final version somewhere around XE 1.8 final release date. FYI, the features targeted for the first final versions are described here :
http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio...
. Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project.
The solution also contains a project named *XWikiLib*. This is an assembly that will contain most logic for the server connection and other utilities. It might be useful for other members of the community that may want to connect to XWiki from a .NET client. This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in).
Regards, Jerome.
Regards, Florin Ciubotaru
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
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/ _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
On Oct 31, 2008, at 6:46 PM, Asiri Rathnayake wrote:
On Thu, Oct 30, 2008 at 5:55 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Vincent Massol wrote:
On Oct 30, 2008, at 12:47 PM, Guillaume Lerouge wrote:
Hi,
On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Hello,
Florin Ciubotaru wrote:
Hi devs,
We need to create a jira project for the MS Office integration. Jerome has proposed to put in "XWiki Core & Products" section, with the "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ?
I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me.
No. that's not possible and not the way to do it in JIRA.
Remember that one jira project = same version = same release. Ah, right. And releasing them as a whole will not be really possible I guess. As well we will surely have distinct releases for word integration and eventual outlook or other MS office integration. Thus we should have separated JIRA project for each product of the suite.
What do you think about the following :
* XWORD => MS Word integration * XPOFFICE => Office importer plugin
I think office importer should have the XOFFICE code name. Because office-importer surpasses all office suits (MsOffice, OpenOffice, StarOffice) and formats.
XP means XWiki Plugin... However it's not just a plugin but an application and for now we've decided to have only 1 JIRA project for both application and plugin so it should be XAOFFICE instead... ;) Thanks -Vincent
Concerning the XWiki .net assembly, I don't have much idea. XDOTNET ?
Jerome.
Thanks -Vincent
The first Add-in in the suite will be the Word Add-in and is currently named *XWriter*( XWord is another option). I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration.
+1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
I target the first milestone release on November 19th, and a first final version somewhere around XE 1.8 final release date. FYI, the features targeted for the first final versions are described here :
http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio...
. Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project.
The solution also contains a project named *XWikiLib*. This is an assembly that will contain most logic for the server connection and other utilities. It might be useful for other members of the community that may want to connect to XWiki from a .NET client. This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in).
Regards, Jerome.
Regards, Florin Ciubotaru
On Fri, Oct 31, 2008 at 11:34 PM, Vincent Massol <vincent@massol.net> wrote:
On Oct 31, 2008, at 6:46 PM, Asiri Rathnayake wrote:
On Thu, Oct 30, 2008 at 5:55 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Vincent Massol wrote:
On Oct 30, 2008, at 12:47 PM, Guillaume Lerouge wrote:
Hi,
On Thu, Oct 30, 2008 at 12:39 PM, Jerome Velociter <jerome@xwiki.com> wrote:
Hello,
Florin Ciubotaru wrote: > Hi devs, > > We need to create a jira project for the MS Office integration. > Jerome > has proposed to put in "XWiki Core & Products" section, with the > "*XOFFICE*" key. WDYT? I'm thinking about the Office integration as we have today the Eclipse integration, thus the idea of the XOffice key.
A question remain : should the office importer project also be part of the Office integration JIRA project ? I think it's ok for now, it could be a component of the project, as the microsoft addin would be. If it's not ok, then XOFFICE might not be the best name, it should then reflect the MS Office suite. XMSOFFICE ?
I think they should both be part of the same project, separated as JIRA components, so keeping XOFFICE is fine with me.
No. that's not possible and not the way to do it in JIRA.
Remember that one jira project = same version = same release. Ah, right. And releasing them as a whole will not be really possible I guess. As well we will surely have distinct releases for word integration and eventual outlook or other MS office integration. Thus we should have separated JIRA project for each product of the suite.
What do you think about the following :
* XWORD => MS Word integration * XPOFFICE => Office importer plugin
I think office importer should have the XOFFICE code name. Because office-importer surpasses all office suits (MsOffice, OpenOffice, StarOffice) and formats.
XP means XWiki Plugin...
However it's not just a plugin but an application and for now we've decided to have only 1 JIRA project for both application and plugin so it should be XAOFFICE instead... ;)
Sounds good :) Thanks. - Asiri
Thanks -Vincent
Concerning the XWiki .net assembly, I don't have much idea. XDOTNET ?
Jerome.
Thanks -Vincent
> The first Add-in in the suite will be the Word Add-in and is > currently > named *XWriter*( XWord is another option). I think XWord is a better name, it let us the possibility to have XWriter for a future possible OOo integration.
+1 for XWord for MSWord and thus XWriter for OOo Writer at a later stage.
> I target the first milestone > release on November 19th, and a first final version somewhere > around XE > 1.8 final release date. FYI, the features targeted for the first final versions are described here :
http://dev.xwiki.org/xwiki/bin/view/Design/MicrosoftOfficeAddin#HFirstversio...
. Namely : " * Users will be able to create a new wiki page from Office(Word works as an WYSIWYG using WebView to directly create HTML) * Users can upload a local document to the wiki, as an attachment * Users can export a local file as a wiki page. "
XE 1.8 should happen somewhere around the end of February 2009. Now you should propose a breakdown of the features in this roadmap for the 1.0 version in several milestones. I think 3 milestones of 3/4 weeks each is good for the 1.0 cycle - keeping in mind we want to be able to ship it with XE 1.8 (this way, remains 3/4 weeks for debugging in releases candidates phases) and keeping in mind too that you are working only 50% of your time on this project. > The solution also contains a project named *XWikiLib*. This is an > assembly that will contain most logic for the server connection > and > other utilities. It might be useful for other members of the > community > that may want to connect to XWiki from a .NET client. This assembly should live in its own project, right ? It source code should also be separated from the actual office integration (the add-in).
Regards, Jerome. > Regards, > Florin Ciubotaru
devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
participants (6)
-
Anca Paula Luca -
Asiri Rathnayake -
Florin Ciubotaru -
Guillaume Lerouge -
Jerome Velociter -
Vincent Massol