Debian Codegraph @

logback-site/src/site/pages/volunteer.html

raw
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3
4 <html xmlns="http://www.w3.org/1999/xhtml">
5 <head>
6 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
7 <title>Volunteers</title>
8 <link rel="stylesheet" type="text/css" href="css/common.css" />
9 <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" />
10 <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" />
11 </head>
12 <body>
13 <script type="text/javascript">prefix='';</script>
14
15 <script src="templates/header.js" type="text/javascript"></script>
16 <div id="left">
17 <noscript>Please turn on Javascript to view this menu</noscript>
18 <script src="templates/left.js" type="text/javascript"></script>
19 </div>
20 <div id="right">
21 <script src="templates/right.js" type="text/javascript"></script>
22 </div>
23
24
25 <div id="content">
26
27 <h2>Call for volunteers</h2>
28
29 <p>We are looking for volunteers in the following areas.</p>
30
31 <ol>
32 <li><span class="label">top priority</span> <b>logback in 10 minutes</b>
33
34 <p>We are looking for a volunteer, preferably a native English
35 speaker, to write a short document describing logback for
36 beginners, entitled say "logback in 10 minutes". This document
37 is likely to be the most widely read document of the
38 project. Writing such a document is an excellent opportunity to
39 learn logback. Obviously, there would be plenty of editorial
40 help and guidance coming from the logback developers.
41 </p>
42 </li>
43
44 <li><span class="label">high priority</span> <b>Proof reading the documentation</b>
45 <p>We are always looking for volunteers to proof-read the
46 documentation. Suggestions as to the design and look-and-feel of
47 the site are also welcome.</p>
48 </li>
49
50 <li><span class="label">medium priority</span> <b>Decoder:
51 parse log files and transform them into logging events</b>
52
53 <p>This effort has been started under the <a
54 href="https://github.com/qos-ch/logback-decoder">logback-decoder</a>
55 project but has stalled. This problem is technically
56 interesting, has a well-defined scope and mostly independent of
57 the logback framework.
58 </p>
59
60 </li>
61
62 <li><span class="label">medium priority</span> <b>Maintain the
63 groovy configurator</b>
64
65 <p>The Groovy configurator, aka Gaffer, although pretty cool, is
66 not getting the attention it deserves. The amount of code
67 involved, although not completely trivial, is far from
68 insurmountable. We are looking for a volunteer to take over
69 Gaffer.
70 </p>
71 </li>
72
73 <li><b>Improve OSGi support</b>
74
75 <p>We are looking for an OSGi expert to review our current
76 practices and improve OSGi support in logback. </p></li>
77
78 <li><b>Fixing bugs</b>
79
80 <p>We are looking for volunteers for fixing logback
81 bugs. Volunteering to solve bugs is a good way to learn about
82 any project.
83 </p>
84
85 <p>For those looking for highly technical challenges with
86 limited scope, have a look at various build failures observable
87 on <a href="http://logback.qos.ch/jenkins/">our Jenkins
88 instance</a>.
89 </p>
90
91 <p>Our build is quite stable but failures occur from time to
92 time on our Jenkins instance hosted on a relatively old
93 computer.</p>
94
95 <ul>
96
97 <li><a
98 href="http://logback.qos.ch/jenkins/job/logback/149/">build
99 #149</a> with test failure in <a
100 href="http://logback.qos.ch/jenkins/job/logback/ch.qos.logback$logback-classic/149/testReport/junit/ch.qos.logback.classic.joran/JoranConfiguratorTest/levelChangePropagator1/">JoranConfiguratorTest.levelChangePropagator1</a>
101 probable cause: parallel execution, j.u.l. shared-state
102 overridden by levelChangePropagator0 while levelChangePropagator1 is running
103 </li>
104
105 <li><a
106 href="http://logback.qos.ch/jenkins/job/logback/298/">build
107 #298</a> with test failure in <a
108 href="http://logback.qos.ch/jenkins/job/logback/ch.qos.logback$logback-core/298/testReport/junit/ch.qos.logback.core/AsyncAppenderBaseTest/workerShouldStopEvenIfInterruptExceptionConsumedWithinSubappender/">AsyncAppenderBaseTest</a>
109 probable cause: race condition
110 </li>
111
112
113 <li><a
114 href="http://logback.qos.ch/jenkins/job/logback/91/">build
115 #91</a> with test failure in <a
116 href="http://logback.qos.ch/jenkins/job/logback/ch.qos.logback$logback-classic/91/testReport/junit/ch.qos.logback.classic.net/SMTPAppender_GreenTest/testMultipleTo/">SMTPAppender_GreenTest</a>
117 probable cause: race condition, GreenMail server not running
118 at time of message transmission</li>
119
120
121 </ul>
122
123 <p>These build failures are quite hard to reproduce. If you
124 intend to work on these problems, you will probably first need
125 to make changes to logback code so that the problem becomes
126 easily reproducible. One the problem is identified and
127 reproducible, solving it should be much easier.
128 </p>
129
130 <h3>Setting up the project</h3>
131
132 <p>If you wish to contribute to the project or just hack for fun,
133 you will probably want to import logback as a project into your
134 favorite IDE. See the instructions for <a
135 href="setup.html#ide">building logback in Eclipse or IntelliJ
136 IDEA</a> for details.</p>
137
138 <script src="templates/footer.js" type="text/javascript"></script>
139 </div>
140 </body>
141 </html>