[Owncloud] Need help triaging bugs in the apps repo

[Jan-Christoph Borchardt]

Alessandro, yes this is kind of my point. The embryonic apps will be in the
»apps« repo (the apps-playground isn’t really used anyway and just makes
stuff more complex).

Thomas:
A new repo with just the shipped apps might alleviate the symptoms but not
really solve the problem. Actually it will be the same problem as before:
Mixed issues and commits and pull requests and an unfiltered mess.

Calendar, Contacts and Tasks might have some technical similarities but
should be split code-wise. People can and should be able to use each of
them independently (or not), so they have lots of different issues. If
there are cross-dependencies or reuse opportunities, then define a clear
API (or whatnot) – we should split apps more to encourage better
interoperability, not mash them together. Issues can easily be interlinked
on Github.

And don’t forget, there can always be a 3rd-party Calendar, Contacts or
Tasks app which is better than the »core« one, so we shouldn’t act like
there’s the grand trifecta of set »PIM« apps which we set.



On Thu, Mar 14, 2013 at 3:06 PM, Thomas Tanghus <thomas at tanghus.net> wrote:

> On Thursday 14 March 2013 14:43 Jan-Christoph Borchardt wrote:
> > Clearly, this will be much easier with each app (at least the ones which
> > get shipped, like Calendar, Contacts etc) in their own repo. Just have
> > http://github.com/owncloud/contacts and
> http://github.com/owncloud/calendar
> > Clear issue distinction, pull requests, git history and people working on
> > it. We moved Mail out of the mess which is the apps repo and the
> experience
> > is great.
> >
> > I still think we should take things slow though. There’s no need for a
> > rapid transition. But if you’re a developer of a shipped app inside the
> > apps repo, you might want to consider if it’s better for your workflow
> (and
> > to attract contributors) to have a dedicated repo for your app, inside
> the
> > ownCloud organisation.
>
> Since Calendar, Contacts and Tasks have many similarities and should imo
> be in
> one repository.
>
> * We've talked about trying to define common interfaces for the backends
> for
> better maintainability.
> * We've talked about splitting 'core' Calendar out, so other apps can use
> it
> without having to enable the Calendar frontend. I could do the same so that
> administrators could use the CardDAV backend without having to enable the
> frontend.
> * Several github issues concern both Calendar and Contacts and having them
> in
> different repositories would add more work if we have to maintain two
> trackers.
>
> > Thoughts, Georg, Thomas, Brice, Robin?
>
> I suggest a new repo - (pim?) - where we group those apps.
>
> --
> Med venlig hilsen / Best Regards
>
> Thomas Tanghus
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20130314/022d2945/attachment.html>