<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><br>Hi all,<div><br></div><div>As a non active member of this group, i do not know if there's a formal way to introduce myself and share my opinions, and please let me know if there is.</div><div><br><div>I've been following this group for a little while and been watching the amazing progress you have done so far. I've been looking for a way to activetly participate, I believe that my experience as a developer with strong emphasis on TDD, continiuos integration, and automation build of php codes using native Linux package build tools can potentially help.</div><div><br></div><div>And this is why, as a tech lead for various organizations and in my current position as development manager, as you can imagine i spent a lot time dealing with QA issues, development process and the always difficult question of integrating best practices including test driven approaches, while minimizing the the amount of effort need by the development team to either make the switch or simple follow it without affecting their output.</div><div><br></div><div>@frank, I would agree with your overall accessment, that why continouis integration and automation builds are key.</div><div><br></div><div>To keep it short, let me know, how i can volunteer to help setup this process. Please note that I currently live in the UK after nearly 13 years in the US.</div><div><br></div><div>Regards,</div><div>Serge</div><div><br>Sent from Samsung tablet </div></div><br>owncloud-request@kde.org wrote:<br>Send Owncloud mailing list submissions to<br> owncloud@kde.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://mail.kde.org/mailman/listinfo/owncloud<br>or, via email, send a message with subject or body 'help' to<br> owncloud-request@kde.org<br><br>You can reach the person managing the list at<br> owncloud-owner@kde.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Owncloud digest..."<br><br><br>Today's Topics:<br><br> 1. Re: regression tests? (Frank Karlitschek)<br> 2. Fwd: regression tests? (Kenny Coyle)<br> 3. Re: regression tests? (Thomas M?ller)<br> 4. password wrong (carachi diego)<br> 5. PHP.ini (Richard Burns)<br> 6. Re: Embedded SGF Viewer app - call for review (Frank Karlitschek)<br> 7. Re: Trackerd based server side search app (Frank Karlitschek)<br> 8. Re: Extended webfinger app (Frank Karlitschek)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sat, 7 Apr 2012 21:13:37 +0200<br>From: Frank Karlitschek <frank@owncloud.org><br>To: J?rn Friedrich Dreyer <jfd@butonic.de><br>Cc: "owncloud@kde.org" <owncloud@kde.org><br>Subject: Re: [Owncloud] regression tests?<br>Message-ID: <94CAAAE0-5F4C-4E73-ADBF-D099291D72AD@owncloud.org><br>Content-Type: text/plain; charset=iso-8859-1<br><br>I think it a great idea to do continuos integration. It?s a good thing to ensure quality.<br>I just wouldn?t introduce too much processes and bureaucracy so that?s still easy and fun to contribute for new people.<br><br>And we need an volunteer to set everything up of course :-)<br><br>Frank<br><br><br>On 06.04.2012, at 13:42, J?rn Friedrich Dreyer <jfd@butonic.de> wrote:<br><br>> Am 06.04.2012 13:08 schrieb "Michiel de Jong" <michiel@unhosted.org>:<br>> > but you just configure git to only accept merges whose tests pass.<br>> > that way it's the responsibility of the person committing new code to<br>> > not create any regressions on existing functionality. in case of<br>> > conflict, the already existing master should be kept, not the new<br>> > commit.<br>> If we start adding continuous integration I highly recommend gerrit to manage branches and commits. We can start by letting gerrit automatically push changes that pass the testsuite into master. Should we need a more in depth review we can later add the voting process.<br>> <br>> So long<br>> <br>> J?rn<br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Sat, 7 Apr 2012 20:29:51 +0100<br>From: Kenny Coyle <kenny@heloo.net><br>To: owncloud@kde.org<br>Subject: [Owncloud] Fwd: regression tests?<br>Message-ID:<br> <CA+30S3QtQLjVbPnHJTCuAqniV4KWwg9FY0WaewE0bfvGUuVrvA@mail.gmail.com><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>This could possibly help in two ways - I know that a lot of developers<br>prefer to hack features, where TDD is not always taken into consideration.<br><br>We could _ask_ that developers take a TDD approach and open a new<br>contributor role to look at any old/new code, refactoring it into a TDD<br>fashion and adding new tests where they are missing?<br><br>Cheers,<br>Kenny.<br><br>p.s. Apologies if this double-post :/<br><br><br>On 7 April 2012 20:13, Frank Karlitschek <frank@owncloud.org> wrote:<br><br>> I think it a great idea to do continuos integration. It?s a good thing to<br>> ensure quality.<br>> I just wouldn?t introduce too much processes and bureaucracy so that?s<br>> still easy and fun to contribute for new people.<br>><br>> And we need an volunteer to set everything up of course :-)<br>><br>> Frank<br>><br>><br>> On 06.04.2012, at 13:42, J?rn Friedrich Dreyer <jfd@butonic.de> wrote:<br>><br>> > Am 06.04.2012 13:08 schrieb "Michiel de Jong" <michiel@unhosted.org>:<br>> > > but you just configure git to only accept merges whose tests pass.<br>> > > that way it's the responsibility of the person committing new code to<br>> > > not create any regressions on existing functionality. in case of<br>> > > conflict, the already existing master should be kept, not the new<br>> > > commit.<br>> > If we start adding continuous integration I highly recommend gerrit to<br>> manage branches and commits. We can start by letting gerrit automatically<br>> push changes that pass the testsuite into master. Should we need a more in<br>> depth review we can later add the voting process.<br>> ><br>> > So long<br>> ><br>> > J?rn<br>><br>> _______________________________________________<br>> Owncloud mailing list<br>> Owncloud@kde.org<br>> https://mail.kde.org/mailman/listinfo/owncloud<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://mail.kde.org/pipermail/owncloud/attachments/20120407/6ecaf9a1/attachment-0001.html><br><br>------------------------------<br><br>Message: 3<br>Date: Sat, 07 Apr 2012 22:48:24 +0200<br>From: Thomas M?ller <thomas.mueller@tmit.eu><br>To: Frank Karlitschek <frank@owncloud.org><br>Cc: "owncloud@kde.org" <owncloud@kde.org><br>Subject: Re: [Owncloud] regression tests?<br>Message-ID: <1333831704.4f80a818e9899@office.tmit.eu><br>Content-Type: text/plain; charset=utf-8<br><br><br>Am Samstag, dem 07.04.2012 um 21:13 schrieb Frank Karlitschek:<br>> I think it a great idea to do continuos integration. It?s a good thing to ensure quality.<br>> I just wouldn?t introduce too much processes and bureaucracy so that?s still easy and fun to contribute for new people.<br>> <br>> And we need an volunteer to set everything up of course :-)<br>> <br><br>*wink* ;-)<br><br>Let's talk next weekend about this!<br><br>Tom<br><br>> Frank<br>> <br>> <br>> On 06.04.2012, at 13:42, J?rn Friedrich Dreyer <jfd@butonic.de> wrote:<br>> <br>> > Am 06.04.2012 13:08 schrieb "Michiel de Jong" <michiel@unhosted.org>:<br>> > > but you just configure git to only accept merges whose tests pass.<br>> > > that way it's the responsibility of the person committing new code to<br>> > > not create any regressions on existing functionality. in case of<br>> > > conflict, the already existing master should be kept, not the new<br>> > > commit.<br>> > If we start adding continuous integration I highly recommend gerrit to manage branches and commits. We can start by letting gerrit automatically push changes that pass the testsuite into master. Should we need a more in depth review we can later add the voting process.<br>> > <br>> > So long<br>> > <br>> > J?rn<br>> <br>> _______________________________________________<br>> Owncloud mailing list<br>> Owncloud@kde.org<br>> https://mail.kde.org/mailman/listinfo/owncloud<br><br><br>------------------------------<br><br>Message: 4<br>Date: Sat, 7 Apr 2012 23:42:11 +0200<br>From: carachi diego <carachi83@gmail.com><br>To: owncloud@kde.org<br>Subject: [Owncloud] password wrong<br>Message-ID:<br> <CADA9fd+iiEw+7NwiXZ0XVMhYECJPKE0f4=CLFHAsyfg6KDjmzQ@mail.gmail.com><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>Hi,<br>I am new in OwnCloud. I installed it into a web space on a hosting and I<br>configured it.<br><br>I can login it on the browser login and I can upload file on my space, but<br>I can't login into my space through Ubuntu client because the client said<br>that the password is wrong.<br>I tried also to login into with the browser to address/file/webdav.php but<br>it said that the user or password is wrong. Why?<br><br>How can I solve the problem?<br><br><br>Thank you<br><br><br><br>-- <br>___________________________<br>www.pcc8.netsons.org<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://mail.kde.org/pipermail/owncloud/attachments/20120407/c5ca0989/attachment-0001.html><br><br>------------------------------<br><br>Message: 5<br>Date: Sat, 7 Apr 2012 23:08:05 +0100<br>From: Richard Burns <t11chb@gmail.com><br>To: owncloud@kde.org<br>Subject: [Owncloud] PHP.ini<br>Message-ID: <76414E1B-1A12-4019-95E8-5905274E923A@gmail.com><br>Content-Type: text/plain; charset=us-ascii<br><br>Hi, i'm also new to this, is this even the right place to ask?<br>I've started using ownCloud but cannot upload anything over 8Mb, my php.ini has been modified and looks like it will work in ownCloud, it shows that it will accept the larger file but fails on anything over 8Mb.<br><br>Your help is much appreciated.<br><br><br>Richard<br><br><br><br>max_execution_time = 1000 ; Maximum execution time of each script, in seconds<br>max_input_time = 1000 ; Maximum amount of time each script may spend parsing request data<br><br>; Maximum size of POST data that PHP will accept.<br>post_max_size = 100M<br><br>; Maximum allowed size for uploaded files.<br>upload_max_filesize = 100M<br><br>------------------------------<br><br>Message: 6<br>Date: Sun, 8 Apr 2012 11:09:30 +0200<br>From: Frank Karlitschek <karlitschek@kde.org><br>To: Florian H?lsmann <fh@cbix.de><br>Cc: owncloud@kde.org<br>Subject: Re: [Owncloud] Embedded SGF Viewer app - call for review<br>Message-ID: <DF2A5B4D-865E-4EC1-AAAD-004A877A13FC@kde.org><br>Content-Type: text/plain; charset=us-ascii<br><br>Cool.<br><br>Very nice feature :-)<br><br><br><br><br>> <br>> Am 02.04.2012 17:55, schrieb Nils Jansen:<br>>> Hi All,<br>>> <br>>> I developed an OC app to review go games within OC. Go games are saved<br>>> in .sgf format. The App is an implementation of the EidoGo Player (SGF<br>>> viewer and editor) http://eidogo.com/source<br>>> <br>>> It works fine with the current master.<br>>> <br>>> As I have only little experience with Javascript and Git, it would be<br>>> great if somebody could check out the code. Here are the according merge<br>>> requests:<br>>> <br>>> http://gitorious.org/owncloud/owncloud/merge_requests/102<br>>> https://gitorious.org/owncloud/apps/merge_requests/3<br>>> <br>>> Any comments?<br>>> <br>>> Thanks,<br>>> <br>>> Nils<br>>> <br><br><br><br>Frank Karlitschek<br>karlitschek@kde.org<br><br><br><br><br>------------------------------<br><br>Message: 7<br>Date: Sun, 8 Apr 2012 11:14:06 +0200<br>From: Frank Karlitschek <frank@owncloud.org><br>To: J?rn Friedrich Dreyer <jfd@butonic.de><br>Cc: owncloud@kde.org<br>Subject: Re: [Owncloud] Trackerd based server side search app<br>Message-ID: <69BD340E-7A3A-41BA-8426-CD22362E0CAB@owncloud.org><br>Content-Type: text/plain; charset=iso-8859-1<br><br>Hi J?rn,<br><br><br>I think this a great idea. <br>The problem is, of course, that it has external dependencies like tracker obviously but it can still be very useful for power users who have tracerd running. So this is a nice optional feature imho.<br><br>The challenge is that indexing has to be done through ownCloud because this is the only way to access encrypted, shared and remote files. <br>Do you think tracer can access the ownCloud files via WebDAB? or do we have to provide a different interface? <br><br><br>Cheers<br>Frank<br><br><br><br>On 06.04.2012, at 05:15, J?rn Friedrich Dreyer <jfd@butonic.de> wrote:<br><br>> Hi all,<br>> <br>> after scratching my itch of server side searching I cleaned up the<br>> code a bit, removed /most/ hardcoded paths and commited a shiny new<br>> app to github: https://gitorious.org/~butonic/owncloud/butonics-owncloud<br>> <br>> On the one hand, the installation is fairly easy on a ubuntu system<br>> (running precise):<br>> <br>> # install trackerd and pear<br>> sudo apt-get install tracker php5-pear<br>> # use pecl to install the php dbus extension<br>> sudo pecl install dbus-beta<br>> # activate the dbus extension<br>> sudo echo "extension=dbus.so" > /etc/php5/conf.d/dbus.ini<br>> # restart apache<br>> sudo service apache2 restart<br>> <br>> On the other hand, running the app is a little more ... hackerish and<br>> I admit: it needs some more love to make it end user ready, so<br>> consider it EXPERIMENTAL!<br>> Before using the app, we need to run a shell script that brings up a<br>> dbus-daemon and starts a headless version of trackerd:<br>> <br>> # open a screen session<br>> screen<br>> # become your webserver user<br>> sudo su www-data<br>> # change into the trackerd_search app directory<br>> cd /var/www/owncloud/apps/trackerd_search<br>> # or cd /home/yourhomedir/public_html/owncloud/apps/trackerd_search<br>> # manually fix the OC_CONFIG_DATADIRECTORY in the trackerd_headless.sh<br>> script. I could propably generate that script when first running<br>> owncloud<br>> vi trackerd_headless.sh<br>> # run it<br>> sh trackerd_headless.sh<br>> # it should now start a dbus-daemon for our trackerd communication,<br>> bring up the tracker store and launch our tracker-miner. It should<br>> auto create any directories and files and start indexing. Maybe you<br>> need to configure the indexed paths:<br>> vi /var/www/owncloud/data/trackerd_search/config/tracker/tracker-miner-fs.cfg<br>> <br>> If you are lucky you will now be able to search through your file<br>> contents and meta information by using the standard search field of<br>> owncloud with the power of a desktop search engine.<br>> Fixing problems requires a bit of knowledge about dbus and trackerd<br>> ... or time on my side, which is kinda scarce at the moment as I am<br>> writing my PhD.<br>> If you want to kill the processes do not forget to also kill the dbus<br>> daemon running for www-data:<br>> <br>> $ ps axu | grep tracker | grep www-data | grep -v grep<br>> www-data 9235 0.0 0.0 24040 1500 ? Ss 03:23 0:00<br>> dbus-daemon --config-file=session.conf<br>> --address=unix:path=/pth/to/your/owncloud/data/trackerd_search/owncloud_trackerd_dbus_socket<br>> --fork<br>> www-data 9236 0.0 0.0 323260 8764 pts/1 Sl 03:23 0:00<br>> /usr/lib/tracker/tracker-store<br>> www-data 9248 0.0 0.0 325720 8504 pts/1 SNl 03:23 0:00<br>> /usr/lib/tracker/tracker-miner-fs<br>> <br>> The plugin itself is only about 160 LoC. I do have some plans for the<br>> plugin but I wanted to let others try it out and hopefully provide a<br>> starting point for a useful server side search. The php / dbus /<br>> tracker hack was originally inpired by providing a sever side search<br>> for a samba share but that also requires a browser plugin or<br>> configuration hack to circumvent the same origin policy for file://<br>> urls. Nevertheless, clicking links in the browser and having them open<br>> files on a mounted webdav share is really nice ...<br>> <br>> Anyway, I'm tired ...<br>> <br>> so long, feedback welcome<br>> <br>> J?rn<br>> <br>> <br>> --<br>> A. Because it breaks the logical sequence of discussion<br>> Q. Why is top posting bad?<br>> _______________________________________________<br>> Owncloud mailing list<br>> Owncloud@kde.org<br>> https://mail.kde.org/mailman/listinfo/owncloud<br><br><br><br>------------------------------<br><br>Message: 8<br>Date: Sun, 8 Apr 2012 11:18:26 +0200<br>From: Frank Karlitschek <frank@owncloud.org><br>To: Florian H?lsmann <fh@cbix.de><br>Cc: "owncloud@kde.org Mailinglist" <owncloud@kde.org><br>Subject: Re: [Owncloud] Extended webfinger app<br>Message-ID: <31D53338-A54A-466C-B143-0DF049295C64@owncloud.org><br>Content-Type: text/plain; charset=iso-8859-1<br><br>Hi Florian,<br><br>thanks a lot for your contribution. I?m not super familiar with webfinger but this looks good.<br><br>And thanks for calling us a "big" FOSS project :-)<br><br><br>Cheers<br>Frank<br><br><br>On 03.04.2012, at 00:38, Florian H?lsmann <fh@cbix.de> wrote:<br><br>> Hi all,<br>> <br>> I've recently been working on reimplementing the webfinger protocol for ownCloud, so other apps than the remoteStorage plugin can also use it. For instructions on how to use webfinger from your app, see the /apps/user_webfinger/webfinger.php file. I first thought of something like OC_Webfinger::register(), but unfortunately that not possible because the OC_Webfinger class must be in classpath before running all the appinfo/app.php scripts :-/<br>> <br>> I also made the need of a symlink to the .well-known folder obsolete by creating a static "host-meta" file during installation (see appinfo/install.php). To make this accessible by pure javascript apps, the install.php also creates a static .htaccess file which sets some additional headers, so to make use of this it's now recommended that you have the apache mod_headers activated.<br>> <br>> If you're pulling from master to update, please reinstall the webfinger app by deleting the .well-known symlink in your document root and calling owncloud/apps/user_webfinger/appinfo/install.php (with CURL or your browser, because it needs some server parameters!) I'm not sure if this could also be done by a built-in upgrade routine, so I'm telling you :P<br>> <br>> Hope you are ok with that (it's kind of my first "direct" contribution to a big FOSS project :D ), have a nice day!<br>> <br>> -- <br>> Florian H?lsmann<br>> <fh@cbix.de><br>> http://cbix.de<br>> _______________________________________________<br>> Owncloud mailing list<br>> Owncloud@kde.org<br>> https://mail.kde.org/mailman/listinfo/owncloud<br><br><br><br>------------------------------<br><br>_______________________________________________<br>Owncloud mailing list<br>Owncloud@kde.org<br>https://mail.kde.org/mailman/listinfo/owncloud<br><br><br>End of Owncloud Digest, Vol 26, Issue 15<br>****************************************<br> </body>