[Owncloud] Need help triaging bugs in the apps repo

[Thomas Tanghus]

On Thursday 14 March 2013 15:22 Jan-Christoph Borchardt wrote:
> 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.

Yes, but they cannot be easily moved. I don't know how much time and annoyance 
it takes from both bug-triagers and -reporters closing issues to have them 
opened in another repo.
It also makes it harder to have Concept issues for discussions - which repo 
should they go in, where was the one I wanted etc etc.

> 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.

I'm not talking about a PIM app, but a PIM repository, and I'm not talking 
about mashing things together but rather splitting them and share common 
*programming* interfaces. That way admins can choose to enable only one 
backend, both backends, one or more UI parts, or choose another UI - or not 
use any of them like e.g. Kolab does.

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

> > 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