ET

2013-04-05T11:15:43Z

Ssaarm: /* Analysis */

Team page for [[ET]].

===Members===
* Indrek Mitt, IT College
* Sander Saarm, IT College
* Panagiota Chatzi, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Nikolaos Karadimitriou, T.E.I. of Crete, Department Of Applied Informatics And Multimedia

===Goal===
*Create an application for our client that is very effective and user friendly.
*A familiar environment for students to upload their exercises.
*In general, to augment E-Learning Environments and facilitate students' exercises evaluation by using our application.

==Activity==
===Monday - 25.03.13===
Things that we did that day
* Learned about documentation and data mining
* Programmed sumo robots
* Got to know our team at welcome dinner in St. Patrick's

===Tuesday - 26.03.13===
Things that we did that day
* Talked about our case and made sure everybody is on the same page
* Put together a list of questions for our client
* Thought of different solutions for our project
* Seperated tasks between team members

Problems that we faced:
* We didn't have enough information about our case
* We wanted to use Moodle, but we didn't know if it's suitable for our project

Things that we plan to do:
* Ask our mentor if Moodle environment suitable for our project
* Prepared to speak to our client Priit Raspel

===Wednesday - 27.03.13===
Things that we did that day
* Spoke to our clent Priit Raspel.
* Learned about Moodle and installed it.

Problems that we faced:
* We couldn't access installed Moodle on Sander's computer.
* We needed a laptop with touchscreen.

Questions and answers from client (consultation)
* The client explained his visions on the project, that were quite similar to our vision. So we didn't have many questions.
* Mostly we talked about the user interface on the teacher's side. We got to know his exact requirements.
* We got telefon numbers of our client and our mentor for further questions.
* We asked about Moodle and it's API from our mentor Mart Mangus.
* We asked for client's touchscreen laptop for two weeks' testings and we got it.

Things that what we plan to do:
* Need to get a wireless router form Indrek Rokk for our own network to access installed Moodle.
* Get to know Moodle's API.
* Creating user interface.

===Thursday - 28.03.13===
Things that we did that day
* Had lecture about Innovation
* Studied Moodle documentation
* Set up our Moodle test environment
* Created test course and users
* Checked if Moodle has needed options for our client's specific needs
* Nikolaos is programming the UI
Problems that we faced:
* Had little problems setting up our workstation
* Some network problems
Things that we plan to do:
* Work more on UI
* Try if Moodle's options and API are enough to continue

===Friday - 29.03.13===
Things that we did that day
* Read the documentation about API in Moodle.
* We divided the parts of documentation for reading & we tried to familiarize with the Moodle's API.
* We created and enrolled users in order to put some necessary and specific requirements that our client needs.
* We logged in as admin, teacher, student to make the proper tests to see if our choices work properly.
* We also created a user through our standalone application using Moodle's API and the service.
* We had to test which protocol suits to our project's requirements because we wanted the right one for connecting with the GUI. The best for us is REST.

Problems that we faced:
* Couldn't login to Moodle with the standalone application (we fixed it).
* A bug since v2.1 in Moodle doesn't record the shortname of the service that the user creates and makes it impossible for the user to log in (we fixed it).
** In table external_services: "shortname" should be the same as "name".

Things that we plan to do:
* Work on the standalone application.
* To get the standalone application to communicate with Moodle.
* Find a way to get names of all students for this course and their files:
** Get courses of teacher.
** Get groups of course.
** Get students of course.
** Get student's assignments.
** Get assignment files.
* Find the functions to upload and download files.

===Saturday - 30.03.13===
Cultural Estonia's day

===Monday - 01.04.13===
Things that we did that day
* Worked on standalone application (implemented the remove functions)
* Worked on Moodle API's connection and functions.

Problems that we faced:
* BIG PROBLEM - Didn't have any success in implementing functions.

Things that we plan to do:
* Work on implementing functions to get standalone app communicating with Moodle.
* Work on the standalone application.
* Meet with client to specify his needs.

===Tuesday - 02.04.13===
Things that we did that day
* Worked on Moodle API's connection and functions.
* Augmenting teacher's application functionality

Problems that we faced:
* MoodleREST API connection with Moodle.

Things that we plan to do:
* Try to finalize the connection to Moodle.

===Wednesday - 03.04.13===
Things that we did that day
* Further functionality in teacher's application and partial connection with MoodleREST API.
* We completed the functions to retrieve data from Moodle through MoodleREST API
* We worked hard till midnight

Problems that we faced:
* Time

Things that we plan to do:
* Integrating data retrieving functions in teacher's application

===Thursday - 04.04.13===
Things that we did that day
* Prepared our presentation
* Nikolaos prepared the demo on client's touchpad
* Sander did some more Java code: getting teacher's students according to courses
* Did the presentation

Problems that we faced:
* A little stage nerv
* Getting the right student files from Moodle

Things that we plan to do:
* Finalize our project

===Friday - 05.04.13===
* Did give feedback to IP
* We did the finalization of the application
* Finalized our wiki

==Results==
We developed a new system for client, so he can use the touchscreen of his laptop, or use the mouse or even a interactive whiteboard to evaluate and manage all of the students' projects(e.g. Entity Relationship Diagrams), instead of undergoing the time-consuming and chaotic process of hand-evaluation with a pen on a paper. Our solution benefits an organizational structure which promotes efficiency and deduction of supply usage(paper, pen, printer, printer cartridge).

===Personal Input===

====Indrek Mitt====
Our first task was to generate ideas how our solution could work. After we decided to use Moodle environment, me and Sander setup our Moodle test environment and with Panagiota create the needed users and courses. Later we did all the needed testing with users and courses. Then after Moodle was set up we studied Moodles API, to help Sander create new functions in Moodle and get his part of the java code right. Also my part was to set up extra meetings with our client. In the last stage of our project I created the skeleton of the presentation, which we finalized together.

What did I learn:
* different things from lectures
* very valuable group work experience in international group
* very good language practice
* experience in real project with time limit
* learned to know Moodle environment much better
* got to know programming a bit better

====Sander Saarm====
First I studied Moodle and it's API, read the documentation and then we (with Panagiota and Indrek) created some test users: students and teachers. Then I started to do the code in Java (used REST protocol) and with the little help from Nikolaos I managed to use Moodle API functions to get different information from database for the application Nikolaos did. I had some help also from Panagiota and Indrek finding all the functions and their descriptions. Mart Mangus, our mentor, gave also some help with creating new functions to Moodle API.

What did I learn:
* A lot about Moodle and Java implementation
* Using and creating Moodle API's functions
* Getting the information from Moodle's database
* Communication with Moodle services through MoodleRest API

====Panagiota Chatzi====

Firstly we divided the reading of the Moodle documentation into parts and with Indrek and Sander we tried to familiarize with it. We created some users, we enrolled them and we made the proper testings in order to see how Moodle works. We were given specific requirements from our client, so we had to put them into Moodle. When Sander began to do the code, me and Indrek helped him by finding all the functions and their descriptions. I want to thank Mart Mangus, for his precious help. He gave us really useful advices during this project. I want to thank also my colleagues for the efficient team work.

What have I learnt:
*How to co-operate and work with other people in such intensive projects
*How to behave in front of a client in order to promote a solution
*I began to familiarize with the idea of a presentation in a different language
*This program gave me the chance to see how companies work and broaden my horizons
*I worked with my colleagues on trying to understand APIs

====Nikolaos Karadimitriou====

What did I do to successfully bring our project to a sufficient state(working):

At first I suggested the task division into 2 parts and the assignment of them to 2 teams. Following this way the strengths of each team member could be exploited in more sufficient form.
My main goal was to create an easy to use, functional application which comprises the following:

*1. Communication with Moodle services through MoodleRest API
*2. Retrieval of several data from Moodle system and translate them to usable and understandable graphical interface objects (e.g. Lists of students in a course(Json Structure) => Table Structure (java))
*3. Image(exercise files, .jpg .bmp .tiff .png) processing and manipulation, in order to evaluate ER-Diagrams.
*4. Correcting marks. Comments. New tables etc. On screen.
*5. Student management and grading frames communicating with Moodle services.
*6. On screen image processing with functional interactive buttons and features.
*7. Touch screen usability.
*8. Application’s capability in working with interactive whiteboards.
*9. The application was implemented in Java and Processing programming language.

*My secondary part in the project was to coordinate the project’s process and give advice to all the members of the project.

Knowledge and Skills I've acquired:

*The most beneficial experience I’ve gained was the teamwork and cooperation with international students, and of course a sufficient and concrete knowledge on presentation methods and methodology in general. I believe some substantial skills, in coordinating and task assigning group members were also acquired.

*Also in the programming domain, I’ve gained a useful amount of skills regarding image manipulation and touchscreen usable graphical interfaces as well as API integration to custom systems.

*One thing also worth mentioning is the familiarization with different cultures and languages.

===Final documentation===
====Analysis====
[[File:analysis.png|400px|thumb|left|Current Evaluation Process]]

===Solution===

====Changes in Moodle environment:====

===== Part one =====
Go to:

Site administration->Advanced features-> Plugins->Web services ->External services->

Add :

1)Add new external service

2)To new external service add functions:

*core_course_get_courses (Get the list of courses where a user is enrolled in)
*core_enrol_get_users_courses (core_enrol_get_users_courses)
*core_enrol_get_enrolled_users (Get enrolled users by course id.)
*core_files_get_files (browse moodle files)
*core_files_upload (upload a file to moodle)
Our created functions:
*core_get_files_by_userid (Returns files by user id)
*core_get_id_by_token (Returns id by token)

3)For new external service add -> Authorised users

=====Part two=====
Create new functions:

==IP Feedback==
===Indrek Mitt's feedback===
I liked the IP and I think that the organisation side was very good. You always knew what will happen next. Very good international teamwork experience. Lectures were interesting as well. Choice of cafeteria was very good. The majority of teamwork topics were in my opinion to much programmer based. No networking projects! Social events helped to get to know everybody better.

===Sander Saarm's feedback===
* I liked the internationality in this course, because I found out so many friendly people from other countries (Lithuania, Greece and Finland). We had our good and bad times during these two weeks.
* I'm glad we also had different cultural activities. I had never been to TV Tower since the restoring and also the Plane Harbour was new and very interesting to me.
* I actually think we could have had a little more time to finish our project 100%, but we have made 90% in my oppinion, so it's pretty great.

===Panagiota Chatzi's feedback===
I liked this and that.

===Nikolaos Karadimitriou's feedback===
I liked this and that. Didn't like.

File:Analysis.png

2013-04-05T11:13:09Z

Ssaarm: The current state of evaluation process and moodle service.

The current state of evaluation process and moodle service.

ET

2013-04-04T15:10:33Z

2013-03-29T15:31:18Z

Ssaarm: moved E-teacher to ET: uus nimi

#REDIRECT [[ET]]

ET

2013-03-29T15:31:18Z

Ssaarm: moved E-teacher to ET: uus nimi

Deploying IT Infrastructure Solutions 2013

2013-03-29T15:30:00Z

Ssaarm: /* Team E-Teacher */

[[Category: Õppetöö]]
[[File:EL_Sotsiaalfond_horisontaal_small.jpg‎‎|right|text-top]]
<br style="clear: both" />
----
__TOC__

----
This is the student results wiki page for the IP program [http://www.itcollege.ee/en/co-operation/dits2013/ "Deploying IT Infrastructure Solutions"] taking place from 24th of March until 6th of April 2013.

All the information regarding program will be presented in the program [http://www.itcollege.ee/en/co-operation/dits2013/ web page].

=Assignments=

==Security testing of web application==

===Description===
Learn about the security of web applications.
Find vulnerabilities from known vulnerable web applications.
Find not known vulnerabilities of development version of web application
Study Information Portal (Used by eleven universities of applied
science in Estonia)
File report that describes methods, tests and findings.

===Expected outcome===
Description of testing methods and findings (all vulnerabilities that
students found in development environment) as testing report.

===Expectations from students===
Understanding web applications (What is difference of GET and POST, how
sessions work, what is header etc).
Knowledge of at least one web programming language (php, java, ruby, C#, python is preferred)

===Lectures support===
Several security related topics will covered during lectures and
practical classes before starting actual testing.
Lecture covers several attack types and vulnerabilities like SQL
injection, cmd injection, XSS, CSRF etc. Practical classes based on DVWA
(Damn Vulnerable Web Application)
After lectures and practical classes students will get access to web
application development environment for practical work.

[http://elab.itcollege.ee:8000/DITS2013/ Lecture/Lab materials and virtual machines]

Lecturer: Margus Ernits (Estonian IT College)

==Driving lessons registration information system==

===Description===
It is a client-server solution which keeps records of student's driving lessons.
Each driving study car has a device / computer where client application runs.

===Expected outcome===
Client application registers the student’s driving lesson time and the GPS
coordinates and sends them to the server over the mobile Internet.
Client application must register driving lessons also without Internet connection
and synchronize with the server when connection is established.
Later a student can check ones driving lesson and travel route on the Internet.

===Limitations===
GPS accuracy at least one point per second.

==Improving toolset for race sailing performance analysis==

===Description===
Implementation of logger that could be used for performance analysis of race sailing teams,
based on data specification for communication between marine electronic devices NMEA
0183.
Learning about the performance analysis needs and specifics of race sailing teams, also
learning about the marine instruments specifics and communication standard NMEA 0183.
Based on core architecture of the NMEA 0183 data logger implementation including
software, hardware and testing.

===Expected outcome===
Fully functioning and tested race sailing performance analysis data logger.

===Expectations from students===
Aspiration to develop in rapid prototyping and testing environment together with professional
and Olympic Team race sailors and marine technology specialists fully functional
performance analysis logger. Both software and hardware development skills. If you can
understand and are interested in what is described
at http://www.boatdesign.net/forums/attachments/onboard-electronics-controls/19260d1204757550-laptop-interface-tacktick-nmea-architecture.png then you are
expected to join team.

===Lectures support===
Lectures and seminars will cover first the needs specification of the performance analysis
logger, NMEA0183 standard description, marine instruments Received Sentences description:
DBT, DPT, GLL, HDG, HDM, MTW, MWV, RMB, RMC, VHW, VLW, VWR. Team will
implement the logger and install the marine wireless range instrument for testing on actual
performance sailing boat. Life saving equipment and wetsuits not needed :)

Lecturer: Linnar Viik (Estonian IT College)

==Robotic competitions organization software system==

===Description===
The software system provides everything from participant registration to the live competition carry out
by the referees. It contains web based interfaces and real-time applications such as score and time
overlay on video broadcast. Different competition (tournament) formats are needed. As much as
possible smart solutions and freely available components shall be used in order to keep the
development time short.

===Expected outcome===
System design description including component, database and sequence diagrams. Suggestion on
database, programming language and reusable components is expected. Creating a project time plan
with at least two scenarios (full scope, minimum scope) is secondary objective. Prototype solution
covering some part of the system would be a bonus task.

===Expectations from students===
Knowledge of database- and web programming. Understanding of software architectures such as MV is
appreciated.

==E-teacher==

In the course of studying Database Fundamentals the students, as independent coursework, must draw ERD-
schemes. Although there is no use of drawing the diagrams if the lector doesn’t give feedback on the success
or failure of said work. The whole process of drawing ERD-diagrams looks like any other teaching process-
The teacher prepares the task, the student draws the ERD-diagram and hands it to the teacher, The teacher
then looks it over and corrects/improves/comments it then returning it to the student. The specificity in here
being that the solutions of the tasks are graphic and no task has one concrete solution – every student solution
is different. This makes every revision unique- the teacher must understand the undergrads intention, check
its compliance whit the task set and then if needed make changes in the model without changing its nature.

For now it has always been done on paper – Undergrad draws a ERD case system model, prints it and hands
it to the lecturer; the lecturer, if needed, corrects it with a pen , writes their comments and the non-grading
evaluation and returns it to the undergrad. The lector marks the results of the test in their ÕIS table.

This process doesn’t exist electronically because during the semester there are many undergrads (ca 140-150)
and there are no comfortable ways to grade them QUICKLY electronically. Herewith, when the lector gets
the work printed on paper he is capable of correcting them with haste. Hence it raises two main problems that
need solving. The Schemes sent on paper must be replaced by electronically forwardable materials and a way
to revise/correct electronically presented ERD quick must be created.

Past couple of years have brought with them the development of portable computer user interface – There are
touch screens and electronic pens, with which one can draw on a computer screen. From there springs the
thought, of making an application for correction of such works, where the lector writes the
corrections/notes/comments directly on the work presented by the undergrad. Using an electronic pen.

The process itself should look like this:
# The undergrad creates an ERD‐diagram and presents it in some from, that is editable by the pen (Would be best if the format permitted layers, for both the teacher and the student, so if needed the teachers additions could be „turned off
# The undergrad logs into the portal where their tests are to be presented and uploads their work. (the status becomes „presented“)
# The lector makes the corrections and adds the grade (the status of the work becomes „graded“; the evaluation can either be „accepted“, „needs personal discussion “ or „Must be reapplied“)
# The undergrad finds out their grade. If needed presents the work again.

Notes:
# The form of the presentation and the correction must be chosen
# The environment should allow the setting of the time for the discussion and medium if the lector wished for it (Time and place of direct contact; Skype etc.)
# The lector must be able to note the appointment
# The system must send an email to the lector if there is a wish for discussion

==A Professional too valuable to lose==

Andrew Bessett (45) is an experienced systems administrator with nearly
20 years of experience in both Microsoft and Unix-like systems. His successful career as a leading sysadmin of Shelley's, a high-profile London insurance company, got a serious setback in Februrary 2012 when the British Airways flight 6201 from Dubai to London with 146 passengers onboard crashed in the Austrian Alps due to bad weather and control system malfunction. Andrew, returning from his winter vacation, was one of the 12 survivors. However, he suffered serious injuries. His two upper vertebrae were smashed on impact, his hands suffered third-degree burns and had to be amputated - right at the shoulder, left at the elbow.

After spending a year in a rehabilitation programme at the Royal National Orthopaedic Hospital in Stanmore, London, he has decided to return to his work. His condition has stabilized but has left him practically paralyzed from neck down - he can move his head and (with very limited power and range) his remaining part of the left hand. He had to use respirator after the accident, but has recovered enough to breathe freely. His speech, hearing, vision and mental aptitude have survived fully intact and he has retained most of his professional skills (interrupted only by the year in therapy). He uses a joystick-controlled powered wheelchair as a means of transportation.

The company has decided to re-hire Andrew if he can prove his ability to handle most of his earlier duties. You are his technical advisory team and have to draft a suitable workstation and necessary software, plus all the necessary amendments in the company infrastructure (premises, workspace, hardware, networking, typical configuration of servers and workstations, intranet, mobile communication, website etc) to allow him return to work. Note: The IT infrastructure at Shelley's makes extensive use of both Microsoft Windows and Debian GNU/Linux platforms.

=Teams and their assignments=
[http://enos.itcollege.ee/~saus/Activity_Chart_Template.xlsx Activity chart]

==Sailing pirates==

Assignment: [[#Improving toolset for race sailing performance analysis|Improving toolset for race sailing performance analysis]]

Documentation: [[Sailing pirates]]

====Members====
* Kristjan Tõnismäe, The Estonian Information Technology College
* Konstantinos Verigos, Technological Educational Institute of Crete
* Stefanos Athanasiadis, Technological Educational Institute of Crete
* Tommi Potapoff, Vaasa University of Applied Sciences
* Jesse Koski, Vaasa University of Applied Sciences
* Mikko Heikkuri, Vaasa University of Applied Sciences

==Security==

Assignment: [[#Security testing of web application|Security testing of web application]]

Documentation: [[Security]]

====Members====
*Sten Aus, Estonian Information Technology College
*Matis Palm, Estonian Information Technology College
*Sandra Suviste, Estonian Information Technology College
*Markus Rintamäki, Vaasa University of Applied Sciences
*Tomas Lepistö, Vaasa University of Applied Sciences
*Mika Salmela, Vaasa University of Applied Sciences
*Kęstutis Tautvydas, Vilnius University of Applied Sciences
*Jurij Lukjančikov, Vilnius University of Applied Sciences

==Team Robo==

Assignment: [[#Robotic competitions organization software system | Robotic competitions organization software system]]

Documentation: [[Team Robo]]

====Members====
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Giorgos Ioannidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Konstantinos Michailidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia

==Team ET==

Assignment: [[#E-teacher|E-teacher]]

Documentation: [[ET]]

===Members===
* Indrek Mitt, IT College
* Sander Saarm, IT College
* Panagiota Chatzi, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Nikolaos Karadimitriou , T.E.I. of Crete, Department Of Applied Informatics And Multimedia

==Team Driving Lessons==

Assignment: [[#Driving lessons registration information system|Driving lessons registration information system]]

Documentation: [[Driving lessons]]

===Members===
* Irena Adamowicz, Vilnius University of Applied Sciences
* Aleksas Janulevičius, Vilnius University of Applied Sciences
* Vilius Nedzveckas, Vilnius University of Applied Sciences
* Rene Pärnpuu, Estonian Information Technology College
* Xiangwei Zuo, Estonian Information Technology College
* Giannis Christofakis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia

ET

2013-03-29T15:29:12Z

Ssaarm:

2013-03-29T11:23:59Z

Ssaarm: /* Friday - 29.03.13 */

Team page for [[E-teacher]].

===Members===
* Indrek Mitt, IT College
* Sander Saarm, IT College
* Panagiota Chatzi, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Nikolaos Karadimitriou, T.E.I. of Crete, Department Of Applied Informatics And Multimedia

==Goal==
*Goal 1 form assignment
*Goal 2 form assignment
*Goal 3 form assignment

==Activity==
===Monday - 25.03.13===
Things what we did that day
* Learned about documentation and data mining
* Programmed sumo robots
* Got to know our team at welcome dinner in St. Patrick's

===Tuesday - 26.03.13===
Things what we did that day
* Talked about our case and made sure everybody is on the same page
* Put together a list of questions for our client
* Thought of different solutions for our project
* Seperated tasks between team members

Problems what we faced:
* We didn't have enough information about our case
* We wanted to use Moodle, but we didn't know if it's suitable for our project

Things what we plan to do:
* Ask our mentor if Moodle environment suitable for our project
* Prepared to speak to our client Priit Raspel

===Wednesday - 27.03.13===
Things what we did that day
* Spoke to our clent Priit Raspel.
* Learned about Moodle and installed it.

Problems what we faced:
* We couldn't access installed Moodle on Sander's computer.
* We needed a laptop with touchscreen.

Questions and answers from client (consultation)
* The client explained his visions on the project, that were quite similar to our vision. So we didn't have many questions.
* Mostly we talked about the user interface on the teacher's side. We got to know his exact requirements.
* We got telefon numbers of our client and our mentor for further questions.
* We asked about Moodle and it's API from our mentor Mart Mangus.
* We asked for client's touchscreen laptop for two weeks' testings and we got it.

Things what we plan to do:
* Need to get a wireless router form Indrek Rokk for our own network to access installed Moodle.
* Get to know Moodle's API.
* Creating user interface.

===Thursday - 28.03.13===
Things what we did that day
* Had lecture about Innovation
* Studied Moodle documentation
* Set up our Moodle test environment
* Created test course and users
* Checked if Moodle has needed options for our client's specific needs
* Nikolaos is programming the UI
Problems what we faced:
* Had little problems setting up our workstation
* Some network problems
Things what we plan to do:
* Work more on UI
* Try if Moodle's options and API are enough to continue

===Friday - 29.03.13===
Things what we did that day
* Read the documentation about API in Moodle
* We separated the practical part of documentation & we tried to be familiar with the staff.
* We created and enrolled users in order to put some necessary and specific requirements that our client wants
* We logged in as admin, teacher, student to make the proper tests

Problems what we faced:
*

Things what we plan to do:
*

===Saturday - 30.03.13===
Cultural Estonia's day

===Monday - 01.04.13===
Things what we did that day
*

Problems what we faced:
*

Things what we plan to do:
*

===Tuesday - 02.04.13===
Things what we did that day
*

Problems what we faced:
*

Things what we plan to do:
*

===Wednesday - 03.04.13===
Things what we did that day
*

Problems what we faced:
*

Things what we plan to do:
*

===Thursday - 04.04.13===
Things what we did that day
*

Problems what we faced:
*

Things what we plan to do:
*

===Friday - 05.04.13===
Things what we did that day
*

==Results==
Summary of what we did and solution what we developed

===Final documentation===
====Analysis====

====Solution====

==IP Feedback==
===Indrek Mitt feedback===
I liked this and that.

===Sander Saarm feedback===
I liked this and that. Didn't like.

===Panagiota Chatzi feedback===
I liked this and that.

===Nikolaos Karadimitriou feedback===
I liked this and that. Didn't like.