1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=us-ascii">
<title> librnd - contribution </title>
<!--AUTO head begin-->
<link rel="icon" href="resources/logo16.png">
<!--AUTO head end-->
</head>
<body>
<!--AUTO navbar begin-->
<table border=0 cellspacing=2 cellpadding=10 bgcolor="#eeeeee" width="100%">
<tr>
<th align=center bgcolor="#ccc0cc"> <a href="index.html"> Main </a>
<th align=center bgcolor="#ccc0cc"> <a href="news.html"> News </a>
<th align=center bgcolor="#ccc0cc"> <a href="developer/">Doc</a> & <a href="faq.html">FAQ</a> & <a href="http://repo.hu/projects/pcb-rnd-aux/pool">pool</a>
<th align=center bgcolor="#ccc0cc"> <a href="support.html"> Support </a>
<th align=center bgcolor="#ccc0cc"> <a href="http://repo.hu/cgi-bin/pcb-rnd-people.cgi?cmd=events">Events</a> & <a href="http://www.repo.hu/cgi-bin/pcb-rnd-people.cgi?cmd=timeline">timeline</a>
<td align=right width="60%"> <font size="+2"><i>librnd</i></font> <img src="resources/logo32.png" alt="[librnd logo]">
</table>
<!--AUTO navbar end-->
<h1> librnd - contribution </h1>
If you are interested to help out, please
<a href="contact.html">contact the lead developer</a>.
<H2> Contributing as a developer </h2>
<p>
The project is lead in an autocratic way by Igor2.
<p>
Developer freedom taken away:
<ul>
<li> the basic concept of librnd is set and won't change
<li> the toolchain is chosen, and won't change; the usual hot topics: svn, scconfig, <a href="developer/c89.html">C</a>.
<li> don't add code that restricts usability for others; add code that increases usability for some; thus prefer to add code in plugins!
</ul>
<p>
Developer freedom promptly granted:
<ul>
<li> svn commit access from day 0
<li> work together in trunk/, not alone in a branch
<li> librnd has a strong plugin support; want to implement a strange/controversial feature? In a plugin, almost anything goes
<li> especially in plugins, work on whatever you want, even if noone else needs that feature
</ul>
<p>
Coding style/indentation: there's an <a href="developer/indent.html">unified style</a>
in core and core plugins. If you work on those parts, try to stick to it. If you
are working on a new plugin, it's still the preferred style but you can use
a different style. However, the rule is that if someone else starts hacking
that part too, he is allowed to convert the code to the unified format; but
unified format can not be converted to anything else. So it's a one way
process which long term grants unified style while not demotivates a plugin
developer by forcing a style on him in the early, "when the bulk of the code
is written" phase.
</body>
</html>
|
