Re: [VOTE] retire zeta components from incubation
+1 GitHub rocks your socks !
Re: Migrating Zeta Componetns to Github
Can't apache just pass the repo to say Derick or something ? https://github.com/apache/zetacomponents
Re: Migrating Zeta Componetns to Github
On Fri, Apr 20, 2012 at 2:16 PM, Derick Rethans der...@apache.org wrote: On Fri, 20 Apr 2012, Benjamin Eberlei wrote: Derick already opened an Organization on Github and I guess all current committers will get write access to it. I've also set-up a mailinglist: z...@lists.xdebug.org Thank you ! How can I subscribe to the ML ? Regards
Re: Migrating Zeta Componetns to Github
Do you want people to maintain their components, contribute to other's components ? If that's a need then the purpose of the migration should help this, and not just about throwing the code at github's face.
Re: [zeta-dev] Re: Zeta Components report is late
On Sun, Feb 12, 2012 at 8:07 PM, Julien Vermillard jvermill...@apache.orgwrote: Hi, Sorry for the late reply, I was busy with my newly born son. I signed off the report. On the lack of activity azc is already quite a mature and used library, why not concentrate on releasing something ? Making a broken/untested release is out of the question. We're almost done migrating to PHPUnit 3.6/master. After PHPUnit accepts this pull request, we can start working on the components one by one again. https://github.com/sebastianbergmann/phpunit/pull/495 Regards
[zeta-dev] Re: PHPUnit regression: cannot run the testsuite of one component
We might have a better solution, if only Sebastian accepts to add a --testsuite filter. Please read the pull request description for details: https://github.com/sebastianbergmann/phpunit/pull/494 Credits to Derick for his great support while finding/implementing this solution (0day fix found, feels great B). Cheers from Portugal
Re: [zeta-dev] Re: PHPUnit regression: cannot run the testsuite of one component
Sorry there was a small isssue with the previous pull request so here's the new URL: https://github.com/sebastianbergmann/phpunit/pull/495
Re: [zeta-dev] Close issue #95
Fantastic, thanks Jerome.
Re: [zeta-dev] Close issue #95
Thanks for your help guys Cheers
Re: [zeta-dev] Zeta Components Release on 2011-12-22 - Issue Management
what would be nice, if you can confirm my two failing unittests for the archive component or if they are not failing for you What patch are you talking about ?
Re: [zeta-dev] Two review requests pending
Did you try another browser (maybe webkit based if you used gecko) ? It works here with chromium...
Re: [zeta-dev] Pake based build system
Hi Jerome, I run into a strange error, both as normal user and as root (which should not change anything according to the file permissions, but i tried anyway): pake website svn update classes exec '/usr/bin/svn' update 'classes' svn update scripts exec '/usr/bin/svn' update 'scripts' svn update templates exec '/usr/bin/svn' update 'templates' file+content/documentation/trunk/MvcTools/HelloMvc/www/.htaccess PHP Warning: copy(../trunk/MvcTools/docs/HelloMvc/www/.htaccess): failed to open stream: No such file or directory in /home/jpic/lib/pear/pake/pakeFunction.php on line 133 # Generating index files file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/ImageConversion/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/PersistentObjectDatabaseSchemaTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/SignalSlot/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/ImageAnalysis/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/File/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/PhpGenerator/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Feed/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/TranslationCacheTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Translation/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/WorkflowEventLogTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/ConsoleTools/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Cache/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/UserInput/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Search/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/PersistentObject/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/TreePersistentObjectTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Template/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/AuthenticationDatabaseTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Base/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Mail/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Tree/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Webdav/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/EventLogDatabaseTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Configuration/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/EventLog/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Execution/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/WorkflowDatabaseTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/DatabaseSchema/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Url/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Workflow/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Authentication/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Graph/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/TreeDatabaseTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/design/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Database/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Document/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/MvcTools/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/SystemInformation/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Archive/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/TemplateTranslationTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/Debug/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/GraphDatabaseTiein/.index.xml file+ /home/jpic/src/zeta/website.svn/content/documentation/trunk/WorkflowSignalSlotTiein/.index.xml # Extracting tarball
Re: [zeta-dev] Proposal: Commit guidelines
Hi Tobias, On Fri, Apr 1, 2011 at 4:06 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I wrote down our commit guidelines. Please review them shortly, before I commit: There is a typo at the end: corrsponding. Thanks for writing down the commit message guidelines, that'll save some IRC action. Cheers
Re: [zeta-dev] Welcome: Benjamin and Jerome
On Fri, Apr 1, 2011 at 7:49 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I'd like to officially welcome Jerome (jeromer) and Benjamin (beberlei) as Apache Zeta Components committers. Congrats for your very well deserved promotion! Thanks again for your participation JB. Cheers
Re: [zeta-dev] FYI: Wiki online
Hi all, Sorry for bumping this old thread but maybe it lacks some critical information. On Fri, Aug 13, 2010 at 1:57 PM, Tobias Schlitt tob...@schlitt.info wrote: Just for the records, On 08/13/2010 01:55 PM, Tobias Schlitt wrote: https://cwiki.apache.org/ZETACOMP/ is actually an export of the generated wiki sites. For editing, https://cwiki.apache.org/confluence/display/ZETACOMP/ is used. I tried my login jpic but it won't log me in. So i signed up as user j...@apache.org but it won't let me create pages. How are we supposed to create pages ? Cheers James
Re: [zeta-dev] Documentation
Hi Gaetano On Tue, Jan 11, 2011 at 10:15 PM, Gaetano Giunta giunta.gaet...@gmail.com wrote: To me, the way the components work often feels like blackmagick: sometimes it is logical, but more often it's just like incantations. The example spells given in the docs are fine, but as soon as you stray a little bit from those, you're on your own - either it works at the very first try or it becomes a thankless test/change/repeat loop (eg. sometimes a certain mix of options work, and another mix does not work, or some methods have to be invoked in a particular order). Looks like a hacker thing :D Isn't that how pretty much all libs, frameworks, and programming languages work in general ? What lib/program/framework does it better than the components and why ? Regards James -- http://jamespic.info Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Documentation
Hi all, On Wed, Jan 12, 2011 at 8:46 AM, Christian Grobmeier grobme...@gmail.com wrote: - a method that can be used to easily debug the code. ... For example, I use PersistentObject and I would like to know why the find query returns me nothing. In the documentation, there's no clue to that could help me to resolve my probleme. And also, there's no way to print the $q-getQuery() without hacking PersistentObject. Isn't it possible by just setting a breakpoint and without hacking ? Maybe we must consider the fact to create a false dependancy to Debug, disabled by default. What would be the benefits of that over xdebug ? I insist for your own good, maybe the source of your problem is not specific to the components... are you sure you're using xdebug correctly ? Regards James -- http://jamespic.info Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Documentation
On Tue, Jan 11, 2011 at 2:39 PM, Ronan Guilloux ronan.guill...@gmail.comwrote: +1 for all that Maxime wrote about. But my very first need tweet was simpler : How to add a set of cronjobs, and how to add a PhpUnit test suite into a HelloMvc-like website (cf. http://goo.gl/TvXVn) . Adding cronjobs is easy, but this should be documented or shown in an example a day, since it's a common need. Do you mean, how to setup a cronjob and post-commit hooks ? What do you think would be zetacomponents-specific about that ? I'll try to improve my frenchy globish english a write a decent tutorial about that, somehwere, some day. Yeah I know, we French are the worst English speakers in the world :D The main difficult I encountered was to implement PhpUnit easely. Some weeks ago I crawled the all Zeta Components example apps (here : http://goo.gl/Xg828) but I didn't found any app implementing PhpUnit yet. PhpUnit doc about bootstrapping was not clear enough to me. Did you consider Arbit project sources ? It's built upon ZetaComponents and uses PHPUnit for testing. I've uploaded the sources of the last app framework i coded with the components, it uses PHPUnit for testing: https://github.com/jpic/zetamad but reading the UnitTest bootstrap.php file (found here : http://goo.gl/nH96H) helped a lot and it finally did the job. Unfortunatly, while UnitTest is listed in the official Zeta Components docs, it's a broken link in the official doc (here : http://goo.gl/wKHnN). UnitTest barely wraps around PHPUnit, providing a few features that are specific to components tests. Which of its features do you need in your project ? Implemeting PhpUnit into Zeta Components needs a tutorial Did you consider: The tutorial to install PHPUnit: http://www.phpunit.de/manual/current/en/installation.html The tutorial to writing tests: http://www.phpunit.de/manual/current/en/writing-tests-for-phpunit.html The tutorial automating builds: http://www.phpunit.de/manual/current/en/build-automation.html The tutorial to continuous integration by Arbit: http://tracker.arbitracker.org/arbit/documentation/view/ContinuousIntegration I'd candidate although i'd need your opinion concerning the following questions: - do these tutorial contain the informations you are looking for ? - if not, what other information do you need ? - if so, why, where and how should the components cover these topics ? Regards James -- http://jamespic.info Customer is king - Le client est roi - El cliente es rey.
[zeta-dev] Apache svn and new website: first steps, log and question
Hi all,
I noticed a glitch in:
http://incubator.apache.org/zetacomponents/community/implementation.html
(search for array(int no quotes)
So i checked out:
http://svn.apache.org/repos/asf/incubator/zetacomponents/website
And changed website/content/community/implementation.txt line 1483:
- Example of a hash array::
+ Example of a hash array::
Then i ran:
scripts/updateCache.php
And it looks working:
http://pub.chocolatpistache.com/zetac/website/website.svn/htdocs/community/implementation.html
As specified by readme.txt:
j...@liria /pd/home/jpic/src/zetac/website/website.svn $ make revert-empty
REVERT_FILES=; \
echo Scanning for files to revert …; \
for FILE in `svn st htdocs/ | grep '^M' | awk '{ print $2; }'`; \
do \
if [ `svn diff --diff-cmd 'diff' -x -U0 $FILE | sed '1,4d' |
grep -v -f 'var/scripts/htdocs_ignore.grep'` = ]; \
then \
REVERT_FILES=$REVERT_FILES '$FILE'; \
fi; \
done; \
if [ $REVERT_FILES = ]; \
then \
echo No files to be reverted.; \
else \
echo Reverting files …; \
echo $REVERT_FILES | xargs svn revert; \
fi; \
Scanning for files to revert …
No files to be reverted. [[ it did revert files the first time i ran it ]]
But it still shows loads of diffs:
j...@liria /pd/home/jpic/src/zetac/website/website.svn $ svn status
M htdocs/news.rss
M htdocs/community/implementation.txt
M htdocs/community/implementation.html
M htdocs/.rss
M htdocs/spam.html
M htdocs/documentation/trunk/EventLog/tutorial.html
M htdocs/documentation/trunk/Archive.html
M htdocs/documentation/trunk/EventLog.html
M htdocs/documentation/trunk/AuthenticationDatabaseTiein.html
M htdocs/documentation/trunk/UserInput.html
M htdocs/documentation/trunk/EventLogDatabaseTiein/tutorial.html
M htdocs/documentation/trunk/Feed/tutorial.html
M htdocs/documentation/trunk/Url.html
M htdocs/documentation/trunk/Feed.html
M htdocs/documentation/trunk/Webdav/tutorial.html
M htdocs/documentation/trunk/ConsoleTools/tutorial.html
M htdocs/documentation/trunk/Mail.html
M htdocs/documentation/trunk/ConsoleTools.html
M htdocs/documentation/trunk/PersistentObject/tutorial.html
M htdocs/documentation/trunk/PersistentObject.html
M htdocs/documentation/trunk/UserInput/tutorial.html
M htdocs/documentation/trunk/Tree/tutorial.html
M htdocs/documentation/trunk/Url/tutorial.html
M htdocs/documentation/trunk/Tree.html
M htdocs/documentation/trunk/Graph.html
M htdocs/documentation/trunk/Search.html
M htdocs/documentation/trunk/Webdav.html
M htdocs/documentation/trunk/Authentication/tutorial.html
M htdocs/documentation/trunk/GraphDatabaseTiein/tutorial.html
M htdocs/documentation/trunk/Archive/tutorial.html
M htdocs/documentation/trunk/Mail/tutorial.html
M htdocs/documentation/trunk/Authentication.html
M htdocs/documentation/trunk/GraphDatabaseTiein.html
M htdocs/documentation/trunk/ImageConversion/tutorial.html
M htdocs/documentation/trunk/Debug.html
M htdocs/documentation/trunk/AuthenticationDatabaseTiein/tutorial.html
M htdocs/documentation/trunk/Translation.html
M htdocs/documentation/trunk/EventLogDatabaseTiein.html
M htdocs/documentation/trunk/Debug/tutorial.html
M htdocs/documentation/trunk/ImageConversion.html
M htdocs/documentation/trunk/Translation/tutorial.html
M htdocs/documentation/trunk/Graph/tutorial.html
M htdocs/documentation/trunk/Search/tutorial.html
M htdocs/news/releases/0.rss
M htdocs/news/general.rss
M htdocs/news/0.rss
M htdocs/news/001_welcome_to_apache_zeta_components.html
M htdocs/news/002_status_update.html
M htdocs/news/releases.rss
M htdocs/news/001_welcome_to_apache_zeta_components.rss
M htdocs/news/002_status_update.rss
M htdocs/news/general/0.rss
M config/site.ini
M config/binaries.ini
M content/community/implementation.txt
Obviously, i'm responsible for the 3 last ones, which brings question
0: what about the other diffs ? is it normal ?
So i'm trying to commit the typo fix:
j...@liria /pd/home/jpic/src/zetac/website/website.svn $ svn commit
-m - Fixed a syntax error which caused a rendering glitch.
content/community/implementation.txt
svn: Commit failed (details follow):
svn: Server sent unexpected return value (403 Forbidden) in response
to MKACTIVITY request for
'/repos/asf/!svn/act/81ab0e7e-a58f-4e3b-a7db-32e6f6674519'
I reset ~/.subversion, and ran svn update --username (which worked)
and other voodoo tricks proposed by google results ... But the commit
fails the same way. Which brings question1: why isn't it working and
how to fix it ?
Note that i've intentionality left as much details as possible, in
case
Re: [zeta-dev] [VOTE] Release process
[X] +1 (accept release process) [ ] 0 (I don't care) [ ] -1 (decline release process, because …) The document is great job. Thanks Cheers James
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
Hi all, I'm not qualified to participate actively to the current discussions, although i'm reading it all. However, i'd like to share how it works with python/pinax projects because it might inspire you. On Thu, Nov 18, 2010 at 9:46 AM, Tobias Schlitt tob...@schlitt.info wrote: Hi Max, On 11/18/2010 09:21 AM, Maxime Thomas wrote: Actually only the packaging of zeta matters as we want to provide everything or a part of it. The jQuery UI package download system seems to be a good start, I guess. Another question comes if we do like this : will it be possible to make heterogeneous packages with this system. I mean can I ask Graph 1.0 with Config 3.2 ? or do I have a minimum rules to follow ? Pinax projects use a requierements.txt file, for example:: --extra-index-url=http://dist.pinaxproject.com/dev/ Django==1.2.1 Pinax==0.9a1 django-debug-toolbar==0.8.3 django-staticfiles==0.2.0 -e git+ssh://g...@github.com:jpic/sorl-thumbnail.git#egg=sorl-thumbnail That file is tracked by the VCS in each project. To deploy a new environment for my project, all i have to do is:: # pip is like pear, for python pip install -r requirements.txt That allows: - each project to have different component dependencies - with specific versions - deployment is piece of cake I don't think it's possible with official pear, anyway: if we decide that it's the way to go then we'll find a way. Regards James -- http://chocolatpistache.com/wiki/public/Contact Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Commit access
On Wed, Oct 13, 2010 at 12:00 PM, Derick Rethans der...@apache.org wrote: On Wed, 6 Oct 2010, James Pic wrote: Were my contributions/credits losts during the svn migration? Nope, of course not. I've tabled your commit access question for voting. Thanks for informing! I'm already planning some time for next week ;) Cheers -- http://jamespic.com/contact Customer is king - Le client est roi - El cliente es rey.
[zeta-dev] Commit access
Hello everybody, Tobias told me ask for commit access on the mailing list. I was not aware of this procedure step when i sent my iCLA a month and a half ago, so sorry for the delay. Regards James -- http://jamespic.com/contact Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Commit access
Hello Christian, On Wed, Oct 6, 2010 at 2:58 PM, Christian Grobmeier grobme...@gmail.com wrote: Hello James, usually people are voted in after they have contributed to a project. In other words, you'll need to prove you have a long term interest in the project before you can join. Please read more at: http://apache.org/foundation/getinvolved.html http://www.apache.org/foundation/how-it-works.html If this is (already) the case, the PMC members will held a vote (usually done on private list). In the special case of incubator, this vote need to be ack'ed by the Incubator PMC afterwards. My bad, i ought to mention that i have already contributed to ez components and that i have pending contributions. Were my contributions/credits losts during the svn migration? Regards James -- http://jamespic.com/contact Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Commit access
On Wed, Oct 6, 2010 at 3:06 PM, Christian Grobmeier grobme...@gmail.com wrote: Hello James, My bad, i ought to mention that i have already contributed to ez components and that i have pending contributions. Were my contributions/credits losts during the svn migration? I didn't look into SVN. I think it should be there. However, if you are already known to the Zeta people there is nothing which prevents them to discuss about your request and then vote you in. Thanks for your support, i really appreciate. Regards James -- http://jamespic.com/contact Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Contributing / ZETACOMP-8
On Tue, Aug 24, 2010 at 1:31 PM, Maxime Thomas maxime.t...@gmail.com wrote: Hi, I had a question linked to James Pic initiative to create a eZC wiki some times ago : http://www.ezcusers.org/ Can it be moved / merged to ZC wiki ? If true, does James have to produce an iCLA ? (@james, sorry :-D ). 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. Regards -- http://jamespic.com/contact Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Welcome Apache Zeta Components - SVN up and running :)
On Mon, Aug 23, 2010 at 6:21 PM, Gaetano Giunta giunta.gaet...@gmail.com wrote: Tobias Schlitt wrote: [...] To give you an impression, what we need to do, here a brain dump: - - Investigate which open issues need to be transfered - - Assign component maintainaners (volunteers?) I'm (maybe the only one) interrested in UserInput, if you'll assign me to it then i'll take for mission to help it evolve into a more complete and cool component for convenient form development. Regards -- http://jamespic.com/contact Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Configuration component override mechanism : requirement doc
On Fri, Aug 13, 2010 at 7:04 PM, Jerome Renard jerome.ren...@gmail.com wrote: 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 ? Sounds excellent! That way people who like systems can use it, and people who don't like systems can still benefit from the upgrade... ... Anyway, that sounds more like design document discussions than requirement document issues ;) Cheers James -- http://jamespic.com/contact Customer is king - Le client est roi - El cliente es rey.
