forked from Catrobat/catrobat.github.com
-
Notifications
You must be signed in to change notification settings - Fork 0
/
gsoc_2023_ideas_page.html
407 lines (374 loc) · 27.5 KB
/
gsoc_2023_ideas_page.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<title>Ideas Page</title>
<link rel="stylesheet" href="stylesheets/styles.css">
<link rel="stylesheet" href="stylesheets/pygment_trac.css">
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body>
<div class="wrapper">
<header>
<h1>Catrobat</h1>
<p>
A visual programming language
<br/>
and set of creativity tools
<br/>
for smartphones.
</p>
<p class="view">
<a href="https://www.catrobat.org/">Home</a>
</p>
<p class="view">
<a href="https://developer.catrobat.org/">Developers' Home</a>
</p>
<p class="view">
<a href="https://developer.catrobat.org/first_steps">First steps into Catrobat</a>
</p>
<p class="view">
<a href="http://catrob.at/pc">Find Pocket Code on Google Play</a>
</p>
<p class="view">
<a href="https://catrob.at/PCios">Find Pocket Code on the App Store</a>
</p>
<p class="view">
<a href="https://catrob.at/plus"><img src="googleplus.png" height="20px"/></a> <a href="http://catrob.at/fb"><img src="facebook.png" height="20px"/></a> <a href="http://catrob.at/pctwitter"><img src="twitter.png" height="20px"/></a> <a href="http://catrob.at/youtube"><img src="youtube.png" height="20px"/></a> <a href="http://catrob.at/mailinglist"><img src="google-group.png" height="20px"/></a> <a href="http://catrob.at/github"><img src="github.png" height="20px"/></a> <a href="mailto:contact@catrobat.org"><img src="mail.jpg" height="20px"/></a>
</p>
</header>
<section>
<h2>Ideas Page for Google Summer of Code 2023</h2>
<br />
<strong>Welcome,
<br />
we officially present our project ideas for this year's Google Summer of Code.</strong>
<br />
Last Updated: 20 March 2023</p>
<p>
<strong><u>General information about the ideas</u>
<br />
<i>These ideas are just some topics we came up with, where currently nobody is working on. However, Catrobat is a project with a wide range of possibilities and we're aware of our blindspots: So let's live the spirit of Open Source and come up with improvements (e.g., new features, extensions, ...) that are related to the project and in which you're interested in. We do have many senior contributors who would be happy to mentor such a project. Don't be shy and check out the last point on the list: <a href="#youridea">Your idea</a>!</i></strong>
</p>
<p>
<strong><u>General knowledge prerequisites for all projects</u></strong>
<ul>
<li>Knowledge in the usage of Git and GitHub</li>
<li>Basic knowledge in the concepts of software testing (e.g., test doubles) and test-driven development</li>
<li>Basic knowledge in app development (for Android and iOS projects)</li>
<li>Java, JUnit, Mockito, Robotium and Espresso for Android development</li>
<li>Swift and Objective C for iOS development</li>
<li>Also please check that you have the proper hardware for the development (e.g., a Android/iOS smartphone for testing, Mac for iOS development)</i>
</ul>
</p>
<p>
<strong><u>Your application</u></strong>
<br />
Please find the mandatory template for the application and additional information on <a href="https://catrob.at/gsoc23application">this shared Google Doc</a>.
</p>
<hr />
<p>
<h3>Overview:</h3>
<ul>
<li>
<a href="#idea_1">Awesome Demo Game Project (175 hour)</a>
</li>
<li>
<a href="#idea_2">Awesome Demo Game Project (350 hour)</a>
</li>
<!-- <li>
<a href="#idea_3">Execute Kotlin Code in Catty (iOS version of Pocket Code) (350 hour)</a>
</li> -->
<!-- <li>
<a href="#idea_4">Paintroid landing page (350 hour)</a>
</li>
<li>
<a href="#idea_5">Paintroid Smudge Tool (175 hour)</a>
</li> -->
<li>
<a href="#idea_1_4">Embroidery Designer Inspect Tool (175 or 350 hour)</a>
</li>
<li>
<a href="#idea_1_5">Catroid Editor for Userdefined Bricks (175 hour)</a>
</li>
<li>
<a href="#idea_6">Pocket Code for Android: Undo/redo functionality in Catroid (175 or 350 hour)</a>
</li>
<li>
<a href="#idea_8">Pocket Paint for Android: Refactoring tests and functionality to Kotlin (175 or 350 hour)</a>
</li>
<li>
<a href="#idea_9">Pocket Code for Android: Refactoring tests and functionality to Kotlin (175 or 350 hour)</a>
</li>
<li>
<a href="#idea_10">Pocket Paint for Android: Erase background tool (make it transparent more easily) (175 hour)</a>
</li>
<!-- <li>
<a href="#idea_11">Pocket Paint for Android: Add a feature that allows a user to see a zoomed in view of the area beneath his finger while drawing (175 hour)</a>
</li> -->
<li>
<a href="#idea_12">Merge Feature for Catroid (350 hour)</a>
</li>
<li>
<a href="#idea_13">Project converter in Dart from Catrobat to Godot (175 or 350 hour)</a>
</li>
<li>
<a href="#idea_14">Reimplement Catroid's Formula Editor in Flutter (175 or 350 hour)</a>
</li>
<li>
<a href="#idea_15">Reimplement Catroid's Sharing Site GUI in Flutter (175 or 350 hour)</a>
</li>
<li>
<a href="#idea_16">Reimplement parts of Catroid's IDE GUI in Flutter (175 or 350 hour)</a>
</li>
<li>
<a href="#idea_17">Add LLM-based AI pair-programming support for users (175 or 350 hour)</a>
</li>
<li>
<a href="#youridea">Your idea</a>
</li>
</ul>
</p>
<p>
<h3>Projects</h3>
<hr />
<h3><a id="idea_1">Awesome Demo Game Project (175 hour)</a></h3>
<p>Spend the whole GSoC time developing and designing one tutorial game for coding using the Luna&Cat IDE app, i.e., programming in the Catrobat visual programming language. The game must be playable both on a phone as well as when cast from the phone to a smart TV.</p>
<p>The game should be strongly inspired by a hugely popular recent 2D game, your own suggestions of popular games are highly welcome. You may also get inspiration by search for lists of the <a href="https://www.google.com/search?q=best+OR+popular+2d+games">best OR popular 2d games.</a> </p>
<p>If you have your own original idea about a game, please feel free to suggest it. Note, however, that the focus in GSoC should be on coding, not story design. Also, reusing existing already successful ideas will tremendously increase the probability that the game will be popular, and allow you to get much further in its implementation. Also note that the game will be published under Catrobat’s licenses as described in detail on <a href="https://catrob.at/licenses">https://catrob.at/licenses</a> and that the game will thus become part of the Catrobat FLOSS project’s source code. Thus, all artwork, sounds, character names etc must be compatible with our licenses, i.e., freely publishable under our licenses, the AGPL version 3 and CC BY-SA 4.0, or under a compatible, possibly even freer license such as CC0. </p>
<p>The artwork, sound effects, and background music must also be of high quality and high resolution, but do not have to be necessarily have been created originally by yourself, as long as the rights are compatible with our licenses. </p>
<p>The development of the game may possibly also be a community effort, but that’s up to you. This means that if you want, you may involve a team of people who want to work together with you on the game, either coding extensions or additional levels, contributing media assets, testing, creating promotion videos of it, etc. How you put together your team is entirely up to you, and you alone are responsible for the recruitment of and coordination within your team. Some Catrobat games have been created by large crowds. You and your team working together on the game would be perfectly fine and welcome, as long as you by yourself spend the full GSoC period working 100% on it too, and you do the main part of the coding, since Google wants GSoC projects to basically be single developer coding subprojects. However, most FLOSS projects are community efforts, and collaboration has always been one of the tenets of such projects. Also note that there will be no T-Shirts etc from Google for the other members of your team, so all contributions by other team members must be motivated intrinsically, or by additional means left to your discretion. </p>
<p>In summary, this GSoC project’s game should become an incredibly awesome & amazing demo game that showcases what kind of mind boggling games can be created with Pocket Code. </p>
<p>In your GSoC application, please add a link to a proof of concept for such a game in landscape mode (because it should be playable when cast to a TV screen) that you have created on your phone using Pocket Code. Also describe shortly your ideas for the story of the game you want to develop in your GSoC project. </p>
<p>Boyakasha!</p>
<p />
<ul>
<li>Required Skills: Coding Basics, PocketCode</li>
<li>Possible Mentors: Yash Punia, Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<hr />
<h3><a id="idea_2">Awesome Demo Game Project (350 hour)</a></h3>
<p>Spend the whole GSoC time developing and designing one tutorial game for coding using the Luna&Cat IDE app, i.e., programming in the Catrobat visual programming language. The game must be playable both on a phone as well as when cast from the phone to a smart TV.</p>
<p>The game should be strongly inspired by a hugely popular recent 2D game, your own suggestions of popular games are highly welcome. You may also get inspiration by search for lists of the <a href="https://www.google.com/search?q=best+OR+popular+2d+games">best OR popular 2d games.</a> </p>
<p>If you have your own original idea about a game, please feel free to suggest it. Note, however, that the focus in GSoC should be on coding, not story design. Also, reusing existing already successful ideas will tremendously increase the probability that the game will be popular, and allow you to get much further in its implementation. Also note that the game will be published under Catrobat’s licenses as described in detail on <a href="https://catrob.at/licenses">https://catrob.at/licenses</a> and that the game will thus become part of the Catrobat FLOSS project’s source code. Thus, all artwork, sounds, character names etc must be compatible with our licenses, i.e., freely publishable under our licenses, the AGPL version 3 and CC BY-SA 4.0, or under a compatible, possibly even freer license such as CC0. </p>
<p>The artwork, sound effects, and background music must also be of high quality and high resolution, but do not have to be necessarily have been created originally by yourself, as long as the rights are compatible with our licenses. </p>
<p>The development of the game may possibly also be a community effort, but that’s up to you. This means that if you want, you may involve a team of people who want to work together with you on the game, either coding extensions or additional levels, contributing media assets, testing, creating promotion videos of it, etc. How you put together your team is entirely up to you, and you alone are responsible for the recruitment of and coordination within your team. Some Catrobat games have been created by large crowds. You and your team working together on the game would be perfectly fine and welcome, as long as you by yourself spend the full GSoC period working 100% on it too, and you do the main part of the coding, since Google wants GSoC projects to basically be single developer coding subprojects. However, most FLOSS projects are community efforts, and collaboration has always been one of the tenets of such projects. Also note that there will be no T-Shirts etc from Google for the other members of your team, so all contributions by other team members must be motivated intrinsically, or by additional means left to your discretion. </p>
<p>In summary, this GSoC project’s game should become an incredibly awesome & amazing demo game that showcases what kind of mind boggling games can be created with Pocket Code. </p>
<p>In your GSoC application, please add a link to a proof of concept for such a game in landscape mode (because it should be playable when cast to a TV screen) that you have created on your phone using Pocket Code. Also describe shortly your ideas for the story of the game you want to develop in your GSoC project. </p>
<p>Boyakasha!</p>
<p />
<ul>
<li>Required Skills: Coding Basics, PocketCode</li>
<li>Possible Mentors: Yash Punia, Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 350 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<hr />
<!-- <h3><a id="idea_3">Execute Kotlin Code in Catty (iOS version of Pocket Code) (350 hour)</a></h3>
<p>Make it possible to execute Kotlin code in catty, so we can use paintroid tools directly in catty</p>
<ul>
<li>Required Skills: Kotlin, Swift, iOS-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 350 hours</li>
<li>Difficulty level: tbd</li>
</ul> -->
<!-- <h3><a id="idea_4">Paintroid landing page (350 hour)</a></h3>
<p>A landing page similar to catroid, where you can see all your saved pictures.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 350 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<h3><a id="idea_5">Paintroid Smudge Tool (175 hour)</a></h3>
<p>Extension of the existing smudge tool. It was part of a GsoC Project last year, but was too complicated to finish PAINTROID-292 - Smudge tool [READY FOR DEVELOPMENT}</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 hours</li>
<li>Difficulty level: tbd</li>
</ul>-->
<h3><a id="idea_1_4">Embroidery Designer Inspect Tool (175 or 350 hour)</a></h3>
<p>An inspection tool for embroidery projects that allows you to get important information about the project, view the embroidery more closely and thus edit it better. In a larger version of the project, first steps can be taken to easily touch-up stiches in order to make small corrections before saving an embroidery robot control file.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 or 350 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<h3><a id="idea_1_5">Catroid Editor for Userdefined Bricks (175 hour)</a></h3>
<p>An editor for user-defined bricks, to be able to modify them after they have been created.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<h3><a id="idea_6">Pocket Code for Android: Undo/redo functionality in Catroid (175 or 350 hour)</a></h3>
<p>In the current version of Catroid, there are a few places where the immediately previously executed step can be undone, thus avoiding a need for an interaction with the user to ask whether, e.g., an object should really be deleted. There are still many places and interactions where this single-step undo has not been implemented. The aim of this project is to add more such single-step undo operations where they are still missing. Depending on the size of the project, and if there is time, these single-step undo operations shall be step by step replaced by a standard undo-redo feature.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 or 350 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<!-- <h3><a id="idea_7">Pocket Paint for Android: Hide the top and bottom bars, and make the drawing surface full screen by default (350 hour)</a></h3>
<p>Currently Menus and Options are shown by default in top and bottom bars, and the default zoom is smaller than the screen's drawing surface, resulting in lost space on the sides of the image. The goal is to have the already existing full screen functionality active by default and find an intuitive way to show menus only by fading in and out depending on whether the finger leaves or touches the screen.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 350 hours</li>
<li>Difficulty level: tbd</li>
</ul> -->
<h3><a id="idea_8">Pocket Paint for Android: Refactoring tests and functionality to Kotlin (175 or 350 hour)</a></h3>
<p>Several parts of the project have already been refactored to use Kotlin, but there are still parts that should be refactored, and reworked to use Kotlin instead of Java.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 or 350 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<h3><a id="idea_9">Pocket Code for Android: Refactoring tests and functionality to Kotlin (175 or 350 hour)</a></h3>
<p>Several parts of the project have already been refactored to use Kotlin, but there are still parts that should be refactored, and reworked to use Kotlin instead of Java.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 or 350 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<h3><a id="idea_10">Pocket Paint for Android: Erase background tool (make it transparent more easily) (175 hour)</a></h3>
<p>The goal is to create a new tool that allows the user to select an area and erase the parts of the drawing surface outside the area, see similar tools in many picture manipulation programs.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<!-- <h3><a id="idea_11">Pocket Paint for Android: Add a feature that allows a user to see a zoomed in view of the area beneath his finger while drawing (175 hour)</a></h3>
<p>The goal is to create a new feature that allows a user to see a zoomed in view of the area beneath his/her finger while drawing, to allow for easier fine manipulation. The magnifying glass should be round, drag-and-droppable, move automatically way to another place (up or down) if the user's finger approaches it by drawing, have a default magnifying level of 3x, and there shall be some setting where one can turn it off (or on again) and change the magnification level. When no finger touches the drawing surface, the magnifying glass shall fade away.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 hours</li>
<li>Difficulty level: tbd</li>
</ul> -->
<h3><a id="idea_12">Merge Feature for Catroid (350 hour)</a></h3>
<p>Design and develop a feature for the Android version of Pocket Code that allows to merge two user projects into one, without duplicating scripts, objects, sounds etc that already exist in both projects. Similar to git merge, but for Catrobat user projects. Repeatedly merging the same project into itself should not increase the project's size. Think about how to handle different screen resolutions, orientations, etc, or how to treat conflicting variable names, correctly update remix graph data, etc.</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, Agile Development</li>
<li>Possible Mentors: Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 350 hours</li>
<li>Difficulty level: tbd</li>
</ul>
<h3><a id="idea_13">Project converter in Dart from Catrobat to Godot (175 or 350 hour)</a></h3>
<p>
Implement a prof-of-concept converter from Catrobat projects to Godot for Android or iOS in Dart.
Only parts need to be implemented, not the full feature set.
</p>
<ul>
<li>Required Skills: Dart, Godot, Test Driven Development, Clean Code</li>
<li>Possible Mentors: Wolfgang Slany</li>
<li>Requirement: self-organized work</li>
<li>Expected size of project: 175 or 350 hours (your choice)</li>
<li>Difficulty level: advanced</li>
</ul>
<h3><a id="idea_14">Reimplement Catroid's Formula Editor in Flutter (175 or 350 hour)</a></h3>
<p>
Reimplement Catroid's Formula Editor in Flutter.
Only parts need to be implemented, not the full feature set.
</p>
<ul>
<li>Required Skills: Flutter, Test Driven Development, Clean Code</li>
<li>Possible Mentors: Wolfgang Slany</li>
<li>Requirement: self-organized work</li>
<li>Expected size of project: 175 or 350 hours (your choice)</li>
<li>Difficulty level: advanced</li>
</ul>
<h3><a id="idea_15">Reimplement the Catrobat Community feature of Catroid in Flutter (175 or 350 hour)</a></h3>
<p>
Reimplement the Catrobat Community feature of Catroid in Flutter.
Only parts need to be implemented, not the full feature set.
</p>
<ul>
<li>Required Skills: Flutter, Test Driven Development, Clean Code</li>
<li>Possible Mentors: Wolfgang Slany</li>
<li>Requirement: self-organized work</li>
<li>Expected size of project: 175 or 350 hours (your choice)</li>
<li>Difficulty level: advanced</li>
</ul>
<h3><a id="idea_16">Reimplement parts of Catroid's IDE GUI in Flutter (175 or 350 hour)</a></h3>
<p>
Reimplement remaining parts of Catroid's IDE GUI in Flutter.
<emph>Not</emph> included would be the representation and manipulation of scripts, the
formula editor, the paint editor, the Catrobat community features, or the stage.
Also, only parts need to be implemented, not the full feature set.
</p>
<ul>
<li>Required Skills: Flutter, Test Driven Development, Clean Code</li>
<li>Possible Mentors: Wolfgang Slany</li>
<li>Requirement: self-organized work</li>
<li>Expected size of project: 175 or 350 hours (your choice)</li>
<li>Difficulty level: advanced</li>
</ul>
<h3><a id="idea_17">Add LLM-based AI programming support for users (175 or 350 hour)</a></h3>
<p>
Add support for an LLM (large language model) based on tools such as GPT-4 to support AI-based
programming support for our users. This support could range from proposing
code from text prompts, help in correcting bugs or other issues, finding a good architecture
or meaningful names, writing Catrobat language tests for one's code, proposing
extensions, proposing project ideas, explaining downloaded code, providing translations
of variable or message names etc from downloaded projects of other users, proposing
image and sound resources based on the context and text prompts, explaining
basic or more advanced concepts needed to realize projects, e.g., simple concepts such as
variables and loops, or more complex ones such as software design patterns or testing
strategies. Only parts need to be implemented, not the full feature set. The API key can be
assumed to be provided by the user and may need to be entered into the settings of our
apps. The initial prompt will have to detail the Catrobat context to the used LLM, and
will be provided by the Catrobat team.
</p>
<ul>
<li>Required Skills: Kotlin, Test Driven Development, Clean Code</li>
<li>Possible Mentors: Wolfgang Slany</li>
<li>Requirement: self-organized work</li>
<li>Expected size of project: 175 or 350 hours (your choice)</li>
<li>Difficulty level: advanced</li>
</ul>
<p>
<a id="youridea"><strong>Your own project ideas ... (175 or 350 hour)</strong></a>
<br />
<p>In the last year we made the experience that you have many great ideas and knowledge! Catrobat is currently still focusing on refactoring and we're aware that there are many ways how to improve performance, reduce memory usage, make our services more stable and of course the code easier to maintain. We're sure you do have ideas how to achieve this, although we may have never heard of this approach before -> that's the great thing about Open Source! And well, that's also the experience we made at last year's GSoC - and we liked it!</p>
<p>Also new features or extensions for iOS and Android are welcome to be introduced to us. Help us to spread coding and Open Source!</p>
<p>Please do not hesitate to bring forward your own ideas and discuss them with our community on our mailing-list: <a href="http://catrob.at/mailinglist"><img src="google-group.png" height="20px"/> catrobat@googlegroups.com</a>!</p>
</p>
<ul>
<li>Required Skills: Kotlin, Java, Android-Development, iOS-Development, Agile Development<</li>
<li>Possible Mentors: Yash Punia, Stefan Kutschera, Patrick Ratschiller, Wolfgang Slany</li>
<li>Expected size of project: 175 or 350 hours</li>
<li>Difficulty level: tbd</li>
</ul>
</section>
</div>
<script src="javascripts/scale.fix.js"></script>
<script>
(function(i, s, o, g, r, a, m) {
i['GoogleAnalyticsObject'] = r;
i[r] = i[r] ||
function() {
(i[r].q = i[r].q || []).push(arguments)
}, i[r].l = 1 * new Date();
a = s.createElement(o), m = s.getElementsByTagName(o)[0];
a.async = 1;
a.src = g;
m.parentNode.insertBefore(a, m)
})(window, document, 'script', '//www.google-analytics.com/analytics.js', 'ga');
ga('create', 'UA-42270417-2', 'catrobat.org');
ga('send', 'pageview');
</script>
</body>
</html>