Projects/MovetoGit/Meeting1111 - Revision history

Boud at 19:50, 25 November 2009

2009-11-25T19:50:59Z

2009-11-25T19:40:48Z

2009-11-12T18:13:03Z

2009-11-12T11:16:51Z

2009-11-12T01:17:28Z

boud, eean and myself have chanops access

2009-11-11T20:31:21Z

2009-11-11T20:28:43Z

2009-11-11T20:28:03Z

2009-11-11T20:27:42Z

2009-11-11T20:22:41Z

@@ Line 1: / Line 1: @@
-* project lay
+* project layout
    ** compromise?
          -> every module in KDE gets a repo, every project in support/extragear
-            gets a repo, koffice gets a repo
+            gets a repo, koffice gets a repo. '''This decision is now final and no longer up for discussion'''
          -> write a script to clone, update and build everything, like kde-svn
             (TASK: Morice).=
@@ Line 8: / Line 8: @@
             however, they will have to help out then. Otherwise, they get lumped
             together. Will have to ask the module maintainers (TASK: Chani will do
-            the asking)
+            the asking) Resolution: EDU wants to stay together at least.l
          -> if a subproject wants to separate all their apps, someone will have to
              help them (TASK)
@@ Line 14: / Line 14: @@
    ** who checks with gitorious
 * user accounts (gitorous accounts need to have a realname)
-   ** get opt-in privacy agreement. TASK: eean. (coordinate with johann)
+   ** <strike>get opt-in privacy agreement. TASK: eean. (coordinate with johann)</strike>. Will not be possible: see http://lists.kde.org/?l=kde-scm-interest&m=125812257311133&w=2.
    ** we need a simple method for people to say "make me a gitorious account".
       (wiki page?) This list warns about privacy issues: it is opt-in. TASK:

@@ Line 1: / Line 1: @@
-* project layout
+* project lay
    ** compromise?
          -> every module in KDE gets a repo, every project in support/extragear
@@ Line 30: / Line 30: @@
             Finish documentation: TASK for Chani
    ** releasing
-        -> ask dirk, cyrille what do they need to create tarballs,
+        -> <strike>ask dirk, cyrille what do they need to create tarballs,
-           collect translations, tag multiple repos (TASK: boud, morice)
+           collect translations, tag multiple repos (TASK: boud, morice)</strike>. We asked the question, got no answer, so no help is needed.
    ** building (kde-git-build, morice)
    ** pre/post commit hooks, write & coordinate with gitorious

@@ Line 62: / Line 62: @@
        -> TASK: Chani and Dario
 * funding to pay gitorious
-    -> TASK: ping KDE e.V. board about this (and Thiago). (boud)
+    -> TASK: <strike>ping KDE e.V. board about this (and Thiago).
        * note: we have to make sure what we get for the funding.
        * service-level-agreement?

@@ Line 62: / Line 62: @@
        -> TASK: Chani and Dario
 * funding to pay gitorious
-    -> TASK: ping KDE e.V. board about this (and Thiago).
+    -> TASK: ping KDE e.V. board about this (and Thiago). (boud)
        * note: we have to make sure what we get for the funding.
        * service-level-agreement?

@@ Line 73: / Line 73: @@
      -> for now, docs/manuals stay in svn. Moving to userbase or git can be done
         later, it is not a blocker. Ask for input.
-* get op on #kde-git: task for argonal
+* <strike>get op on #kde-git: task for argonal</strike>
 * AOB:

← Older revision		Revision as of 20:31, 11 November 2009
Line 74:		Line 74:
	later, it is not a blocker. Ask for input.		later, it is not a blocker. Ask for input.
	* get op on #kde-git: task for argonal		* get op on #kde-git: task for argonal
		+
		+	* AOB:
		+
		+	-> Chani: movetogit page has some false info about having individual
		+	developer groups.
		+	-> drf(Dario):

@@ Line 71: / Line 71: @@
      -> email issue: in the next gitorious sprint (TASK: johan-s)
 * docs/ folders will need to be sync'd with svn?
 * gitorious emails
 * get op on #kde-git: task for argonal