brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [1/2] brooklyn-docs git commit: Add page with information about GSoC 2018
Date Tue, 27 Feb 2018 22:16:17 GMT
Repository: brooklyn-docs
Updated Branches:
  refs/heads/website 21673fe02 -> 53f00b678

Add page with information about GSoC 2018


Branch: refs/heads/website
Commit: 269b4ea14b2ffd48a8666be5926086c207782fa3
Parents: 21673fe
Author: Richard Downer <>
Authored: Tue Feb 27 21:39:56 2018 +0000
Committer: Richard Downer <>
Committed: Tue Feb 27 22:15:09 2018 +0000

 community/  | 58 +++++++++++++++++++++++++++++++++++++++++++++++++
 community/ |  1 +
 2 files changed, 59 insertions(+)
diff --git a/community/ b/community/
new file mode 100644
index 0000000..2058e97
--- /dev/null
+++ b/community/
@@ -0,0 +1,58 @@
+layout: website-normal
+title: Google Summer of Code
+<div class="panel panel-default">
+  <div class="panel-heading" markdown="1">
+#### Current Status
+  </div>
+  <div class="panel-body" markdown="1">
+The Apache Software Foundation is participating in 2018's Google Summer of Code!
+Apache Brooklyn, along with our fellow projects at the ASF, are welcoming
+contact from potential GSoC students. You are welcome to work on your own ideas
+for our project, or look at the [list of project ideas](
+(note that this list is for *all* of the Foundation's projects, not just
+Applications open on **March 12th 2018** and must be received by **March 27th
+2018**. It will greatly benefit your application if you join our community and
+discuss your proposals with us before you make your application - see below for
+more details.
+  </div>
+## Potential students
+Thank you for considering Apache Brooklyn and The Apache Software Foundation for
+your GSoC project. Welcome to our community!
+Firstly, if you have not already done so, please read the [Student Guide to
+Google Summer of Code]( It
+contains essential information about how to approach your project before and
+after your application is submitted. Also, please read the [GSoC information
+provided by The Apache Software Foundation](
+Secondly, Apache values community, and the community and all its work is done in
+the open, on public mailing lists and IRC channels. Please [subscribe to our
+mailing lists](mailing-lists.html) and optionally [join our IRC channel](irc.html).
+You can also [read our list archives](
+to see what we've discussed in the past. Observe how we do things, and then
+please jump in and introduce yourself and your ideas for our project. The
+["Making First Contact" page of the GSoC Student Guide](
+will guide you here.
+We, the Apache Brooklyn community, would be interested in hearing your ideas for
+what and how you would like to do with your GSoC project for Brooklyn. Whilst we
+have given some ideas for *what* we would like our GSoC projects to be about, we
+have deliberately left the *how* up to you. Please use the mailing list to ask
+questions, make suggestions, and "sound out" potential solutions that meet the
+requirements. Such discussions will be valuable to you when you come to make
+your formal project proposal.
+We recommend against emailing project individuals directly - Apache prefers to
+communicate in the open as much as possible, therefore you should direct your
+emails to the public mailing list. If you have any questions which you would
+prefer to ask privately, please email the project's private address at
diff --git a/community/ b/community/
index 870f0ee..622e5bc 100644
--- a/community/
+++ b/community/
@@ -7,6 +7,7 @@ children:
 - security/
 - { link: '', title: 'Bug Tracker (JIRA)' }
 - { path: }
 <div class="row">

View raw message