Re: [zeta-dev] Draft: Status update blog entry
On 11/19/2010 07:01 PM, Nicolas Pastorino wrote: On Nov 17, 2010, at 21:44 , Tobias Schlitt wrote: On 11/17/2010 02:33 PM, Nicolas Pastorino wrote: On Wed, Nov 17, 2010 at 1:49 PM, Tobias Schlitt tob...@schlitt.info wrote: I'd love if our blog posts could be aggregates somehow on share.ez.no. Moving the blog there is not a good idea and would conflict with ASF rules AFAIK. I would also not like to duplicate content. I was of course not suggesting moving the Zeta blog there :) I understand that duplicating content is tedious SEO-wise. Is an automatic aggregation to share.ez.no possible? Yes. Until now, http://planetezpublish.org/ is the feed aggregator. We are planning on surfacing this aggregator's feed on share.ez.no, under the blogs section. We can safely imagine subscribing the Zeta blog to this aggregator, in turn soon displayed on share.ez.no. What would you think ? Sounds great, you can just go ahead and start aggregating http://incubator.apache.org/zetacomponents/news.rss Done. Zeta stands high proud at the top of the list, right-column : http://planetezpublish.org/ And posts are fed into the aggregated feed ( http://planetezpublish.org/rss/feed/rss20.xml ) Very cool, thanks! :) Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
Re: [zeta-dev] Draft: Status update blog entry
Hi all ! On Nov 17, 2010, at 21:44 , Tobias Schlitt wrote: Hi Nicolas, On 11/17/2010 02:33 PM, Nicolas Pastorino wrote: On Wed, Nov 17, 2010 at 1:49 PM, Tobias Schlitt tob...@schlitt.info wrote: On 11/17/2010 11:27 AM, Nicolas Pastorino wrote: From a community management perspective, i think this is a mandatory process : let information flow, regularly. I can also propose, if you guys judge this helps, to push these posts on a dedicated Apache Zeta Components blog on share.ez.no (it is now possible to create personal blogs on share.ez.no). I'd love if our blog posts could be aggregates somehow on share.ez.no. Moving the blog there is not a good idea and would conflict with ASF rules AFAIK. I would also not like to duplicate content. I was of course not suggesting moving the Zeta blog there :) I understand that duplicating content is tedious SEO-wise. Is an automatic aggregation to share.ez.no possible? Yes. Until now, http://planetezpublish.org/ is the feed aggregator. We are planning on surfacing this aggregator's feed on share.ez.no, under the blogs section. We can safely imagine subscribing the Zeta blog to this aggregator, in turn soon displayed on share.ez.no. What would you think ? Sounds great, you can just go ahead and start aggregating http://incubator.apache.org/zetacomponents/news.rss Done. Zeta stands high proud at the top of the list, right-column : http://planetezpublish.org/ And posts are fed into the aggregated feed ( http://planetezpublish.org/rss/feed/rss20.xml ) Cheers ! -- Nicolas for now. Thanks, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn -- Nicolas Pastorino eZ Community Manager Community portal : http://share.ez.no Twitter : @ezcommunity / @jeanvoye Skype : bimbamboombimbla Phone : +33 (0)671791318 eZ Systems | http://ez.no
Re: [zeta-dev] Draft: Status update blog entry
Hi Tobias, On Wed, Nov 17, 2010 at 9:48 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi Jerome, [...] PS : shamefulI really have to work on that override mechanism for Configuration/shameful That'd be great. I'll try to get the wiki up for such stuff soonish, as discussed here. Did you already send an iCLA? As far as I remember I did. I know there is a page on apache.org where you can see people who sent their iCLA but I do not remember which one. Maybe Christian remembers it. -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Draft: Status update blog entry
That'd be great. I'll try to get the wiki up for such stuff soonish, as discussed here. Did you already send an iCLA? As far as I remember I did. I know there is a page on apache.org where you can see people who sent their iCLA but I do not remember which one. Maybe Christian remembers it. Yes he does: http://people.apache.org/committer-index.html Your name is mentioned on the unlisted CLA section == your ICLA has been received Cheers
Re: [zeta-dev] Draft: Status update blog entry
Tobias Schlitt wrote: Hi, I've made up a draft for a status update blog entry on our website. Please find this post attached and in SVN for review (links are still missing), so I can publish it in a near future. I would be happy if we could provide such status updates somewhat regularly (maybe once a month?), in order to keep people informed and to attract more contributors. What do you think? Cheers, Toby We did not role an official release, yet, = We did not roll an official release yet, At this place, we want to seize the chance to = We want to take the opportunity to ciao Gaetano
Re: [zeta-dev] Draft: Status update blog entry
I would be happy if we could provide such status updates somewhat regularly (maybe once a month?), in order to keep people informed and to attract more contributors. What do you think? Great idea! Btw, you can have an apache blog by requesting it from jira http://blogs.apache.org/ In this blog you have the chance for a preview and send the preview to the dev list were people can make suggestions or vote about. Best regards, Christian
Re: [zeta-dev] Draft: Status update blog entry
Excellent ! A blog is effectively the best way to inform people with some modern way to inform (RSS). 2010/11/17 Christian Grobmeier grobme...@gmail.com I would be happy if we could provide such status updates somewhat regularly (maybe once a month?), in order to keep people informed and to attract more contributors. What do you think? Great idea! Btw, you can have an apache blog by requesting it from jira http://blogs.apache.org/ In this blog you have the chance for a preview and send the preview to the dev list were people can make suggestions or vote about. Best regards, Christian
Re: [zeta-dev] Draft: Status update blog entry
Hi Nicolas, On 11/17/2010 11:27 AM, Nicolas Pastorino wrote: From a community management perspective, i think this is a mandatory process : let information flow, regularly. I can also propose, if you guys judge this helps, to push these posts on a dedicated Apache Zeta Components blog on share.ez.no (it is now possible to create personal blogs on share.ez.no). I'd love if our blog posts could be aggregates somehow on share.ez.no. Moving the blog there is not a good idea and would conflict with ASF rules AFAIK. I would also not like to duplicate content. Is an automatic aggregation to share.ez.no possible? Cheers, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
Re: [zeta-dev] Draft: Status update blog entry
Hi Gaetano, On 11/17/2010 11:41 AM, Gaetano Giunta wrote: Tobias Schlitt wrote: I've made up a draft for a status update blog entry on our website. Please find this post attached and in SVN for review (links are still missing), so I can publish it in a near future. We did not role an official release, yet, = We did not roll an official release yet, At this place, we want to seize the chance to = We want to take the opportunity to thanks for the corrections. They're incorporated in SVN. Regards, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
Re: [zeta-dev] Draft: Status update blog entry
Hi Christian, On 11/17/2010 11:58 AM, Christian Grobmeier wrote: I would be happy if we could provide such status updates somewhat regularly (maybe once a month?), in order to keep people informed and to attract more contributors. What do you think? Great idea! Btw, you can have an apache blog by requesting it from jira http://blogs.apache.org/ In this blog you have the chance for a preview and send the preview to the dev list were people can make suggestions or vote about. Sounds neat. We can then incorporate the blog into the website by aggregating it on the front page. What do the others think? Regards, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
Re: [zeta-dev] Draft: Status update blog entry
Hi Toby, On Wed, Nov 17, 2010 at 1:49 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi Nicolas, On 11/17/2010 11:27 AM, Nicolas Pastorino wrote: From a community management perspective, i think this is a mandatory process : let information flow, regularly. I can also propose, if you guys judge this helps, to push these posts on a dedicated Apache Zeta Components blog on share.ez.no (it is now possible to create personal blogs on share.ez.no). I'd love if our blog posts could be aggregates somehow on share.ez.no. Moving the blog there is not a good idea and would conflict with ASF rules AFAIK. I would also not like to duplicate content. I was of course not suggesting moving the Zeta blog there :) I understand that duplicating content is tedious SEO-wise. Is an automatic aggregation to share.ez.no possible? Yes. Until now, http://planetezpublish.org/ is the feed aggregator. We are planning on surfacing this aggregator's feed on share.ez.no, under the blogs section. We can safely imagine subscribing the Zeta blog to this aggregator, in turn soon displayed on share.ez.no. What would you think ? Cheers, -- Nicolas Cheers, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
Re: [zeta-dev] Draft: Status update blog entry
Hi Tobias, On Tue, Nov 16, 2010 at 10:58 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I've made up a draft for a status update blog entry on our website. Please find this post attached and in SVN for review (links are still missing), so I can publish it in a near future. I would be happy if we could provide such status updates somewhat regularly (maybe once a month?), in order to keep people informed and to attract more contributors. What do you think? Minor fixes in the patch attached. Cheers :) PS : shamefulI really have to work on that override mechanism for Configuration/shameful -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard 002_status_update.diff.gz Description: GNU Zip compressed data
Re: [zeta-dev] Draft: Status update blog entry
Hi all, On 11/17/2010 01:54 PM, Tobias Schlitt wrote: On 11/17/2010 12:22 PM, Maxime Thomas wrote: Excellent ! A blog is effectively the best way to inform people with some modern way to inform (RSS). actually, the current news section on the website is already a blog (WCV) but with the commenting and trackback functionality stripped, since we can only use static content. I agree that a full-featured blog would be nice. after discussing this roughly with Kore and Derick, I came to a different conclusion. By now we have a blog in our website integrated which works well for publishing news and status updates. I don't think we will have enough content to be published on a dedicated blog yet. And opening one on blogs.a.o now would bring just another system to take care of. So, I think we should stick with the current solution. Regards, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
Re: [zeta-dev] Draft: Status update blog entry
Hi Nicolas, On 11/17/2010 02:33 PM, Nicolas Pastorino wrote: On Wed, Nov 17, 2010 at 1:49 PM, Tobias Schlitt tob...@schlitt.info wrote: On 11/17/2010 11:27 AM, Nicolas Pastorino wrote: From a community management perspective, i think this is a mandatory process : let information flow, regularly. I can also propose, if you guys judge this helps, to push these posts on a dedicated Apache Zeta Components blog on share.ez.no (it is now possible to create personal blogs on share.ez.no). I'd love if our blog posts could be aggregates somehow on share.ez.no. Moving the blog there is not a good idea and would conflict with ASF rules AFAIK. I would also not like to duplicate content. I was of course not suggesting moving the Zeta blog there :) I understand that duplicating content is tedious SEO-wise. Is an automatic aggregation to share.ez.no possible? Yes. Until now, http://planetezpublish.org/ is the feed aggregator. We are planning on surfacing this aggregator's feed on share.ez.no, under the blogs section. We can safely imagine subscribing the Zeta blog to this aggregator, in turn soon displayed on share.ez.no. What would you think ? Sounds great, you can just go ahead and start aggregating http://incubator.apache.org/zetacomponents/news.rss for now. Thanks, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
Re: [zeta-dev] Draft: Status update blog entry
Hi Jerome, On 11/17/2010 04:09 PM, Jerome Renard wrote: On Tue, Nov 16, 2010 at 10:58 PM, Tobias Schlitt tob...@schlitt.info wrote: I've made up a draft for a status update blog entry on our website. Please find this post attached and in SVN for review (links are still missing), so I can publish it in a near future. I would be happy if we could provide such status updates somewhat regularly (maybe once a month?), in order to keep people informed and to attract more contributors. What do you think? Minor fixes in the patch attached. Thanks, applied. :) PS : shamefulI really have to work on that override mechanism for Configuration/shameful That'd be great. I'll try to get the wiki up for such stuff soonish, as discussed here. Did you already send an iCLA? Regards, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
[zeta-dev] Draft: Status update blog entry
Hi, I've made up a draft for a status update blog entry on our website. Please find this post attached and in SVN for review (links are still missing), so I can publish it in a near future. I would be happy if we could provide such status updates somewhat regularly (maybe once a month?), in order to keep people informed and to attract more contributors. What do you think? Cheers, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn = Status update = It's been a while since Apache Zeta Components was `officially accepted for incubation`__ in the Apache Software Foundation in May 2010. Since then, a lot of progress has been made, especially in the area of technical infrastructure and code drop. So, it's time to present the current status of the project and ask you to actively take part in the community! -- Infrastructure -- There's been a lot of work on the technical infrastructure for Zeta. First off, we have a `new SVN`__, which you should use from now on to obtain the Zeta code. We did not role an official release, yet, mostly due to the fact that the release process is right now in discussion, to be adjusted to ASF needs. The project mandatory mailing lists have been set up. So, if you want to contribute and take part in the community, please register for `zeta-...@incubator.apache.org`__. If you are only using Zeta Components, please use the `user mailinglist at zeta-u...@incubator.apache.org`__ to discuss issues with other users. However, the developer mailinglist is also open for questions and problems. If you want to be up to date on commits to the SVN repository, you should subscribe to `zeta-comm...@incubator.apache.org`__ and if you want to help fixing bugs, please subscribe to `zeta-iss...@incubator.apache.org`__. Subscribing to any of the Zeta mailing lists is easy. Just send an empty email to :: zeta-*-subscr...@incubator.apache.org so, for example for the dev list, email `zeta-dev-subscr...@incubator.apache.org`__. We also have a new `issue tracker`__, which you can use to file bugs. Furthermore, there is a `code browser`__ which you can use to inspect our source code without downloading it or checking it out from SVN. - Code drop - `eZ Systems AS`__ has performed the so-called *code drop*, which essentially means that the complete eZ Components SVN history was sent to the ASF and a contract was signed which completes the donation. Furthermore, Ole from eZ Systems has performed license and copyright changes after the code was imported to `our new SVN`__. So, the (now) Zeta Components code is from now on licensed under the `Apache License 2.0`__. For you as a user, this does not change much, since the Apache License is basically as permissive as the former New BSD license was. At this place, we want to seize the chance to thank eZ Systems a lot for donating the eZ Components source code base to the ASF and therefore making Apache Zeta Components possible. - Contributions - Quite some contributions to Apache Zeta Components are in discussion on the developer mailinglist: Jerome Renard and James Pic joined forces for providing an `overrider mechanism`__ for the Configuration component. This technique should allow you to specify multiple directories for configuration files (INIs) of which the first contains default values and all further ones can override these defaults. This is especially useful in large applications and for application modules. Gustavo Solt from the PHProject__ team is implementing a `proof-of-concept for CalDAV support`__ for the Webdav component. CalDAV is an extension to WebDAV, which allows to synchronize calendars to a central server. CalDAV was already in mind when the Webdav component was originally started a couple of years ago, but time did not permit to implement it until now. Therefore, we are happily looking forward to this contribution. There are some more enhancements in discussion on the mailinglist, so please subscribe there, if you want to take part in designing and/or implementing those! Furthermore, we are actively looking for contributors. So, if you use Zeta Components (or still eZ Components) and have a cool idea, found a bug or just want to provide a helping hand, please subscribe to `zeta-...@incubator.apache.org`__ and join our team! .. Local Variables: mode: rst fill-column: 79 End: vim: et syn=rst tw=79
