Re: [call for review] Keeping the eZ Publish Community in the loop
Hi, On Thu, Apr 26, 2012 at 9:21 PM, Benjamin Eberlei kont...@beberlei.dewrote: The naming is completely undecided yet, we have contacted apache trademarks, since we don't know how to proceed. Ok, and thanks Julien for raising the point too. I will then wait until we receive a response from the foundation. Also i agree with julien, the inactivity was the major reason to retire from ASF, since we couldnt follow procedure with quarterly reports anymore due to lack of time and didnt manage to get a first release under Apache flag out. This point was added to the post. The seperation of components into their own repositories are also done to seperate the maintained from the unmaintained ones more easily :-) Added too. The draft still is available here : https://docs.google.com/a/ez.no/document/d/1SLuBI6HQqX_PJnswCOaV6MyW2AbOd0-1wTDwhHIf3f4/edit Thanks everyone for the feedback, Awaiting the final name before publishing, feel free to send additional input in the meantime, -- Nicolas On Thu, Apr 26, 2012 at 1:56 PM, Julien Vermillard jvermill...@gmail.com wrote: Hi, Even if I think it's a good idea to keep the community in the loop I would like to remeber two points : - the zeta podling retirement vote was start due to lack of progress - if you want to use the Apache/ASF word you need to contact the Apache PR for that Julien On Thu, Apr 26, 2012 at 11:35 AM, Nicolas Pastorino n...@ez.no wrote: Dear everyone, I thought it would be wise to keep the eZ Publish Community in the loop, since they are likely to be the largest share of AZC users today. Here is a small blog-post, on which I would love to have your input : https://docs.google.com/a/ez.no/document/d/1SLuBI6HQqX_PJnswCOaV6MyW2AbOd0-1wTDwhHIf3f4/edit (anyone should be able to edit it, or make remarks through comments). I hope this fits you well and I am looking forward to your feedback ! -- Nicolas
[call for review] Keeping the eZ Publish Community in the loop
Dear everyone, I thought it would be wise to keep the eZ Publish Community in the loop, since they are likely to be the largest share of AZC users today. Here is a small blog-post, on which I would love to have your input : https://docs.google.com/a/ez.no/document/d/1SLuBI6HQqX_PJnswCOaV6MyW2AbOd0-1wTDwhHIf3f4/edit (anyone should be able to edit it, or make remarks through comments). I hope this fits you well and I am looking forward to your feedback ! -- Nicolas
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 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
