I appreciate the patience to reply, even though I realize now that this is 
the incorrect forum. I spent quite a bit of time reading resources about 
"what" to do when starting off (i.e., contributing to open source) but when 
I set out to do it, I realized I had no idea "how" to do it, even with 
something as simple as finding a project to help with. The suggestions here 
are a great starting off point, and I'm very grateful for you taking the 

On Thursday, September 10, 2015 at 6:31:38 PM UTC-4, Gergely Polonkai wrote:
> Hello,
> although I feel this a bit off-topic, but here are my two cents.
> Just like Philip said, find projects that interest you. Not just from the 
> making side, but from using it. If you like cooking, look for an app that 
> can store your recipes. Maybe you don't hate your previous job and you will 
> find an energy management related thingie.
> Then get involved. Mailing lists, IRC channels, forums, whatever. The 
> GNOME desktop, for example, have a "subproject" called GNOME Love, which 
> collects bugs that are probably easily solvable by newbies, be it 
> documentation, tests or code. Although you want to code, I suggest you 
> should get involved in documentation for a short while, especially if it's 
> a project you know nothing of. You will learn using the app on the way, and 
> maybe you will point out some typos or ambiguities the developers didn't 
> see.
> The next step is to get your hands dirty. Dig deep into the code, try to 
> understand it, how it starts, what happens, why it happens. Try to track 
> down the root cause of bugs in the reports, even if it has been already 
> found, it's a nice excercise. Then try to fix them, or get involved in the 
> fixing. If they try to scare you away with "shut up noob", stay. 
> Persistence is important, asd let's face it, some devs can be real jerks.
> I read this article[1] a while ago, I think it has some good points. There 
> was a much better one I can't dig from my pile of bookmarks right now, but 
> I can send you privately when/if I find it.
> Best,
> Gergely
> [1] 
> http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/
> On 10 Sep 2015 22:11, "Delbert Legg" <del.le...@gmail.com <javascript:>> 
> wrote:
>> Fantastic...thanks so much for the feedback! Not much of an ego here, so 
>> to be honest I'd prefer a group that would beat me up if it meant that I 
>> improved in the process, right?
>> Thanks again!
>> On Thursday, September 10, 2015 at 3:52:57 PM UTC-4, Philip Oakley wrote:
>>> ----- Original Message ----- 
>>> *From:* Delbert Legg 
>>> *To:* Git for human beings 
>>> *Sent:* Thursday, September 10, 2015 12:46 PM
>>> *Subject:* [git-users] New to Git (and programming in general)
>>> Hey all...recently embarking on a career change (from management in the 
>>> energy sector to computer science, focusing on software development) and 
>>> about six weeks away from my degree. I plan on diving back into the course 
>>> material since I feel like much of it was skimmed over or I just didn't get 
>>> what I needed out of the class at the time, but I want to concurrently 
>>> start refining some coding skills and contributing meaningfully while 
>>> building a portfolio. From what I've read (I don't have ready access to a 
>>> group of like minded individuals), open source is a great way for a newbie 
>>> to dive in, but I'm not sure how to become active or really what I can 
>>> contribute at this point, as I'm certainly not an "experienced" programmer 
>>> as of yet. 
>>> Short question to the backstory: How can I get plugged in to the open 
>>> source world and start contributing, even in a minimal way? I'm willing to 
>>> do all the b*tch work necessary even for exposure to good coding practices. 
>>> I'd appreciate any help, and would greatly appreciate working closely and 
>>> exponentially with a singular group (for rapport and progression purposes).
>>> Thanks!
>>> Some personal thoughts...
>>> First, select a few projects you might be interested in - if you aren't 
>>> that interested in some allegedly new and exiting area, then it will become 
>>> "work" (like going back to energy management ;-).
>>> Having found a few potential projects, get on their mailing lists, and 
>>> have a look at their archives. 
>>> Some are said to be quite 'harsh' with a thick skin and lots of self 
>>> confidence / arrogance required. 
>>> Others are 'firm but fair', which can also take time to adjust to.
>>> Also checkout the size of the active team, the occasional team, and the 
>>> lurkers - if it's too small it will eventually fold - it needs to feel like 
>>> it's on a growth track, and isn't just a me too project just like many 
>>> other similar projects.
>>> Perhaps introduce yourself if it feels like the norm, or otherwise wait 
>>> for a topic that you can comment upon, or comment on an area that tripped 
>>> you up while using the code / product / project.
>>> Helping with the documentation is always helpful, though you may need to 
>>> select if the extra info goes in a blog, a wiki, a tutorial or a man page 
>>> (along with arguing the right tone for the contribution).
>>> In summary, make sure it's a project you'd enjoy, and that will feed you 
>>> back.
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Git for human beings" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to git-users+...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to