First commit!

Author: alranel

README.md

@@ -0,0 +1,18 @@
+# Arduino @ Google Summer of Code
+
+Arduino is applying as a mentoring organization for GSoC 2020. This repository stores the relevant information.
+
+[Arduino](https://arduino.cc) is an open source electronics platform based on easy-to-use hardware and software. It's intended for anyone making interactive projects. Over the years Arduino has been the brain of thousands of projects, from everyday objects to complex scientific instruments. A worldwide community of makers - tens of millions of students, hobbyists, artists, programmers, and professionals - has gathered around this open-source platform, their contributions have added up to an incredible amount of accessible knowledge that can be of great help to novices and experts alike.
+
+[Google Summer of Code](https://summerofcode.withgoogle.com/) is an annual open source internship program sponsored by Google. For general information about the program, including this year's application timeline and key phases involved, please see the [GSoC website](https://summerofcode.withgoogle.com/how-it-works/).
+
+## Why should I work with Arduino?
+
+Arduino is fully committed to creating open source hardware and software. The Arduino community is one of the largest tech communities in the world, and our collaborative efforts have a big impact on democratizing electronics. Working with us is a great opportunity to work on code that is used daily by millions of people. The quality of the Arduino hardware as well as the Arduino software and libraries is what glued this community: will you work with us to improve all this?
+
+## How can I apply?
+
+Read [this document](how-to-apply.md) to learn how to apply for the GSoC program with Arduino. Please also check out our [ideas list](ideas.md).
+
+For any questions, please open an issue in our [issue tracker](https://github.com/arduino/summer-of-code/issues) or send an e-mail to [[email protected]](mailto:[email protected]).
+

how-to-apply.md

@@ -0,0 +1,56 @@
+# GSoC @ Arduino: Application Instructions
+
+## Before you apply
+
+If you are a student interested in submitting a proposal to CC, start by checking out our [Project Ideas](ideas.md) page to find an idea that you would like to write a proposal to work on during GSoC.
+
+Take a look at the [Arduino website](https://arduino.cc) to learn more about what we do. Also look at our GitHub organizations ([arduino](https://github.com/arduino) and [arduino-libraries](https://github.com/arduino-libraries)) and our [forum](https://forum.arduino.cc) to get a sense of the code and projects we work on. Making a successful contribution to one of our projects will help us get a sense of your work and is highly recommended.
+
+## Expectations
+
+### During the application phase
+
+_These tips can help your application! They are not strictly required._
+
+* Read the official [GSoC student guide](https://google.github.io/gsocguides/student/) and the [GSoC FAQ](https://developers.google.com/open-source/gsoc/faq).
+* Review our [ideas list](ideas.md) and ask questions about projects you're potentially interested in on the [issue tracker](https://github.com/arduino/summer-of-code/issues)
+* Once you've decided on a project, follow these Application Instructions to write a draft proposal.
+* Experience shows that the best thing to help your application is to contact the organization you want to work with early. For this you can introduce yourself on our [GSoC issue tracker](https://github.com/arduino/summer-of-code/issues), and perhaps fix a small bug in our of our repositories and link it in your introductive post. 
+* Get feedback from us before you submit a final application.
+* If you're proposing a project that's not on our official ideas list, please talk to us to see if there is any mentor interested in mentoring that project before you put any work into the proposal.
+
+### During the community bonding period
+
+* Continue to plan your project with your mentor and the community.
+* Get an Arduino (an original one!) and familiarize with it so that you know what you're working for.
+
+### During the summer
+
+* Write a short report for us every second week in a public forum topic.
+* Work 30-40 hours per week (or agree on a different plan with your mentor ahead of time).
+* Commit early and commit often! Push to a public GitHub repository so that we can see and review your work.
+* Actively work on our project timeline and communicate with us during the community bonding period.
+* Be available on Slack whenever you are working and post at least once a (work) day to talk about what you're working on that day.
+* If there is a reason why you can't work or can't contact us on a regular basis please make us aware of this in advance.
+* If you don't communicate with us regularly, we will fail you.
+* Set a realistic goal for all evaluation deadlines. If you fail to meet your own goal we are more likely to fail you in the evaluations.
+* Be proactive about asking for help, especially when you're stuck.
+
+## Applying
+
+### How to write a great proposal
+
+Your proposal must be submitted through the Google Summer of Code website. It is a good idea to submit drafts and get feedback from CC mentors before you submit your final proposal.
+
+Please read and follow the [GSoC student guide on writing proposals](https://google.github.io/gsocguides/student/writing-a-proposal). Also:
+
+* Don't be afraid to give us lots of detail about how you would approach the project.
+* Our application should make us believe that you are capable of completing the project and delivering the functionality to our users. If you aren't sure about anything, get in touch with us, we're happy to advise you.
+
+You can use our [base template](proposal-template.md) to draft your application in Markdown format. If you don't know what Markdown is, we recommend you familiarize with it anyway ;-)
+
+Your final proposal must be submitted to GSoC as a PDF file, so you can use Pandoc to generate one from your Markdown file:
+
+```
+$ pandoc -f markdown -t pdf your-name.md
+```

ideas.md

@@ -0,0 +1,36 @@
+# GSoC @ Arduino: Ideas List
+
+## Write examples for official libraries
+
+[Libraries](https://www.arduino.cc/en/reference/libraries) are a fundamental component of Arduino. They allow users to enrich their applications with advanced functionality or to support shields, sensors, actuators connected to their Arduino board.
+We now have more than 70 [official libraries](https://github.com/arduino-libraries), in addition to 2,400+ contributed libraries.
+Many of those official libraries need more examples in order to help users understand how they can be used. Examples are located in the same repository as the library itself.
+
+* *Languages:* C++
+* *Difficulty:* Easy/Medium (according to the libraries complexity)
+* *Note:* your application should contain a list of libraries which need examples and which you would like to work on.
+
+## Write MicroPython examples and tools for Portenta
+
+The new [Portenta](https://www.arduino.cc/pro/hardware/product/portenta-h7) board supports [MicroPython](https://micropython.org) in addition to Arduino code. This combination opens up many new opportunities. This task is about writing examples about using MicroPython on a Portenta board.
+
+* *Languages:* Python, C++
+* *Difficulty:* Medium/Advanced
+* *Note:* accepted students will be sent a free Portenta board.
+
+## Write JerryScript (JavaScript) examples and tools for Portenta
+
+The new [Portenta](https://www.arduino.cc/pro/hardware/product/portenta-h7) board supports [JerryScript](https://jerryscript.net) in addition to Arduino code. This combination opens up many new opportunities. This task is about writing examples about using MicroPython on a Portenta board.
+
+* *Languages:* JavaScript, C++
+* *Difficulty:* Medium/Advanced
+* *Note:* accepted students will be sent a free Portenta board.
+
+## Add network discovery support to arduino-cli
+
+[arduino-cli](https://github.com/arduino/arduino-cli) is a command line tool for programming Arduino boards. This task is about implementing a functionality for discovering boards over network in addition to USB.
+See more details in https://github.com/arduino/arduino-cli/issues/344
+
+* *Languages:* Go
+* *Difficulty:* Advanced
+

proposal-template.md

@@ -0,0 +1,61 @@
+#  Title 
+
+## Abstract
+
+Short description of your project. Max 10 sentences. This **SHOULD NOT** be a
+copy of the project idea text.
+
+## Technical Details
+
+Long description of the project. **Must** include all technical details of the
+projects, like libraries involved.
+
+Here you can show relevant pieces of code that you want to change. You can
+link to literature you used during the research.
+
+## Schedule of Deliverables
+
+Here should come a list of your milestones. This list is a start based on the
+difference phases of GSoC. Use it as a start. You can/should add more details
+for each phase by breaking it down into weeks or set specific targets for each
+phase. Each target should be split into sub task with a time estimate, [work
+breakdown structures](https://en.wikipedia.org/wiki/Work_breakdown_structure) are helpful here.
+
+### **Community Bonding Period**
+
+What will you do during the community bonding period?
+
+### **Phase 1**
+
+Deliverables
+
+### **Phase 2**
+
+Deliverables
+
+### **Final Week**
+
+At this stage you should finish up your project. At this stage you should make
+sure that you have code submitted to your organization. Our criteria to mark
+your project as a success is to submit code before the end of GSoC.
+
+## Development Experience
+
+Do you have code on GitHub? Can you show previous contributions to other projects?
+Did you do other code related projects or university courses?
+
+Do you have experience with Arduino?
+
+## Other Experiences
+
+...
+
+
+## Why this project?
+
+Why you want to do this project?
+
+## Do you have any other commitments during the GSoC period?
+
+Provide dates, such as holidays, when you will not be available.
+