Changes between Version 1 and Version 2 of SCS_MAIL_LIST_R3

Timestamp:

01/11/09 11:59:22 (16 years ago)

Author:

deyan

Comment:

--

SCS_MAIL_LIST_R3

@@ -6 +6 @@
 
 = Analysis =
-^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^
-
 == Overview ==
-^(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^
-
+Mail list eases communication between team members.
 == Task requirements ==
-^(Necessary requirements that the task must fulfill.)^
-
+Send 2 e-mails
+ * Mail 1 should contain information from the sprint closing
+ * Mail 2 should contain sub-team information
+  * Collect information about sub-team mail lists
+  * Suggest creating sub-team mail lists where none (See implementation idea)
+  * Send an e-mail containing information on sub-team e-mails
 == Task result ==
-^(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))^
+e-mails sent to the developers mail list
 
 == Implementation idea ==
-^(It is advisable to include some rough implementations ideas.)^
+Implement this tasks in parallel with [wiki:SCS_PROJECT_BLOG_R2] [[BR]]
+For the sub-team mail list sophie2-devs-teamname@googlegroups.. format would be usable.
 
 == Related ==
-^(Here you can add related tasks that could be useful or helpful.)^
-
+[wiki:SCS_PROJECT_BLOG_R2][[BR]]
+[wiki:SCS_MAIL_LIST_R2][[BR]]
 == How to demo ==
 ^(In this section you must add instructions for the demo of the task.)^