Am Dienstag, 11. November 2014, 14.00:51 schrieb Thomas Friedrichsmeier:
> Hi once more,


> On Thursday 06 November 2014 19:44:12 Nicolás Alvarez wrote:
> > Non-fast-forward pushes (force pushes) and branch deletions are only
> > allowed for the "repository owners". You'll have to decide who that
> > will be.
> I guess I'll state that in the ticket, whenever I request the repository to
> be moved to playground, right? (Mario, or would we go for kdereview,
> directly?)

I think that's done now, right? It looks like it's playground.

> Also one more admin question: So far we had a dedicated mailing list for
> SCM- commits. That was quite convenient. And in fact, it would be even
> more convenient, if we had merged it in one list with build bot
> notifications(*). That would make it easy for all developers to subscribe
> to a single pack of "all that noise" that is relevant to those who commit,
> but not so much for other interested bystanders. I'm sort of hoping to
> achieve this as part of the transition to

I think other KDE projects go in this direction as well. One development list 
and one noisy, commits, rr, etc. list.

> Now the KDE way of doing things seems to be using
> Some questions:
> - Is is possible to direct commitfiltered mail to a mailing list? (Or will
> commitfilter mail out password reminders and some such?)
> - Alternatively, is it possible to set up custom notification hooks on a
> git repo on

I think so. But KDE sysadmins know for sure.

> - Or is the list I have in mind a poor plan, in the first place?
> Regards
> Thomas
> (*) Potentially also bug tracker notifications, although perhaps it makes
> more sense for those to go to rkward-devel, after all.


Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
RKWard-devel mailing list

Reply via email to