/[gentoo]/xml/htdocs/proj/en/overlays/devguide.xml
Gentoo

Diff of /xml/htdocs/proj/en/overlays/devguide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.14 Revision 1.15
7<author title="Author"> 7<author title="Author">
8 <mail link="stuart">Stuart Herbert</mail> 8 <mail link="stuart">Stuart Herbert</mail>
9</author> 9</author>
10<author title="Author"> 10<author title="Author">
11 <mail link="jokey">Markus Ullmann</mail> 11 <mail link="jokey">Markus Ullmann</mail>
12</author> 12</author>
13<author title="Author"> 13<author title="Author">
14 <mail link="robbat2">Robin H. Johnson</mail> 14 <mail link="robbat2">Robin H. Johnson</mail>
15</author> 15</author>
16 16
17<abstract>This guide helps developers understand how to use the Gentoo 17<abstract>This guide helps developers understand how to use the Gentoo
18Overlays service.</abstract> 18Overlays service.</abstract>
19 19
20<license/> 20<license/>
21 21
22<version>2.1</version> 22<version>2.2</version>
23<date>2008-10-12</date> 23<date>2008-10-30</date>
24 24
25<chapter> 25<chapter>
26<title>Introduction</title> 26<title>Introduction</title>
27 27
28<section> 28<section>
29<title>Audience</title> 29<title>Audience</title>
30<body> 30<body>
31<p>This document has been written for Gentoo developers and Gentoo staff members. If you are a Gentoo user, or you just want to start downloading and using overlays, please see <uri link="/proj/en/overlays/userguide.xml">the Gentoo Overlays User Guide</uri> instead.</p> 31<p>This document has been written for Gentoo developers and Gentoo staff members. If you are a Gentoo user, or you just want to start downloading and using overlays, please see <uri link="/proj/en/overlays/userguide.xml">the Gentoo Overlays User Guide</uri> instead.</p>
32</body> 32</body>
33</section> 33</section>
34 34
35<section> 35<section>
36<title>What is overlays.gentoo.org?</title>
37<body>
38<p><uri link="http://overlays.gentoo.org">overlays.gentoo.org</uri> provides social workspaces to allow Gentoo projects, developers and users to collaborate together on tomorrow's Gentoo packages. We do this by hosting overlays for Gentoo projects, and overlays for Gentoo developers.</p>
39</body>
40</section>
41
42<section>
43<title>Who Can Use overlays.gentoo.org?</title> 36<title>Who Can Use overlays.gentoo.org?</title>
44<body> 37<body>
45<p>Any Gentoo project, or Gentoo developer, can have their own overlay hosted on overlays.gentoo.org, with the RSS feed from the changelog included on <uri link="http://overlays.gentoo.org">the overlays.gentoo.org homepage</uri>.</p> 38<p>Any Gentoo project, or Gentoo developer, can have their own overlay hosted on (git.)overlays.gentoo.org, with the RSS feed from the changelog included on <uri link="http://overlays.gentoo.org">the overlays.gentoo.org planet</uri>.</p>
46 39
47<p>Any Gentoo staff member or user (ie, anyone who doesn't have write access to 40<p>Any User can download and use the contents of any hosted
48the main Portage package tree) can download and use the contents of any hosted
49overlay. If you choose, you can also give users write access to your 41overlay. If you choose, you can also give users write access to your
50overlay.</p> 42overlay.</p>
51</body> 43</body>
52</section> 44</section>
53 45
54<section> 46<section>
55<title>What Does overlays.gentoo.org Give Me?</title> 47<title>What Does overlays.gentoo.org Give Me?</title>
56<body> 48<body>
57<p>The overlays.gentoo.org service currently provides:</p> 49<p>The (git.)overlays.gentoo.org service currently provides:</p>
58<ul> 50<ul>
59<li><uri link="http://trac.edgewall.com">Trac</uri> (a wiki w/ integrated subversion browser), for quickly creating and maintaining documentation about your overlay</li> 51<li><uri link="http://trac.edgewall.com">Trac</uri> (a wiki w/ integrated subversion browser), for quickly creating and maintaining documentation about your Subversion based overlay</li>
60<li><uri link="http://subversion.tigris.org">Subversion</uri> - a centralised version control system</li>
61<li>Publishing the changelog for your overlay on <uri link="http://overlays.gentoo.org/">the o.g.o homepage</uri>, so that everyone who's interested can see what's going on</li> 52<li>Publishing the changelog for your overlay on <uri link="http://overlays.gentoo.org/">the o.g.o homepage</uri>, so that everyone who's interested can see what's going on</li>
62<li><uri link="http://git.or.cz">Git</uri> - Fast Version Control System</li>
63<li><uri link="http://git.or.cz/gitwiki/Gitweb">gitweb</uri> - provides full-fledged web interface for viewing Git repositories.</li> 53<li><uri link="http://git.or.cz/gitwiki/Gitweb">gitweb</uri> - provides full-fledged web interface for viewing Git repositories.</li>
64</ul> 54</ul>
65 55
66<p>... all hosted on secure, backed-up Gentoo infrastructure, administered by 56<p>... all hosted on secure, backed-up Gentoo infrastructure, administered by
67<uri link="/proj/en/infrastructure">the Gentoo Infrastructure team</uri> (hardware / base OS) and <uri link="/proj/en/overlays">the Gentoo Overlays team</uri> 57<uri link="/proj/en/infrastructure">the Gentoo Infrastructure team</uri> (hardware / base OS) and <uri link="/proj/en/overlays">the Gentoo Overlays team</uri>
68(wiki / VCS / ACLs).</p> 58(wiki / VCS / ACLs).</p>
69 59
70<p>Each overlay has separate authentication lists for Trac, Subversion and Git. 60<p>Each overlay has separate authentication lists for Trac, Subversion and Git.
71It's no problem at all to give someone write access to just Trac (e.g. for 61It's no problem at all to give someone write access to just Trac (e.g. for
72writing documentation) without giving them write access to Subversion.</p> 62writing documentation) without giving them write access to Subversion.</p>
73</body> 63</body>
74</section> 64</section>
75 65
76<section> 66<section>
77<title>Why Should We Use overlays.gentoo.org?</title> 67<title>Why Should We Use overlays.gentoo.org?</title>
130 120
131<section> 121<section>
132<title>Introduction</title> 122<title>Introduction</title>
133<body> 123<body>
134<p>There are two types of overlay - "project" overlays, and "developer" 124<p>There are two types of overlay - "project" overlays, and "developer"
135overlays. The only difference between them is responsibility and 125overlays. The only difference between them is responsibility and
136accountability.</p> 126accountability.</p>
137 127
138<impo>Before requesting an overlay, please make sure that you have read our <uri link="/proj/en/overlays/policy.xml">Policy Document</uri>. It clearly sets out what's allowed and what is not, and what your responsibilities will be.</impo> 128<impo>Before requesting an overlay, please make sure that you have read our <uri link="/proj/en/overlays/policy.xml">Policy Document</uri>. It clearly sets out what's allowed and what is not, and what your responsibilities will be.</impo>
139</body> 129</body>
140</section> 130</section>
141 131
142<section> 132<section>
143<title>Project Overlays</title> 133<title>Project Overlays</title>
144<body> 134<body>
145<p>"Project" overlays are overlays for official Gentoo projects. A good 135<p>"Project" overlays are overlays for official Gentoo projects. An example is <uri link="http://overlays.gentoo.org/proj/php">the PHP Overlay</uri>.</p>
146example is <uri link="http://overlays.gentoo.org/proj/php">the PHP Overlay</uri>.</p>
147 136
148<p>An official Gentoo project is a project that has a project page on 137<p>An official Gentoo project is a project that has a project page on
149www.gentoo.org, and that has an elected lead. (This definition comes from <uri link="http://www.gentoo.org/proj/en/glep/glep-0039.html">the 138www.gentoo.org, and that has an elected lead. (This definition comes from the
150metastructure document</uri>, which is Gentoo's governing document). The project 139metastructure document). The project lead(s) are responsible for the project overlay, including its contents, and any problems it causes other Gentoo projects and developers.</p>
151lead(s) are responsible for the project overlay, including its contents, and
152any problems it causes other Gentoo projects and developers.</p>
153 140
154<p>To request a SVN project overlay, the project's lead just needs to pop into 141<p>To request a SVN project overlay, the project's lead just needs to pop into
155#gentoo-overlays on IRC and ask for an overlay to be created. Or, if he/she 142#gentoo-overlays on IRC and ask for an overlay to be created. Or, if he/she
156prefers, drop an email to overlays@gentoo.org. We'll take care of the rest, 143prefers, drop an email to overlays@gentoo.org. We'll take care of the rest,
157including granting write access to all the members of your project (as listed 144including granting write access to all the members of your project (as listed
158on your project page).</p> 145on your project page).</p>
159 146
160<p>To request a Git project overlay, just visit the <uri 147<p>To request a Git project overlay, just visit the <uri
161link="http://git.overlays.gentoo.org">git.overlays</uri> site, and follow the 148link="http://git.overlays.gentoo.org">git.overlays</uri> site, and follow the
162setup instructions, emailing the completed template as directed.</p> 149setup instructions, emailing the completed template as directed.</p>
163 150
164<p>For an SVN request, we will:</p> 151<p>For an SVN request, we will:</p>
165<ul> 152<ul>
166<li>create your overlay (trac site + svn)</li> 153<li>create your overlay (trac site + svn)</li>
167<li>add your overlay's RSS feed to the o.g.o homepage</li> 154<li>add your overlay's RSS feed to the o.g.o homepage</li>
168<li>create an o.g.o account for you if you don't already have one</li> 155<li>create an o.g.o account for you if you don't already have one</li>
169<li>give you write access to your overlay's Trac wiki and Subversion 156<li>give you write access to your overlay's Trac wiki and Subversion
170repository</li> 157repository</li>
171<li>give write access to all project members who already have an o.g.o 158<li>give write access to all project members who already have an o.g.o
172account</li> 159account</li>
173<li>contact all of the other project members, and sort out their access</li>
174</ul> 160</ul>
175 161
176<p>For an Git request, we will:</p> 162<p>For an Git request, we will:</p>
177<ul> 163<ul>
178<li>create your overlay (git, gitweb, no trac)</li> 164<li>create your overlay (git, gitweb, no trac)</li>
179<li>add your overlay's RSS feed to the o.g.o homepage</li> 165<li>add your overlay's RSS feed to the o.g.o homepage</li>
180<li>create an git.o.g.o account for you if you don't already have one</li> 166<li>create an git.o.g.o account for you if you don't already have one</li>
181<li>give you write access to your overlays Git repository</li> 167<li>give you write access to your overlays Git repository</li>
182<li>give write access to all project members who already have an o.g.o account</li> 168<li>give write access to all project members who already have an o.g.o account</li>
183<li>contact all of the other project members, and sort out their access</li>
184</ul> 169</ul>
185
186 170
187</body> 171</body>
188</section> 172</section>
189 173
190<section> 174<section>
191<title>Developer Overlays</title> 175<title>Developer Overlays</title>
192<body> 176<body>
193 177
194<p>"Developer" overlays are overlays owned by individual Gentoo developers. One 178<p>"Developer" overlays are overlays owned by individual Gentoo developers. One
195example is <uri link="http://overlays.gentoo.org/dev/tcort">tcort's overlay</uri>.</p> 179 example is <uri link="http://overlays.gentoo.org/dev/beandog">beandog's overlay</uri>.</p>
196 180
197<p>If you have an @gentoo.org email address, and you've passed the ebuild quiz, 181<p>If you have an @gentoo.org email address, and you've passed the ebuild quiz,
198then you can have your own developer overlay on o.g.o.</p> 182then you can have your own developer overlay on o.g.o.</p>
199 183
200<p>To request a SVN developer overlay, just pop into #gentoo-overlays on IRC 184<p>To request a SVN developer overlay, just pop into #gentoo-overlays on IRC
201and ask for an overlay to be created for you. Or, if you prefer, drop an email 185and ask for an overlay to be created for you. Or, if you prefer, drop an email
202to overlays@gentoo.org.</p> 186to overlays@gentoo.org.</p>
203 187
204<p>To request a Git developer overlay, just visit the <uri 188<p>To request a Git developer overlay, just visit the <uri
205link="http://git.overlays.gentoo.org">git.overlays</uri> site, and follow the 189link="http://git.overlays.gentoo.org">git.overlays</uri> site, and follow the
206setup instructions, emailing the completed template as directed.</p> 190setup instructions, emailing the completed template as directed.</p>
207 191
208<p>For an SVN request, we will:</p> 192<p>For an SVN request, we will:</p>
209<ul> 193<ul>
210<li>create your overlay (trac site + svn)</li> 194<li>create your overlay (trac site + svn)</li>
217<p>For an Git request, we will:</p> 201<p>For an Git request, we will:</p>
218<ul> 202<ul>
219<li>create your overlay (git, gitweb, no trac)</li> 203<li>create your overlay (git, gitweb, no trac)</li>
220<li>add your overlay's RSS feed to the o.g.o homepage</li> 204<li>add your overlay's RSS feed to the o.g.o homepage</li>
221<li>create an git.o.g.o account for you if you don't already have one</li> 205<li>create an git.o.g.o account for you if you don't already have one</li>
222<li>give you write access to your overlays Git repository</li> 206<li>give you write access to your overlays Git repository</li>
223</ul> 207</ul>
224</body> 208</body>
225</section> 209</section>
226 210
227<section> 211<section>
228<title>A Word About Accounts</title> 212<title>A Word About Accounts</title>
229<body> 213<body>
230<p>Because o.g.o is designed to support a blend of both Gentoo developers and 214<p>Because o.g.o is designed to support a blend of both Gentoo developers and
231Gentoo users, we don't create 'real' system-level accounts on the o.g.o host. 215Gentoo users, we don't create 'real' system-level accounts on the o.g.o host.
232All access is currently through Apache, and is managed by Apache htpasswd and 216</p>
233htgroup files.</p>
234 217
235<impo>You do *not* have SSH access to o.g.o.</impo> 218<impo>You do *not* have SSH access to o.g.o.</impo>
236</body> 219</body>
237</section> 220</section>
238</chapter> 221</chapter>
239 222
240<chapter> 223<chapter>
241<title>Working With Your Overlay</title> 224<title>Working With Your Overlay</title>
242 225
243<section> 226<section>
244<title>Introduction</title> 227<title>Introduction</title>
245<body> 228<body>
246<p>You can access your overlay as soon as it has been created. Project and 229<p>You can access your overlay as soon as it has been created. Project and
247developer overlays have different URLs, so that everyone can tell one from the 230developer overlays have different URLs, so that everyone can tell one from the
248other, but otherwise they are identical in every way.</p> 231other, but otherwise they are identical in every way.</p>
283all commits via HTTPS. If you need to switch between modes, use:</p> 266all commits via HTTPS. If you need to switch between modes, use:</p>
284<pre caption="Switching your developer overlay from HTTP to HTTPS">svn sw --relocate http://overlays.gentoo.org/svn/dev/foo/ https://overlays.gentoo.org/svn/dev/foo/</pre> 267<pre caption="Switching your developer overlay from HTTP to HTTPS">svn sw --relocate http://overlays.gentoo.org/svn/dev/foo/ https://overlays.gentoo.org/svn/dev/foo/</pre>
285 268
286<p>We maintain <uri link="http://overlays.gentoo.org/dev/">a full list of developer overlays hosted on overlays.gentoo.org</uri>.</p> 269<p>We maintain <uri link="http://overlays.gentoo.org/dev/">a full list of developer overlays hosted on overlays.gentoo.org</uri>.</p>
287</body> 270</body>
288</section> 271</section>
289 272
290<section> 273<section>
291<title>Getting Started With Trac</title> 274<title>Getting Started With Trac</title>
292<body> 275<body>
293<p>Your overlay comes with <uri link="http://trac.edgewall.com">Trac</uri>. Trac is a wiki, a subversion repository browser, and a bug tracking system that's 276<p>Your overlay comes with <uri link="http://trac.edgewall.com">Trac</uri>. Trac is a wiki, a subversion repository browser, and a bug tracking system that's
294very popular with open source developers.</p> 277very popular with open source developers.</p>
295 278
296<p>We have disabled the bug tracking system in Trac. Use <uri link="http://bugs.gentoo.org">Gentoo's bugzilla</uri> for bug tracking your overlay.</p> 279<p>We have disabled the bug tracking system in Trac. Use <uri link="http://bugs.gentoo.org">Gentoo's bugzilla</uri> for bug tracking your overlay.</p>
297 280
298<p>Your overlay's RSS feed - the one that is shown on <uri link="http://overlays.gentoo.org">the o.g.o homepage</uri> - comes from Trac's Timeline page.</p> 281<p>Your overlay's RSS feed - the one that is shown on <uri link="http://overlays.gentoo.org">the o.g.o homepage</uri> - comes from Trac's Timeline page or GitWeb's summary.</p>
299
300<p>We have installed several Trac plugins, which we hope will make your wiki even
301more useful to you. If you come across any additional plugins that you'd like
302to see installed, please let us know, and we'll take a look at them.</p>
303
304<ul>
305<li><e>LayOnTrac</e> - lists the packages from the overlay.</li>
306<li><uri link="http://muness.textdriven.com/trac/wiki/tags/Setup">TracTags</uri> - displays a tag cloud</li>
307<li><uri link="http://trac.edgewall.org/wiki/WebAdmin">TracWebAdmin</uri> - provides web-based admin panel for Trac</li>
308</ul>
309
310<p>We have installed several Trac macros, which we hope will make your wiki even more useful to you. If you come across any additional macros that you'd like to see installed, please let us know, and we'll take a look at them.</p>
311
312<ul>
313<li><uri link="http://trac-hacks.org/wiki/AddCommentMacro">AddComment</uri> - allows visitors to add comments to the bottom of your pages</li>
314<li><uri link="http://trac-hacks.org/wiki/FootNoteMacro">FootNote</uri> - adds support for adding footnotes to a page</li>
315<li><uri link="http://trac-hacks.org/wiki/TocMacro">TOC</uri> - adds support for publishing a Table of Contents on a page</li>
316</ul>
317 282
318</body> 283</body>
319</section> 284</section>
320 285
321<section> 286<section>
322<title>Getting Started With Subversion</title> 287<title>Getting Started With Subversion</title>
323<body> 288<body>
324<p>Your overlay comes with <uri link="http://subversion.tigris.org">Subversion</uri>, a modern alternative to CVS. The advantages of Subversion over CVS include real versioning of directories, full changeset support, and it's much easier to do branching if you need to. The main disadvantage of Subversion is that it is slower than CVS, and that a local Subversion checkout requires more disk space.</p> 289<p>The advantages of Subversion over CVS include real versioning of directories, full changeset support, and it's much easier to do branching if you need to. The main disadvantage of Subversion is that it is slower than CVS, and that a local Subversion checkout requires more disk space.</p>
325 290
326<p>If you have never used Subversion before, the <uri link="http://svnbook.red-bean.com/">online book</uri> is an excellent way to learn Subversion. You can buy it in dead-tree format too if you prefer.</p> 291<p>If you have never used Subversion before, the online book is an excellent way to learn Subversion. You can buy it in dead-tree format too if you prefer.</p>
327 292
328<p>Here are some basic commands to get you started.</p> 293<p>Here are some basic commands to get you started.</p>
329<pre caption="Checking out your overlay">svn co https://overlays.gentoo.org/proj/php</pre> 294<pre caption="Checking out your overlay">svn co https://overlays.gentoo.org/proj/php</pre>
330<pre caption="Seeing which files need committing">svn status</pre> 295<pre caption="Seeing which files need committing">svn status</pre>
331<pre caption="Adding files to your overlay">svn add my.ebuild</pre> 296<pre caption="Adding files to your overlay">svn add my.ebuild</pre>
332<pre caption="Committing your changes">svn commit -m 'My changelog entry'</pre> 297<pre caption="Committing your changes">svn commit -m 'My changelog entry'</pre>
333 298
334</body> 299</body>
335</section> 300</section>
336 301
337<section> 302<section>
338<title>Layman</title> 303<title>Layman</title>
339<body> 304<body>
340<p>We are telling users to use layman to download and manage your overlay. 305<p>We are telling users to use layman to download and manage your overlay.
341layman is a utility written by <mail link="wrobel@gentoo.org">Gunnar Wrobel</mail> which makes it very easy for users to work with overlays.</p> 306layman is a utility written by <mail link="wrobel@gentoo.org">Gunnar Wrobel</mail> which makes it very easy for users to work with overlays.</p>
387<pre caption="clone it!">git clone git://git@git.overlays.gentoo.org/(proj or dev)/(name)/</pre> 352<pre caption="clone it!">git clone git://git@git.overlays.gentoo.org/(proj or dev)/(name)/</pre>
388</body> 353</body>
389</section> 354</section>
390</chapter> 355</chapter>
391 356
392<chapter> 357<chapter>
393<title>Giving Access To Your Overlay To Others</title> 358<title>Giving Access To Your Overlay To Others</title>
394 359
395<section> 360<section>
396<title>Introduction</title> 361<title>Introduction</title>
397<body> 362<body>
398<p>One of the key features of o.g.o is that people who do not have write access 363<p>One of the key features of o.g.o is that people who do not have write access
399to the Gentoo Portage package tree can have write access to one or more 364to the Gentoo Portage package tree can have write access to one or more
400overlays. Several Gentoo projects have found that this is a great way to train 365overlays. Several Gentoo projects have found that this is a great way to train
401and evaluate potential Gentoo developers in a safe environment.</p> 366and evaluate potential Gentoo developers in a safe environment.</p>
402
403<p>At the moment, only the Overlays team can update the access control lists for
404overlays.gentoo.org. We will provide a web-based tool for managing the access
405control lists at a later date. But, for now, if you need a change made,
406please drop by #gentoo-overlays on IRC for assistance.</p>
407</body> 367</body>
408</section> 368</section>
409 369
410<section> 370<section>
411<title>Project Overlays: Giving Write Access To Team Members</title> 371<title>Project Overlays: Giving Write Access To Team Members</title>
412<body> 372<body>
413<p>Any developer listed on a team's project page on www.g.o can have write 373<p>Any developer listed on a team's project page on www.g.o can have write
414access to the team's overlay. The project lead can ask on their behalf, or 374access to the team's overlay. The project lead can ask on their behalf, or
415the developer can come and ask for access themselves.</p> 375the developer can come and ask for access themselves.</p>
416 376
417<p>If the developer doesn't have an o.g.o account yet, he/she will need to drop 377<p>If the developer doesn't have an o.g.o account yet, he/she will need to drop
418by #gentoo-overlays so that we can create an account for them.</p> 378by #gentoo-overlays so that we can create an account for them.</p>
419</body> 379</body>
420</section> 380</section>
421 381
539 499
540<section> 500<section>
541<title>o.g.o Administration</title> 501<title>o.g.o Administration</title>
542<body> 502<body>
543 503
544<p>Q: How do I contact the o.g.o admin staff?</p> 504<p>Q: How do I contact the o.g.o admin staff?</p>
545<ul> 505<ul>
546<li>A: You can pop into #gentoo-overlays on IRC, and talk to us there. The 506<li>A: You can pop into #gentoo-overlays on IRC, and talk to us there. The
547 current staff are mostly in European timezones.</li> 507 current staff are mostly in European timezones.</li>
548<li>A: You can send an email to overlays@gentoo.org. Someone will answer you as 508<li>A: You can send an email to overlays@gentoo.org. Someone will answer you as
549 soon as possible.</li> 509 soon as possible.</li>
550</ul> 510</ul>
551 511
552<p>Q: Why can't I edit the access control list directly?</p> 512<p>Q: Why can't I edit the access control list directly?</p>
553<ul> 513<ul>
554<li>A: (SVN) The access control list currently lives in htpasswd / htgroup files used 514<li>A: (SVN) The access control list currently lives in htpasswd format. Only o.g.o admin staff members have ssh access to the o.g.o box.</li>
555 by Apache. Only o.g.o admin staff have ssh access into the o.g.o box.</li>
556<li>A: (Git) The access control list currently lives in the gitosis-admin repository, 515<li>A: (Git) The access control list currently lives in the gitosis-admin repository, which is writable only by the o.g.o staff.</li>
557 which is writable only by the o.g.o staff.</li>
558</ul> 516</ul>
559</body> 517</body>
560</section> 518</section>
561 519
562<section> 520<section>
563<title>Security</title> 521<title>Security</title>
564<body> 522<body>
565<p>Q: Is my overlay available via https?</p> 523<p>Q: Is my overlay available via https?</p>
566<ul> 524<ul>
567<li>A: Yes, it is.</li> 525<li>A: Yes, it is.</li>
568</ul> 526</ul>
569</body> 527</body>
570</section> 528</section>
571 529
572<section> 530<section>

Legend:
Removed from v.1.14  
changed lines
  Added in v.1.15

  ViewVC Help
Powered by ViewVC 1.1.20