You will find the Gentoo booth at Hall 7.2a, Booth 101a, right next to the entrance. Come and visit us! You will meet many of our developers and users, talk with us, plus get some of the Gentoo merchandise you have always wanted.
Robert Buchholz and Alex Legler contributed the draft for this announcement.
]]>If you'd like to apply to be a mentor, you can do so on the webapp. Please read the mentoring guide before applying.
Interested students can browse Gentoo's project ideas and student applications will be accepted starting March 23rd.
]]>On the ARM side, we are currently releasing stages for the following CHOSTs:
On the SuperH/SH side, we are currently releasing stages for the following processors:
The stages are available under the /releases/arm/autobuilds directory for ARM and /releases/sh/autobuilds for SH at your favorite mirror.
Because building stages for these architectures takes a while, we plan on releasing stages on a monthly or bi-monthly basis. If you would like to talk about Gentoo on those architectures, please join us on #gentoo-embedded @ irc.freenode.net.
We would like to thank QNAP Inc. and Marvell Technology Group for providing us with support and hardware for ARM based chips. However we would like to expand our ARM support to the armv6 and armv7 processors. If you or your company can provide us with some hardware we would greatly appreciate it. Please contact the Gentoo ARM team if you or your company are able to assist us.
We would like to also thank Renesas Technology Corp. who has graciously provided us hardware and support for the SuperH platform.
]]>Where: irc.freenode.net, #gentoo-bugs
When: Saturday, January 3, in a timezone near you
What do you need to bring?
What's a bug? Gentoo's way of tracking change requests. A change request can be anything from "I've found a typo in foo" to "I've built this really useful program called bar but there's no ebuild for it." Bugs have various levels of helpfulness, from identifying the existence of a problem to localizing the problem to providing the patch to fix it.
There are bugs in documentation such as man pages as well as ebuilds and the source code that Gentoo distributes. These bugs are problem reports. Bugs for things Gentoo doesn't do yet but you think should be done are feature requests. Bugday is more about fixing problems than adding features, but you won't be turned away if you want help with a new feature.
Want to know more about Bugday? It's held on the first Saturday of every month. It's an opportunity for everyone to contribute to making Gentoo better, and eventually you might even become a Gentoo developer. See the Bugday project page for more details.
Bugday is about community spirit. Gentoo is a community—there is no "me" and "them", there is only "we," so instead of lobbying for "them" to fix your particular bug, work together to fix it! Bugday is an opportunity to get help to help yourself.
If you've been wanting to get involved but weren't sure how, Bugday is a great way for you to see what goes on in making a distribution and get involved in Gentoo.
Roy Bamford contributed the draft for this announcement.
]]>We're still working to add automated builds for ppc, ppc64 and hppa as well as CD images for architectures lacking them. We built the stage3 tarballs from the latest stable packages. Fresh builds will show up every week, although sometimes we might skip a week if build problems crop up.
Because these builds are automated, they have not been rigorously tested as the old releases. Occasionally, you might run into problems. If that happens, just try a file from a different week.
Please try out these new builds and leave your feedback on the forums. As always, please report any bugs on Bugzilla.
Happy holidays!
Ben de Groot contributed the draft for this announcement.
]]>Consequently, we're canceling the 2008.1 release. The release engineering team has to reconsider its priorities—we overstretched our human resources during the prolonged 2008.0 release process. This caused too much stress for our release engineers and multiple postponements of the release.
You can help! The release engineering team is looking for new volunteers because it perpetually has a severe lack of manpower. We are particularly looking for people with a good grasp of ebuild development and the ability to debug/fix problems that crop up during building and testing of the stage tarballs and ISO images. We will update the staffing needs page with more details.
Ben de Groot contributed the draft for this announcement.
]]>Where: irc.freenode.net, #gentoo-bugs
When: Saturday, September 6, in a timezone near you
What do you need to bring?
What's a bug? Gentoo's way of tracking change requests. A change request can be anything from "I've found a typo in foo" to "I've built this really useful program called bar but there's no ebuild for it." Bugs have various levels of helpfulness, from identifying the existence of a problem to localizing the problem to providing the patch to fix it.
There are bugs in documentation such as man pages as well as ebuilds and the source code that Gentoo distributes. These bugs are problem reports. Bugs for things Gentoo doesn't do yet but you think should be done are feature requests. Bugday is more about fixing problems than adding features, but you won't be turned away if you want help with a new feature.
Want to know more about Bugday? It's held on the first Saturday of every month. It's an opportunity for everyone to contribute to making Gentoo better, and eventually you might even become a Gentoo developer. See the Bugday project page for more details.
Bugday is about community spirit. Gentoo is a community—there is no "me" and "them", there is only "we," so instead of lobbying for "them" to fix your particular bug, work together to fix it! Bugday is an opportunity to get help to help yourself.
If you've been wanting to get involved but weren't sure how, Bugday is a great way for you to see what goes on in making a distribution and get involved in Gentoo.
Roy Bamford contributed the draft for this announcement.
]]>