aboutsummaryrefslogtreecommitdiff
path: root/gsoc
diff options
context:
space:
mode:
authorHisham Muhammad <hisham@gobolinux.org>2018-01-23 12:09:37 -0200
committerHisham Muhammad <hisham@gobolinux.org>2018-01-23 12:09:37 -0200
commit5b56da11d31b64ca760a8c5a67b757efe87186c8 (patch)
tree6e3bbef0fe1edd604a754ceb9e75004a38a3deb9 /gsoc
parent854ab7fcd2828b2c6e11455fe9f67b8abc6ba9c9 (diff)
downloadluarocks-5b56da11d31b64ca760a8c5a67b757efe87186c8.tar.gz
luarocks-5b56da11d31b64ca760a8c5a67b757efe87186c8.tar.bz2
luarocks-5b56da11d31b64ca760a8c5a67b757efe87186c8.zip
Add GSoC 2018 application data
Diffstat (limited to 'gsoc')
-rw-r--r--gsoc/apply2018.html74
-rw-r--r--gsoc/ideas2018.html283
2 files changed, 357 insertions, 0 deletions
diff --git a/gsoc/apply2018.html b/gsoc/apply2018.html
new file mode 100644
index 00000000..b51f5a97
--- /dev/null
+++ b/gsoc/apply2018.html
@@ -0,0 +1,74 @@
1<!doctype html>
2<html>
3<head>
4<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:400italic,400,700" type="text/css"/>
5<link rel="stylesheet" href="../style.css" type="text/css"/>
6<style>
7table {
8 width: 100%;
9}
10td {
11 padding: 5px;
12 background-color: white;
13 border: 1px solid #c1cce4;
14}
15h3 {
16 border-bottom: solid 2px black;
17}
18
19</style>
20</head>
21<body>
22 <div class="content">
23 <div class="header"><div class="header_inner"><div class="user_panel"><a href="https://github.com/keplerproject/luarocks/wiki/Download">Install</a> &middot; <a href="https://github.com/keplerproject/luarocks/wiki/Documentation">Docs</a> &middot; <a href="https://luarocks.org/login">Log In</a> &middot; <a href="https://luarocks.org/register">Register</a></div><a href="https://luarocks.org/"><img alt="LuaRocks" class="text_logo" src="https://luarocks.org/static/header_luarocks_name.svg"/></a><form method="GET" action="https://luarocks.org/search" class="header_search"><input type="text" placeholder="Search modules or uploaders..." name="q"/></form></div></div>
24 <div class="index_page">
25 <div class="main_column">
26
27<h2>Student Application - Google Summer of Code 2018</h2>
28
29<p><i>(Many thanks to LabLua for the student application template on which this one is largely based!)</i></p>
30
31<h3>Basics</h3>
32
33<ol><li>What is your preferred email address?
34</li><li>Do you have a web page / blog / GitHub account?
35</li><li>What is your academic background?
36</li><li>What other time commitments, such as school work, another job (<i>GSoC is a full-time activity!</i>), or planned vacations will you have during the period of GSoC?
37</li></ol>
38
39<h3>Experience</h3>
40
41<ol><li>What programming languages are you fluent in? Which tools do you normally use for development?
42</li><li>Are you familiar with the Lua programming language? Have you developed any projects using Lua?
43</li><li>Have you ever used LuaRocks?
44</li><li>Have you developed software in a team environment before? Any projects with actual users?
45</li><li>What kinds of projects/software have you worked on previously?
46 (anything larger than a class project: academic research,
47 internships, freelance, hobby projects, etc.)
48</li><li>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.
49</li></ol>
50
51<h3>PROJECT</h3>
52
53<ol><li>Did you select a project from our list? If yes, which project did
54 you select? Why did you choose this project?
55 If you are proposing a project, give a description of your proposal,
56 including the expected results.
57</li><li>Please provide a schedule with dates and important milestones/deliverables,
58in two week increments).
59</li><li>What will be showable one month into the project?
60</li><li>What will be showable two months into the project?
61</li></ol>
62
63<h3>GSOC</h3>
64
65<ol><li>Have you participated as a student in GSoC before? If so, How many times, which year, which project?
66</li><li>Have you applied but were not selected? When, and to which organization?
67</li><li>Did you apply this year to any other organizations?
68</li></ol>
69
70 </div>
71 </div>
72 </div>
73</body>
74</html>
diff --git a/gsoc/ideas2018.html b/gsoc/ideas2018.html
new file mode 100644
index 00000000..b631b3c6
--- /dev/null
+++ b/gsoc/ideas2018.html
@@ -0,0 +1,283 @@
1<!doctype html>
2<html>
3<head>
4<title>Ideas List - Google Summer of Code 2018</title>
5<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:400italic,400bold,400,700" type="text/css"/>
6<link rel="stylesheet" href="../style.css" type="text/css"/>
7<style>
8table {
9 width: 100%;
10}
11td {
12 padding: 5px;
13 background-color: white;
14 border: 1px solid #c1cce4;
15}
16h3 {
17 border-bottom: solid 2px black;
18}
19h4 {
20 font-style: italic;
21 border-bottom: solid 1px #c0c0c0;
22}
23</style>
24</head>
25<body>
26 <div class="content">
27 <div class="header"><div class="header_inner"><div class="user_panel"><a href="https://github.com/keplerproject/luarocks/wiki/Download">Install</a> &middot; <a href="https://github.com/keplerproject/luarocks/wiki/Documentation">Docs</a> &middot; <a href="https://luarocks.org/login">Log In</a> &middot; <a href="https://luarocks.org/register">Register</a></div><a href="https://luarocks.org/"><img alt="LuaRocks" class="text_logo" src="https://luarocks.org/static/header_luarocks_name.svg"/></a><form method="GET" action="https://luarocks.org/search" class="header_search"><input type="text" placeholder="Search modules or uploaders..." name="q"/></form></div></div>
28 <div class="index_page">
29 <div class="main_column">
30
31<h2>Ideas List - Google Summer of Code 2018</h2>
32
33<ul>
34<!--
35<li><a href="#orgsite">
36Module management enhancements for LuaRocks.org
37</a></li>
38-->
39<li><a href="#gui">
40A GUI front-end for LuaRocks
41</a></li>
42<li><a href="#windows-binaries">
43Auto-building Windows binaries
44</a></li>
45<li><a href="#distro">
46Auto-building distro packages
47</a></li>
48<li><a href="#static">
49Static build support for LuaRocks
50</a></li>
51<li><a href="#upgrade">
52A command to upgrade all installed rocks
53</a></li>
54<li><a href="#unit-tests">
55Unit tests for LuaRocks
56</a></li>
57</ul>
58
59<!--
60<div class="project">
61<h3 id="orgsite">Module management enhancements for LuaRocks.org</h3>
62<h4>Brief explanation</h4>
63
64<p>
65The LuaRocks.org website is where Lua users and developers find and upload Lua modules. Users
66can currently create accounts for uploading modules, and each module becomes attached to one
67user account. For organizations with multiple developers, this can prove cumbersome. Also,
68the only ways to upload modules are via the command-line tool or via the web interface.
69This project aims to improve LuaRocks.org support for organizations, via two main goals:
70</p>
71
72<ul>
73<li>Organization accounts/modules shared across accounts, showing module stats on
74module pages</li>
75<li>Better GitHub integration: automatically creating new module
76versions with webhook, automatically syncing readme, showing module popularity
77on GitHub</li>
78</ul>
79
80<h4>Knowledge prerequisites</h4>
81<ul>
82<li>Lua</li>
83<li>web development</li>
84<li>JSON and REST APIs</li>
85<li>LuaRocks experience is a plus</li>
86<li>MoonScript is a plus (but can be learned for the project!)</li>
87<li>experience with the GitHub API would be a major plus</li>
88</ul>
89
90<h4>Skill level</h4>
91<p>medium</p>
92
93<h4>Mentor</h4>
94<p>
95<a href="http://leafo.net/">Leaf Corcoran</a> - <a href="mailto:leafot@gmail.com">leafot@gmail.com</a>
96</p>
97</div>
98-->
99
100<div class="project">
101<h3 id="gui">A GUI front-end for LuaRocks</h3>
102<h4>Brief explanation</h4>
103
104<p>
105A cross-platform GUI desktop front-end for LuaRocks. It should allow users to
106search for rocks, list installed rocks, install and remove them, view rock
107details, etc. There are some options on portable Lua toolkits for developing
108this front-end (WxLua, TekUI, QtLua, etc.)
109</p>
110
111<p>
112A possible side-result of this project would be to define an API for
113interfacing the LuaRocks backend. The LuaRocks backend is currently accessible
114via the command-line tool, but an API is desired. By making a API wrapper around
115the command-line tool, this project could provide good insights into a design
116for an UI-agnostic API.
117</p>
118
119<h4>Knowledge prerequisites</h4>
120<ul>
121<li>Lua</li>
122<li>LuaRocks experience is a plus</li>
123<li>some previous experience with UI APIs is preferred</li>
124</ul>
125
126<h4>Skill level</h4>
127<p>easy/medium</p>
128
129<h4>Mentor</h4>
130<p>
131<a href="http://thijsschreijer.nl/">Thijs Schreijer</a> - <a href="mailto:thijs@thijsschreijer.nl">thijs@thijsschreijer.nl</a>
132</p>
133</div>
134
135<!--
136<div class="project">
137<h3 id="typedlua">Port LuaRocks to Typed Lua and make it a library</h3>
138<h4>Brief explanation</h4>
139
140<p>
141LuaRocks is currently not a reentrant library. We would like to make usable as
142a library, embeddable into applications. This would require a good deal of
143refactoring, and encapsulating all state into a main instance object. Porting
144the code base to Typed Lua would be a great opportunity to make the codebase
145reentrant. Since Typed Lua generates plain Lua, it would not become a new
146dependency for LuaRocks, but instead it would be used as a tool in the
147refactoring process.
148</p>
149
150<h4>Knowledge prerequisites</h4>
151<ul>
152<li>Lua</li>
153<li>LuaRocks experience is recommended</li>
154</ul>
155
156<h4>Skill level</h4>
157<p>medium/hard</p>
158
159<h4>Mentor</h4>
160<p>
161<a href="http://hisham.hm/">Hisham Muhammad</a> - <a href="mailto:h@hisham.hm">h@hisham.hm</a>
162</p>
163</div>
164-->
165
166<div class="project">
167<h3 id="windows-binaries">Auto-building Windows binaries</h3>
168<h4>Brief explanation</h4>
169
170<p>
171Making LuaRocks build binary rocks for Windows. By automatically building
172packages and repack them as binary rocks. Especially on the windows platform
173where users are less familiar with command line tools, let alone compilers and
174other build tools. The availability of binary rocks would reduce the entry
175barrier for using Lua on Windows.
176</p>
177
178<h4>Knowledge prerequisites</h4>
179<ul>
180<li>Lua</li>
181<li>Windows</li>
182<li>LuaRocks is a plus</li>
183</ul>
184
185<h4>Skill level</h4>
186<p>medium</p>
187
188<h4>Mentor</h4>
189<p>
190<a href="http://thijsschreijer.nl/">Thijs Schreijer</a> - <a href="mailto:thijs@thijsschreijer.nl">thijs@thijsschreijer.nl</a>
191</p>
192</div>
193
194<div class="project">
195<h3 id="static">Static build support for LuaRocks</h3>
196<h4>Brief explanation</h4>
197
198<p>
199LuaRocks currently builds Lua modules as dynamic libraries. The aim of this
200project is to add support for building static libraries. The local manifest
201format needs to be extended. Also, research if it would be possible to make
202that work beyond the LuaRocks 'builtin' rockspec mode (including a possible
203extension of the rockspec format). Another possibility is adding a command
204that builds a custom interpreter bundling a set of rocks statically. Other
205targets benefitting from static builds could be embedded systems: research how
206to improve LuaRocks support for cross-compiling.
207</p>
208
209<h4>Knowledge prerequisites</h4>
210<ul>
211<li>Lua</li>
212<li>LuaRocks experience is recommended</li>
213</ul>
214
215<h4>Skill level</h4>
216<p>medium</p>
217
218<h4>Mentor</h4>
219<p>
220<a href="http://daurnimator.com/">Daurnimator</a> - <a href="mailto:quae@daurnimator.com">quae@daurnimator.com</a>
221</p>
222</div>
223
224<div class="project">
225<h3 id="upgrade">A command to upgrade all installed rocks</h3>
226<h4>Brief explanation</h4>
227
228<p>
229LuaRocks users have wanted <code>luarocks upgrade</code> for a long
230time, but implementing it is not trivial and will involve trade-offs (see
231<a href="https://github.com/luarocks/luarocks/issues/22">the GitHub issue</a>
232and
233<a href="http://article.gmane.org/gmane.comp.lang.lua.general/112719">this
234email</a>). The goal of this project is to identify those trade-offs clearly,
235document them, come to a decision regarding their resolution, and finally
236implement the command.</p>
237
238<h4>Knowledge prerequisites</h4>
239<ul>
240<li>Lua</li>
241<li>LuaRocks experience is recommended</li>
242</ul>
243
244<h4>Skill level</h4>
245<p>medium</p>
246
247<h4>Mentor</h4>
248<p>
249<a href="http://catwell.info/">Pierre Chapuis</a> - <a href="mailto:catwell@archlinux.us">catwell@archlinux.us</a>
250</p>
251</div>
252
253<div class="project">
254<h3 id="unit-tests">Unit tests for LuaRocks</h3>
255<h4>Brief explanation</h4>
256
257<p>
258LuaRocks features an extensive test suite, but it is mostly comprised
259of black-box integration tests. The aim of this project is to produce
260a unit-test suite, to improve the maintainability of the tool and
261increase our code coverage.
262</p>
263
264<h4>Knowledge prerequisites</h4>
265<ul>
266<li>Lua</li>
267<li>Basic understanding of unit testing</li>
268</ul>
269
270<h4>Skill level</h4>
271<p>easy</p>
272
273<h4>Mentor</h4>
274<p>
275<a href="http://hisham.hm/">Hisham Muhammad</a> - <a href="mailto:h@hisham.hm">h@hisham.hm</a>
276</p>
277</div>
278
279 </div>
280 </div>
281 </div>
282</body>
283</html>
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-01 19:29:28 +0000