Leaving the project
Hi all, I just wanted to let you know that I am leaving the project. Due to a recent carrer move I stopped using PHP and stopped using the Components. Is it possible to get my commit access revoked so it avoids any potential problem ? If you prefer I can ask Infra to do this, just le me know. I wish you all the best for the future. Best Regards, -- Jérôme
Re: [zeta-dev] Close issue #95
Hi, Regarding you problem with Jira, Julien should be able to fix it, ref https://issues.apache.org/jira/browse/INFRA-4208 -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Thought experiment: A first release …
Good morning, On Fri, Apr 8, 2011 at 8:05 AM, Jerome Renard jerome.ren...@gmail.com wrote: [...] The list I propose (anything can be discussed/added/removed of course :)) - Template string functions are not multibyte safe : https://issues.apache.org/jira/browse/ZETACOMP-15 - Extractor does not extract comment : https://issues.apache.org/jira/browse/ZETACOMP-2 - Component crashes with large uploads (1GB) : https://issues.apache.org/jira/browse/ZETACOMP-70 - Links to PHPDoc are broken in code snippets in tutorials : https://issues.apache.org/jira/browse/ZETACOMP-65 - Autoloader should support namespaces in custom class repositories : https://issues.apache.org/jira/browse/ZETACOMP-66 - X-Powered-By:eZ Components MvcTools in the PHP header and User-Agent: eZ Components in the email header : https://issues.apache.org/jira/browse/ZETACOMP-49 As a follow-up ZETACOMP-15,2 and 49 are fixed. I am having a look at ZETACOMP-66. (It is really time to get a release) Have a nice day :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Issues Integrating ezcDbHandler into other code
Hi Davy, On Tue, Aug 9, 2011 at 11:11 PM, Davey Shafik da...@php.net wrote: Hi, I'm having an issue with the reusability of the ezcDbHandler within my project. ezcDbHandler directly extends the internal PDO class; which when instantiated, represents the actual DB connection. This causes problems when I already have a connection. Specifically, the issue is that I wish to use ezcWorkflowDatabaseTiein, which requires an ezcDbHandler object in it's constructor. This is fine, except that in order to fulfill this requirement, I need to instantiate a /second/ connection to the DB with ezcDbHandler instead of re-using the PDO instance I already have elsewhere in my code. A solution to this is to make ezcDbHandler a facade for the PDO instance, and allow passing in an existing PDO instance instead of a DSN. The only backwards compatibility issue is that any code that currently does: [snip] You can find a readable patch for this relatively simple change here: https://gist.github.com/09c3ab355dd9d95da5ff And this is the actual patch, with the whitespace changes (I put an is_array() around the dbParams too, bumping the indent): https://gist.github.com/1bdd3fb370c0449f8aa4 What are the chances of this being integrated into Zeta? I am concerned about the BC break here as it is clearly stated in the development process that BC can not be broken once a component in Final state [1]. There is absolutely no way for you to use ezcDbHandler everywhere instead of mixing pure PDO and ezcDbHandler ? 1. https://incubator.apache.org/zetacomponents/community/dev_process.html#version-states -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Incubator PMC/Board report for August 2011 (zeta-dev@incubator.apache.org)
Heya, On Fri, Aug 5, 2011 at 1:40 PM, Julien Vermillard jvermill...@gmail.com wrote: I think we should blame Holidays :) He he, month of August ... ;) On Fri, Aug 5, 2011 at 12:44 PM, Christian Grobmeier grobme...@gmail.com wrote: Hello - is anybody out there? Sir yes Sir ! ;) The wiki has been updated if there is anything incorrect/missing/unclear/whatever feel free to ping me. Have a nice day :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Re: [zeta-commits] svn commit: r1145100 - in /incubator/zetacomponents/trunk/Authentication: src/options/session_options.php src/session/authentication_session.php tests/session/session
Hi Derick, On Mon, Jul 11, 2011 at 2:28 PM, Derick Rethans der...@apache.org wrote: On Mon, 11 Jul 2011, Jerome Renard wrote: On Mon, Jul 11, 2011 at 12:11 PM, Derick Rethans der...@apache.org wrote: On Mon, 11 Jul 2011, jero...@apache.org wrote: @@ -45,12 +47,16 @@ * /code * * @property int $validity + * The maximal amount of seconds the session is valid. + * @property int $idleTimeout * The amount of seconds the session can be idle. * @property string $idKey * The key to use in $_SESSION to hold the user ID of the user who is * logged in. I thought I had commented on this before, but doesn't this change the already existing behaviour? If you commented on this before I did not receive anything (which is weird) Normally this does not change the already existing behaviour. And in which abnormally cases does it? (I just want to make this clear!) :-) None ;), using normally is a frenchism. Furthermore the entire test suite passes which means nothing has been broken and the initial behaviour has been left unchanged. It's probably also good to add this to the tutorial! Ho, good idea, I'll try to do that when I have spare time. -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
[zeta-dev] Re: Review Request: Session timeout
Hi James,
2011/6/16 James Pic james...@gmail.com:
I was thinking of:
$lastActivity = time() - $_SESSION[$this-options-lastActivityTimestampKey]
if ( isset( $_SESSION[$this-options-lastActivityTimestampKey] )
$lastActivity = $this-options-idleTimeout )
What do you think ?
Then we would forced to do this :
$lastTimestampKey = false;
if ( isset( $_SESSION[$this-options-lastActivityTimestampKey] )
{
$lastTimestampKey = $_SESSION[$this-options-lastActivityTimestampKey];
$lastActivity = $now - $_SESSION[$this-options-lastActivityTimestampKey];
}
if ( $lastTimestampKey $lastActivity = $this-options-idleTimeout )
{
$this-destroy();
$this-regenerateId();
return self::STATUS_EXPIRED;
}
I am not sure it is more readable, what do you think ?
Have a nice day :)
--
Jérôme Renard
http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Documentation
Hi James, On Tue, Jun 7, 2011 at 12:27 PM, James Pic james...@gmail.com wrote: Hello everybody, Kudos to Gavin for setting up my wiki access! Here is the table of contents i propose: https://cwiki.apache.org/confluence/display/ZETACOMP/Tutorial+TOC Any early thoughts you want to share ? I Like :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Pake based build system
James, On Mon, Jun 6, 2011 at 6:09 PM, James Pic james...@gmail.com wrote: On Mon, Jun 6, 2011 at 5:43 PM, Jerome Renard jerome.ren...@gmail.com wrote: Just in case, what is your version of PHP ? 5.3, the error was solved after enabling bz2.so php extension ... I'll try to fix the many warnings that happen on my setup ... Thanks for making the Pakefile btw, it looks great! You are welcome, any feedback/help is much welcome :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Build system evaluation
Hi Maxime, On Fri, Apr 15, 2011 at 10:09 AM, Maxime Thomas maxime.t...@gmail.com wrote: [...] Reading all the mails on this topic, I was wondering if all this can be turned in a component to add to AZC. It could be the 'Package' component and it could be compliant with all standards (Phing, Pake, Phar, Ant, blablabla). What do you think ? Could you please elaborate ? :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] PHP based build system : Phing VS Pake
Gaetano, On Thu, Apr 14, 2011 at 11:23 AM, Gaetano Giunta giunta.gaet...@gmail.com wrote: Jerome Renard jero...@apache.org wrote on 14/04/2011 11:11: [...] I believe you can define environment variables on Windows: - https://fisheye6.atlassian.com/browse/zetacomponents/website/Pakefile?hb=true#to150 Sure enough - albeit it's not as common to do it as it's on unix. Ok. I still prefer cli options than env vars for 90% of the time though, as it's easier to understand what is happening when the options are explicit. But, as far as I can see in your code, what you can do is that you can swap out one config file with another. What I was asking to is to separate cofig options: one set that is project-specific (stored in the config file), and one set that is specific to the build environment (passed via cli options or env vars). I'll see how to pass arguments from the command line in Pake then. -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] PHP based build system : Phing VS Pake
Hi Alexey, thanks for your feedback. On Wed, Apr 13, 2011 at 10:40 PM, Alexey Zakhlestin indey...@gmail.com wrote: [...] Any feedback welcome :) line 30: I'd use pake_echo_comment() instead. same for other similar lines Fixed. lines 94-117: 1) I'd use pake_sh($command, true) Fixed. 2) don't forget to use escapeshellarg() where appropriate Yep, I will take care of that later. lines 134-137: pake_mkdirs($targetDir, 0755); // no need for if. pake take cares of that Fixed lines 139-149: pake_copy($tarball, $targetDir.'/'.$options['build.name'].'.tar.bz2'); Fixed lines 142-143: pake_remove_dir($options['build.dir'] . '/phpdoc/'); Fixed lines 243-245: pake_rename( $HTMLFile, dirname( $HTMLFile ) . '/' . $newHTMLFile ); Fixed pake's versions of basic filesystem-functions are good because: 1) they do nothing, if nothing has to be done (won't try to delete non-existant file, won't copy file if source is older than target) 2) they report what they do to console as the result, you have to type less code Yep that is what I noticed, and that gave me a couple of ideas to enhance ezcBaseFile Thanks :)
Re: [zeta-dev] Migration from Make to Ant
Hi Gavin, On Tue, Apr 12, 2011 at 12:46 AM, Gav... ga...@16degrees.com.au wrote: -Original Message- From: Derick Rethans [mailto:der...@apache.org] Sent: Tuesday, 12 April 2011 6:13 AM To: zeta-dev@incubator.apache.org Subject: Re: [zeta-dev] Migration from Make to Ant On Mon, 11 Apr 2011, Jerome Renard wrote: I started to create an Ant based version of the Makefile available in website/ The problem with the Makefile is that it does not work at all on Mac Os X and is kind of hard to read. I am afraid that nobody else uses Ant here, so I would oppose that. Have you asked every user of Zetacomponents whether or not they use Ant? Where are the emails and replies for that? This is an open source project in an open source world housed at an open source organisation. You cannot oppose volunteers scratching their own itch. If jerome wants to provide an Ant alternative I do not see the harm. If Jerome then wants to replace Make with Ant then that is another matter but still something that 'you' personally cannot oppose, that is a decision for the Podling PMC or the Incubator PMC, no one person has power here and the sooner folks realise this the sooner you might start attracting those new committers your board report said you needed. Well I think I should have explained the context which lead me to translate the Makefile to its Ant equivalent. At the end of last week I was discussing with Tobias as couple of things about the documentation and patches I had for it. I then realized the Makefile simply did not work on my laptop and after spending quite some time to fix stuff here and there with no acceptable results I thought it would be easier and faster to use something more cross-platform than this Makefile. The choice of Ant came naturally because: 1. it is cross-platform (well if you do not use system specific executables of course :)) 2. it is an ASF project So using a ASF cross-platform tool looked like the right choice to me. -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
[zeta-dev] PHP based build system : Phing VS Pake
Hi There, The debate we got earlier [1] on this list after I posted a very early version of the Ant based build script showed that we were possibly going in the wrong direction. After chatting on IRC we realized that (some statements might look obvious to you): 1. the actual Makefile is hard to read 2. the actual Makefile is not cross-platform at all 3. the actual Makefile is a PITA to maintain 4. the Ant build file is not as cross-platform as I hoped it was (my bad) 5. the Ant build file will most likely be a PITA to maintain as well So we thought it could be a good idea to have a look at PHP based build systems. Our requirements are: - the build system must be cross platform as much as possible - the build system must be simple to use and simple (our part) to maintain. - the build system must be easy to use I found Phing and Pake and here is what I think about them (please not that I had a look at those tools during lunch as it was the best I could do. If I overlooked anything feel free to tell me): Phing: - looks big (bigger than the default Ant) - provides a lot of features - is XML based - is supposed to be Ant for PHP but does not seem to be 100% compatible with Ant files - is very well documented Pake: - is smaller than Phing (not hard) - is not as clearly documented as Phing, some parts of the documentation are still missing - is not XML based (Derick will appreciate that :P) - claims to be Make for PHP and it seems it is My preference would go to Pake as it looks much simpler for our needs and we could end up with a very-easy-to-maitain build script. What I appreciate with Pake is that you can get total control and freedom on what you do. It already provides all the features [2] we need in order to build the docs and the website, and if one of the library is not what we need we could use AZC easily. I will try to give Pake a try as soon as possible. But if one of you already has experience with Phing or Pake I would be happy to get your feedback about these tools :) this is the auto flagellation part I plead guilty for imposing Ant, the reason is that I have been using it for a couple of years already and I thought it would solve problems we got in the Makefile. But I was wrong. this was the auto flagellation part 1. http://mail-archives.apache.org/mod_mbox/incubator-zeta-dev/201104.mbox/%3cbanlktikgtskkg1yc+ierxt66a7ka_85...@mail.gmail.com%3E 2. https://github.com/indeyets/pake/tree/master/lib/pake
[zeta-dev] Re-generating tutorials
Hello, I have a couple of fixes for #ZETACOMP-33 [1] and I need to regenerate the tutorials in the website in order to check that my changes are correct. I ran make tutorials in website/ but got nothing generated, did I do anything wrong ? Note: all changes are local, I have not committed anything. :) 1. https://issues.apache.org/jira/browse/ZETACOMP-33 -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
[zeta-dev] Karma for Jira
Hi there, I can not close issues in Jira, could I get a karma update for my Jira account (username: jeromer) ?. Thanks a lot and have (hopefully) a sunny week-end :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Bug with Webdav + Bugfix
Hi Christian, On Wed, Mar 30, 2011 at 2:40 PM, Christian Weber webe...@hdpmail.de wrote: Hi all. I wanted to open a Bug at the issue tracker but at some reasons i didn't receive any registration mail. This is weird. I filed an issue on your behalf : - https://issues.apache.org/jira/browse/ZETACOMP-70 However I did not attach your patches to avoid any legal issue. I would recommend you to upload the patches yourself (once you can login into JIRA) and to grant license to ASF for inclusion in our code base. Best Regards, -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Re: Review board
Hi Tony, On Tue, Mar 29, 2011 at 1:03 PM, Tony Stevenson pct...@apache.org wrote: I take that last bit back. Jeroem has been added to the group, he can now login and manage the remaining members. I confirm, it works just fine. Thanks for your support :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
[zeta-dev] New group in Review Board
Hi Christian, I just discovered that ASF provides a Review Board instance there : https://reviews.apache.org/ There is no Zeta Components group yet and it seems I can not create one. Do I have to ask Infra for a new group or do I need something else ? Have a nice day :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Naming convention : *List variables
Bertrand, On Mon, Mar 21, 2011 at 8:07 PM, Bertrand Dunogier b...@ez.no wrote: On 21 March 2011 19:26, Jerome Renard jerome.ren...@gmail.com wrote: 19:20 jerome@gimli/private/tmp/ezpublish% grep -nR [a-z]List kernel lib | wc -l 6012 I have given my opinion, not the 10 past years authors' :-) Yeah I know, that was just to tease you a bit ;) There are indeed a few situations where I believe a word makes much more sense than a simple 's', but not generally speaking. Anyway, let's say my idea was stupid/useless/not relevant/other and close this thread. Sorry if my answer was irrelevant and made you feel that way... I thought I had merely given my view about the proposal you had made. Ho, everything is OK. The discussion showed my idea was not as good as I initially thought. I would just avoid losing time on this (bad) idea and focus and the rest in order to get a release. Cheers :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Git mirror ?
Hi all, On Sun, Mar 6, 2011 at 7:47 AM, Jerome Renard jerome.ren...@gmail.com wrote: Hi there, [...] Ticket closed. We now have a Git repository available at http://git.apache.org/zetacomponents.git/ It seems the repository is empty. I synced with Infra in order to see how they can fix that. I'll let you know when it is OK. -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
[zeta-dev] [patch] ezcBaseOptions should be traverseable
Related issue : https://issues.apache.org/jira/browse/ZETACOMP-39 Hi there, you will find attached a patch for two alternatives to fix ZETACOMP-39. Alternative 1 (alternative1.diff): simply add a new method that return the list of available properties so a user can fetch them and do anything he wants with it. Alternatice 2 (alternative2.diff): ezcBase implements Iterator so doing a simple foreach makes it possible to loop through properties Any feedback welcome. :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard alternative2.diff.gz Description: GNU Zip compressed data alternative1.diff.gz Description: GNU Zip compressed data
Re: [zeta-dev] [patch] ezcBaseOptions should be traverseable
All, On Wed, Feb 23, 2011 at 6:51 PM, Gaetano Giunta giunta.gaet...@gmail.comwrote: Jerome Renard wrote: Related issue : https://issues.apache.org/jira/browse/ZETACOMP-39 [...] Alternative 2 (alternative2.diff): ezcBase implements Iterator so doing a simple foreach makes it possible to loop through properties Here is a new patch implementing alternative 2 correclty (I completely forgot next(), current() ... functions). The patch (alternative3.diff) is now much cleaner. -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard alternative3.diff.gz Description: GNU Zip compressed data
Re: [zeta-dev] Patch: DateTime functionality for Template
Hi Tobias, On Mon, Jan 31, 2011 at 2:08 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I had a quick chat with Derick during PHP Benelux about this patch. He suggested to make the DateTime objects in Template immutable. I'm pretty much for doing so and would actually desire to change that in PHP itself, if it would be possible. Making DateTime objects immutable would result in much more sane behavior of date_modify(), date_add() and friends, since they would no more change the original object, but return a new one which has the desired manipulation applied. We've an implementation for immutable DateTime lying around, which we could just move to Base/ so it's available for others easily, too. Find the code attached. What do you think? Totally agree. BTW your implementation of the DateTime extension looks a bit too complex. Do we really need all these private function *add() methods ? Wouldnt'it be possible to just avoid them and move their contents to the public ones ? I may have overlooked something though. +1 for moving the code to Base anyway. :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] [VOTE] Release process
Hello, [X ] +1 (accept release process) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Online: Survey on PHP library release modes
Hi Tobias, On Thu, Dec 2, 2010 at 9:58 AM, Tobias Schlitt tob...@schlitt.info wrote: Hi, as already mentioned yesterday, the survey is now online. If you want to link it, please use http://bit.ly/phplibrelsur or link to my blog entry about it, which can be found at http://schlitt.info/opensource/blog/0738_php_library_release_survey.html I added a blog entry here (mostly a copy and paste version of your post) : - http://jrenard.info/blog/php-library-release-survey.html Cheers :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Survey on PHP library release modes
Hi Tobias, On Wed, Dec 1, 2010 at 4:17 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, you can find the survey under https://spreadsheets.google.com/gform?key=tLcGit0fRn5vovDpGSpFOag Looks good to me :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Documenting our coding style
Hi,
On Fri, Nov 26, 2010 at 2:23 PM, Derick Rethans der...@apache.org wrote:
On Tue, 16 Nov 2010, Tobias Schlitt wrote:
for another project I needed to give advice on the coding standard used
by Apache Zeta Components. There is some very old version of the eZ
Publish coding style in [1] (from 2001) but no reliable, recent source.
So I think we should document our coding style on the website.
Please complete / correct my following brainstorming:
- Indentation with 4 spaces
- After a {
- On breakup of long lines ( 78 chars) after a (
- { and } on a new line
- 1 space after ( and before )
- No space after [ and before ]
- 1 space after ,
- 1 space before and after .
- Almost always camelCase
- classes always start with ezc followed by an upper case char
- constants all in upper case with _
There is also a script at
http://svn.apache.org/repos/asf/incubator/zetacomponents/scripts/syntax-check.sh
that has a few rough automated checks.
I remember I used a PHP Code Sniffer standard for ZC is it still
available somewhere ?
I tried the old URL and it seems it's no longer there.
Best Regards,
--
Jérôme Renard
http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Documenting our coding style
Maxime, On Sat, Nov 27, 2010 at 10:29 AM, Maxime Thomas maxime.t...@gmail.com wrote: I saved in my bookmarks this one : http://pear.xplib.de/get/ http://pear.xplib.de/get/Max Cool, thanks :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] PHPUnit's usage
Hi Sebastian, On Sat, Nov 27, 2010 at 10:57 AM, Sebastian Bergmann sebast...@apache.org wrote: Am 27.11.2010 10:51, schrieb Jerome Renard: for those of you who are forced (like me) to use PHPUnit 3.4.* and can not (or do not want to) upgrade, you can run the following command to restore the PHPUnit 3.4.* compatible version of UnitTest/ Why are you forced to use PHPUnit 3.4? Because I work on something else that seems to be incompatible with the latest PHPUnit stable version. And since I can not commit fixes I am stuck with PHPUnit 3.4 Hopefully that will be fixed in a couple of weeks :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Survey on PHP library release modes
Hi Tobias, On Sat, Nov 27, 2010 at 7:40 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I'm about to start a little online survey to check out how users in the PHP world would love to see their favorite libraries being released. I'll mainly do this out of private interest, but it might also help us to optimize our release process. Excellent idea :) Find below some questions for discussion. Whenever there is no additional info, only a single answer may be chosen. 1. Which libraries / frameworks do you use? (multiple answers possible) - ADOdb - Apache Zeta Components - Cake PHP - CodeIgniter - Doctrine 1 - Doctrine 2 - eZ Components - Horde - PEAR - Propel - Seagull - Symfony - Zend Framework - Another framework / library (free text) - I code everything on my own 2. What is your preferred way of installing PHP libraries? - PEAR - Custom installer - Manual download - OS based package management I would just add something like (apt-get, yum, rpm), just to avoid any confusion from beginner users. - Version control (SVN external, Git sub-module, etc.) - Something else (free Text) 3. Do you prefer bundles over single component installs? - I want to install each component separately - I want a bundle with all components from a library 4. How would you expect a PHP library project to do releases? - Irregularly whenever something is ready - Regularly with multiple additions bundled 5. How do you want to deploy PHP library components? - I bundle library components with my application - I deploy libraries and application separately Do you have anything to add / change? Even though I think it looks really good, would you think relevant to add a question about depedency ? For example framework needs external dependency X or Y. How do they prefer installing this dependency ? Possible options: - via PEAR - I want to get it bundled with the framework - I want to install it manually Not sure I am completely clear here. If it's not just tell me :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Introducing myself
Hi Henri, On Tue, Nov 23, 2010 at 4:43 PM, Henri Bergius henri.berg...@iki.fi wrote: Hi, [...] So, how to get started? I guess the main thing is to get familiar with the existing Zeta Components, and then to start thinking of what of those we could use within our framework, and what parts of our framework could be contributed back to Zeta. Some low-hanging fruit could include: As you said, the very first thing to do is to get familiar with Zeta Components. But with regards to what you have already done with Midgard, I believe it will be a piece of cake. You have to start with ezcBase [1] for two reasons : 1. to get the whole idea of the autoload mechanism because can be quite confusing when it comes to add your own classes. 2. because this is the only dependency for any other component. If you need to get a helicopter view in order to understand how ZC are organized you can have a look at at talk Derick gave a while ago [2]. Maybe Tobias and Kore have more recent slides. * Geolocation library: https://github.com/bergie/midgardmvc_helper_location This one is really interesting. * Our MVC framework: https://github.com/midgardproject/midgardmvc_core If possible I would prefer getting only one MVC component in order to avoid confusion for users if they want to do MVC. This does not meant yours is bad at all, it just means that being able to compare differences with MVCTools [3] and your MVC framework would be ideal first. And then we could see how to manage with this, maybe we could integrate some parts of your system in MVCTools. This needs to be debated actually. Anyway welcome to the Zeta Components community :) 1. http://incubator.apache.org/zetacomponents/documentation/trunk/Base/tutorial.html 2. http://derickrethans.nl/talks/ezc-ezconf9.pdf 3. http://incubator.apache.org/zetacomponents/documentation/trunk/MvcTools/tutorial.html -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
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] Proposal: Release process
Hi Tobias; On Thu, Nov 4, 2010 at 5:28 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I have studied the guidelines for releases in the ASF and tried to make up a release process document for us. Please find it attached for discussion. You can also find it in our SVN under docs/release_process.txt The document summarizes the requirements for releases roughly and then tries to relealize these in a release process specific to Zeta. There are some open issues marked with notes in this document, which need to be decided on. I just read the document and I have a few (nitpicking) questions. In ASF, an **RC is any kind of package that is meant to be published later**, but is at first only provided to developers for testing. How will version numbers will be managed ? I have the feeling the version numbering system will become completely different from the previous versions (eZ Components days). Am I correct ? The first type refers to a release of a single component, independently from any other. Since (almost) all ZC have a dependecy with the Base component, what will be the process in case of (major) update of ezcBase ? Will all the other components released once again ? This choice can happen informally among the maintainers of a component. What does informally means here ? If that means deciding to release over jabber or IRC while chatting with a maintainer after lunch I do not agree. It is not really a of matter of trust but more a matter of transparency. If a (group of) maintainer(s) decide to release a new version of a specific component, fair enough but I think this decision must be sent to the dev-(users ?) mailing list to at least inform that an update will happen. A full package release does not occur as needed, but fixed dates twice a year. I believe you meant every 6 months. Just to avoid any miscomprehension .. note:: Determine release times. How about March and September ? I do not know what you guys think but release in January and June (or July) does not sound that good to me. I also fixed a few minor issues (spelling, typos etc) in the document, patch attached. :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard release_process.diff.gz Description: GNU Zip compressed data
Re: [zeta-dev] Proposal: Release process
Hi Gaetano, 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 ;) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Proposal: Release process
Hi Maxime, On Tue, Nov 16, 2010 at 5:47 PM, Maxime Thomas maxime.t...@gmail.com wrote: [...] And honestly, I cannot see the problem of downloading all even if you don't use some parts. Who can do the more can do the less. Yes, but less is more :D Ok --- [] -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
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] Contributing / ZETACOMP-8
James, On Tue, Aug 24, 2010 at 3:12 PM, James Pic james...@gmail.com wrote: [...] I sent the iCLA last week, still waiting for commit access to migrate the stuff and get the design doc started for the current Configuration proposals. I did not have time to work on that yet. -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Contributing / ZETACOMP-8
Hi (hijacking the thread a bit) On Mon, Aug 23, 2010 at 11:24 PM, Craig L Russell craig.russ...@oracle.com wrote: For future reference, the best way to send ICLAs to Apache is to print, sign, scan, and email the pdf document, exactly as Patrick did. Patrick's ICLA was filed this morning. I just sent my iCLA to secret...@apache.org, if there is anythin wrong feel free to tell me. Best Regards, -- Jérôme Renard http://39web.fr | http://jrenard.info
Re: [zeta-dev] PHPUnit's usage
On Fri, Aug 20, 2010 at 7:54 AM, Sebastian Bergmann sebast...@apache.org wrote: Am 20.08.2010 07:49, schrieb Tobias Schlitt: Is there a chance we can replace the current UnitTest stuff with a proper usage? There is nothing in the UnitTest test runner that we need. The only reason we still have it is because Derick (and maybe others) prefer commandline switches over PHPUnit's XML configuration file to configure the test suite (the database connection, for instance). There are two problematics here : 1. being PHPUnit compliant 2. providing control to each user I propose the following : 1. provide a default XML file with everything preconfigured along with a README file explaining requirements for the database for instance 2. provide a system that loads custom phpunit XML file where everyone can define whatever he wants. Basically that would work that way : if custom phpunit.xml fil existst then load and use it else load and use the default one fi Is that possible ? Cheers, -- Jérôme Renard http://39web.fr | http://jrenard.info
Re: [zeta-dev] PHPUnit's usage
Hi Sebastian, On Fri, Aug 20, 2010 at 8:11 AM, Sebastian Bergmann sebast...@apache.org wrote: Am 20.08.2010 08:01, schrieb Jerome Renard: Is that possible ? That functionality is built into PHPUnit already: * If phpunit.xml exists, it will be used. * If phpunit.xml does not exist but phpunit.xml.dist exists, the latter will be used phpunit.xml.dist is under version control while phpunit.xml is not (and ignored from version control as well). Ha cool, then it seems we could get all what we need with this system and we could get rid of the UnitTest component. Am I correct ? -- Jérôme Renard http://39web.fr | http://jrenard.info
Re: [zeta-dev] [Vote] Restricted wiki usage
+1
Re: [zeta-dev] Configuration component override mechanism : requirement doc
James, Hopefully my brain works better than earlier today. The more I think about the override thingy the more I tend to think the following : - The merge/inheritance (pick the word you like :D) could easily be integrated in the native Configuration component. I also already have the algorithm for that as well as tests, so I believe that could be quite fast to integrate this feature in Configuration. - The system around such as the directory structure, compilation and caching stuff could be integrated into a dedicated component that could be a tiein between Configuration and Cache. That way, everything is clean and separate, if you want to use only the merge algorithm for a few configuration files, then fair enough just use Configuration only. If you want more than that, then use the tiein. What do you think ? :) -- Jérôme Renard http://39web.fr | http://jrenard.info
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] Re: Class prefix change, was: Re: [zeta-dev] Welcome Apache Zeta Components - SVN up and running :)
Hello, On Sat, Jul 31, 2010 at 6:31 PM, Tobias Schlitt tob...@schlitt.info wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Andreas, On 07/31/2010 05:15 PM, Andreas Schamberger wrote: for me it seems wrong if I think 'zeta' and have to type 'ezc'. But maybe this is just a problem for me ;) I fully understand your concern here and I would still be in favor of changing the prefix. However, there should be way of full BC for this and until now we did not find any. Maybe, we will come to a point where we start building Zeta 2.0 somewhen in the future. The we should migrate to using namespaces anyway and the issue will be fixed. I just wanted to have raised my concern. I'll shut up and let's forget about it ;) I think it was quite useful having this discussed publicly again. :) Both options (keeping and updating the ezc prefix) have both pro and cons and as far as I am concerned I have no preference. However I think it is important not to confuse ZC users and as such I would recommend to provide some kind of FAQ explaining why the prefix is ezc for now, and what are (of any) plans for the future. Maybe a full page explaining the history of ZC, from eZ Components to Zeta Components would help clarify the context for new users. I can write such a page if you want. Confused users became generally unhappy user after some period users, and that we should definitely try to avoid. What do you think ? My 0.02 cents, -- 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
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
Re: [zeta-dev] SVN test import online; releases/ and release-info/?
Hi Tobias, On Mon, Jul 19, 2010 at 7:36 AM, Tobias Schlitt tob...@schlitt.info wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, our test import is up and running on http://svn.apache.org/repos/test/gmcdonald/zeta/ Looks good so far. :) Please check out and test! 404 I wonder what should happen with - - releases/ - - release-info/ directories. They contain all previous eZ Components releases and corresponding release notes (release-info/). I think we should not keep them in the new SVN, but have them imported anyway. We can then delete them afterwards. This way, we still keep their history. What do you say? I think releases/ and release-info should stay in SVN, unless there is a very good reason to move them elsewhere. Cheers, :) -- Jérôme Renard http://39web.fr | http://jrenard.info
