[Owncloud] Need help triaging bugs in the apps repo

[Jan-Christoph Borchardt]

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.


Thoughts, Georg, Thomas, Brice, Robin?





On Thu, Mar 14, 2013 at 2:28 PM, Thomas Müller <thomas.mueller at tmit.eu>wrote:

>
> To be honest:
> Every app maintainer should take care about his bug himself.
> And yes - I know there are a hell of issues for me regarding pdf and odf.
>
> I simple have no time ....
>
> Tom
>
> Am Donnerstag, dem 14.03.2013 um 14:26 schrieb Bernhard Posselt:
> > Can someone "volunteer" to triage bugs in the apps repo? like correctly
> > assign and notify maintainers of issues without labels.
> >
> > I'm already handling core and tbh I'm a bit exhausted right now ;)
> > _______________________________________________
> > Owncloud mailing list
> > Owncloud at kde.org
> > https://mail.kde.org/mailman/listinfo/owncloud
> _______________________________________________
> 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/f76e72bd/attachment.html>