Doc: GsoC first public draft of documentation (#2092)

* GSoC root file

This is the root file for the Google Summer of Code program

* Fixed TOC

* Introduction to GSoC with Joplin

The first draft cloned from https://community.kde.org/GSoC

* Joplin's Application at GSoC template

Cloned from https://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2019/Organisation_application

* GSoC 2019, idea #1: deeper Nextcloud integration

* GSoC 2019, idea #2: sharing notes

* GSoC 2019, idea #2: tag handling

* GSoC 2019, idea #4: search improvements

* GSoC 2019, idea #5: per note password protection

* Update GSoC_Idea#1.md

* Update GSoC_Idea#2.md

* Rename GSoC_Idea#2.md to GSoC_Idea#2_sharing.md

* Rename GSoC_Idea#1.md to GSoC2019_Idea#1_Nextcloud.md

* Rename GSoC_Idea#2_sharing.md to GSoC2019_Idea#2_sharing.md

* Update and rename GSoC_Idea#3.md to GSoC2019_Idea#3_tagging.md

* Rename GSoC_Idea#4.md to GSoC2019_Idea#4_Search.md

* Rename GSoC_Idea#5.md to GSoC2019_Idea#5_Password per Note.md

* Update GSoC2019_Idea#1_Nextcloud.md

* Create GSoC2019.md

cloned from https://community.kde.org/GSoC/2019/Ideas

* Rename Introduction.md to GSoCIntroduction.md

* Rename GSoCIntroduction.md to GSoC_Introduction.md

* Rename Application.md to GSoC_Application.md

* first draft of a public introduction and project idea page, plus first (filled) template for ideas

* added idea

* started to update org details

* Delete GSoC_Application.md

moved to forum

* Update summer_of_code.md

put the template in a <details> block. little improvements where to publish ideas and applications

* Update summer_of_code.md

put application in quote

readme/GSoC/GSoC2019.md

@@ -0,0 +1,21 @@
+
+
+2020 is Joplin first round at Google Summer of Code, so excuse some incompleteness here.  
+Detailed information on how to get involved and apply are given in the general Summer of Code introduction. 
+
+**These are all proposals! We are open to new ideas you might have!!** Do you have an awesome idea you want to work on with Joplin but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of Joplin.
+
+### Information for Students
+
+These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, you are urged to contact the developers and find out more about the particular suggestion you're looking at.
+
+Becoming accepted as a Google Summer of Code student is quite competitive. Accepted students typically have thoroughly researched the technologies of their proposed project and have been in frequent contact with potential mentors. **Simply copying and pasting an idea here will not work.** On the other hand, creating a completely new idea without first consulting potential mentors rarely works.
+
+# Ideas
+
+- deeper integration in collaborations application such as Nextcloud
+- introduce sharing future
+- Improve tagging
+- Improve the search engine
+- Password-protection of a single note
+- Multiple synchronization targets

readme/GSoC/GSoC2019_Idea#1_Nextcloud.md

@@ -0,0 +1,43 @@
+# Nextcloud notes integration (Web client)
+
+## What is the goal of the project 
+
+There is the community's wish to have the notes integrated Nextcloud, so that Notes can be sought by Nextcloud itsself. Although this idea focuses on Nextcloud it shall allow to extend it to other collaboration applications going beyond the current scope of  [Synchronisation](https://joplinapp.org/#synchronisation).
+
+There is already the [web application](https://github.com/foxmask/joplin-web) what may can be integrated in collaboration application
+
+### what shall be answered in the application
+
+
+
+## Why shall this idea be realized 
+
+Allowing broader use of the application and better integration of the existing open source world, we don't want to invent the wheel twice
+
+## Who is talking about it
+
+The idea is outcome of (but not limited to) of some discussion taking place in the Forum and on GitHub: 
+
+- [Support Joplin structure and notebooks #248](https://github.com/nextcloud/notes/issues/248)
+- [Joplin Web](https://discourse.joplinapp.org/t/joplin-web-web-application-companion-for-joplin/555)
+- [New search engine in Joplin](https://discourse.joplinapp.org/t/new-search-engine-in-joplin/1479)
+- [How is WebDAV sync implemented?](https://discourse.joplinapp.org/t/how-is-webdav-sync-implemented/3102)
+- [Nextcloud notes integration (Web client)](https://github.com/laurent22/joplin/issues/228)
+
+----
+
+COMMENTS:
+
+1. “Nextcloud notes integration (Web client)” is not well defined. What would be nice is a built-in Nextcloud web client for Joplin. But the top post in there is about something else that won’t be changed (explained in the FAQ: https://joplinapp.org/faq/#is-it-possible-to-use-real-file-and-folder-names-in-the-sync-target)
+
+2. That would be interesting to know what they think about such an integration and how they see it because it’s an old subject, we (the staff) are periodically debating:
+
+   - https://github.com/laurent22/joplin/issues/228
+   - https://discourse.joplinapp.org/t/nextcloud-fanboy-quest-ce-quils-veulent/844/3
+
+   I imagined they just need a joplin-api in PHP and “plug” it on the right datasource to switch between “Nextcloud native note/Qownote” to Nextcloud/Qownnote “Joplin note”.
+
+3. “How is WebDAV sync implemented?” appears twice. It should only be in Summer of Doc.
+
+   
+

readme/GSoC/GSoC2019_Idea#2_sharing.md

@@ -0,0 +1,13 @@
+sharing
+
+- [Feature Request: Multiple note directories #108](https://github.com/laurent22/joplin/issues/108)
+- [[Feature Request\] Note Sharing #1085](https://github.com/laurent22/joplin/issues/1085)
+- [[Feature Request\] Multiple synchronization targets #1293](https://github.com/laurent22/joplin/issues/1293)
+- ([Please give the ability to share from another Android app into Joplin. #110](https://github.com/laurent22/joplin/issues/110))
+- ([Mobile - Add share menu #876](https://github.com/laurent22/joplin/issues/876))
+- [Turtl’s sharing - Choose who you share with and what they can do.](https://turtlapp.com/features/)
+- [Turtl Documentation - App architecture](https://turtlapp.com/docs/architecture)
+
+
+“Please give the ability to share from another Android app into Joplin”: This is already done
+

readme/GSoC/GSoC2019_Idea#3_tagging.md

@@ -0,0 +1,16 @@
+tag handling
+
+- [[Feature Request\] Tags on whole markdown lines #1498](https://github.com/laurent22/joplin/issues/1498)
+- [[Feature Request\] Option to have a space for tags after the title #1399](https://github.com/laurent22/joplin/issues/1399)
+- [Feature request: set @tags from markdown editor #1407](https://github.com/laurent22/joplin/issues/1407)
+- [So many tags #1221](https://github.com/laurent22/joplin/issues/1221)
+- [Organize and share using Turtl’s Spaces.](https://turtlapp.com/features/)
+
+
+
+“[Feature Request] Tags on whole markdown lines #1498”: I prefer we remove this as this too far from standard markdown.
+
+“Feature request: set @tags from markdown editor #1407”. I prefer if we remove this too for the same reason. I think tagging is already easy since there’s a keyboard shortcut for it. Maybe back then there wasn’t.
+
+“So many tags #1221”: Was a bug, which has been fixed.
+

readme/GSoC/GSoC2019_Idea#4_Search.md

@@ -0,0 +1 @@
+[Search engine improvements](https://github.com/laurent22/joplin/issues/1877)

readme/GSoC/GSoC2019_Idea#5_Password per Note.md

@@ -0,0 +1,8 @@
+additinal protection per note
+
+- [[Feature request\] Password or pin protection](https://github.com/laurent22/joplin/issues/289)
+- [[Suggestion\] Add instructions to generate app-specific password enhancement](https://github.com/laurent22/joplin/issues/419)
+- [Turtl Documentation - Security and encryption](https://turtlapp.com/docs/security)
+
+
+[Password or pin protection](https://github.com/laurent22/joplin/issues/289): It’s very unclear what people want. It seems the threat model is you give your unlocked phone or laptop to someone, and you don’t want them to see your notes. But of course, the solution is to not do that. All devices these days support multiple accounts, so there’s no point giving their unlocked device to someone they don’t trust. I think we should remove this issue until it’s betted defined. Perhaps it should go to a different category like, “to be specified”. We need to know what’s the threat model, what people want. I’ve heard dozens of variations (locking the app, obfuscating the data, encrypting the data, encrypting a note, a notebook, encrypting a part of a note, etc.) so it’s unclear what needs to be done. I guess for me it seems so unnecessary  that I can’t quite wrap my head around it. 

readme/summer_of_code.md

@@ -0,0 +1,149 @@
+Joplin has a young but well proven history. It all started by single idea but is rising more and more commitment as well as demands. 
+Joplin is about to make another big step to answers these demands by applying at Google Summer of Code.
+All students and Joplin users and developers are welcome to participate in the hopefully first year Summer of Code program with Joplin. Here's how.
+
+Mentors, administrators and students: read [Summer of Code](https://developers.google.com/open-source/gsoc) occasionally. Also read the [Summer of Code FAQ](https://developers.google.com/open-source/gsoc/faq).
+
+All participants will need a Google account in order to join the program. So, save time and create one now. In addition, all participants need to join the  [Joplin Forum](https://discourse.joplinapp.org). 
+
+### Programming Language                  
+
+All application share the same back-end written in JavaScript (Node.js), with Redux for state management. The back-end runs locally.
+
+The GUI's, as listed on the [Joplin's website](https://joplinapp.org/#installation)  are use
+
+- ClL: terminal-kit
+- Desktop: Electron
+- Mobile: React Native
+
+More details can be found on 
+
+- [How to contribute]( https://github.com/laurent22/joplin/blob/master/CONTRIBUTING.md ) 
+- [How to build]( https://github.com/laurent22/joplin/blob/master/BUILD.md#building-the-tools) 
+
+Moreover there are community driven projects such as 
+
+- [Joplin  Web](https://github.com/foxmask/joplin-web)
+
+Submissions and ideas for projects in any other language should specifically mention the choice.
+
+## Instructions for students
+
+Students wishing to participate in Summer of Code must realize, that this is a important professional opportunity. You will be required to produce applicable and readable code for Joplin in 3 months. Your mentors, will dedicate a portion of their time to mentoring you. Therefore, we seek candidates who are committed to helping Joplin and its community long-term and are willing to both do quality work, and be proactive in communicating with your mentor(s).
+
+You don't have to be a proven developer -- in fact, this whole program is meant to facilitate joining Joplin and other Open Source communities. However, experience in coding and/or experience with the above mentioned programming languages and the applications is welcome. 
+Currently there is only [How to contribute]( https://github.com/laurent22/joplin/blob/master/CONTRIBUTING.md ) and [How to build]( https://github.com/laurent22/joplin/blob/master/BUILD.md#building-the-tools) but more details are bout to come on how to interact and how to commit. 
+In general it can be said, that question shall be asked early and clearly, given everyone the possibility to understand why you want to have this question answered and how it helps to achieve the project's goal.
+
+Before you can be accepted as a student we expect you to fix some bugs and link that work on your proposal. 
+
+You should start learning the components that you plan on working on before the start date. Support can be found in the forum and on our dedicated discourse channel. 
+Do not worry, the the timeline from Google reserves a lot of time for bonding periods but use that time wisely. Good communication is key. To allow us to respond quickly tag your questions with #GSoC and #2020. 
+You should plan to communicate with your team several times per week, and formally report progress and plans weekly. You are free to chose the format, it can be an sophisticated online document or simple continuous blog on GitHub.  
+Moreover, we require that you come to clear agreement on how to commit, test and build. We don't see us loosing time on how to test instead accentually testing your commits. 
+**Students who neglect active communication will be failed**. 
+
+### General instructions
+
+First of all, please read the above referenced resources and the [GSoC FAQ](https://developers.google.com/open-source/gsoc/faq). Pay special attention to the **Eligibility** section of the FAQ.
+
+### Recommended steps
+
+1. Join the [Joplin Forum](https://discourse.joplinapp.org), introduce yourself, and meet your fellow developers in the [Development category](https://discourse.joplinapp.org/c/development)
+2. Read Student proposal guidelines and the [GSoC Student Manual](https://developers.google.com/open-source/gsoc/resources/manual#student_manual)
+3. Take a look at the [list of ideas]. You can have you own idea addeed by posting it in the [Features category](https://discourse.joplinapp.org/c/features)
+4. Come up with project that you're interested in and discusse it in [Development category](https://discourse.joplinapp.org/c/development)
+5. Write a first draft and get someone to review it
+6. Remember: you must link to work such as commits in your proposal. A private place will be created wihtinn the forum for that purposes.
+7. Read [How to write a kickass proposal for GSoC](http://teom.org/blog/kde/how-to-write-a-kick-ass-proposal-for-google-summer-of-code/)
+8. Submit proposal using [Google's web interface](https://summerofcode.withgoogle.com/) ahead of the deadline
+9. Submit proof of enrollment well ahead of the deadline
+
+Coming up with an interesting idea is probably the most difficult part. It should be something interesting for Joplin, for Open Source in general and for you. And it must be something that you can realistically achieve in the time available to you.
+
+A good start is finding out what the most pressing issues are in the projects in which you are interested. Join the forum and subscribe to GitHub repository for that project or go into its discourse channel: meet developers and your potential mentor, as well as start learning the code-base. We recommend strongly getting involved in advance of the beginning of GSoC, and we will look favorably on applications from students who have already started to act like Open Source developers.
+
+### Student proposal guidelines
+
+A project proposal is what you will be judged upon. Write a clear proposal on what you plan to do, the scope of your project, and why we should choose you to do it. Proposals are the basis of the GSoC projects and therefore one of the most important things to do well. The proposal is not only the basis of our decision of which student to choose, it has also an effect on Google's decision as to how many student slots are assigned to Joplin.
+
+<details>
+  <summary>Below is the application template.</summary>
+  
+>  **Introduction**
+>
+>  Every software project should solve a problem. Before offering the solution (your Google Summer of Code project), you should first define the problem. What’s the current state of things? What’s the issue you wish to solve and why? Then you should conclude with a sentence or two about your solution. Include links to discussions, features, or bugs that describe the problem further if necessary.
+>
+> **Project goals**
+>
+>Be short and to the point, and perhaps format it as a list. Propose a clear list of deliverables, explaining exactly what you promise to do and what you do not plan to do. “Future developments” can be mentioned, but your promise for the Google Summer of Code term is what counts.
+>
+>**Implementation**
+>
+>Be detailed. Describe what you plan to do as a solution for the problem you defined above. Include technical details, showing that you understand the technology. Illustrate key technical elements of your proposed solution in reasonable detail. Include writing unit tests throughout the coding period, as well as code documentation. These critical elements cannot be left to the last few weeks of the program. If user documentation will be required, or apidox, etc. these should be written during each week, not at the end.
+>
+>**Timeline**
+>
+>Show that you understand the problem, have a solution, have also broken it down into manageable parts, and that you have a realistic plan on how to accomplish your goal. Here you set expectations, so don’t make promises you can’t keep. A modest, realistic and detailed timeline is better than promising the impossible.
+>
+>If you have other commitments during GSoC, such as a job, vacation, exams, internship, seminars, or papers to write, disclose them here. GSoC should be treated like a full-time job, and we will expect approximately 40 hours of work per week. *If you have conflicts, explain how you will work around them.* If you are found to have conflicts which you did not disclose, you may be failed.
+>
+>Open and clear communication is of utmost importance. **Include your plans for communication in your proposal; daily if possible.** You will need to initiate weekly formal communication such as a blog post on to be agreed placed. Lack of communication will result in you being failed.
+>
+>**About me**
+>
+>Provide your contact information (IRC nick, email, IM, phone) and write a few sentences about you and why you think you are the best for this job. **Prior contributions to Joplin are required; list your commits.** Name people (other developers, students, professors) who can act as a reference for you. Mention your field of study if necessary. Now is the time to join the relevant irc/telegram channels, mail lists and blog feeds. We want you to be a part of our community, not just contribute your code.
+>
+>*Tell us if you are submitting proposals to other organizations, and whether or not you would choose Joplin if given the choice.*
+>
+>*Other things to think about:*
+>
+>- Are you comfortable working independently under a supervisor or mentor who is several thousand miles away, and perhaps 12 time zones away? How will you work with your mentor to track your work? Have you worked in this style before?
+>
+>- If your native language is not English, are you comfortable working closely with a supervisor whose native language is English? What is your native language, as that may help us find a mentor who has the same native language?
+>
+>- After you have written your proposal, you should get it reviewed. Do not rely on the Joplin mentors to do it for you via the web interface, although we will try to comment on every proposal. It is wise to ask a colleague or a developer to critique your proposal. Clarity and completeness are important.
+ 
+</details>
+
+### Hints
+
+**Submit your proposal early**: early submissions get more attention from developers because that they have more time to read them. The more people see your proposal, the more it will be discussed.
+
+**Do not leave it all to the last minute**: while it is Google that is operating the webserver, it would be wise to expect a last-minute overload on the server. So, be sure you send your application and proof of enrollment before the final rush. Also, applications submitted very late will get the least attention from mentors, so you may get a lower vote because of that. Submitting a draft early will give time for feedback from prospective mentors.
+
+**Keep it simple**: Be concise and precise. Provide a clear, descriptive title. "My Project" is the worst possible title!
+
+**Know what you are talking about**: Do not submit proposals that cannot be accomplished over a summer or that are not related to Joplin. If your idea is unusual, be sure to explain why you have chosen Joplin to be your mentoring organization.
+There could be exceptional reason to accept proposal what cannot be finished over the sumer if either it is clearly recognisable that there will be commitment beyond the summer period or the project can be well separated in sub-project. If you want to go that way, your proposal must be very easy readable to allow us to evaluate the changes of a project going through several coding programs. 
+
+**Aim wide**: submit more than one proposal. You are allowed to submit to another organisation as well. If you do submit more than one proposal, tell us that and which proposal you would choose, if both were selected. Former students would advise you to do one or two kick-ass proposals rather than trying to do three.
+
+### Accepted Students
+
+Your primary responsibility is finishing your project under the guidance of your mentors. To do that, you must submit code regularly and stay in frequent and effective communication with your mentors and team. To pass the evaluations, you must do both the communication **and** the coding plus documentation.
+
+All students will create a report page by tool up to their choice. Keep this up-to-date, as this is one of our primary evaluation tools. 
+
+## Instructions for mentors
+
+### Ideas
+
+If you're a Joplin developer or motivated user and you wish to participate in Summer of Code, make a proposal in the the [Features category of the Joplin Forum](https://discourse.joplinapp.org/c/features), based what your Joplin project needs.
+
+If you wish to mentor, please read the [GSoC Mentor Guide](https://google.github.io/gsocguides/mentor/org-application) and the [Summer of Code FAQ](https://developers.google.com/open-source/gsoc/faq#general). Also, please contact the [staff](https://discourse.joplinapp.org/g/staff) and get the go-ahead from them before editing the ideas page, adding your idea.
+
+Your idea proposal should be a brief description of what the project is, what the desired goals would be, what the student should know and an email address for contact. Students are not required to follow your idea to the letter, so regard your proposal as inspiration for the students.
+
+### Mentoring
+
+Anyone developer can be a mentor if you meet the GSoC eligiibity requirements. We will potentially assign a student to you who has never worked on such a large project and will need some help. Make sure you're up for the task. Mentoring takes time, and lots and lots of communication.
+
+Before subscribing yourself as a mentor, please make sure that  the [staff](https://discourse.joplinapp.org/g/staff) is aware of that. Ask them to send the Summer of Code  Administrators an email confirming your involvement in the team. This is just a formality to make sure you are a real person we can trust; the administrators cannot know all active developers by their Google account ID. Then drop us an message in the forum.
+
+Prospective mentors should read the [mentoring guide](http://www.booki.cc/gsoc-mentoring). Also, Federico Mena-Quintero has written some helpful information based on his experiences in previous years. [His HOWTO](https://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/index.html) has some useful suggestions for anyone planning to mentor this year.
+
+You will subscribe to the relvant tags in the forum to discuss ideas. You will need to read the proposals as they come in, and vote on the proposals. Daily communication is required with your student during the Community Bonding period, and multiple times per week during the coding period.
+
+Finally, know that we will never assign you to a project you do not want to work on. We will not assign you more projects than you can/want to take on either. And you will have a backup mentor, just in case something unforeseen takes place.
+