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

[satyaakam goswami]

>
> 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/164fa6e3/attachment.html>