Changes

Jump to: navigation, search

Development Guide

6,153 bytes added, 3 months ago
no edit summary
=== Overview ===
Okay, so you want to get involved. How do you do it?  First, it is important you understand the Funtoo way. == The BDFL == Funtoo Linux follows a BDFL model. Think Linux kernel. There is a benevolent dictator for life (me, Daniel Robbins) that oversees all things. Note that this is not the same as *doing* all things nor does it mean *deciding all things*. We are a user-focused distribution so *your*needs are important.  The jobs of a BDFL are many.  One job I have is to define a process for development for Funtoo. This process involves sending pull requests via https://code.funtoo.org.It is important to understand this process, and also understand how https://bugs.funtoo.org is a part of it. As BDFL I am always tellingpeople to file a bug. I repeat it over and over again. I sometimes see people saying "that Daniel really loves his bugs." Well, there isa reason why I love bugs, or at least bug reports. == The Importance of Bug Reports... and Bad Kung-Fu == From the perspective of making Funtoo better, the following statements are true: **Reporting bugs is much more beneficial than reporting problems on forums.** **Reporting bugs is much more beneficial chatting with Funtoo users online about your technical issue.** **If you are experiencing an ongoing problem with Funtoo and have not reported a bug, you have not done enough communicate your problem.** I love bug reports because the goal of Funtoo is to create and maintain reliable software, even perfect software (why not?) If you have comefrom Gentoo, you may be used to figuring out what {{c|USE}} variables to set by hand, and then dealing with any problems from your choices,and getting your system working. Along the way, maybe you encountered some weird issues but found ways around them either by your owntroubleshooting or on resources like forums or similar. Maybe you filed a bug with Gentoo but it was not fixed in a reasonable time frameso you just learned to fix your own problems. I am not saying any of this to disparage Gentoo -- it is just that I believe this is a common experience and we have people coming from Gentoo all the time who tend to have these habits and perspectives. You are a Gentoofrontiersman, and have learned to fend for yourself. This "deal with the problems on your own" approachcan be rewarding, and you can learn things from it, but I will argue that if you come from this way of doing things that you may have *learned some bad Kung-Fu*. In Funtoo, you are part of a community. You are expected to "join in" with this community, and our core way of joining in is by filing bug reports. In Funtoo, if you leave out this part, then you are not fully participating. I'll explain this in more detail below. == Funtoo Should Work. Because We All Benefit. == I want Funtoo to work, because I use it. I want it to work for everyone. If it doesn't work for you, a bug report lets Funtoo "see"that there is a problem. Due to the community nature of Funtoo, we rely on your eyes to tell us what isn't working, so we can fix it.We want it to work for you, and for us. We also understand "the law of the jungle" -- that if it works better for *you*, it will workbetter for *us*, too. Your eyes and voice are important for the community to work. We also rely on your requests to know what packages to add, so we can add them -- though we really like to have a clear explanationfor why the package you want is important to *you*. Funtoo is a community of people, and we maintain a technology that works for us. We are motivated by the needs of our users, and when we fully and deeply understandyour need, not just your "ask", we take it seriously and try to support you if possible. == Help Me To Help You == So when you don't report a bug, you are not letting others help you. And really, it hurts others, because eventually we will run into thisbug too, and we will be frustrated by it, because we want software to just work, too. The earlier a bug is reported, the sooner it will be fixed, and the fewer people will befrustrated by it. So that's why it's so very important to file bugs. When you file a bug at https://bugs.funtoo.org, you are trulyparticipating in the Funtoo community and helping the community to have visibility of these issues so they can be fixed quickly. Maybe you came from a project where developers really hated getting duplicate bug reports. I love duplicate bug reports. File all the duplicate bugsyou want. I will gladly deal with duplicate bugs if it helps us make sure that we have all bugs reported. Dealing with duplicate bugreports is a piece of cake, but trying to fix a problem you don't even know exists is impossible. So if you have a problem, *make sure* there is a bug for it. If you don't see a bug for your problem, *create a new bug.* == Funtoo Philosophy on Bugs == The Funtoo philosophy on bugs is very simple: #. All problems should be reported to the bug tracker, so we can see problems.#. If it is broken, it should be fixed correctly, so we can make software more perfect.#. If fixing the problem correctly isn't feasible, we should find an acceptable and elegant workaround, so the software is usable.#. If neither of these options are possible, a manual workaround should be documented, to prevent frustration.#. Our documentation and software should be simple, so we continually try to reduce or eliminate any required manual workarounds. == Bug-Tracker Centered Development == With all of the above in mind, it should now be clear why the bug tracker at https://bugs.funtoo.org is central to our work. To use the bug tracker, log in using your Funtoo account you created at https://auth.funtoo.org, and specify your username *in lowercase.* File a bug. It will be in the "Intake" state. When it is ready to be worked on, it will be moved to the "Ready to Fix" state.When it is in "Ready to Fix" state, then pull requests (PR) can be submitted via https://code.funtoo.org. When you file a bug, have confidence that we want the software to work for you, and will try our best to support you. Andhave confidence that you are fully participating in the Funtoo community. == The Nitty Gritty ==  Well, here's how we want you to start:
* First, make sure you have the ''current release of Funtoo Linux installed'' on at least one system.
Bureaucrats, Administrators, wiki-admins, wiki-staff
6,564
edits

Navigation menu