Project-A: Provide a way for Wireshark to automatically check-for and optionally auto-retrieve the most recent version from wireshark's site/mirrors, automagically every X timeframe (where X is user-configurable to every X days/weeks), in the background asynchronously. This should be disabled by default. It should also display the major enhancements/fixes in a dialog box about a new version with a URL link to full release notes. And it should minimally do hash-based validation of the new version retrieved, preferably cert-signature-based authentication, etc. Extra credit for having it also auto-install and restart wireshark after user agrees. (a la Firefox, et al)
Project-B: Provide a viewer/manager mechanism for Lua plugins, which lists available Lua plugins from wirehark's site/mirrors, downloads them on request, and puts them in the user plugins folder. It should also list the installed ones, and let the user remove them, through wireshark's GUI (as opposed to making the user find the right folders and deleting them). There should be meta-data about the plugin/script, including description, wireshark version compatibility info, etc. Naturally this requires wireshark.com to be willing to host such a repository, or at least a repository of meta-data with info on where to pull down each plugin via other URLs. :) In theory Project-A and B could use the same underlying code, just for slightly different purposes. And of course there are many open-source implementations of this concept for other things - for example apps like Firefox, or language package systems like Luarocks/RubyGems/CPAN/etc. Most of them use licenses compatible with Wireshark's GPL for this case I think, so re-using some of their code+concepts for the above projects might make this a reasonable project size for a GSoC. -hadriel On Feb 14, 2013, at 5:18 PM, Gerald Combs <ger...@wireshark.org> wrote: > Google recently announced the Google Summer of Code 2013. Proposals are > due March 29. Anyone have any ideas for projects? > > > -------- Original Message -------- > Subject: Google Summer of Code 2013 > Date: Mon, 11 Feb 2013 11:02:27 -0800 > From: Carol Smith <car...@google.com> > Reply-To: google-summer-of-code-announce+own...@googlegroups.com > To: Google Summer of Code Announce > <google-summer-of-code-annou...@googlegroups.com> > > > > Hi all, > > We're pleased to announce that Google Summer of Code will be happening > for its ninth year this year. Please check out the blog post [1] about > the program and read the FAQs [2] and Timeline [3] on Melange for more > information. > > [1] - > http://google-opensource.blogspot.com/2013/02/flip-bits-not-burgers-google-summer-of.html > [2] - > http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page > [3] - http://www.google-melange.com/gsoc/events/google/gsoc2013 > > Cheers, > Carol > > -- > You received this message because you are subscribed to the Google > Groups "Google Summer of Code Announce" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to google-summer-of-code-announce+unsubscr...@googlegroups.com. > To post to this group, send email to > google-summer-of-code-annou...@googlegroups.com. > Visit this group at > http://groups.google.com/group/google-summer-of-code-announce?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
