Hi,

Thank you for your interest in GNU Wget. You can start with the Wget Wiki
at: http://wget.addictivecode.org/
This will give you a basic understanding of the application and will link
you to the source repository and bug tracker too.

GNU Wget uses Git. You should have a fairly working knowledge of Git and
version control systems. Clone the repository first and look at the
bug-tracker to find some bugs that you think you can help fix. Once you're
done with that, use `git format-patch` to generate a patch file and send it
over to this group. Remember to add an entry to the ChangeLog file before
creating the patch.

You could start off with simple bugs like: 40746 or 40656. A patch is
tentatively supplied with the former while the latter requires creating a
test case for replicating the results first.

There is also simple bug in the output of Wget that you could attempt to
resolve. When invoked with -O and an extremely long URL, Wget's output is
faulty. This has been documented in Bug #40908. It should be a trivial
solution.


On Mon, Dec 16, 2013 at 8:20 AM, jennifer stone <jenny.stone...@gmail.com>wrote:

> Hello,
> Greetings
> I am a novice who is really interested in contributing to wget. guidance
> and suggestions are required
> Thanking you in anticipation
>



-- 
Thanking You,
Darshit Shah

Reply via email to