Gold sponsors

Intel logo

IBM Corporation

Cisco

JBoss

Sonatype

SAP

Oracle

Silver sponsors

Blackberry

agitar

bsi logo

Microsoft

Google

Instantiations

Soyatec

Xored

amazon

Actuate

Bronze sponsors

Purple Scout

froglogic

Paremus

objectivity

Sopera

Genuitec

itemis

excelsior

Activity sponsor

eclipsesource

Media sponsors

Methods & Tools

SD Times logo

TSSJS

Be a Sponsor

The good, the bad and the ugly: Eclipse Bugs and how to increase your chance getting heard

Martin Oberhuber (Wind River ), Pawel Piech (Wind River )

Making Community · Standard (25 mins)
Thursday, 14:30, 25 minutes | Grand Ballroom

Tags: Committer And Contributor , Communication Docs/Education , pc_top_5
7
·
8
·
9
·
10
·
11
·
12
·
13
·
14
·
15
·
16
·
17
·
18

Writing an Eclipse bug or feature request is simple. Writing it such that committers can use it is a bit harder. But committers can even appreciate bugs with just a little care from the start! Learn what it takes to keep committers happy and interested about your requests, revive items that have been forgotten, and how to negotiate about items that you find important but committers decline: and most of all, how to save time doing all that.

Martin is the chair of the Eclipse Architecture Council, member on the Eclipse and DSDP PMC, Platform core and e4 committer, Target Management project lead and a certified ScrumMaster. Driven by his desire for constant improvement, he is involved in many areas around Open Source and Eclipse. Martin holds a degree in Telematics from the University of Technology Graz, and has been working for Wind River in Salzburg, Austria since 1998.

Pawel is a committer on the CDT and Platform Debug projects.  Currently working for Wind River Systems in Alameda, CA since 2000. Graduated from Boston University with a BSCE degree. 

Slides