Talk:ETH Zurich 2006

From 2006.igem.org

(Difference between revisions)
Jump to: navigation, search
(→Availability)
m
 
(12 intermediate revisions not shown)
Line 4: Line 4:
* indentions are made by adding as many colons as you want. Answers to a comment with one colon thus should start with two colons etc.
* indentions are made by adding as many colons as you want. Answers to a comment with one colon thus should start with two colons etc.
-->
-->
-
=Some stuff from the original page=
 
-
that should be on the discussion page. Espacially since it is no more actually.
 
 +
'''Structure'''
-
=== HOT ===
+
I suggest to put the coordination part to the bottom and add a "team" part instead to the top --[[User:Dimo|Dimo]] 05:29, 30 October 2006 (EST)
-
* 17-jul 17:30 meet @cnb, seminar room
 
-
<pre>
 
-
Hello
 
-
As you might have noticed on the wiki we want to make an informal meating at monday.
+
'''writing everything small?'''
-
@Robert & Marco Jovanovic:
+
I propose to have a correct usage of capital letters within our wiki (if possible). Texts are hard to read if everything is written small. Furthermore, it gives the impression of being not competent. --[[User:Dimo|Dimo]] 10:03, 26 October 2006 (EDT)
-
It would be quite usefull if you attend as you havent been part of the wet-lab course
+
-
and therefore yu should use the opportunity to get in contact with the other members
+
-
of the team.
+
-
Michael
 
-
</pre>
 
-
=== Informal meeting ===
 
-
After today`s lab there was the idea of an informal meeting at monday for doing some brainstorming.
+
'''everything on one page?'''
-
Would this fit for everyone? What time would fit best? For further discussion we may use the discussion page.
+
-
I think to get an idea when people can come we should make a list here (easier than the other one, just enter a line for you and make marks where you can come):
+
should this all stay on the entry page? with all the details? --[[User:Dimo|Dimo]] 10:06, 12 October 2006 (EDT)
-
<!-- just verbatim text, so it's desplayed as you see it in the editing window -->
+
: I see little reason to separate it, espacially at this point, unless there is a compelling reason why something cannot sensibly be placed on the front page. Maybe when finishing the documentation I'll worry about dividing it up. Granted the table of contents are too long but this wiki does not provide any means to control which sections show up there ... --[[User:Ajk|Ajk]] 10:13, 12 October 2006 (EDT)
-
<pre>
+
-
Monday 17th July
+
-
Names                08  09  10  11  12  13    14    15    16    17  18    19
+
'''Table of Contents on the Wiki'''
-
Michael              ok  ok  ok  ok  ok  ok    ok    ok    ok    ok  ok    ok
+
-
Dimo                ok  ok  ok  ok  ok  ok    ok    ok    ok    ok  ok    ok
+
-
Alexandra                          ok  ok  ok    ok                ok  ok    ok
+
-
Franz                I'm busy on Monday (MEMS Lab)
+
-
Arthur              Away
+
-
Robert              It's ok for me after 5 PM
+
-
</pre>
+
-
= Availability =
+
:You can eliminate the computer generated TOC by adding
-
I think, the following chart is also not necessary any more (it has never been applicable from my point of view).
+
-
Anyway, we could put known longer absences here.
+
:<underscore><underscore>NOTOC<underscord><underscore>        (Note: change the <underscore> to the underscore character)
-
* Dimo: I will not be in Zurich from September 4-19
+
-
* Alexandra:
+
-
**I will not be in Zurich from Juli 27 to August6
+
-
**I will not be available after 16.00 o'clock in August 21-27
+
 +
:to the page.  Then, you can write your own TOC entries with total control. -- Randy
-
 
+
:: Thanks for the hint. As long as the wiki is volatile I want to have it generated automatically though. --[[User:Ajk|Ajk]] 04:01, 16 October 2006 (EDT)
-
== Availability chart ==
+
-
 
+
-
Sorry Alexandra, the table I made is terrible to edit, so I think we can use that: [http://www.doodle.ch/dpstPwMnysUQ]
+
-
 
+
-
The meaning of the marks is inverted, make '''marks where you are not available!!''' (to save clicking work on your part I hope ;))
+

Latest revision as of 11:27, 30 October 2006


Structure

I suggest to put the coordination part to the bottom and add a "team" part instead to the top --Dimo 05:29, 30 October 2006 (EST)


writing everything small?

I propose to have a correct usage of capital letters within our wiki (if possible). Texts are hard to read if everything is written small. Furthermore, it gives the impression of being not competent. --Dimo 10:03, 26 October 2006 (EDT)


everything on one page?

should this all stay on the entry page? with all the details? --Dimo 10:06, 12 October 2006 (EDT)

I see little reason to separate it, espacially at this point, unless there is a compelling reason why something cannot sensibly be placed on the front page. Maybe when finishing the documentation I'll worry about dividing it up. Granted the table of contents are too long but this wiki does not provide any means to control which sections show up there ... --Ajk 10:13, 12 October 2006 (EDT)

Table of Contents on the Wiki

You can eliminate the computer generated TOC by adding
<underscore><underscore>NOTOC<underscord><underscore> (Note: change the <underscore> to the underscore character)
to the page. Then, you can write your own TOC entries with total control. -- Randy
Thanks for the hint. As long as the wiki is volatile I want to have it generated automatically though. --Ajk 04:01, 16 October 2006 (EDT)
Retrieved from "http://2006.igem.org/wiki/index.php/Talk:ETH_Zurich_2006"
Personal tools
Past/present/future years