Difference between pages "News:How We're Keeping You At the Center of the Funtoo Universe" and "Translations:Metro/122/en"

(Difference between pages)
 
(Importing a new version from external source)
 
Line 1: Line 1:
{{News
+
On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that {{c|buildrepo}} has been configured to manage. The first number on each line is a '''failcount''', which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount:
|Summary=Read about recent developments that keep you, our users, at the forefront of our focus as Funtoo moves forward.
+
|News Format=Extended
+
|News Category=General
+
|Author=Drobbins
+
|Publication Status=Published
+
|Publication Date=2015/04/10
+
}}
+
When people ask about what makes Funtoo Linux different, I always mention our user-centric model. This means that the project is focused, as much as possible, on the needs and concerns of our users. Developers and contributors, including myself, are considered users of Funtoo Linux first and foremost, and the voice, ideas and suggestions of a user are given the same weight as a developer.
+
 
+
In this news item, I'm going to describe several recent developments in the Funtoo Linux project that are a reflection of our user-centric model.
+
 
+
=== Bug Squashing ===
+
 
+
Recently, we've been squashing a lot of bugs. By "we", I mean myself ({{User|Drobbins}}), {{User|Oleg}} and {{User|Damex}}, which are basically the day-to-day staff touching the ebuilds and technologies of Funtoo Linux on a regular basis. Although a tiny team, we've made a pretty big dent in our bugs over the past month:
+
 
+
[[File:Bug-squash.png]]
+
 
+
It's my goal to stay on top of our open bugs, and scale our bug squashing capabilities as our project grows, so that we don't get a huge backlog of open bugs. We are moving in the right direction on that front.
+
 
+
=== GitHub Integration ===
+
 
+
We have a number of git repositories mirrored [http://github.com/funtoo on GitHub], and up until recently, issues filed against these repositories on GitHub were often missed. Our GitHub issue integration is now complete and no longer beta, and issues are imported from GitHub every few days. This means that issues on GitHub will be acted upon in a timely manner.
+
 
+
=== Getting You Fixes Faster ===
+
 
+
Funtoo Linux started as a project to get my baby Gentoo Linux to build reliably, and started as a small set of patches. Over time, these patches grew into their own overlay, which was merged with the Gentoo Linux tree by hand. This was a time-consuming and frustrating process and required me or another Funtoo Linux developer to resolve conflicts that would inevitably arise. At one point, I wondered why were were doing so much manual work, and wrote a set of merge tools to automatically combine Funtoo's overlays as well as third-party overlays with the latest Gentoo changes, in a way that prevented conflicts from even occuring.  It was wonderful to have everything update automatically. Up until recently, we regenerated our tree and merged in Gentoo changes every 4 hours, so every 4 hours, {{c|emerge --sync}} would give you new stuff.
+
 
+
'''I've massively overhauled this merge process.''' Now, as soon as something is committed to one of our Funtoo overlays, the portage tree is automatically regenerated. In addition, new Gentoo changes are imported every 4 hours. This means that you will see changes at least every 4 hours. The only exception to this rule is that we now have a special "hand-brake", where we can lock the Gentoo tree to a certain commit, and stop importing new Gentoo changes into Funtoo for a period of time. This is a useful thing to have -- sometimes there is quite a bit of maintenance going on in the Gentoo tree, and it can make sense to pull the hand-brake and wait until the dust has settled. Now we can :)
+
 
+
=== Enhanced QA ===
+
 
+
The enhanced tree update process doesn't end there. Metro has been enhanced with a QA engine, so that prior to any changes being sent to Funtoo Linux users, a number of QA checks are performed. Currently this includes ensuring that any updates to ebuilds in a stage3 merge cleanly for both funtoo-current and funtoo-stable. If the QA test fails, changes are not pushed to you. This is a great example of how we are looking out for our users.
+
 
+
=== Simplified Subarch Selection ===
+
 
+
As described in [http://forums.funtoo.org/topic/447-subarch-profiles/ this forums post], subarch profiles are now part of Funtoo Linux. By user request, I've added an [[Intel64-sandybridge]] subarch, and will be auto-building Intel Sandy Bridge stages soon.
+
 
+
Our selection of custom CPU-optimized builds is quite extensive, and is built using [[Metro]] using some its [[Metro#Advanced_Features]], such as distributed builds. Our collection of stages is managed by Metro's repository management feature. And to make things easier to navigate, Tabs have been added to the [[Subarches]] page for each kind of CPU. This turns what was a long list into something much more manageable.
+
 
+
=== And There's More... ===
+
 
+
Regarding Funtoo's unique [[Funtoo Profiles|profile system]], I am currently in the process of rewriting {{c|eselect profile}} to make it much faster, more powerful, useful, and easy-to-use. To do this, I will be introducing a new tool that will  be used instead of the venerable {{c|eselect}}. This tool should be available within a week.
+
 
+
=== Funtoo Hosting ===
+
 
+
And to top things off, [[Funtoo Hosting]] is back with additional capacity! We now have a server located in Denver, CO, USA, on a 1Gbit uplink. A monthly donation of $15, $30 or $45 a month will get you a SSD-backed virtual Funtoo Linux container with good, crazy, or just plain silly capabilities. Check out our [[Funtoo Hosting]] page and consider getting one! Your funds are used to build out Funtoo infrastructure and also help support me and my staff.
+
 
+
I hope that this has given you some insight into great things that are happening with Funtoo Linux -- and served as examples of how you are important to us.
+
 
+
Best Regards,
+
 
+
 
+
Daniel Robbins<br/>
+
BDFL
+
{{NewsFooter}}
+

Latest revision as of 17:31, July 12, 2015

On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that buildrepo has been configured to manage. The first number on each line is a failcount, which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount: