On Mon, Jul 14, 2003 at 09:55:22AM +0200, Jilles Oldenbeuving wrote:
>...
> My problem is this: i'd like to help, but where do I start? In the issue
> tracker there are some bit-sized tasks but some/most of them are
> integrated deeply with subversions architecture/implementation which
> makes it a hard starting point for me. There is however issue #780
> (http://subversion.tigris.org/issues/long_list.cgi?issuelist=780)
> Which seems like a good starting point, even if the general opinion is
> that this is something for post-1.0.
Issues are usually marked bite-sized because they appear to be easy to
tackle. Generally, they shouldn't require too much in-depth knowledge.
If you want to dig in, then (as Paul said) feel free to choose anything that
looks interesting. Make sure you're an Observer of the project and log in.
You'll then be able to assign an issue to yourself and then mark it as
STARTED (do those steps in that order); that will let others know you're
going to work on a particular issue. If it is reasonably big, then you may
want to have some discussion on the list and to post interim patches.
At the end, follow the patch submission guidelines in HACKING and send the
patch to this list.
If you have a particular interest that isn't covered in the issue list, then
bring it up. I will warn you that new features will generally be
discouraged. It never fails that we get some new feature that seems awfully
handy and great and low-impact on the rest of the system; while all true, it
then proceeds to consume maintenance time (sigh). Rounding out an existing
feature? Fixing edge cases? Making the code more robust and clean? Oh yah...
all that is great.
But again: whatever interests you. We're all volunteers. Well, mostly. :-)
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 16 09:57:53 2003