[Adium-devl] Beginner looking to make a contribution

[Ankur Oberoi]

Okay I see that its important to update pretty often, thanks for the
explanations and clarifications.
Is there any visual "map" of the branches and such of the development of
Adium?
I think its important for new people like me to see such a map to understand
where Adium is going. For example, I had no idea there was a voice and video
group working on a that branch for Adium to have that functionality. If i
wanted to implement a new feature, this map may serve the purpose of
informing me that such a feature is already under development or not.
Maybe, these situations are caught by the bug tracking system in tickets,
but if so, I wouldn't know how to utilize the bug tracking system to see all
the branches and what features they are trying to include in each one.

On 10/30/07, Peter Hosey <boredzo at gmail.com> wrote:
>
> On Oct 29, 2007, at 20:51:45, Ankur Oberoi wrote:
> > How often should i be doing an update through subversion?
>
> For general usage of trunk, you can update however often you want.
> You may find it a good idea to subscribe to our Adium-svn list[1],
> and read the commit messages, and update whenever there's a new
> feature or a bug fix that you want.
>
> Speaking of the Adium-svn list, it's also cool for you to read the
> code differences and submit a patch if you spot a newly-introduced
> (or long-standing) bug. It's not a requirement, though.
>
> There are three circumstances in which you should always update first:
>
> 1. You've found a bug.
>
> Find reliable steps to reproduce, then update and try them again.
> This saves you filing a ticket and us closing it for a bug that we
> already fixed.
>
> 2. You're about to start writing a patch.
>
> Keep an always-clean checkout around. Before you start writing a
> patch, update that checkout. Then copy it (cp -R clean-checkout my-
> patch-wc), and begin working in the copy (the *working copy* as the
> phrase was originally intended).
>
> 3. You're finished writing the patch.
>
> When you believe you're done, cd into your working copy and update
> again. If anything has changed, build and test again. Wash, rinse,
> and repeat, until (1) your code builds and runs and works and (2)
> there are no further changes to retrieve.
>
> > What's a good rule of thumb? … 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?
>
> If you don't start your work on a fully-up-to-date copy of Adium,
> you're very likely to have conflicts in your patch when we go to
> apply it. If you're lucky, we'll still be able to use the patch;
> otherwise, we may reject it outright and ask you to regenerate the
> diff against the current revision of Adium.
>
> [1]: http://adiumx.com/mailman/listinfo/adium-svn_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/97f2c0be/attachment-0001.html>