[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-scm-interest
Subject:    [Kde-scm-interest] IRC Meeting Summary + Log
From:       Casey Link <unnamedrambler () gmail ! com>
Date:       2009-01-26 20:22:23
Message-ID: fb3727060901261222g738dc024i8586b7bfc3e15eb2 () mail ! gmail ! com
[Download RAW message or body]

The meeting just ended on IRC. The focus was: what things needed to be
done to make the switch (for amarok) happen, and who was going to do
the work.

I've really got to be somewhere so I am going to make this summary
short. See attachment for the meeting log or here
http://pastie.org/371418

* Scripty
It needs a port to git. Ian and Boyd (bss03) are going to work on it.
Albert (tsdegos) will assist them in a code-checking/review function.

* Accountability
We will use Thiago's and Thomas Zander's idea to use a post-receive
hook that matches the pusher via their ssh key and publishes a PushLog
in a branch.

* Other Hooks (bko, commit filter, etc)
This hooks live in trunk/kde-common/svn/hooks. Boyd offered to help port them.

* Server Setup/Infrastructure
No sysadmins were present at the meeting, so we still need to contact
them about setting up git.kde.org w/ git + gitorious + ssh
authentication.

* Pushing
We pretty much agreed with the discussion that has already happened on
KDE-SCM-Interest. Everyone (with an ssh key) will have push rights.
Only sysadmins will have force-push rights.

* IRC Channel (because nothing is official until it has an IRC channel)
#kde-git was created and  registered. It will serve as a counterpart
to this mailing list.


So our current bottleneck is Scripty and getting the infrastructure setup.

Casey Link

["amarok.git.meeting.log" (application/octet-stream)]

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest


[prev in list] [next in list] [prev in thread] [next in thread]