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 <[email protected]> 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 <[email protected]> wrote: >> >> On 17.03.2013, at 21:30, Jakob Sack <[email protected]> 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 >>> [email protected] >>> https://mail.kde.org/mailman/listinfo/owncloud >> >> _______________________________________________ >> Owncloud mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/owncloud > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
