Gentoo Archives: gentoo-commits

From: "Robin H. Johnson (robbat2)" <robbat2@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/news: 20081227-bugday.xml
Date: Wed, 31 Dec 2008 23:08:32
Message-Id: E1LIAAv-00052y-9a@stork.gentoo.org
1 robbat2 08/12/31 23:08:29
2
3 Added: 20081227-bugday.xml
4 Log:
5 Add Bugday January 2009 announcement. dertobi123 couldn't find somebody from PR to commit it.
6
7 Revision Changes Path
8 1.1 xml/htdocs/news/20081227-bugday.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/news/20081227-bugday.xml?rev=1.1&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/news/20081227-bugday.xml?rev=1.1&content-type=text/plain
12
13 Index: 20081227-bugday.xml
14 ===================================================================
15 <?xml version="1.0" encoding="UTF-8"?>
16 <!DOCTYPE news SYSTEM "/dtd/guide.dtd">
17 <news gentoo="yes" category="gentoo">
18
19 <!-- Enter your name here -->
20 <poster>dertobi123</poster>
21
22 <!-- Date to be displayed - usually the GWN release date -->
23 <date>2008-12-27</date>
24
25 <!-- Title of the news item - don't forget to change the date -->
26 <title>Get involved: Bugday coming up Saturday</title>
27
28 <body>
29
30 <!-- Alter to your own likings -->
31 <p>
32 <b>What:</b> Gentoo contributors get together to help each other fix bugs
33 </p>
34
35 <p>
36 <b>Where:</b> irc.freenode.net, #gentoo-bugs
37 </p>
38
39 <p>
40 <b>When:</b> Saturday, January 3, in a timezone near you
41 </p>
42
43 <p>
44 <b>What do you need to bring?</b>
45 </p>
46
47 <ul>
48 <li>A Gentoo system, an Internet connection and an IRC client</li>
49 <li>Your bug. If you don't have one, we will find you one to suit your area
50 of interest and your skills</li>
51 <li>Your favorite editor</li>
52 <li>A way to test that your bug is fixed (asking people counts!)</li>
53 <li>You <b>don't</b> need to know C, C++, or bash</li>
54 </ul>
55
56 <p>
57 <b>What's a bug?</b> Gentoo's way of tracking change requests. A change
58 request can be anything from "I've found a typo in foo" to "I've built this
59 really useful program called bar but there's no ebuild for it." Bugs have
60 various levels of helpfulness, from identifying the existence of a problem
61 to localizing the problem to providing the patch to fix it.
62 </p>
63
64 <p>
65 There are bugs in documentation such as man pages as well as ebuilds and the
66 source code that Gentoo distributes. These bugs are problem reports. Bugs
67 for things Gentoo doesn't do yet but you think should be done are feature
68 requests. <b>Bugday is more about fixing problems than adding features</b>,
69 but you won't be turned away if you want help with a new feature.
70 </p>
71
72 <p>
73 <b>Want to know more about Bugday?</b> It's held on the first Saturday of
74 every month. It's an opportunity for everyone to contribute to making Gentoo
75 better, and eventually you might even become a Gentoo developer. See the
76 <uri link="http://www.gentoo.org/proj/en/bugday/index.xml">Bugday project
77 page</uri> for more details.
78 </p>
79
80 <p>
81 <b>Bugday is about community spirit</b>. Gentoo is a community&mdash;there
82 is no "me" and "them", there is only "we," so instead of lobbying for "them"
83 to fix your particular bug, work together to fix it! Bugday is an
84 opportunity to get help to help yourself.
85 </p>
86
87 <p>
88 If you've been wanting to get involved but weren't sure how, Bugday is a
89 great way for you to see what goes on in making a distribution and get
90 involved in Gentoo.
91 </p>
92
93 <p>
94 <uri link="http://forums.gentoo.org/viewtopic-t-721883.html">Discuss
95 this!</uri>
96 </p>
97
98 <p>
99 <e>Roy Bamford contributed the draft for this announcement.</e>
100 </p>
101
102 </body>
103
104 </news>