Re: [zeta-dev] Proposal: Release process
Hi all On Thu, Nov 18, 2010 at 10:45 AM, Gaetano Giunta giunta.gaet...@gmail.comwrote: otoh: would we have such info available for existing components or would it be so hard to extract it in a precise and useful way that it would not be done anyway (I mean apart from the obvious compatibility that we get from the complete bundles)? Actually, there is something: http://pear.php.net/package/PEAR_PackageFileManager2 (thanks radagast from #pear for the heads up!) This opens two possibilities: * documenting it's usage with ZC instead or in addition to proposing a full package release * using it to make a full or custom (ie. jquery ui) package archive Regards James -- http://chocolatpistache.com/wiki/public/Contact Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Proposal: Release process
On 18. nov. 2010, at 07.44, Tobias Schlitt wrote: Hi guys, On 11/17/2010 03:58 PM, Jerome Renard wrote: On Tue, Nov 16, 2010 at 5:43 PM, Gaetano Giunta giunta.gaet...@gmail.com wrote: [...] But think about this: why is eZ Publish bundling the whole of the ZetaC when it only uses a couple of components? Simply because that was the easiest (and quickest) solution when I wrote the build system ;) I agree with you only required components should be included though but this discussion must go to another list ;) without talking too much of eZ Publish here, I think it makes sense in that case. eZ Publish is a framework for which people want to write extensions easily. So delivering the whole Zeta stack provides them with more comfort actually. Precisely, having all components available in such a project, is a big help, as it developers know that they every component at their disposal, for making extensions. Rolling out new features can also make use of components, which is going to be present. And as Jérôme says, it makes the process simpler. However, for a custom app, it does not make sense to bundle all Zeta Components if you only want to use e.g. Graph or Mail (which are 2 of the most used components). Yes. -- Regards, Ole Marius
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
