Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E8828EB03 for ; Wed, 29 May 2013 14:35:46 +0000 (UTC) Received: (qmail 10665 invoked by uid 500); 29 May 2013 14:35:46 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 10602 invoked by uid 500); 29 May 2013 14:35:45 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 10323 invoked by uid 99); 29 May 2013 14:35:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 14:35:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ng.tuna@gmail.com designates 209.85.217.176 as permitted sender) Received: from [209.85.217.176] (HELO mail-lb0-f176.google.com) (209.85.217.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 14:35:40 +0000 Received: by mail-lb0-f176.google.com with SMTP id x10so9032172lbi.21 for ; Wed, 29 May 2013 07:35:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KmbP2gPbnWnd0Fg/jidqw+KqhI2Cx3MIoyAX/4573nQ=; b=rGUiKT248fY5hubEaN4LJ/4Q+LNOyZKQx2PllfHs+is0D1JV86AterCjItrZHuv1dX glpvg4dN2Lra5QKGK9CQDR3ljdTTlq2UxUNyMSrwZ1IlcZLfNiiTD5DbcpKakCuYqiaS /0Om8AHs3f+7ClrAPQZZxW7hKnzyyL7CBvmy0gmc3V9eiFonKfPZ8tQJ5U0HeG+md/BO mB3E2kbo3+gIwvBi9zdV7jAolLvAjVwbTXsYW+G8PYUcXvIBCiLDmswIsbzc1M6fWuLd tEdJNfi0ztKMkpnmijIB5rbFacsR5mB33wtyrUr24OEnbhpqj8hi0bmqEgy+hDhL7Q5n 07IQ== MIME-Version: 1.0 X-Received: by 10.112.126.9 with SMTP id mu9mr1687925lbb.99.1369838119119; Wed, 29 May 2013 07:35:19 -0700 (PDT) Received: by 10.112.138.170 with HTTP; Wed, 29 May 2013 07:35:19 -0700 (PDT) In-Reply-To: <72ECB7B2-2AF2-433F-9629-2810E501CB32@gmail.com> References: <72ECB7B2-2AF2-433F-9629-2810E501CB32@gmail.com> Date: Wed, 29 May 2013 21:35:19 +0700 Message-ID: Subject: Re: [GSOC] Community Bonding Period From: Nguyen Anh Tu To: Sebastien Goasguen Cc: "dev@cloudstack.apache.org" , Dharmesh Kakadia , Meng Han , Ian Duffy , Shiva Teja Content-Type: multipart/alternative; boundary=001a11c378647d72e804dddc4a72 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c378647d72e804dddc4a72 Content-Type: text/plain; charset=ISO-8859-1 @Sebgoa: Done! My account on every page: tuna. Looking forward :-) 2013/5/29 Sebastien Goasguen > Hi Dharmesh, Meng, Ian, Nguyen and Shiva, > > Congratulations again on being selected for the 2013 Google Summer of Code. > > The program has started and we are now in "community bonding period". On > June 17th you will officially start to code. > > I will mentor Dharmesh and Meng > Abhi will mentor Ian > Hugo will mentor Nguyen > Kelcey will mentor Shiva > I will act as overall coordinator. > > While these are your official mentors from a Google perspective, the > entire CloudStack community will help you. > > There are a few things to keep in mind: > ------------------------------------------------------ > -The timeline: Check [0]. Note that there are evaluations throughout the > program and that if progress is not satisfactory you can be dropped from > the program. Hopefully with terrific mentoring from us all at CloudStack > this will not happen and you will finish the program with flying colors. > > -Email: At the Apache Software Foundation, official communication happen > via email, so make sure you are registered to the > dev@cloudstack.apache.org (you are). This is a high traffic list, so > remember to setup mail filters and be sure to keep the GSOC emails where > you can read them, without filters you will be overwhelmed and we don't > want that to happen. When you email the list for a GSOC specific question, > just put [GSOC] at the start of the subject line. I CC you in this email > but will not do it afterwards and just email dev@cloudstack.apache.org > > -IRC: For daily conversation and help, we use IRC. Install an IRC client > and join the #cloudstack and #cloudstack-dev on irc.freenode.net [1]. > Make yourself none and learn a few IRC tricks. > > -JIRA: Our ticketing system is JIRA [2], create an account and browse > JIRA, you should already know where your project is described (which ticket > number ?). As you start working you will create tickets and subtasks that > will allow us to track progress. Students having to work on Mesos, Whirr > and Provisionr will be able to use the same account. > > -Review Board [3]: This is the web interface to submit patches when you > are not an official Apache committer. Create an account on review board. > > -Git: To manage the CloudStack source code we use git [4]. You will need > to become familiar with git. I strongly recommend that you create a > personal github [5] account. If you are not already familiar with git, > check my screencast [6]. > > -Wiki: All our developer content is on our wiki [7]. Browse it, get an > account and create a page about your project in the Student Project page > [8]. > > -Website: I hope you already know our website :) [9] > > -CloudStack University: To get your started and get a tour of CloudStack, > you can watch CloudStack University [10] > > Expectations for bonding period: > -------------------------------------------- > *To get you on-board I would like to ask each of you to send an email > introducing yourself in couple sentences, describe your project (couple > sentences plus link to the JIRA entry and the wiki page you created), > confirm that you joined IRC and if you registered a nick tell us what it is > and finally confirm that you created an account on review board and JIRA. > > *By the end of the period, I would like to see your first patch submitted. > It will be your GSOC proposal in docbook format contributed to a GSOC guide > I will create. There is no code writing involved, this will just serve as a > way to make sure you understand the process of submitting a patch and will > be the start of a great documentation of our GSOC efforts. More on that > later > > On behalf of everyone at CloudStack and especially your mentors (Abhi, > Kelcey, Hugo and myself) , welcome and let's have fun coding. > > -Sebastien > > > [0] - http://www.google-melange.com/gsoc/events/google/gsoc2013 > [1] - http://www.freenode.net > [2] - https://issues.apache.org/jira/browse/CLOUDSTACK > [3] - https://reviews.apache.org/dashboard/ > [4] - http://git-scm.com > [5] - https://github.com > [6] - > http://www.youtube.com/watch?v=3c5JIW4onGk&list=PLb899uhkHRoZCRE00h_9CRgUSiHEgFDbC&index=5 > [7] - https://cwiki.apache.org/CLOUDSTACK/ > [8] - https://cwiki.apache.org/CLOUDSTACK/student-projects.html > [9] - http://cloudstack.apache.org > [10] - > http://www.youtube.com/playlist?list=PLb899uhkHRoZCRE00h_9CRgUSiHEgFDbC > > > > -- N.g.U.y.e.N.A.n.H.t.U --001a11c378647d72e804dddc4a72--