[Owncloud] repository restructuring

[Matthew Dawson]

On Tuesday 01 November 2011 22:45:09 Frank Karlitschek wrote:
> Hi all,
> 
> at the developer meeting in Zürich 2 weeks ago we talked about a cleaner separation of the different parts of ownCloud.
> 
> The idea is that we keep the core of ownCloud as small as possible and provide an easy way to install and update more apps via the application installer. I plan to work on this in the next few weeks.
> 
> I suggest that we move all the apps that are not absolutely core functionality to the "apps" repository and provide an easy way to browse and install this apps from within ownCloud. This has the benefit that 
we can add new features via new apps anytime and that we make it easier for new developers to contribute to ownCloud. 
> 
> I plan to do this in a transparent way so that the users doesn´t have to care if an apps is shipped with ownCloud or installed afterward from the net.
> 
> https://gitorious.org/owncloud/apps
> 
> Does this make sense?
> 
> 
> Cheers
> Frank
> 
> 
> 
> Frank Karlitschek
> karlitschek at kde.org
> 
> 
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud

Hi all,

I think its a great idea to minimize the core.  This is especially great if a new app version doesn't require a new ownCloud version, allowing for the app to upgrade.  Users are interested in this, as can be seen 
by people trying to use the fullcalendar branch with ownCloud 2.

My only suggestion is to make one repository per app/set of apps.  So for instance, the calendar/contacts apps might be in one (even if it involves 2+ apps), one for media, etc.  My only concern for having 
one big repository is alot of history and files if someone wants to work on only one app.  It would help lower the barrier to entry to help (they find the one specific project they are interested in, clone it, and 
work on it).  By grouping similar apps (such as calendar/contacts) its easier to deal with dependencies between the apps (they all exist in the one repository), and avoids an unnecessary explosion of 
repositories.


Matthew