bug-wget
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] Google Summer of Code 2016


From: Darshit Shah
Subject: Re: [Bug-wget] Google Summer of Code 2016
Date: Wed, 2 Mar 2016 08:35:55 +0100
User-agent: Mutt/1.5.24+60 (909cf6dd067c) (2015-08-30)

On 03/02, Kushagra Singh wrote:
Hi,

Thanks for the quick reply. I went through the repository and the issues,
and found a couple of things I would like to work on.

I have a couple of questions about Wget2. Is it a complete rewrite of the
Wget project, available at git://git.savannah.gnu.org/wget.git, or are we
using existing code and extending functionality? I guess it is the second
one because I saw `libwget` in the repo. However if such is the case, then
how do we change existing functions in wget? For example, implementing [2]
would require making changes to the file cookies.c, which is present in
/src in the wget repo, but not in /src in the wget2 repo.

Wget2 is a complete rewrite of GNU Wget. It is also available on the savannah server as its own repository at [1]. Wget2 is meant to be a modern (almost) drop-in replacement for Wget. It strives to maintain backward compatible command line options and behaviour as far as it makes sense. The codebase for the two projects has diverged by significant amounts and hence new features need to be implemented separately for each.

I was looking at #43 [1], and have already submitted a patch for
consideration for the first suggestion [2]. The second suggestion mentioned
[3] is one of the things I'd like to work on, however this is not something
which will take three months :)

You submitted a patch for Wget. This is the Wget2 repository. Anyways, I already have a working patch for most of that issue, got sidetracked when writing the tests and eventually forgot about it. I think I'll spend some time on it this week and have that patch merged. Don't spend time on that part.

Another thing to remember is, not all GitHub issues are valid GSoC projects. Since the number of issues is few, it is easy to scout out the larger ones. Some issues are pretty tiny, just need someone willing to spend time working on them.


Another project I am interested in, is implementing FTPS. I saw this listed
under one of the ideas of GSoC 2015, but I'm not sure whether it was
implemented, as I didn't see it under 'Development Status' in the wget2
readme on Github.

Wget2 as far as I'm aware is still lacking FTPS support. Remember that Wget and Wget2 are two different projects.

Also, in #67 [4], we are talking about adhering to some specific parts of
RFC 7230. I'm not sure which all parts would be right, as the discussion
thread mentions that it won't be good to stick to each point of the RFC.
WDYT?

This is a minor grievance I raised. We stick to most of it anyways. As Tim points out, being completely RFC compliant may make the tool unusuable thanks to the number of bad servers out there. If anything, that issue needs to be split into multiple smaller issues about specific parts of the RFC that we want to adhere to.

Open projects I currently see are:
1. FTP / FTPS support
2. SOCKS5 Proxy support (This may be too small.)
3. Progress Bar implementation (Looks deceptively simple, isn't)
4. WARC support and tests
5. Brotli compression (May be too small)

The README file also has more pointers on features not implemented in Wget2. You may get some ideas from there. Request pipelining and DNSSEC are two features I'd be interested in seeing implemented.

Moreover, you are always welcome to submit your own ideas for either Wget or Wget2.

Tim can add more details or comment on whether something is too small to work on for a GSoC project.

[1]: git://git.savannah.gnu.org/wget/wget2.git

[1] https://github.com/rockdaboot/wget2/issues/43
[2] https://tools.ietf.org/html/draft-west-leave-secure-cookies-alone-04
[3] https://tools.ietf.org/html/draft-west-cookie-prefixes-05
[4] https://github.com/rockdaboot/wget2/issues/67

On Tue, Mar 1, 2016 at 9:57 PM, Giuseppe Scrivano <address@hidden> wrote:

Kushagra Singh <address@hidden> writes:

> Hi,
>
> Will we be taking part in GSoC this year? I would really like to work on
a
> project related to Wget this summer. Any specific ideas that are of
> importance to the community presently?

yes, we will be take part in GSoC.  I think we would like to see more
work happening on wget2, at the moment there is a list of issues on
github that can be useful to you to pick some ideas to work on:

  https://github.com/rockdaboot/wget2/issues

Could you take a look at it?  Do you see anything interesting that you
would like to work on?

Regards,
Giuseppe


--
Thanking You,
Darshit Shah

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]