I believe there should be different branches of a single apps repository, rather than a different apps-playground repo. Merges with the master branch would be easier in this case.
@Georg: maybe I don't understand it, you are suggesting something of this kind: <path>/owncloud/apps/ <path>/apps how do you specify which app folder should owncloud refer to? thanks, Alessandro On Fri, Apr 27, 2012 at 12:44 PM, Frank Karlitschek <[email protected]> wrote: > > On 27.04.2012, at 18:42, Georg Ehrke <[email protected]> wrote: > >> >> Am 27.04.2012 um 18:40 schrieb Georg Ehrke: >> >>> Am 27.04.2012 um 18:27 schrieb Alessandro Cosentino: >>> >>>> After those changes, I am a bit confused. Jakob and Jan suggested that >>>> I develop the feed reader app in the apps repo, since even core apps >>>> are going to move there. Two questions in particular: >>>> >>>> 1. should I create a work branch of the apps repo or work in the >>>> master? I would say a work branch is better, since even core apps are >>>> going to move there. At the same time, I see that now all apps are >>>> developed in master (mail app, for instance); >>>> >>> In my opinion we should create an apps-experimental repository where we can >>> store apps that are unstable. >> I just saw that there is already a repository called apps-playground. > > Exactly. You can use that if you want. > But a branch of the apps repo is also fine. > > >>>> 2. locally where should I clone the apps repo? I figure that if I >>>> clone it in the owncloud/app sub-folder, things will get messed up >>>> with the two git configurations. >>> You can clone all in the same directory >>> e.g.: >>> /path/3rdparty >>> /path/apps >>> /path/owncloud >>> >>> Cheers, >>> Georg >>>> Thanks, >>>> Alessandro >>>> >>>> On Fri, Apr 27, 2012 at 8:24 AM, Georg Ehrke >>>> <[email protected]> wrote: >>>>> >>>>> Am 27.04.2012 um 13:00 schrieb Frank Karlitschek: >>>>> >>>>>> >>>>>> On 27.04.2012, at 09:54, Georg Ehrke <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Am 26.04.2012 um 23:24 schrieb Thomas Müller: >>>>>>> >>>>>>>> Am Donnerstag, dem 26.04.2012 um 23:17 schrieb Frank Karlitschek: >>>>>>>>> On 26.04.2012, at 23:00, Thomas Müller <[email protected]> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> will this also result in a movement of all apps from the owncloud >>>>>>>>>> repo to the apps repo? >>>>>>> Are we also going to remove the 3rdparty files from the main repo? >>>>>> >>>>>> Yes. We switch the the "3rdparty" repository. >>>>>> >>>>>>>>> >>>>>>>>> Exactly >>>>>>>>> >>>>>>>> >>>>>>>> Cool - will make app develoment easier as well! >>>>>>>> >>>>>>>> >>>>>>>>>> How will the tar-balls on Release be created e.g. what will they >>>>>>>>>> contain? >>>>>>>>> >>>>>>>>> This won´t change. >>>>>>>>> We still ship the apps that we all decide with the tar file >>>>>>>>> independently from the repo. >>>>>>>>> >>>>>>>> >>>>>>>> Ok >>>>>>>> >>>>>>>>> >>>>>>>>>> Especially the last question is interesting from a distro packaging >>>>>>>>>> point of view (as I have it, >>>>>>>>>> because I recently started to work on bringing ownCloud to the real >>>>>>>>>> Debian repo). >>>>>>>>> >>>>>>>>> Awesome. :-) >>>>>>>>> >>>>>>>> >>>>>>>> aka Sweet ;-) >>>>>>>> >>>>>>>> Our plan is to bring OC4 to the next Debian stable (7 aka Wheezy). >>>>>>>> A long way to go as some core dependencies are simple not there e.g. >>>>>>>> MDB2_Schema and SabreDAV. >>>>>>>> >>>>>>>>> >>>>>>>>>> It would be nice to have a core tar ball only with the file and sync >>>>>>>>>> handling stuff (and maybe contacts and calendar). >>>>>>>>>> An an additional tar ball containing the apps, which can then be >>>>>>>>>> packaged separately. >>>>>>>>> >>>>>>>>> Yes. Thats possible now. And the good thing is that the apps can live >>>>>>>>> outside the owncloud directory. I suppose thats should make packaging >>>>>>>>> a bit more easy. >>>>>>>>> >>>>>>>> >>>>>>>> For sure! >>>>>>>> >>>>>>>> Tom >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> As off today the release tar ball 'only' contains the owncloud repo. >>>>>>>>>> Apps from the apps repo are not released at all. (By intention?) >>>>>>>>> >>>>>>>>> In the future the release tarball can contain apps independently from >>>>>>>>> the repo (core or apps). >>>>>>>>> >>>>>>>>> Frank >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Take care, >>>>>>>>>> >>>>>>>>>> Tom >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Thomas Müller E-Mail: [email protected] >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Am Donnerstag, dem 26.04.2012 um 22:49 schrieb Frank Karlitschek: >>>>>>>>>>> Great work! :-) >>>>>>>>>>> This means that the apps folder can now live outside the owncloud >>>>>>>>>>> folder. >>>>>>>>>>> Very nice >>>>>>>>>>> >>>>>>>>>>> Frank >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 26.04.2012, at 22:23, Georg Ehrke <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> today i finished my work on movable apps. >>>>>>>>>>>> I will merge it tomorrow into master. >>>>> I just merged it. >>>>>>>>>>>> Important changes: >>>>>>>>>>>> • files app moved to app folder >>>>>>>>>>>> • there is still /owncloud/files/webdav.php >>>>>>>>>>>> • php and css files will be loaded through >>>>>>>>>>>> /owncloud/index.php >>>>>>>>>>>> • example: >>>>>>>>>>>> • /?app=files -> app >>>>>>>>>>>> • /?app=files&getfile=/ajax/rename.php -> >>>>>>>>>>>> execute file of an app >>>>>>>>>>>> • you can add %webroot% and %appswebroot% to css files >>>>>>>>>>>> • use in urls of background images >>>>>>>>>>>> • please use our internal functions to generate paths >>>>>>>>>>>> • js: OC.filePath >>>>>>>>>>>> • php: OC_Helper::linkTo >>>>>>>>>>>> • Files for *Dav and ampache are still in the app folder >>>>>>>>>>>> • i think about creating a /owncloud/remote folder >>>>>>>>>>>> where apps can write the php files for their remote services >>>>>>>>>>>> • what do you think about this? >>>>>>>>>>>> • I made every app in main ownCloud repo work with this >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> Georg >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Owncloud mailing list >>>>>>>>>>>> [email protected] >>>>>>>>>>>> https://mail.kde.org/mailman/listinfo/owncloud >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Owncloud mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> https://mail.kde.org/mailman/listinfo/owncloud >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Owncloud mailing list >>>>>>> [email protected] >>>>>>> https://mail.kde.org/mailman/listinfo/owncloud >>>>> >>>>> _______________________________________________ >>>>> Owncloud mailing list >>>>> [email protected] >>>>> https://mail.kde.org/mailman/listinfo/owncloud >>> >>> _______________________________________________ >>> Owncloud mailing list >>> [email protected] >>> https://mail.kde.org/mailman/listinfo/owncloud >> >> _______________________________________________ >> Owncloud mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/owncloud > > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
