[zeta-dev] Website #2
Hello, on the website: http://incubator.apache.org/zetacomponents/documentation/install.html its stating you are using BSD license. This should be changed. Btw - do you prefer Jira bugs for my website comments? Cheers christian
Re: [zeta-dev] Website online, help appreciated
Apache Zeta Components is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by eZ Systems. Apache Zeta Components originally were developed by eZ Systems under the name eZ Components and was generously sponsored to the Apache Software Foundation for further development. For me it's sounding wrong, the code was *donated*, the incubation is not sponsored, or perhaps I'm missing something there. +1 donated sounds more fitting to me too. But I am not native a native speaker, as you already might have noticed :-)
Re: [zeta-dev] Website online, help appreciated
Hi, I just browsed through the website and noticed that all internal links are broken besides the ones in the navigation bar. E.g. /documentation/overview.html. Here the top level zetacomponents directory is missing in the path. Btw. is it possible to redirect the whole ezcomponents.org to the new website? Maybe to a special info page that ezc is now zeta. And is it also possible to put the old issue tracker in read only mode with a small notice? Regards, Andreas Am 06.08.2010 09:24, schrieb Tobias Schlitt: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, as you probably noted, our website is online in a first version. The official address is http://incubator.apache.org/zetacomponents In addition to that, I redirect http://zeta-components.net http://zeta-components.org http://zetacomponents.org to this address. Kore owns http://zetacomponents.org in addition, but this one is not redirecting, yet, since he is on vacation. If we become a top level project somewhen, I'd suggest one of these to be transfered to the ASF to avoid the need redirecting. I wonder, which of these domains we want to have as the official one? I'd prefer zeta-components.org or zetacomponents.org. What do you think? The website is by now mainly a migration of the old eZ Components content. However, there are still lots of old references in it, e.g. to the eZ SVN and stuff. I'd appreciate help in checking all the sites for such stuff. Patches are very welcome. :) You can find the source in our SVN: https://svn.apache.org/repos/asf/incubator/zetacomponents/website Thanks in advance to every helping hand, have a nice weekend, 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxbuJAACgkQ5bO3TcRivBT9RACeNDGmhfQKPqqrOg6S1tCtU9k8 V9IAnRG/9nY0QOIUVG0GYRRRO8fTr4M6 =cBck -END PGP SIGNATURE-
Re: [zeta-dev] Website online, help appreciated
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 08/10/2010 11:43 AM, Derick Rethans wrote: On Mon, 9 Aug 2010, Tobias Schlitt wrote: On 08/06/2010 03:15 PM, Sebastian Bergmann wrote: Am 06.08.2010 09:24, schrieb Tobias Schlitt: You can find the source in our SVN: https://svn.apache.org/repos/asf/incubator/zetacomponents/website Is there a reason why the generated HTML files are stored as binary in Subversion Index: support.html === Cannot display: file marked as a binary type. svn:mime-type = application/octet-stream This makes diff-before-commit impossible. The reason here is, that committing a full doc update would otherwise result in a huge lot of commit mails. They are not binary files, so they shouldn't be marked as binary. I don't see the point here. We already used such binary marking for other huge portions of plain text, which tend to change now and then and pollute the commit mailinglist with a large amount of mails. So why shouldn't we do it here, too? Having diffs of generated HTML on the list feels quite senseless to me. The diff of the content source is much more important. 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxhI28ACgkQ5bO3TcRivBTBbwCeP2Bwl60iPSyxcpfvQRHsKKwy ZUMAnA+tsw50cJj7fXfISKfmKJ+u2WZU =aDvh -END PGP SIGNATURE-
Re: [zeta-dev] Website online, help appreciated
Hi Tobias, On Fri, Aug 6, 2010 at 9:24 AM, Tobias Schlitt tob...@schlitt.info wrote: [...] If we become a top level project somewhen, I'd suggest one of these to be transfered to the ASF to avoid the need redirecting. I wonder, which of these domains we want to have as the official one? I'd prefer zeta-components.org or zetacomponents.org. http://zetacomponents.org definitely. What do you think? The website is by now mainly a migration of the old eZ Components content. However, there are still lots of old references in it, e.g. to the eZ SVN and stuff. I'd appreciate help in checking all the sites for such stuff. Patches are very welcome. :) You can find the source in our SVN: https://svn.apache.org/repos/asf/incubator/zetacomponents/website I'll if I have spare time today to help. Cheers, -- Jérôme Renard http://39web.fr | http://jrenard.info
Re: [zeta-dev] Website
Hi there, On Fri, Jul 30, 2010 at 9:05 AM, Kore Nordmann m...@kore-nordmann.dewrote: Hi Maxime, On Fri, 2010-07-30 at 08:33 +0200, Maxime Thomas wrote: Good job ! Thanks. Is there a thing we can do about the copy paste that occurred on PHP code ? When you select the code and past it, each line are prefixed by # or number. It could be an improvement. Those are the code snippets generated by PHPDoc, which uses ol. I will commit the full custom code used to generate the API docs to the SVN, once it has been seconded by the ML. The PHPDocumentor Code is, let's say, not optimal. It combines Smarty templates with PHP code generating HTML code - not that easy to customize (beside generating docs and website takes something between 10 to 300 minutes depending on various factors). Feel free to fix that, though. :) Else, I ve looked to Sphynx, is it only for Python ? Looked like it to me … Jerome? :) I am currently writing a book using Sphinx and I also deliver my customer documentation using SPhinx as well. Basically, Sphinx uses RST + some cool stuff around it so migrating ZC tutorials from plain RST to Sphinx is a matter of around 2 hours of work, just to add the correct Sphinx instructions to get syntax coloring for example. However Sphinx is initially built for Python project which means it know absolutely nothing about PHP Doc, but coupling the documentation generated by Sphinx and the PHP Doc should not be that difficult actually. Hope that helps :) -- Jérôme Renard http://39web.fr | http://jrenard.info
Re: [zeta-dev] Website
On Thu, 2010-07-29 at 13:20 +0200, Jerome Renard wrote: - Is that normal that some methods do not point to the API doc ? For example if you take this page : http://zeta-components.org/documentation/trunk/Base/tutorial.html#file-operations the string ezcBaseFile::findRecursive() from This example shows how to use the ezcBaseFile::findRecursive() method: does not point anywhere, is that normal ? Yes, for now. There are no links and source code highlighting in the tutorial. It is comlicated to setup natively with python-docutils and the post-processing of the generated HTML files is just not implemented yet. I will add that at some point. - Do you think you can add some syntax coloring to the PHP code so it is easier to read ? The source highlighting in the API docs is just a matter of some CSS rules - should be easy to add. :) For the tutorials: See above. Other than that, the website looks good, I especially love the new logo, who created it ? That would be me. Thanks. :-) Kind regards, Kore -- Kore Nordmann(GPG 0xDDC70BBB) - What I do: http://kore-nordmann.de/portfolio.html - Motivate me: http://wishlist.kore-nordmann.de/ signature.asc Description: This is a digitally signed message part
Re: [zeta-dev] Website
Kore, On Thu, Jul 29, 2010 at 1:29 PM, Kore Nordmann m...@kore-nordmann.dewrote: On Thu, 2010-07-29 at 13:20 +0200, Jerome Renard wrote: - Is that normal that some methods do not point to the API doc ? For example if you take this page : http://zeta-components.org/documentation/trunk/Base/tutorial.html#file-operationsthe string ezcBaseFile::findRecursive() from This example shows how to use the ezcBaseFile::findRecursive() method: does not point anywhere, is that normal ? Yes, for now. There are no links and source code highlighting in the tutorial. It is comlicated to setup natively with python-docutils and the post-processing of the generated HTML files is just not implemented yet. I will add that at some point. Do you think that migrating to Sphinx [1] would be relevant ? Just asking. - Do you think you can add some syntax coloring to the PHP code so it is easier to read ? The source highlighting in the API docs is just a matter of some CSS rules - should be easy to add. :) Cool :) For the tutorials: See above. Other than that, the website looks good, I especially love the new logo, who created it ? That would be me. Thanks. :-) Kudos to you then :) 1. http://sphinx.pocoo.org/ -- Jérôme Renard http://39web.fr | http://jrenard.info
