@@ -57,5 +57,46 @@ $this->headTitle('About');
57
57
you'd better try to find a sponsor for covering the costs.
58
58
Otherwise it seems more like a conference, doesn't it?</p>
59
59
</dd>
60
+ <dt>How does it work?</dt>
61
+ <dd>
62
+ <p>
63
+ Whoever knows of a usergroup can promote it. You have to log in with
64
+ a twitter-account and are then able to promote a usergroup. We will
65
+ then check some basic stuff and might get in contact with the group
66
+ to clear issues and as soon as everything is cleared the group will
67
+ show up on the map.
68
+ </p><p>
69
+ As soon as the group appears on the map it is also available via the API
70
+ </p>
71
+ <p>Users whos twitter-account has been associated with a group can
72
+ - after logging in - edit their groups information. In the groups
73
+ information-popup there is a little edit-icon on the right hand
74
+ side of the contact-informations. That brings you to the edit-screen.
75
+ So <strong>you</strong> are in charge of your groups information</p>
76
+ </dd>
77
+ <dt>
78
+ Do we need an iCalendar-File?
79
+ </dt>
80
+ <dd>
81
+ <p>Short answer: No. You do not need one. But you should have one</p>
82
+ <p>
83
+ We use a provided iCalendar-File to retrieve your groups next meeting
84
+ so we can display that in your groups information popup. So everyone
85
+ interested in your group can see right from the start when and where
86
+ your next meeting will be. No digging for new users where to find
87
+ that information, it's right there.
88
+ </p><p>
89
+ As the API also provides the link to the iCalendar-file all sites using
90
+ it might also want to display your next event beneath your username.
91
+ This is already in progress on <a href="http://php.net/ug.php">php.net</a>.
92
+ </p><p>
93
+ When your groups does not have an iCalendar-File we are not able to
94
+ provide that information, but that's it.
95
+ </p><p>
96
+ So even if you are meeting on a regular basis (say every last thursday
97
+ of every second month) you should create an iCalendar-File with that
98
+ one recurring event to give people an idea of when you are meeting.
99
+ </p>
100
+ </dd>
60
101
</dl>
61
102
</section>
0 commit comments