You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by Florian Müller <fm...@opentext.com> on 2010/04/30 00:50:59 UTC
OpenCMIS release check list
Hi,
At the face-to-face meeting we gave us two weeks for the discussed changes and then start the release process. It's about time now.
Let's see where we are:
- code formatting ... done (?)
- PagingList refactoring ... done (?)
- new server SPI ... done
- local binding implementation ... done
- query parser integration ... done (?)
- extract type manager ... not started yet
- adapt basic documentation ... started, but still a lot to do
- web site update (as source of the documentation to be packaged) ... not started yet
- retire the old code streams and provide migration hints ... not done
Based on this, what's our timeline and who does what and when?
I sign up for the documentation adjustments.
Cheers,
Florian
RE: OpenCMIS release check list
Posted by Florian Müller <fm...@opentext.com>.
I like C) best.
What else has to be discussed regarding this refactoring task?
- Florian
-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
Sent: Freitag, 30. April 2010 11:32
To: chemistry-dev@incubator.apache.org
Subject: RE: OpenCMIS release check list
Hi,
>> - PagingList refactoring ... done (?)
>
> Initial scope of refactor is done. But there's another round of refactor todo after mailing list discussion. >>Don't know who's assigned to do that - either myself or Stephan?
I can do that. But we have to decide on the naming:
A) PagingIterable (as it is for now)
B) SkipableIterable (proposed by Florent)
C) ItemIterable (proposed by me)
D) other
Do we get an consensus on that?
Stephan
-----Original Message-----
From: David Caruana [mailto:david.caruana@alfresco.com]
Sent: Freitag, 30. April 2010 10:22
To: chemistry-dev@incubator.apache.org
Subject: Re: OpenCMIS release check list
> - code formatting ... done (?)
Done
> - PagingList refactoring ... done (?)
Initial scope of refactor is done. But there's another round of refactor todo after mailing list discussion. Don't know who's assigned to do that - either myself or Stephan?
> - web site update (as source of the documentation to be packaged) ... not started yet
I can now confirm that Alfresco can provide someone to design/provide a skin for the web site.
> - retire the old code streams and provide migration hints ... not done
There are at least two projects we should pull out of the old code streams into sub-projects (the TCK, and the Abdera extension). I'll pull those out.
I'll update the JIRA issues to reflect the above.
Dave
On 29 Apr 2010, at 23:50, Florian Müller wrote:
> Hi,
>
> At the face-to-face meeting we gave us two weeks for the discussed changes and then start the release process. It's about time now.
>
> Let's see where we are:
>
> - code formatting ... done (?)
> - PagingList refactoring ... done (?)
> - new server SPI ... done
> - local binding implementation ... done
> - query parser integration ... done (?)
> - extract type manager ... not started yet
> - adapt basic documentation ... started, but still a lot to do
> - web site update (as source of the documentation to be packaged) ... not started yet
> - retire the old code streams and provide migration hints ... not done
>
>
> Based on this, what's our timeline and who does what and when?
> I sign up for the documentation adjustments.
>
>
> Cheers,
>
> Florian
RE: OpenCMIS release check list
Posted by Florian Müller <fm...@opentext.com>.
Hi Paul, hi Gabriele,
I like the general idea that Paul laid out. (I haven't looked into all the details yet.)
A nice version of the Confluence Wiki should become the main Chemistry web site. But we also have to export the Confluence content to SVN when we cut the OpenCMIS release since this should become the documentation that we want to ship. So we need the Doxia import as well.
- Florian
-----Original Message-----
From: Goetz, Paul [mailto:paul.goetz@sap.com]
Sent: Montag, 3. Mai 2010 14:51
To: chemistry-dev@incubator.apache.org
Subject: RE: OpenCMIS release check list
Hi Gabriele,
sorry if the illustration might have caused some misunderstanding:
About step [1]: I didn't meant that there is a need for wget - it's just to illustrate how a browser would retrieve the documentation. This and Step [2] is part of the Apache infrastructure anyway, so nothing to do about it.
All we need to do on project side is to define how /www/incubator.apache.org/chemistry is populated on minotaur.
There, we have three options:
- get content by a plain SVN checkout (step [3])
- get content generated from Maven (steps [6]/[7])
- get content edited in Confluence (steps [9]/[10])
We discussed that in the F2F - see Florian's mail "More F2F Notes" from 2010/04/14:
---8<---
Chemistry web site:
* We would like to make an exported version of the Confluence Wiki the main Chemistry web site.
--->8---
So my understanding was, that we combine the three options as follows:
- Static content (like landing page, icons, stylesheets) goes to SVN ([4]/[3])
- Manually edited content (the documentation) goes to Confluence ([8]/[9]/[10])
- Automated reports are still generated by Maven where applicable ([5]/[6]/[7])
If I got it right, you're suggesting to rethink that proposal and use Maven also for edited content (moving the Confluence content to Maven).
So I will raise this question: Ok to use Confluence as "editing system", or should we go for Maven sites?
I would prefer Confluence:
1. Others (e.g. Apache CXF and Apache Tuscany) do it that way, too.
2. It can be easily automated (autoexport-plugin already set up, [9] simply requires a velocity template to be defined (in progress), [10] then becomes a copy operation).
3. It seems to be flexible enough to cover also non-Maven-built projects.
What do you think?
Best regards,
Paul
-----Original Message-----
From: Gabriele Columbro [mailto:columbro@gmail.com]
Sent: Montag, 3. Mai 2010 13:53
To: chemistry-dev@incubator.apache.org
Subject: Re: OpenCMIS release check list
Hey Paul,
thanks for putting effort on linearizing the documentation process. A
more than needed ECM effort :)
Below my comments on the process: I might be missing some details,
but I believe we could leverage better the standard documentation
tools from maven.
On May 2, 2010, at 11:33 PM, Goetz, Paul wrote:
> Hi,
>
> with regards to the documentation: you might have a look at http://people.apache.org/~pgoetz/chemistry
> .
> There's a first proposal how we could build the documentation.
>
> But as always, there are some open questions:
> - Is the proposed process ok for everyone? Any changes / suggestions?
As per step 1: isn't the site at http://incubator.apache.org/
chemistry/ just a plain empty generated "mvn site" with generic info
about the project? Why we need to wget it when we can easily
regenerate it as part of the mvn site process (step 6/7 in your
process)?
> - For Step [7]: I'd assume that we will use the Maven Site info for
> OpenCMIS. I wouldn't expect other (Non-Java) subprojects (cmislib,
> JS-Client) to generate a Maven Site - so would one site be
> sufficient (vs. every subproject having its own site)?
Agreed. Also for documentation deployment, can't we just use maven
site deployment [1] with SSH target repository, instead of using
rsync / rcp? This can all be run by Hudson, by the means of a 'mvn
site-deploy'.
> - For Step [10]: We could either do some magic transformation (like
> HTML Tidy + removing some sections like <style.../style>|<script.../
> script>|<div class="greynavbar".../div>|<div class="footer".../div>,
> and then apply the style sheets) - or we could change the template
> for the CMIS site in Confluence (like CXF). Is there someone
> experienced with Confluence templates?
Doxia, the Maven site engine, supports Confluence markup source pages
[2], so we could do an initial import of confluence markup pages in
SVN and have them neatly built by mvn (centralizing all documentation
efforts in Maven from that point on).
I can try to spike this in the next days, to basically streamline a
process where:
- Current Confluence pages are added to SVN and then build by maven
- Current project information at incubator.apache.org/chemistry is
regenerated by the mvn build
1. New pages are added in any of the mvn site supported input formats
[3] (BTW, you could also develop pages as drafts on Confluence first,
and then add them to SVN when wanting to aggregate them to the
"official" site)
2. Site is deployed by hudson by mvn site-deploy, possibly by a
specific build plan on a different schedule
This approach definitely still needs to be tested, but I believe it
can take off some maintenance burden and get us up to speed on this
topic.
Am I missing something (I guess) ? :)
>
> If nobody objects, I would continue with the following todos:
> 1) initial check-in for website content to SVN [4]
> 2) add cronjob to do the SVN update for the website [3]
> 3) update OpenCMIS Maven site content and check-in to SVN [5]
> 4) add cronjob or Hudson task to replicate OpenCMIS' Maven site
> target build to /www/incubator.apache.org/chemistry/site.opencmis [7]
> 5) change the template for CMIS in Confluence
> 6) add cronjob to copy /www/confluence_export/CMIS to /www/
> incubator.apache.org/chemistry/wiki
>
> Best regards,
> Paul
As I said I'm happy to help on this, as I've been working on mvn doc
sites quite extensively in the past and it might get tricky to do the
configuration bits.
Could start by adding a visual of the process here [4] , if you guys
believe it's a valid option.
WDYT?
Ciao,
Gab
[1] http://maven.apache.org/plugins/maven-site-plugin/deploy-mojo.html
[2] http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-confluence/
[3] http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
[4] http://people.apache.org/~pgoetz/chemistry/
>
> -----Original Message-----
> From: David Caruana [mailto:david.caruana@alfresco.com]
> Sent: Freitag, 30. April 2010 10:22
> To: chemistry-dev@incubator.apache.org
> Subject: Re: OpenCMIS release check list
>
> ---8<---
>> - web site update (as source of the documentation to be
>> packaged) ... not started yet
>
> I can now confirm that Alfresco can provide someone to design/
> provide a skin for the web site.
> --->8---
>
>
--
Eng. Gabriele Columbro
Alfresco Software, Ltd.
M: +31 (0)627 565 103
P: +39 320 161 28 46
D: +44 (0)1628 876 654
Skype: gabrielecolumbro
Blog: http://www.mindthegab.com
RE: OpenCMIS release check list
Posted by "Goetz, Paul" <pa...@sap.com>.
Hi Gabriele,
sorry if the illustration might have caused some misunderstanding:
About step [1]: I didn't meant that there is a need for wget - it's just to illustrate how a browser would retrieve the documentation. This and Step [2] is part of the Apache infrastructure anyway, so nothing to do about it.
All we need to do on project side is to define how /www/incubator.apache.org/chemistry is populated on minotaur.
There, we have three options:
- get content by a plain SVN checkout (step [3])
- get content generated from Maven (steps [6]/[7])
- get content edited in Confluence (steps [9]/[10])
We discussed that in the F2F - see Florian's mail "More F2F Notes" from 2010/04/14:
---8<---
Chemistry web site:
* We would like to make an exported version of the Confluence Wiki the main Chemistry web site.
--->8---
So my understanding was, that we combine the three options as follows:
- Static content (like landing page, icons, stylesheets) goes to SVN ([4]/[3])
- Manually edited content (the documentation) goes to Confluence ([8]/[9]/[10])
- Automated reports are still generated by Maven where applicable ([5]/[6]/[7])
If I got it right, you're suggesting to rethink that proposal and use Maven also for edited content (moving the Confluence content to Maven).
So I will raise this question: Ok to use Confluence as "editing system", or should we go for Maven sites?
I would prefer Confluence:
1. Others (e.g. Apache CXF and Apache Tuscany) do it that way, too.
2. It can be easily automated (autoexport-plugin already set up, [9] simply requires a velocity template to be defined (in progress), [10] then becomes a copy operation).
3. It seems to be flexible enough to cover also non-Maven-built projects.
What do you think?
Best regards,
Paul
-----Original Message-----
From: Gabriele Columbro [mailto:columbro@gmail.com]
Sent: Montag, 3. Mai 2010 13:53
To: chemistry-dev@incubator.apache.org
Subject: Re: OpenCMIS release check list
Hey Paul,
thanks for putting effort on linearizing the documentation process. A
more than needed ECM effort :)
Below my comments on the process: I might be missing some details,
but I believe we could leverage better the standard documentation
tools from maven.
On May 2, 2010, at 11:33 PM, Goetz, Paul wrote:
> Hi,
>
> with regards to the documentation: you might have a look at http://people.apache.org/~pgoetz/chemistry
> .
> There's a first proposal how we could build the documentation.
>
> But as always, there are some open questions:
> - Is the proposed process ok for everyone? Any changes / suggestions?
As per step 1: isn't the site at http://incubator.apache.org/
chemistry/ just a plain empty generated "mvn site" with generic info
about the project? Why we need to wget it when we can easily
regenerate it as part of the mvn site process (step 6/7 in your
process)?
> - For Step [7]: I'd assume that we will use the Maven Site info for
> OpenCMIS. I wouldn't expect other (Non-Java) subprojects (cmislib,
> JS-Client) to generate a Maven Site - so would one site be
> sufficient (vs. every subproject having its own site)?
Agreed. Also for documentation deployment, can't we just use maven
site deployment [1] with SSH target repository, instead of using
rsync / rcp? This can all be run by Hudson, by the means of a 'mvn
site-deploy'.
> - For Step [10]: We could either do some magic transformation (like
> HTML Tidy + removing some sections like <style.../style>|<script.../
> script>|<div class="greynavbar".../div>|<div class="footer".../div>,
> and then apply the style sheets) - or we could change the template
> for the CMIS site in Confluence (like CXF). Is there someone
> experienced with Confluence templates?
Doxia, the Maven site engine, supports Confluence markup source pages
[2], so we could do an initial import of confluence markup pages in
SVN and have them neatly built by mvn (centralizing all documentation
efforts in Maven from that point on).
I can try to spike this in the next days, to basically streamline a
process where:
- Current Confluence pages are added to SVN and then build by maven
- Current project information at incubator.apache.org/chemistry is
regenerated by the mvn build
1. New pages are added in any of the mvn site supported input formats
[3] (BTW, you could also develop pages as drafts on Confluence first,
and then add them to SVN when wanting to aggregate them to the
"official" site)
2. Site is deployed by hudson by mvn site-deploy, possibly by a
specific build plan on a different schedule
This approach definitely still needs to be tested, but I believe it
can take off some maintenance burden and get us up to speed on this
topic.
Am I missing something (I guess) ? :)
>
> If nobody objects, I would continue with the following todos:
> 1) initial check-in for website content to SVN [4]
> 2) add cronjob to do the SVN update for the website [3]
> 3) update OpenCMIS Maven site content and check-in to SVN [5]
> 4) add cronjob or Hudson task to replicate OpenCMIS' Maven site
> target build to /www/incubator.apache.org/chemistry/site.opencmis [7]
> 5) change the template for CMIS in Confluence
> 6) add cronjob to copy /www/confluence_export/CMIS to /www/
> incubator.apache.org/chemistry/wiki
>
> Best regards,
> Paul
As I said I'm happy to help on this, as I've been working on mvn doc
sites quite extensively in the past and it might get tricky to do the
configuration bits.
Could start by adding a visual of the process here [4] , if you guys
believe it's a valid option.
WDYT?
Ciao,
Gab
[1] http://maven.apache.org/plugins/maven-site-plugin/deploy-mojo.html
[2] http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-confluence/
[3] http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
[4] http://people.apache.org/~pgoetz/chemistry/
>
> -----Original Message-----
> From: David Caruana [mailto:david.caruana@alfresco.com]
> Sent: Freitag, 30. April 2010 10:22
> To: chemistry-dev@incubator.apache.org
> Subject: Re: OpenCMIS release check list
>
> ---8<---
>> - web site update (as source of the documentation to be
>> packaged) ... not started yet
>
> I can now confirm that Alfresco can provide someone to design/
> provide a skin for the web site.
> --->8---
>
>
--
Eng. Gabriele Columbro
Alfresco Software, Ltd.
M: +31 (0)627 565 103
P: +39 320 161 28 46
D: +44 (0)1628 876 654
Skype: gabrielecolumbro
Blog: http://www.mindthegab.com
Re: OpenCMIS release check list
Posted by Gabriele Columbro <co...@gmail.com>.
Hey Paul,
thanks for putting effort on linearizing the documentation process. A
more than needed ECM effort :)
Below my comments on the process: I might be missing some details,
but I believe we could leverage better the standard documentation
tools from maven.
On May 2, 2010, at 11:33 PM, Goetz, Paul wrote:
> Hi,
>
> with regards to the documentation: you might have a look at http://people.apache.org/~pgoetz/chemistry
> .
> There's a first proposal how we could build the documentation.
>
> But as always, there are some open questions:
> - Is the proposed process ok for everyone? Any changes / suggestions?
As per step 1: isn't the site at http://incubator.apache.org/
chemistry/ just a plain empty generated "mvn site" with generic info
about the project? Why we need to wget it when we can easily
regenerate it as part of the mvn site process (step 6/7 in your
process)?
> - For Step [7]: I'd assume that we will use the Maven Site info for
> OpenCMIS. I wouldn't expect other (Non-Java) subprojects (cmislib,
> JS-Client) to generate a Maven Site - so would one site be
> sufficient (vs. every subproject having its own site)?
Agreed. Also for documentation deployment, can't we just use maven
site deployment [1] with SSH target repository, instead of using
rsync / rcp? This can all be run by Hudson, by the means of a 'mvn
site-deploy'.
> - For Step [10]: We could either do some magic transformation (like
> HTML Tidy + removing some sections like <style.../style>|<script.../
> script>|<div class="greynavbar".../div>|<div class="footer".../div>,
> and then apply the style sheets) - or we could change the template
> for the CMIS site in Confluence (like CXF). Is there someone
> experienced with Confluence templates?
Doxia, the Maven site engine, supports Confluence markup source pages
[2], so we could do an initial import of confluence markup pages in
SVN and have them neatly built by mvn (centralizing all documentation
efforts in Maven from that point on).
I can try to spike this in the next days, to basically streamline a
process where:
- Current Confluence pages are added to SVN and then build by maven
- Current project information at incubator.apache.org/chemistry is
regenerated by the mvn build
1. New pages are added in any of the mvn site supported input formats
[3] (BTW, you could also develop pages as drafts on Confluence first,
and then add them to SVN when wanting to aggregate them to the
"official" site)
2. Site is deployed by hudson by mvn site-deploy, possibly by a
specific build plan on a different schedule
This approach definitely still needs to be tested, but I believe it
can take off some maintenance burden and get us up to speed on this
topic.
Am I missing something (I guess) ? :)
>
> If nobody objects, I would continue with the following todos:
> 1) initial check-in for website content to SVN [4]
> 2) add cronjob to do the SVN update for the website [3]
> 3) update OpenCMIS Maven site content and check-in to SVN [5]
> 4) add cronjob or Hudson task to replicate OpenCMIS' Maven site
> target build to /www/incubator.apache.org/chemistry/site.opencmis [7]
> 5) change the template for CMIS in Confluence
> 6) add cronjob to copy /www/confluence_export/CMIS to /www/
> incubator.apache.org/chemistry/wiki
>
> Best regards,
> Paul
As I said I'm happy to help on this, as I've been working on mvn doc
sites quite extensively in the past and it might get tricky to do the
configuration bits.
Could start by adding a visual of the process here [4] , if you guys
believe it's a valid option.
WDYT?
Ciao,
Gab
[1] http://maven.apache.org/plugins/maven-site-plugin/deploy-mojo.html
[2] http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-confluence/
[3] http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html
[4] http://people.apache.org/~pgoetz/chemistry/
>
> -----Original Message-----
> From: David Caruana [mailto:david.caruana@alfresco.com]
> Sent: Freitag, 30. April 2010 10:22
> To: chemistry-dev@incubator.apache.org
> Subject: Re: OpenCMIS release check list
>
> ---8<---
>> - web site update (as source of the documentation to be
>> packaged) ... not started yet
>
> I can now confirm that Alfresco can provide someone to design/
> provide a skin for the web site.
> --->8---
>
>
--
Eng. Gabriele Columbro
Alfresco Software, Ltd.
M: +31 (0)627 565 103
P: +39 320 161 28 46
D: +44 (0)1628 876 654
Skype: gabrielecolumbro
Blog: http://www.mindthegab.com
RE: OpenCMIS release check list
Posted by Florian Müller <fm...@opentext.com>.
There is a description how to do it here: [1]
I guess it's a bit different for incubator web sites, though.
Florian
[1] https://cwiki.apache.org/CWIKI/#Index-Canweusetheautoexportsiteaspartofourmainwebsite%3F
-----Original Message-----
From: Nick Burch [mailto:nick.burch@alfresco.com]
Sent: Donnerstag, 6. Mai 2010 11:31
To: chemistry-dev@incubator.apache.org
Subject: RE: OpenCMIS release check list
On Thu, 6 May 2010, Florian Müller wrote:
> - Redirecting http://incubator.apache.org/chemistry/ to
> https://cwiki.apache.org/CMIS/ .
I think it's more normal to place the exported site into your main
website, rather than redirecting to the wiki. This also makes it easier to
bundle the documentation into releases
I've not done this myself though, so it might be worth asking for advice
on general@incubator for how other projects do this.
Nick
RE: OpenCMIS release check list
Posted by Nick Burch <ni...@alfresco.com>.
On Thu, 6 May 2010, Florian Müller wrote:
> - Redirecting http://incubator.apache.org/chemistry/ to
> https://cwiki.apache.org/CMIS/ .
I think it's more normal to place the exported site into your main
website, rather than redirecting to the wiki. This also makes it easier to
bundle the documentation into releases
I've not done this myself though, so it might be worth asking for advice
on general@incubator for how other projects do this.
Nick
RE: OpenCMIS release check list
Posted by "Klevenz, Stephan" <st...@sap.com>.
Hi,
> - Generating the OpenCMIS JavaDoc: Should be done via Hudson ([6]).
Ok, I will handle this.
Stephan
-----Original Message-----
From: Goetz, Paul [mailto:paul.goetz@sap.com]
Sent: Donnerstag, 6. Mai 2010 11:36
To: chemistry-dev@incubator.apache.org
Subject: RE: OpenCMIS release check list
Hi Florian,
well, basically the proposal is as simple as this, except for the redirect :o)
- Creating an auto export template: I'm working on that. I installed a Confluence Wiki on my PC to learn about that mechanism, but I'm not finished yet... In the end I need to create a Velocity template.
- Adding some useful information: That is for sure a good idea ;o)
- Redirecting: From my point of view that is not needed - once the auto export is working, the content would simply be copied ([9]/[10]). And as far as I understood the landscape, the Confluence Wiki is not intended for high-volume access, therefore we should put the "read-only" stuff to incubator.apache.org.
- Generating the OpenCMIS JavaDoc: Should be done via Hudson ([6]).
Best regards,
Paul
-----Original Message-----
From: Florian Müller [mailto:fmueller@opentext.com]
Sent: Donnerstag, 6. Mai 2010 11:24
To: chemistry-dev@incubator.apache.org
Subject: RE: OpenCMIS release check list
Hi,
Can we start with some simple things here?
I'm thinking of:
- Creating an auto export template for Confluence. The current output is ... pretty ugly. (Paul?)
- Adding some useful information about Apache Chemistry and CMIS on the Wiki front page.
- Redirecting http://incubator.apache.org/chemistry/ to https://cwiki.apache.org/CMIS/ .
- Generating the OpenCMIS JavaDoc again. (Stephan?)
- Florian
-----Original Message-----
From: Goetz, Paul [mailto:paul.goetz@sap.com]
Sent: Sonntag, 2. Mai 2010 23:33
To: chemistry-dev@incubator.apache.org
Subject: RE: OpenCMIS release check list
Hi,
with regards to the documentation: you might have a look at http://people.apache.org/~pgoetz/chemistry.
There's a first proposal how we could build the documentation.
But as always, there are some open questions:
- Is the proposed process ok for everyone? Any changes / suggestions?
- For Step [7]: I'd assume that we will use the Maven Site info for OpenCMIS. I wouldn't expect other (Non-Java) subprojects (cmislib, JS-Client) to generate a Maven Site - so would one site be sufficient (vs. every subproject having its own site)?
- For Step [10]: We could either do some magic transformation (like HTML Tidy + removing some sections like <style.../style>|<script.../script>|<div class="greynavbar".../div>|<div class="footer".../div>, and then apply the style sheets) - or we could change the template for the CMIS site in Confluence (like CXF). Is there someone experienced with Confluence templates?
If nobody objects, I would continue with the following todos:
1) initial check-in for website content to SVN [4]
2) add cronjob to do the SVN update for the website [3]
3) update OpenCMIS Maven site content and check-in to SVN [5]
4) add cronjob or Hudson task to replicate OpenCMIS' Maven site target build to /www/incubator.apache.org/chemistry/site.opencmis [7]
5) change the template for CMIS in Confluence
6) add cronjob to copy /www/confluence_export/CMIS to /www/incubator.apache.org/chemistry/wiki
Best regards,
Paul
-----Original Message-----
From: David Caruana [mailto:david.caruana@alfresco.com]
Sent: Freitag, 30. April 2010 10:22
To: chemistry-dev@incubator.apache.org
Subject: Re: OpenCMIS release check list
---8<---
> - web site update (as source of the documentation to be packaged) ... not started yet
I can now confirm that Alfresco can provide someone to design/provide a skin for the web site.
--->8---
RE: OpenCMIS release check list
Posted by "Goetz, Paul" <pa...@sap.com>.
Hi Florian,
well, basically the proposal is as simple as this, except for the redirect :o)
- Creating an auto export template: I'm working on that. I installed a Confluence Wiki on my PC to learn about that mechanism, but I'm not finished yet... In the end I need to create a Velocity template.
- Adding some useful information: That is for sure a good idea ;o)
- Redirecting: From my point of view that is not needed - once the auto export is working, the content would simply be copied ([9]/[10]). And as far as I understood the landscape, the Confluence Wiki is not intended for high-volume access, therefore we should put the "read-only" stuff to incubator.apache.org.
- Generating the OpenCMIS JavaDoc: Should be done via Hudson ([6]).
Best regards,
Paul
-----Original Message-----
From: Florian Müller [mailto:fmueller@opentext.com]
Sent: Donnerstag, 6. Mai 2010 11:24
To: chemistry-dev@incubator.apache.org
Subject: RE: OpenCMIS release check list
Hi,
Can we start with some simple things here?
I'm thinking of:
- Creating an auto export template for Confluence. The current output is ... pretty ugly. (Paul?)
- Adding some useful information about Apache Chemistry and CMIS on the Wiki front page.
- Redirecting http://incubator.apache.org/chemistry/ to https://cwiki.apache.org/CMIS/ .
- Generating the OpenCMIS JavaDoc again. (Stephan?)
- Florian
-----Original Message-----
From: Goetz, Paul [mailto:paul.goetz@sap.com]
Sent: Sonntag, 2. Mai 2010 23:33
To: chemistry-dev@incubator.apache.org
Subject: RE: OpenCMIS release check list
Hi,
with regards to the documentation: you might have a look at http://people.apache.org/~pgoetz/chemistry.
There's a first proposal how we could build the documentation.
But as always, there are some open questions:
- Is the proposed process ok for everyone? Any changes / suggestions?
- For Step [7]: I'd assume that we will use the Maven Site info for OpenCMIS. I wouldn't expect other (Non-Java) subprojects (cmislib, JS-Client) to generate a Maven Site - so would one site be sufficient (vs. every subproject having its own site)?
- For Step [10]: We could either do some magic transformation (like HTML Tidy + removing some sections like <style.../style>|<script.../script>|<div class="greynavbar".../div>|<div class="footer".../div>, and then apply the style sheets) - or we could change the template for the CMIS site in Confluence (like CXF). Is there someone experienced with Confluence templates?
If nobody objects, I would continue with the following todos:
1) initial check-in for website content to SVN [4]
2) add cronjob to do the SVN update for the website [3]
3) update OpenCMIS Maven site content and check-in to SVN [5]
4) add cronjob or Hudson task to replicate OpenCMIS' Maven site target build to /www/incubator.apache.org/chemistry/site.opencmis [7]
5) change the template for CMIS in Confluence
6) add cronjob to copy /www/confluence_export/CMIS to /www/incubator.apache.org/chemistry/wiki
Best regards,
Paul
-----Original Message-----
From: David Caruana [mailto:david.caruana@alfresco.com]
Sent: Freitag, 30. April 2010 10:22
To: chemistry-dev@incubator.apache.org
Subject: Re: OpenCMIS release check list
---8<---
> - web site update (as source of the documentation to be packaged) ... not started yet
I can now confirm that Alfresco can provide someone to design/provide a skin for the web site.
--->8---
RE: OpenCMIS release check list
Posted by Florian Müller <fm...@opentext.com>.
Hi,
Can we start with some simple things here?
I'm thinking of:
- Creating an auto export template for Confluence. The current output is ... pretty ugly. (Paul?)
- Adding some useful information about Apache Chemistry and CMIS on the Wiki front page.
- Redirecting http://incubator.apache.org/chemistry/ to https://cwiki.apache.org/CMIS/ .
- Generating the OpenCMIS JavaDoc again. (Stephan?)
- Florian
-----Original Message-----
From: Goetz, Paul [mailto:paul.goetz@sap.com]
Sent: Sonntag, 2. Mai 2010 23:33
To: chemistry-dev@incubator.apache.org
Subject: RE: OpenCMIS release check list
Hi,
with regards to the documentation: you might have a look at http://people.apache.org/~pgoetz/chemistry.
There's a first proposal how we could build the documentation.
But as always, there are some open questions:
- Is the proposed process ok for everyone? Any changes / suggestions?
- For Step [7]: I'd assume that we will use the Maven Site info for OpenCMIS. I wouldn't expect other (Non-Java) subprojects (cmislib, JS-Client) to generate a Maven Site - so would one site be sufficient (vs. every subproject having its own site)?
- For Step [10]: We could either do some magic transformation (like HTML Tidy + removing some sections like <style.../style>|<script.../script>|<div class="greynavbar".../div>|<div class="footer".../div>, and then apply the style sheets) - or we could change the template for the CMIS site in Confluence (like CXF). Is there someone experienced with Confluence templates?
If nobody objects, I would continue with the following todos:
1) initial check-in for website content to SVN [4]
2) add cronjob to do the SVN update for the website [3]
3) update OpenCMIS Maven site content and check-in to SVN [5]
4) add cronjob or Hudson task to replicate OpenCMIS' Maven site target build to /www/incubator.apache.org/chemistry/site.opencmis [7]
5) change the template for CMIS in Confluence
6) add cronjob to copy /www/confluence_export/CMIS to /www/incubator.apache.org/chemistry/wiki
Best regards,
Paul
-----Original Message-----
From: David Caruana [mailto:david.caruana@alfresco.com]
Sent: Freitag, 30. April 2010 10:22
To: chemistry-dev@incubator.apache.org
Subject: Re: OpenCMIS release check list
---8<---
> - web site update (as source of the documentation to be packaged) ... not started yet
I can now confirm that Alfresco can provide someone to design/provide a skin for the web site.
--->8---
RE: OpenCMIS release check list
Posted by "Goetz, Paul" <pa...@sap.com>.
Hi,
with regards to the documentation: you might have a look at http://people.apache.org/~pgoetz/chemistry.
There's a first proposal how we could build the documentation.
But as always, there are some open questions:
- Is the proposed process ok for everyone? Any changes / suggestions?
- For Step [7]: I'd assume that we will use the Maven Site info for OpenCMIS. I wouldn't expect other (Non-Java) subprojects (cmislib, JS-Client) to generate a Maven Site - so would one site be sufficient (vs. every subproject having its own site)?
- For Step [10]: We could either do some magic transformation (like HTML Tidy + removing some sections like <style.../style>|<script.../script>|<div class="greynavbar".../div>|<div class="footer".../div>, and then apply the style sheets) - or we could change the template for the CMIS site in Confluence (like CXF). Is there someone experienced with Confluence templates?
If nobody objects, I would continue with the following todos:
1) initial check-in for website content to SVN [4]
2) add cronjob to do the SVN update for the website [3]
3) update OpenCMIS Maven site content and check-in to SVN [5]
4) add cronjob or Hudson task to replicate OpenCMIS' Maven site target build to /www/incubator.apache.org/chemistry/site.opencmis [7]
5) change the template for CMIS in Confluence
6) add cronjob to copy /www/confluence_export/CMIS to /www/incubator.apache.org/chemistry/wiki
Best regards,
Paul
-----Original Message-----
From: David Caruana [mailto:david.caruana@alfresco.com]
Sent: Freitag, 30. April 2010 10:22
To: chemistry-dev@incubator.apache.org
Subject: Re: OpenCMIS release check list
---8<---
> - web site update (as source of the documentation to be packaged) ... not started yet
I can now confirm that Alfresco can provide someone to design/provide a skin for the web site.
--->8---
RE: OpenCMIS release check list
Posted by "Klevenz, Stephan" <st...@sap.com>.
Hi,
>> - PagingList refactoring ... done (?)
>
> Initial scope of refactor is done. But there's another round of refactor todo after mailing list discussion. >>Don't know who's assigned to do that - either myself or Stephan?
I can do that. But we have to decide on the naming:
A) PagingIterable (as it is for now)
B) SkipableIterable (proposed by Florent)
C) ItemIterable (proposed by me)
D) other
Do we get an consensus on that?
Stephan
-----Original Message-----
From: David Caruana [mailto:david.caruana@alfresco.com]
Sent: Freitag, 30. April 2010 10:22
To: chemistry-dev@incubator.apache.org
Subject: Re: OpenCMIS release check list
> - code formatting ... done (?)
Done
> - PagingList refactoring ... done (?)
Initial scope of refactor is done. But there's another round of refactor todo after mailing list discussion. Don't know who's assigned to do that - either myself or Stephan?
> - web site update (as source of the documentation to be packaged) ... not started yet
I can now confirm that Alfresco can provide someone to design/provide a skin for the web site.
> - retire the old code streams and provide migration hints ... not done
There are at least two projects we should pull out of the old code streams into sub-projects (the TCK, and the Abdera extension). I'll pull those out.
I'll update the JIRA issues to reflect the above.
Dave
On 29 Apr 2010, at 23:50, Florian Müller wrote:
> Hi,
>
> At the face-to-face meeting we gave us two weeks for the discussed changes and then start the release process. It's about time now.
>
> Let's see where we are:
>
> - code formatting ... done (?)
> - PagingList refactoring ... done (?)
> - new server SPI ... done
> - local binding implementation ... done
> - query parser integration ... done (?)
> - extract type manager ... not started yet
> - adapt basic documentation ... started, but still a lot to do
> - web site update (as source of the documentation to be packaged) ... not started yet
> - retire the old code streams and provide migration hints ... not done
>
>
> Based on this, what's our timeline and who does what and when?
> I sign up for the documentation adjustments.
>
>
> Cheers,
>
> Florian
Re: OpenCMIS release check list
Posted by Florent Guillaume <fg...@nuxeo.com>.
On Fri, Apr 30, 2010 at 10:21 AM, David Caruana
<da...@alfresco.com> wrote:
>On Fri, Apr 30, 2010 at 12:50 AM, Florian Müller <fm...@opentext.com> wrote:
>> - PagingList refactoring ... done (?)
>
> Initial scope of refactor is done. But there's another round of refactor todo after mailing list discussion. Don't know who's assigned to do that - either myself or Stephan?
I'd also like to play with it; in the comparable cases I've worked on
before all the methods were on the iterable, not the iterator. The
advantage of this is that the iterable is always available, whereas
the iterator is often hidden, in Java 5, behind foreach loop syntax.
And you have one less interface (you use the standard Iterator). The
implementations of that pattern that I've seen implement both Iterable
and Iterator on the same class — it means that you cannot ask for a
second independent iterator for the iterable, but that's a use case
I've yet to see.
I'll make a proposal in a branch when I find the time.
>> - extract type manager ... not started yet
I have this in my pipeline, but couldn't get around to do it yet :(
Maybe this afternoon if I'm lucky.
>> - web site update (as source of the documentation to be packaged) ... not started yet
>
> I can now confirm that Alfresco can provide someone to design/provide a skin for the web site.
I have to commit the logos I showed you, what would be the best
location? Somewhere in src/site?
>> - retire the old code streams and provide migration hints ... not done
>
> There are at least two projects we should pull out of the old code streams into sub-projects (the TCK, and the Abdera extension). I'll pull those out.
>
> I'll update the JIRA issues to reflect the above.
Florent
>
> Dave
>
>
> On 29 Apr 2010, at 23:50, Florian Müller wrote:
>
>> Hi,
>>
>> At the face-to-face meeting we gave us two weeks for the discussed changes and then start the release process. It's about time now.
>>
>> Let's see where we are:
>>
>> - code formatting ... done (?)
>> - PagingList refactoring ... done (?)
>> - new server SPI ... done
>> - local binding implementation ... done
>> - query parser integration ... done (?)
>> - extract type manager ... not started yet
>> - adapt basic documentation ... started, but still a lot to do
>> - web site update (as source of the documentation to be packaged) ... not started yet
>> - retire the old code streams and provide migration hints ... not done
>>
>>
>> Based on this, what's our timeline and who does what and when?
>> I sign up for the documentation adjustments.
>>
>>
>> Cheers,
>>
>> Florian
>
>
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
Re: OpenCMIS release check list
Posted by David Caruana <da...@alfresco.com>.
> - code formatting ... done (?)
Done
> - PagingList refactoring ... done (?)
Initial scope of refactor is done. But there's another round of refactor todo after mailing list discussion. Don't know who's assigned to do that - either myself or Stephan?
> - web site update (as source of the documentation to be packaged) ... not started yet
I can now confirm that Alfresco can provide someone to design/provide a skin for the web site.
> - retire the old code streams and provide migration hints ... not done
There are at least two projects we should pull out of the old code streams into sub-projects (the TCK, and the Abdera extension). I'll pull those out.
I'll update the JIRA issues to reflect the above.
Dave
On 29 Apr 2010, at 23:50, Florian Müller wrote:
> Hi,
>
> At the face-to-face meeting we gave us two weeks for the discussed changes and then start the release process. It's about time now.
>
> Let's see where we are:
>
> - code formatting ... done (?)
> - PagingList refactoring ... done (?)
> - new server SPI ... done
> - local binding implementation ... done
> - query parser integration ... done (?)
> - extract type manager ... not started yet
> - adapt basic documentation ... started, but still a lot to do
> - web site update (as source of the documentation to be packaged) ... not started yet
> - retire the old code streams and provide migration hints ... not done
>
>
> Based on this, what's our timeline and who does what and when?
> I sign up for the documentation adjustments.
>
>
> Cheers,
>
> Florian
Re: OpenCMIS release check list
Posted by Nick Burch <ni...@alfresco.com>.
On Fri, 30 Apr 2010, Florian Müller wrote:
> Based on this, what's our timeline and who does what and when?
> I sign up for the documentation adjustments.
Don't forget the giant incubator document on releases:
http://incubator.apache.org/guides/releasemanagement.html
There a few bits from there that I think you might still need to do.
Writing your own release management documentation is one, and stubbing out
the "what's changed" stuff ready for the release after are two things that
spring to mind
Nick