You are viewing a plain text version of this content. The canonical link for it is here.
Posted to zeta-dev@incubator.apache.org by Tobias Schlitt <to...@schlitt.info> on 2010/11/16 21:58:49 UTC
[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 Schlitt http://schlitt.info GPG 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
Posted by Tobias Schlitt <to...@schlitt.info>.
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 Schlitt http://schlitt.info GPG 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
Posted by Gaetano Giunta <gi...@gmail.com>.
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
Posted by Christian Grobmeier <gr...@gmail.com>.
>> 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
Posted by Jerome Renard <je...@gmail.com>.
Hi Tobias,
On Wed, Nov 17, 2010 at 9:48 PM, Tobias Schlitt <to...@schlitt.info> wrote:
> Hi Jerome,
>
[...]
>
>> PS :
>> <shameful>I 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
Posted by Tobias Schlitt <to...@schlitt.info>.
Hi Jerome,
On 11/17/2010 04:09 PM, Jerome Renard wrote:
> On Tue, Nov 16, 2010 at 10:58 PM, Tobias Schlitt <to...@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 :
> <shameful>I 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 Schlitt http://schlitt.info GPG 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
Posted by Jerome Renard <je...@gmail.com>.
Hi Tobias,
On Tue, Nov 16, 2010 at 10:58 PM, Tobias Schlitt <to...@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 :
<shameful>I 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
[zeta-dev] Published "Status update" [Was: Re: [zeta-dev] Final: "Status update"]
Posted by Tobias Schlitt <to...@schlitt.info>.
Hi all,
I just published the "Status update" article on our website. You can
find it on
http://incubator.apache.org/zetacomponents/news/002_status_update.html
and it is also visible on the home page and the RSS feed.
Thanks to everyone for the feedback,
cheers,
Toby
--
Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14
Want to hire me? Need quality assurance? http://qafoo.com
eZ Components are Zeta Components now! http://bit.ly/9S7zbn
[zeta-dev] Final: "Status update" [Was: Re: [zeta-dev] Draft: "Status update"
blog entry]
Posted by Tobias Schlitt <to...@schlitt.info>.
Hi,
I incorporated all feedback into the status update blog entry and would
ask you to review it once more. I also added the links and meta
information to it.
Please find the final version attached and in SVN under
website/content/news/002_status_update.txt
My plan is to publish it on Monday morning.
Regards,
Toby
--
Tobias Schlitt http://schlitt.info GPG 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
Posted by Tobias Schlitt <to...@schlitt.info>.
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 Schlitt http://schlitt.info GPG 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
Posted by Tobias Schlitt <to...@schlitt.info>.
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 Schlitt http://schlitt.info GPG 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
Posted by Tobias Schlitt <to...@schlitt.info>.
Hi Thomas,
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.
Regards,
Toby
--
Tobias Schlitt http://schlitt.info GPG 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
Posted by Maxime Thomas <ma...@gmail.com>.
Excellent !
A blog is effectively the best way to inform people with some modern way to
inform (RSS).
2010/11/17 Christian Grobmeier <gr...@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
Posted by Christian Grobmeier <gr...@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
Posted by Tobias Schlitt <to...@schlitt.info>.
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 <to...@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 Schlitt http://schlitt.info GPG 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
Posted by Nicolas Pastorino <nf...@ez.no>.
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 <to...@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 Schlitt http://schlitt.info GPG 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
Posted by Tobias Schlitt <to...@schlitt.info>.
Hi Nicolas,
On 11/17/2010 02:33 PM, Nicolas Pastorino wrote:
> On Wed, Nov 17, 2010 at 1:49 PM, Tobias Schlitt <to...@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 Schlitt http://schlitt.info GPG 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
Posted by Nicolas Pastorino <nf...@ez.no>.
Hi Toby,
On Wed, Nov 17, 2010 at 1:49 PM, Tobias Schlitt <to...@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 Schlitt http://schlitt.info GPG 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
Posted by Tobias Schlitt <to...@schlitt.info>.
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 Schlitt http://schlitt.info GPG 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
Posted by Nicolas Pastorino <nf...@ez.no>.
Hi Toby,
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).
Cheers,
--
Nicolas
On Nov 16, 2010, at 22:58 , 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
>
> --
> Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14
> Want to hire me? Need quality assurance? http://qafoo.com
> eZ Components are Zeta Components now! http://bit.ly/9S7zbn
> <002_status_update.txt>
--
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