Re: [Bug-wget] C developper offer

[Darshit Shah]

Hi Julián,

Let me elaborate a little more over what Ángel mentioned.

As stated by Ángel, you should first download the git sources and try
to build the program and run the tests. Once you've done that, you
have your development environment ready for that project.

Next, you want to hack on the code and submit changes. For that first,
you want to be acquinted with the coding guidelines. Usually, it is
easy to glean the guidelines from the existing source itself, but you
can also read the official guidelines here:
https://www.gnu.org/prep/standards/standards.html#Formatting

Once you're done making changes, you want to submit that code for
merging into mainline. For this again, each project has their own
guidelines. At GNU Wget, we tend to prefer patches formatted using
`git format-patch` commands attached to the plain text emails. These
patches should be built against the current origin/HEAD so that
Guiseppe (current maintainer) can easily apply them.

Another thing, pretty specific to Wget would be that you document the
changes you made to the respective ChangeLog files in the source.

Regarding the copyright attribution, I believe the rule is, once your
total contributions exceed 10 lines, you need to submit your copyright
attribution forms to FSF. We will notify you about the same when the
time arises.

As for ideas to code on Wget, you could, as Ángel suggested look at
the bug tracker. You can also look at our GSoC ideas page. It lists 4
ideas, of which one of them is currently being worked on by Jure.
Since its his GSoC project, you cannot collaborate on that part of the
code with him right now. That eliminated the concurrency support idea
from the page. However, feel free to pick any of the others up.
https://www.gnu.org/software/soc-projects/ideas-2014.html#wget

Looking forward to hearding from you!

On Sat, May 31, 2014 at 10:57 PM, Ángel González <address@hidden> wrote:
> Hola Julián,
> Thanks a lot for your offer.
>
> I will try to document a bit how to contribute. Note that although focused
> on wget,
> most of it is generic and is applicable to other projects.
>
> The first step would be that you download the program from the development
> sources
> [ wget git repository is at git://git.savannah.gnu.org/wget.git ] and are
> able to build,
> run tests, etc.
>
> You would then post your changes to this mailing list as patches. You may
> get some
> objections and send a revised patch multiple times. Finally, the maintainer
> (Giuseppe)
> commits it to the main repository.
>
> For complex patches, some GNU projects require some paperwork for copyright
> attribution, unlike
> most other open source projects, see
> https://www.gnu.org/prep/maintain/maintain.html#Legal-Matters
> (that may delay adoption of your code) You will be told if/when it's needed.
>
> I currently don't have a suggestion for you to code on wget. You can get
> ideas on the bug tracker at savannah
> and the mailing list archive. I encourage you pick something simple and that
> appeals you.
>
>
> I hope to hear from you soon
> Best regards
>
>
>



-- 
Thanking You,
Darshit Shah