<div dir="ltr">Oh and please – don’t put off these discussions as unnecessary just because they don’t improve the user experience. They need to be solved. We can’t just break off certain things because »there are more important things right now, like fixing bugs« because then we’ll not move forward. There are always bugs to be fixed. This is not a binary choice, as so often, but we need to balance.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 18, 2013 at 1:31 PM, Jan-Christoph Borchardt <span dir="ltr"><<a href="mailto:hey@jancborchardt.net" target="_blank">hey@jancborchardt.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">How we moved Mail:<div><br><div>* asked Frank for a new repo »mail«, with the relevant people to be added as contributors/admins</div>
<div>* 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</div>
<div>* started using the new issue tracker and moved the old issues (only 10) by hand</div><div><br></div><div>There seems to be a better way to bulk move issues, see the 2 solutions proposed at <a href="http://stackoverflow.com/questions/9720718/how-do-i-move-an-issue-on-github-to-another-repo" target="_blank">http://stackoverflow.com/questions/9720718/how-do-i-move-an-issue-on-github-to-another-repo</a>, please advise if you try it out.</div>
<div><br></div><div>Alessandro: There is a repo »news« as requested by Bernhard, I suppose you can move the News app there.</div><div><br></div><div><br></div><div><br></div></div></div><div class="HOEnZb"><div class="h5">
<div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Mar 18, 2013 at 9:35 AM, Alessandro Cosentino <span dir="ltr"><<a href="mailto:cosenal@gmail.com" target="_blank">cosenal@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
agreed. sorry for the futile discussion.<br>
<br>
some more practical information:<br>
- can we already go ahead and move the code?<br>
- is each maintainer going to do it by himself?<br>
- is it easy to move the issues too? some of them are not properly<br>
tagged, maybe we should do some triaging before.<br>
- has anyone already done this and can provide a 2-lines howto?<br>
<br>
Thanks,<br>
Alessandro<br>
<div><div><br>
<br>
On Mon, Mar 18, 2013 at 9:10 AM, Jakob Sack <<a href="mailto:mail@jakobsack.de" target="_blank">mail@jakobsack.de</a>> wrote:<br>
> Hi,<br>
><br>
> I did not want to start a discussion about splitting up of the apps<br>
> repository. I know that this is already happening and I think that it's a<br>
> good idea.<br>
> The point I'm talking about is the introduction of a namespace for the new<br>
> app repositories. As some of you pointed out that it won't improve the UX<br>
> and everybody knows how to use the search I consider this proposal to be<br>
> rejected.<br>
><br>
> Jakob<br>
><br>
> Am 18.03.2013 07:50, schrieb Frank Karlitschek:<br>
><br>
>> As I said.<br>
>> It's O.K. for curtain "bigger" apps to have an own repository. And only if<br>
>> the maintainer requests it.<br>
>> Having this for every single small app introduces chaos without a benefit.<br>
>><br>
>> In the meantime I suggest that we try to fix the urgent bugs that we<br>
>> currently have instead of discussions like that that don't improve the<br>
>> experience for ownCloud users.<br>
>><br>
>> Frank<br>
>><br>
>><br>
>> On 17.03.2013, at 23:06, Alessandro Cosentino<<a href="mailto:cosenal@gmail.com" target="_blank">cosenal@gmail.com</a>> wrote:<br>
>><br>
>>> I totally agree on this splitting and I totally agree with the naming<br>
>>> proposed by Jakob.<br>
>>> Code and commits should be easy to migrate. Is it easy to do the<br>
>>> migration of the issues to the new repos?<br>
>>><br>
>>> Alessandro<br>
>>><br>
>>><br>
>>> On Sun, Mar 17, 2013 at 9:44 PM, Frank Karlitschek<<a href="mailto:frank@owncloud.org" target="_blank">frank@owncloud.org</a>><br>
>>> wrote:<br>
>>>><br>
>>>> On 17.03.2013, at 21:30, Jakob Sack<<a href="mailto:mail@jakobsack.de" target="_blank">mail@jakobsack.de</a>> wrote:<br>
>>>><br>
>>>>> Hello,<br>
>>>>><br>
>>>>> I really like the idea of splitting up the apps repository by creating<br>
>>>>> a<br>
>>>>> repository for each app.<br>
>>>><br>
>>>> I think it makes sense for the big apps where the developers request<br>
>>>> such a change. For a lot of the smaller ones an apps repo for "the rest" is<br>
>>>> not a problem.<br>
>>>><br>
>>>><br>
>>>>> However, I dislike the current names of these<br>
>>>>> repositories.<br>
>>>>> I'd prefer a naming schema like "app-mail" and "app-news". This way<br>
>>>>> it'd be<br>
>>>>> easy to distinguish the app repositories from the other 20+<br>
>>>>> repositories.<br>
>>>><br>
>>>> Yes. I can rename them if the people who are working in them agree.<br>
>>>><br>
>>>><br>
>>>>> Any comments?<br>
>>>>> Best,<br>
>>>>><br>
>>>>> Jakob<br>
><br>
> _______________________________________________<br>
> Owncloud mailing list<br>
> <a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
_______________________________________________<br>
Owncloud mailing list<br>
<a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>