Hi, Sorry for the late reply. I just got a chance to organize some source code files. I will have plenty of time in the summer (from May). Thank you very much for all suggestions of getting involved in open source development. It is really helpful. I am excited to contribute to Hugin and open source community. I learned quite a lot about open source before, but think taking some good actions from now is good.
This Gsoc project will be a wonderful opportunity for me to start. I have uploaded some source code in Hugin Google Groups: http://groups.google.com/group/hugin-ptx/web/Sample%20source%20code.zip or, the Sample source code.zip file at: http://groups.google.com/group/hugin-ptx/files?upload=1 I also uploaded another zip file, Hugin patch-screenshots.zip, in the same directory. That is my patch work to support the application of Hugin Gsoc project, Enfuse and Enblend Gimp Plugins. I have write a description for those files in the first email. I have shared source code before, and I agree that it is really great to give back. Thank you. Elle. On Thu, Apr 15, 2010 at 9:12 AM, Yuval Levy <goo...@levy.ch> wrote: > I should be packing boxes and the computer should be already in one of > them. > so concise and to the point: > > On April 15, 2010 01:24:13 am Elle Yan wrote: > > I should have asked how to send a patch. > > or read the messages on this mailing list. I think it was Antoine that > asked. > Learning from other peoples questions and answers is an important skill in > Open Source. > > > > Since everyone in the mailing list can see the email > > addresses of the senders, why are they private information? > > everybody can see my phone number in the phone book but it is still private > information and an unsolicited call on it without permission is not a good > thing. > > > > > ... maybe you can explain why I didn't notice you in this community > > > before? > > > > I just started to communicate in the community recently. Before, when I > > reviewed the code base, and found very useful sources, I made use of > them, > > e.g. spline.cpp. > > OpenSource 101: FEEDBACK. Saying "Thank You" when making use of the code. > > > > > can you share some links to code you committed in the repository of the > > > mentioned projects? > > > > I am happy to share some. I did not often commit to the repository of > large > > software though. > > I don't expect you to have commit right to the repository of large > software. > > OpenSource 102: Contribution starts with communication. > > Usually forwarding the changes to a maintainer (somebody with access to the > repository); or publishing a patch somewhere. Subsequently the maintainer > may > or may not accept the patch. If the patch is accepted, it leaves a trace in > a > commit and most maintainers will credit the contributor in the commit log. > For > an example, see [0]. > > > > Usually, I code for the software out of my own interest or > > goal. For example, I code within the code base, to make and change some > > features as I needed. Or, I use their routines or libraries. It is not > the > > formal commit. > > OpenSource 103: it is common for people to code out of their own interest. > It's called "scratch your itches". > > The spirit of Open Source is that when you make changes you publish them > for > the next person in your same situation. Sometimes this spirit is enshrined, > to > different extent, in the more or less permissive licenses. > > > > For smaller software, I did have many commits. It is open source projects > > locally in two universities. They do not currently have commit info on > line > > publicly. > > Do they have the source code published in other form, e.g. a tarball? > > OpenSource 104: Giving back to the general public is key to be a good Open > Source citizen. In the days prior to the internet, these were off line > tools > such as CDs, books, or other media. > > > > However, I have many written source code for projects mentioned. Please > let > > me know if you need code samples. I have many of them for image > processing > > purposes. > > Yes, please. Put them online somewhere and post links here. This > GoogleGroup > has a facility for uploading files, in case you want to use that as the > "online somewhere" I mention above. Learning to use the communication tools > is > the very basic skills that you need to participate successfully in Open > Source > development. > > > > I appreciate your comments and correction. > > We all started from the same point where you are now. I am not sure if you > have enough time to acquire the necessary skills to succeed in a GSoC > project > now. You definitely have enough time to acquire them and become an Open > Source > contributor in general. I recommend you learn about how Open Source works > and > start participating *publicly* on a smaller scale. There will be other > opportunities (maybe GSoC 2011) for you to harness when you're ready. > > To finish on a positive note: in Open Source it is good to re-use what > already > exist and to credit those who have created it. You are already doing this > quite well in your communication. Next you need to add some of your own > ideas > and code to the mix. This may take more time than what you currently have > at > hand but as the example of the many contributors on this list shows, it is > possible. Next time you think of Open Source, think of giving back > something > from you. The gift of giving is what makes Open Source tick. > > Good luck > Yuv > > (disconnecting and putting the PC in a moving box. It will get out of it in > 7-10 days. I might get online with a notebook while moving but don't expect > any further feedback from me as I have other priorities). > > [0] http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=5100 > > -- > You received this message because you are subscribed to the Google Groups > "hugin and other free panoramic software" group. > A list of frequently asked questions is available at: > http://wiki.panotools.org/Hugin_FAQ > To post to this group, send email to hugin-ptx@googlegroups.com > To unsubscribe from this group, send email to > hugin-ptx+unsubscr...@googlegroups.com<hugin-ptx%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/hugin-ptx > > To unsubscribe, reply using "remove me" as the subject. > -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
