Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Anyone can contribute... but the code is discussed and reviewed before making it into the kernel or a major distribution.
Typically, many people who develop full time for Linux do get paid to do it. Usually as their employer uses Linux and benefits from their efforts. But, officially, no. You contribute because you want to... not for a return.
Yep, anyone can contribute code. "Linux" properly refers to one specific part of the operating system known as the kernel, but it is often used to refer to entire OS's which use Linux. Anyone can contribute code, but most programs have someone managing them. So, if your patch is really ugly or awful, it can be rejected. This helps things from becoming a mess. Also, many programs try to achieve modularity, so that you can work on a part of a program without seeing the rest of it. Some programs are a mess though.
As far as compensation - not really. Some people are lucky enough to be hired by someone like Red Hat or Canonical who will pay them to develop, but for the most part software is done on a volunteer basis.
Perhaps one reason that Linux and Open Source have not caught on more is that people have a hard time visualizing how it can all possibly work.
You questions apply to all Open Source SW--not just Linux. Each project has a management hierarchy which control what modifications get accepted. I would imagine that the selection process for the leaders varies widely. If, for example, anyone is paying the developers, then that would have a big influence on who the leader is.
The reward? Some, I am sure, are simply altruistic and donate their time while still holding down a "day job". Others are paid by companies who will at least indirectly benefit from their work.
Do some Googling using "open source" and you will find a lot more stuff.
True, the reason why (at least me) dont dare to use linux is because it is confusing.
For windows, i know there's a company developing it, call microsoft. when i wan to buy, i go into a shop, ask the sale person and he/she will advice me on which OS best suite me, easy. If i face a problem, i can just ask friends around me.
For linux, i need to do my own research, and linux got alot of brand, i dont known which best suite me, and worst none of my friend use linux.
That's the reason why i wait till now, when i finally have enough courage to try linux.
Maybe none of your friends use linux now, but make a bunch of friends here and you'll have a bunch of friends who use linux. :-) But seriously, Linux tends to be much better supported than Windows, because a large portion (relatively) of the developers and users are very community oriented. I've never sought help here and not found it.
Just so you don't get scared off of Linux too easily (which is quite easy to have happen), I suggest starting out with a distribution like Mandriva - it has alot of easy-to-use configuration tools all located in a program called "MCC" - Mandriva Control Centre.
I've also heard of Mepis and Ubuntu being very newbie-friendly.
EDIT: To further add to what PatrickNew is saying:
Linux has amazing support (compared to Microsoft, which - last I heard - asks for $40 USD per hour for support). There are some issues that may arise where you may not get an answer, but those issues are very few, and far between.
Yep, anyone can contribute code. "Linux" properly refers to one specific part of the operating system known as the kernel, but it is often used to refer to entire OS's which use Linux. Anyone can contribute code, but most programs have someone managing them. So, if your patch is really ugly or awful, it can be rejected. This helps things from becoming a mess. Also, many programs try to achieve modularity, so that you can work on a part of a program without seeing the rest of it. Some programs are a mess though.
As far as compensation - not really. Some people are lucky enough to be hired by someone like Red Hat or Canonical who will pay them to develop, but for the most part software is done on a volunteer basis.
Can anyone advice me on where i can read more about this linux governing community, for example which community is in charge of accepting/rejecting code. If a developer edit some code, where do he/she send the edited code to?
Can anyone advice me on where i can read more about this linux governing community, for example which community is in charge of accepting/rejecting code. If a developer edit some code, where do he/she send the edited code to?
I think it's pretty important to make the distinction between wanting to code on Linux, and wanting to code on software for Gnu/Linux. If you want to code for the kernel, then try the kernel.org and kernelnewbies.org. If you don't know what a kernel is, you probably want to code for programs that run on linux. The structure here varies from program to program. Just look until you find one you like and email the developers to offer help.
Surf to places like http://www.kerneltrap.org and you will begin to get a sense of what Linux kernel-development is all about.
Really, the idea of Linux isn't "business illegitimate." Some very big players, including the Ultimate Kahuna, IBM, are behind it and for perfectly-sensible reasons.
(Bear in mind that "open source" does not necessarily equate to "all is free.")
As we all know, one viable strategy is the one that companies like Microsoft use: you want to buy an operating system, and you don't want to develop it. You want us to develop it, and to maintain it, and in exchange we "own" it.
That, of course, is "legitimate." It made Bill a very rich man and deservedly so. But it is not the only one...
Another strategy is the one used by Linux. Here, cooperative development of the operating-system kernel (and related software) puts everyone on equal footing in exchange for everyone's professional contribution. No one can make a proprietary, "this is mine" claim on it, so everyone can share the benefits of it.
From this "thus so nobly advanced" vantage-point, all of the contributors can take advantage of "the rising tide that lifts all boats." They make their money in other ways.
And .. it works.
Last edited by sundialsvcs; 01-16-2007 at 09:30 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.