[Adium-devl] Beginner looking to make a contribution

Tue Oct 30 04:22:07 UTC 2007

On Oct 30, 2007, at 12:03 AM, Jordan S. wrote:

> That's a good question, I have only submit two very tiny patches so  
> far, which meant I didn't do any updates between start and  
> completion of the patch. I think svn diff only does a diff of data  
> that you have changed compared to any svn updated data (meaning you  
> could update in the middle of working on a patch, but this could  
> create a problem if you were working on the exact same code that  
> was part of the update).
>
> I think it's probably best to wait until someone who has submit  
> more and/or larger patches answers this one.
>
> Jordan


	Updating your working copy is generally advisable before editing a  
file, to make sure the diff that results from your edits applies  
cleanly against what's stored in the server. There are of course  
exceptions to this "rule" in more complex scenarios than the standard  
one, but Im sure those are not something someone is likely to run  
into if he/she is just getting started with open source and/or svn.

	Also, 'svn diff' by default shows you the differences between your  
working copy (which you are presumably editing) and a "pristine copy"  
of the file you edited that's hidden in a dot folder ($pwd/.svn/).  
Therefore, if you don't 'svn up' first before editing then you wont  
see the full changes against the most recent version of the file  
stored in the server; this may create problems when sending a diff  
for somebody else to apply and commit, in the case the submitter  
doesn't have write access to the repository (the usual case for a  
beginner), as that diff may not be "complete".

	My 2 cents,...


-jmpp


>
>
> On 10/30/07, Ankur Oberoi <aoberoi at gmail.com> wrote:
> Thanks Jordan.
>
>
> Since I am new to open source software dev, I have a general  
> question. How often should i be doing an update through subversion?  
> What's a good rule of thumb? Should I do an update before i start  
> working each time so that the patching is easiest later on? Should  
> I wait until later on, when I am done with my fix, to update so  
> that all my changes can be integrated all at once, or will this  
> likely be difficult?
>
>
> I appreciate the patience you guys have for the "new kid"
>
> On 10/29/07, Jordan S. < jas8522 at gmail.com> wrote:
> Ankur,
>
>
> These aren't necessarily starter bugs, but you can always take a  
> look at the upcoming milestones (found in the Roadmap) and take a  
> peek at the open tickets. You can pick through them and give some  
> fixes a shot if you find it interesting or possibly easier for you.  
> The 1.1.4 and 1.2 milestones will hopefully be completed in the  
> next few months, so those would be nice to have completed first,  
> but they may not be simple for a first bug fix. There's also the  
> "Good idea for later" milestone that is filled with some small and  
> some large enhancements as well as a few minor bugs that could be  
> fixed. In there you'll find old and new stuff so you can be sure  
> it's not all outdated.
>
>
> Those milestones are a straightforward way of finding newer bugs  
> and enhancements to work on, but they might not be the easiest, so  
> feel free to pick through them and submit patches if you find a  
> solution, otherwise you can just skip over it and try another!
>
>
> Jordan
>
> On 10/30/07, Ankur Oberoi < aoberoi at gmail.com > wrote:
> Thanks for all the responses!
>
>
> I've taken a look at the starter bugs, thanks for that link. It  
> seems like those tickets havent been cleaned up in a while though.  
> Most of them have either "needs dev review" in the status or have  
> been dismissed by people saying that a certain release fixed the  
> problem. I don't really know enough about this project to be  
> cleaning up the tickets or anything, but if any of you know of  
> additional tickets that might be for starters like me, could you  
> add them to that list?
>
>
> The coding link looks really helpful, and I've read that page  
> before, but thanks for the link!
>
>
> I'm not very experienced with Obj-C and Cocoa but I've already  
> begun learning them and am well on my way to catch up with the  
> syntax and features that are new to me. I think it won't be too  
> hard to pick up because i have a strong background in OOP.
>
>
> Thanks again for all your help.
>
> On 10/26/07, Peter Hosey < boredzo at gmail.com> wrote:
> On Oct 26, 2007, at 02:54:06, Ankur Oberoi wrote:
> > I am new to development for OSS and was hoping to get a chance to
> > get started with Adium. I wanted some help from the rest of you to
> > find a good starting point.
>
> Good to hear!
>
> The place where anyone who wants to work on Adium should start is  
> here:
>
>          http://adiumx.com/faq/ContributingToAdium
>
> The entire Coding section is of interest to you.
>
> Let us know if you need any more info.
>
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
>
>
>
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
>
>
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
>
>
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
>
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20071030/a5dd872d/attachment-0001.html>