Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

Devsummit 2010

ā€¢
ā€¢
Dru Lavigne
Dru Lavigne

The document discusses ways that the FreeBSD and PC-BSD projects can better coordinate their efforts to address bugs and issues found by desktop users. It suggests improving communication between various teams involved in ports management, window managers, graphics drivers, and hardware support. The goal is to streamline feedback loops and prioritize fixes for usability problems reported by non-technical desktop users of PC-BSD.

1 of 6
Download to read offline
Cooperation with the PC-BSD Project Dru Lavigne dru@freebsd.org EuroBSDCon DevSummit, 2010
PC-BSD Perspective ā—desktop users tend to find different bugs than system administrators; bugs tend to be with ports and hardware drivers ā—desktop users tend to find bugs earlier as they install and use new releases right away, rather than waiting for a branch to stabilize (dot 0 releases) ā—would like to increase awareness and streamline processes and feedback loops so users' needs are addressed in a timely fashion
How to Better Coordinate? Ports management team ā—heads up on upcoming major changes (e.g. perl), especially those scheduled near or shortly after a release date ā—coordinate requests for software not currently ported
How to Better Coordinate? Window managers porters teams: 9.0 will support multiple window managers, ā— meaning users will find lots of usability bugs ā—template for submitting a useful bug/usability report to freebsd-ports-bugs@ ? ā—porters subscribe to our wm bug testing forums? http://forums.pcbsd.org/forumdisplay.php?f=64
How to Better Coordinate? Xorg porters team, general hardware drivers, and Foundation: ā—desktop users can't always get the most out of their graphics hardware ā—fund work to address missing kernel graphics support? coordinate hardware driver requests? ā—
Conclusion Some thoughts for discussion: ā—how do we efficiently coordinate the submission of and responses to user feedback? ā—are both projects currently aware of each projects' current procedures and resources? ā—how can we work more closely together to improve and promote FreeBSD?

More Related Content

Devsummit 2010

  • 1. Cooperation with the PC-BSD Project Dru Lavigne dru@freebsd.org EuroBSDCon DevSummit, 2010
  • 2. PC-BSD Perspective ā—desktop users tend to find different bugs than system administrators; bugs tend to be with ports and hardware drivers ā—desktop users tend to find bugs earlier as they install and use new releases right away, rather than waiting for a branch to stabilize (dot 0 releases) ā—would like to increase awareness and streamline processes and feedback loops so users' needs are addressed in a timely fashion
  • 3. How to Better Coordinate? Ports management team ā—heads up on upcoming major changes (e.g. perl), especially those scheduled near or shortly after a release date ā—coordinate requests for software not currently ported
  • 4. How to Better Coordinate? Window managers porters teams: 9.0 will support multiple window managers, ā— meaning users will find lots of usability bugs ā—template for submitting a useful bug/usability report to freebsd-ports-bugs@ ? ā—porters subscribe to our wm bug testing forums? http://forums.pcbsd.org/forumdisplay.php?f=64
  • 5. How to Better Coordinate? Xorg porters team, general hardware drivers, and Foundation: ā—desktop users can't always get the most out of their graphics hardware ā—fund work to address missing kernel graphics support? coordinate hardware driver requests? ā—
  • 6. Conclusion Some thoughts for discussion: ā—how do we efficiently coordinate the submission of and responses to user feedback? ā—are both projects currently aware of each projects' current procedures and resources? ā—how can we work more closely together to improve and promote FreeBSD?