[Owncloud] Name of app repositories

Mon Mar 18 12:31:32 UTC 2013

How we moved Mail:

* asked Frank for a new repo »mail«, with the relevant people to be added
as contributors/admins
* moved the code from the apps repo to the new repo (of course history gets
lost but that’s ok), deleted the code in the apps repo
* started using the new issue tracker and moved the old issues (only 10) by
hand

There seems to be a better way to bulk move issues, see the 2 solutions
proposed at
http://stackoverflow.com/questions/9720718/how-do-i-move-an-issue-on-github-to-another-repo,
please advise if you try it out.

Alessandro: There is a repo »news« as requested by Bernhard, I suppose you
can move the News app there.

On Mon, Mar 18, 2013 at 9:35 AM, Alessandro Cosentino <cosenal at gmail.com>wrote:

> agreed. sorry for the futile discussion.
>
> some more practical information:
> - can we already go ahead and move the code?
> - is each maintainer going to do it by himself?
> - is it easy to move the issues too? some of them are not properly
> tagged, maybe we should do some triaging before.
> - has anyone already done this and can provide a 2-lines howto?
>
> Thanks,
> Alessandro
>
>
> On Mon, Mar 18, 2013 at 9:10 AM, Jakob Sack <mail at jakobsack.de> wrote:
> > Hi,
> >
> > I did not want to start a discussion about splitting up of the apps
> > repository. I know that this is already happening and I think that it's a
> > good idea.
> > The point I'm talking about is the introduction of a namespace for the
> new
> > app repositories. As some of you pointed out that it won't improve the UX
> > and everybody knows how to use the search I consider this proposal to be
> > rejected.
> >
> > Jakob
> >
> > Am 18.03.2013 07:50, schrieb Frank Karlitschek:
> >
> >> As I said.
> >> It's O.K. for curtain "bigger" apps to have an own repository. And only
> if
> >> the maintainer requests it.
> >> Having this for every single small app introduces chaos without a
> benefit.
> >>
> >> In the meantime I suggest that we try to fix the urgent bugs that we
> >> currently have instead of discussions like that that don't improve the
> >> experience for ownCloud users.
> >>
> >> Frank
> >>
> >>
> >> On 17.03.2013, at 23:06, Alessandro Cosentino<cosenal at gmail.com>
>  wrote:
> >>
> >>> I totally agree on this splitting and I totally agree with the naming
> >>> proposed by Jakob.
> >>> Code and commits should be easy to migrate. Is it easy to do the
> >>> migration of the issues to the new repos?
> >>>
> >>> Alessandro
> >>>
> >>>
> >>> On Sun, Mar 17, 2013 at 9:44 PM, Frank Karlitschek<frank at owncloud.org>
> >>> wrote:
> >>>>
> >>>> On 17.03.2013, at 21:30, Jakob Sack<mail at jakobsack.de>  wrote:
> >>>>
> >>>>> Hello,
> >>>>>
> >>>>> I really like the idea of splitting up the apps repository by
> creating
> >>>>> a
> >>>>> repository for each app.
> >>>>
> >>>> I think it makes sense for the big apps where the developers request
> >>>> such a change. For a lot of the smaller ones an apps repo for "the
> rest" is
> >>>> not a problem.
> >>>>
> >>>>
> >>>>> However, I dislike the current names of these
> >>>>> repositories.
> >>>>> I'd prefer a naming schema like "app-mail" and "app-news". This way
> >>>>> it'd be
> >>>>> easy to distinguish the app repositories from the other 20+
> >>>>> repositories.
> >>>>
> >>>> Yes. I can rename them if the people who are working in them agree.
> >>>>
> >>>>
> >>>>> Any comments?
> >>>>> Best,
> >>>>>
> >>>>> Jakob
> >
> > _______________________________________________
> > 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/20130318/e4471d01/attachment.html>