From 583b13c96e44b8aea08355d791f73d2546dae6bc Mon Sep 17 00:00:00 2001 From: Hisham Muhammad Date: Wed, 6 Feb 2019 19:53:36 +0100 Subject: GSoC 2019 --- gsoc/apply2019.html | 74 ++++++++++++++++ gsoc/ideas2019.html | 250 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 324 insertions(+) create mode 100644 gsoc/apply2019.html create mode 100644 gsoc/ideas2019.html diff --git a/gsoc/apply2019.html b/gsoc/apply2019.html new file mode 100644 index 00000000..e311ced1 --- /dev/null +++ b/gsoc/apply2019.html @@ -0,0 +1,74 @@ + + + + + + + + +
+
Install · Docs · Log In · Register
+
+
+ +

Student Application - Google Summer of Code 2019

+ +

(Many thanks to LabLua for the student application template on which this one is largely based!)

+ +

Basics

+ +
  1. What is your preferred email address? +
  2. Do you have a web page / blog / GitHub account? +
  3. What is your academic background? +
  4. What other time commitments, such as school work, another job (GSoC is a full-time activity!), or planned vacations will you have during the period of GSoC? +
+ +

Experience

+ +
  1. What programming languages are you fluent in? Which tools do you normally use for development? +
  2. Are you familiar with the Lua programming language? Have you developed any projects using Lua? +
  3. Have you ever used LuaRocks? +
  4. Have you developed software in a team environment before? Any projects with actual users? +
  5. What kinds of projects/software have you worked on previously? + (anything larger than a class project: academic research, + internships, freelance, hobby projects, etc.) +
  6. Are you (or have you been) involved with any free software development project? If so, briefly describe the project and the scope of your involvement. +
+ +

PROJECT

+ +
  1. Did you select a project from our list? If yes, which project did + you select? Why did you choose this project? + If you are proposing a project, give a description of your proposal, + including the expected results. +
  2. Please provide a schedule with dates and important milestones/deliverables, +in two week increments). +
  3. What will be showable one month into the project? +
  4. What will be showable two months into the project? +
+ +

GSOC

+ +
  1. Have you participated as a student in GSoC before? If so, How many times, which year, which project? +
  2. Have you applied but were not selected? When, and to which organization? +
  3. Did you apply this year to any other organizations? +
+ +
+
+
+ + diff --git a/gsoc/ideas2019.html b/gsoc/ideas2019.html new file mode 100644 index 00000000..31aa6c98 --- /dev/null +++ b/gsoc/ideas2019.html @@ -0,0 +1,250 @@ + + + +Ideas List - Google Summer of Code 2019 + + + + + +
+
Install · Docs · Log In · Register
+
+
+ +

Ideas List - Google Summer of Code 2019

+ + +
+

Expression-level coverage analysis for LuaCov

+ +

Brief explanation

+ +

+LuaCov only offers line-level coverage analysis, meaning that it can tell if a line executed or not, but not if every possible branch within that line executed. That means, for example, that if a statement like if x and y > 20 then return 10 end is written in a single line, we don't have coverage information if it has been tested both with the condition being true and being false. This is due to a limitation in the Lua debug library, which only gives traces with at most line granularity. The idea of this project is to patch the Lua VM adding expression-level tracing, and then adjusting LuaCov to make it use it. +

+ +

Knowledge prerequisites

+
    +
  • C
    • +
  • Lua
    • +
+ +

Mentor

+

+Hisham Muhammad - h@hisham.hm +

+
+ + +
+ +
+

Lua graphing library

+ +

Brief explanation

+ +

+To create a graphical library possibly using IUP extensible by Lua to allow easy creation of software like a schematic editor/flowchart creator/mind maps/block diagrams in Lua. The library needs to create basic mechanisms and graphic checks to create custom blocks and interconnections and provide an API to use these to create complex interactions like hierarchical schematic editors, etc. +

+ +

Knowledge prerequisites

+
    +
  • Lua
    • +
+ +

Mentor

+

+Milind Gupta - milind.gupta@gmail.com +

+
+ + +
+ +
+

Better binary support for LuaRocks on Windows

+ +

Brief explanation

+ +

+Goal: have a number of binary basics available (eg. lfs, luasocket, OpenSSL based ones) +

+

+Things to do: +

+ +
    +
  • +Establish a proper naming scheme to identify Windows runtime dependencies, see #786 +
    • +
  • +Make LR aware of the runtimes (storing in config), current MSVCRT entry +
    • +
  • +Implement packing binary rocks with new binary tags +Set up some CI which builds some basic binary rocks as a minimal set for multiple compiler targets (eg. lfs, LuaSocket) +
    • +
  • +Set up some CI which builds some basic binary rocks with external dependencies as a minimal set for multiple compiler targets (eg. OpenSSL based ones) +
    • +
  • +Optional: use pe-parser at LR runtime to validate that created libs adhere to the runtime required +
    • +
  • +Optional: make LR installable without toolchain (just using binary rocks) +
    • +
  • +Optional: integrate toolchain into LR installation +
    • +
+ +

+See #788. +

+ +

Knowledge prerequisites

+
    +
  • Lua
    • +
  • general knowledge of development on Windows platforms
    • +
+ + +

Mentor

+

+Thijs Schreijer - thijs@thijsschreijer.nl +

+
+ + +
+ +
+

+New command line argument handling and auto-completion for luarocks +

+ +

+Update the command-line argument handling of +LuaRocks and add support for Tab auto-completion +support for popular shells such as bash, fish, zsh. +

+

+May involve updates to the argparse library. +

+ +

+See #879. +

+ +

Knowledge prerequisites

+
    +
  • Lua
    • +
  • some shell scripting
    • +
+ +

Mentor

+

+Daurnimator - quae@daurnimator.com +

+
+ + +
+ +
+

+Prosody plugin installer +

+ +

+This project would produce an easy way to install and manage plugins for the Prosody server. +

+ +

+Prosody has hundreds of community modules that provide additional features and extensions to the core server. Currently installing these is a manual process that currently involves a number of manual steps. +

+ +

+The goal of this project would be to produce simple commands to install, update and remove community modules. Rather than inventing a new package manager, the project would ideally build on top of the LuaRocks project. +

+ + +

Deliverables / Expected Results:

+ +
    +
  • +Commands to install, update, remove and list installed plugins. +
    • +
  • +Scripts to build and manage a repository of plugins. +
    • +
+ +

+Milestones: +

+ +
    +
  • Implement command to install a plugin from a repository +
    • +
  • +Implement commands to remove and update installed plugins +
    • +
  • +Develop scripts to build a plugin repository. +
    • +
+ +

More info:

+ + + +

Knowledge prerequisites

+
    +
  • Lua
    • +
+ +

Mentors

+

+Matthew Wild - mwild1@gmail.com +
+Kim Alvefur +

+
+ + +
+
+
+ + -- cgit v1.2.3-55-g6feb