


You need to be fluent in shell scripting, you need to know bash.ratch3t.x wrote:i have always wanted to become a developer. where do i start? what languages should i learn? any information telling me what to learn helps, thanks
I think regular expressions might be handy, but I think that ties into sed/awk.antarus wrote:You need to be fluent in shell scripting, you need to know bash.ratch3t.x wrote:i have always wanted to become a developer. where do i start? what languages should i learn? any information telling me what to learn helps, thanks
Bonus if you know autotools, and any other build systems.
You need to be familiar (able to read) almost any programming language, unless you are going to focus on a particular class of package (say java packages or something).
Did I mention you need to know bash?*
Also, devmanual.gentoo.org is a good reference for the layperson.
awk,sed,cut,tr,perl,sort,grep,wc, and more, you also need to know (minimally what each does and how to use it and when)
*(Hint, you need to know a LOT about bash)

Sed + bash and you can do an awfully lot...vibrokatana wrote:sed spoils you to hell and back, I vote it for the most useful program ever, lol.
Seriously what cant you do with sed? With a little thought and some sed you can do practically anything.
You know this question comes up a lot. The answer hasn't changed much
over the years, and you may not like it, but it's the honest to goodness
best way to start helping: just start helping. There are numerous
avenues to do so, and in no particular order they are:
1. gentoo-user mailing list
2. the gentoo forums
3. join an irc channel or two (#gentoo has a steady stream of traffic of
people who need help)
4. figure out what you're good at and/or what you want to learn and hop
on over to bugzilla and find bugs in those areas.
The caveat to the bugzilla one is this: most people who want to help go
straight to maintainer-wanted bugs or try and create ebuilds for new
packages. To be perfectly honest, those areas are not where gentoo
needs help. We need help to maintain stuff already in the tree, so start
at maintainer-needed or drill into some specific teams (gnome, pam,
kerberos, kde, bsd, samba, mail, web-apps, there's a list of herds
somewhere).
Spread the word!

Show up at a Bugday. Bugday is one of the best ways to be seen by developers. Hang out in the IRC channel the first Saturday in the month and learn from others how to fix bugs. If you have any questions about it feel free to contact me on IRC (eroyf).ratch3t.x wrote:i have always wanted to become a developer. where do i start? what languages should i learn? any information telling me what to learn helps, thanks

root|vaio runs it, and wrote a large part of the wiki, as did greycat.edit: excellent FAQ on BASH from greycat (who seems to run #bash)
Seriously you can't count with sed.Seriously what cant you do with sed? With a little thought and some sed you can do practically anything.