This site is an archive; learn more about 8 years of OpenHatch.

[OH-Dev] Fwd: question in regard to working on open hatch projects

Karen West karenwest15 at gmail.com
Thu Jan 3 22:13:34 UTC 2013


Since I have not yet heard a reply from Satya, I thought I would forward to
the mailing
list, to see if that helps.

Thanks,
Karen West

---------- Forwarded message ----------
From: Karen West <karenwest15 at gmail.com>
Date: Thu, Jan 3, 2013 at 2:22 PM
Subject: Re: [OH-Dev] question in regard to working on open hatch projects
To: satyaakam goswami <satyaakam at gmail.com>
Cc: Karen West <KarenWest15 at gmail.com>


Thank you for the information on how the open hatch projects work Satya.  I
am job searching as I mentioned, so this is not a project on which I would
be working outside my current job, but rather to keep old skills fresh and
perhaps learn some new ones while job searching.

I was wondering if you recommended that I inquire on the mailing list to
whom would recommend a specific open hatch project based on your current
skill set, or if you might know the answer.  Currently, I know C and Python
best, and my C++ is a bit rusty.  Also, much of my experience was in
embedded systems, but I'm not exclusive to that market, and have done some
projects in other areas in high tech as well, but never for pay!

Also, if a job ever came along, what are the commitments to these open
hatch projects?  I've met people who work on them outside their main job,
but I've never done that.  I also am currently signed up for some of those
online courses while job searching, but someone mentioned that I should
check out the open hatch projects to see what those are like.

Thank you for your help.
Karen West


On Thu, Jan 3, 2013 at 6:50 AM, satyaakam goswami <satyaakam at gmail.com>wrote:

> So my question is as follows: In my role where I took bugs from a
>> database and tried to fix one of them, we had access
>> to all the firmware, and if it was associated with a specific
>> application, the app code as well, along with documentation.
>> We built the entire piece of code and tried to reproduce the problem
>> (also on a specific embedded device), suggest a solution, and even
>> test our recommendation, before putting that in the bug database.  It
>> was unclear to me how this would work on open hatch, since it seemed
>> to just list problems within a bug database, without any further
>> information.
>>
>
> All the bugs you see listed are coming from projects , so if you click on
> bug link then you would find a link more about this project , click on that
> link to know
> from where the bug is coming , now this is the source of the buglist, you
> can either subscribe to the developer list of that particular project and
> start with setting up development environment
> then start replicating the bug and then try fixing it by submitting a
> patch . Almost all projects on there development project page/wiki  will
> also have a link to the IRC channel where developers of
> that project hang out , you can start communicating with the developers
> when you get stuck .
>
> these are the pretty much starting  steps in trying to contributing for
> any project in Open  source world . you can also try interacting with folks
> on #openhatch on IRC too get guidance when in doubt .
>
> welcome to the wonderful world where there are no bosses and people to
> tell you what needs to be done , yes its is a bit strange for people who
> are used to corporate hierarchy but soon they realize the power of the
> system.
>
> may the source be with you .
>
>
> -Satya
> fossevents.in
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/devel/attachments/20130103/a90d7834/attachment.html>


More information about the Devel mailing list