Thanks Serge! This is a very important effort you are leading Alexandre
> On Feb 17, 2016, at 5:27 AM, Serge Stinckwich <serge.stinckw...@gmail.com> > wrote: > > Dear all, > > just a quick update to GSOC application of Pharo this year > > - We have enough topics I guess. I already send a reminder on the > various mailing-list. > List of topics here: > https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics.st > > We have to generate the html from the topics list and put the result > on the gsoc.pharo,org website. I ask Uko to have a look to this, but I > don't want to loose to much time on this. I was wondering if we should > transform the list as a Markdown document on github just to keep it > simple. > > - Finish the 2016 Application and Organization profile on Google > website. The questions are a little bit different from 2015 and we > should complete them. > Please find below the answers to the questions right now. > > I add in parenthesis, the number of words of each answers and the > maximum allowed. > > Please us to refine our answers. We need to wrote "guidance for students". > > Thank you. > > ========================================================================== > > Why does your org want to participate in Google Summer of Code? (898/1000) > > Supporting open-source projects is one of the most important > objectives of the Pharo community. Participating at GSoC will increase > the visibility of Pharo project efforts, thus favoring interactions > with other communities. We are also interested in providing > interesting projects to students allowing them to learn and have a fun > job for the summer. > > We expect also to bring more people into our community. That's very > interesting as the Pharo community is trying to be innovation-driven > and more open minded than the Smalltalk community from which we have > evolved. We want people from other communities to join ours and we are > also interested in what is happening outside and to share experiences > or ideas. Fortunately for us, dynamic languages like Python, Ruby, > among others, enjoy increasing popularity. This is an excellent > opportunity to join, show and learn from and with other communities. > > ========================================================================== > > How many potential mentors have agreed to mentor this year? > > 11-15 > > ========================================================================== > > How will you keep mentors engaged with their students? (668/1000) > > We chose mentors from people who are long time in our community and > have proven to be reliable. Usually we try to match mentors with > projects that are important for themselves. This means that the mentor > has an own interest in the project that the student doing it. Also we > try to ensure that there is a co-mentor for every project who can > replace the main mentor if needed. Also it is very important for us to > keep a good record and expand the community, and in previous years we > even managed to organize our own "summer code" programs for a couple > of students, so in the worst case we will find a replacement from the > core part of the community, or the board itself. > > ========================================================================== > How will you help your students stay on schedule to complete their > projects? (886/1000) > > As mentioned before we've already organized our own small "summer > code" programs, as usually we have more interested students than the > fundings that we can spend for them. However we acknowledge that > maintaining student's motivation is very important. We are a very open > and friendly community, and we encourage the students to take part on > the mailing list discussions from the beginning of their projects. > There is a specific pharo-users mailing-list more suitable for > beginners than the pharo-dev mailing-list. > Usually students get feedback and requests from the beginning of their > projects, and they have people interested in the prototypes as soon as > they are ready. From our experience having real users for the project > serves as the best motivation. Also our mentors try to maintain a > constructive and friendly discussion to ensure that the student enjoys > working on the project. > > ========================================================================== > > How will you get your students involved in your community during GSoC? > (608/1000) > > As mentioned above we encourage students to announce their status on > the mailing list as well as discuss questions on our Slack channel. We > also encourage them to write blogs about their project experience to > both promote themselves and give others an opportunity to familiarize > with the project more and share ideas between students. We are > organizing PharoDays every year (this year in Belgium, website: > http://pharodays2016.pharo.org) and we participate to the ESUG > (European Smalltalk User Group) conference in the end of each summer > and plan to invite the students of the best projects to present there. > > ========================================================================== > > Has your org been accepted as a mentoring org in Google Summer of Code before? > > Yes > > ========================================================================== > > Which years did your org participate in GSoC? > > - 2012 > - 2010 > - 2008 > - 2007 > > ========================================================================== > > What is your success/fail rate per year? > > - 2012: 10 projects pass / 3 fail > - 2010: 6 projects pass / 0 fail > - 2008: 5 projects pass / 0 fail > - 2007: 5 projects pass / 0 fail > > > ========================================================================== > > If your org has applied for GSoC before but not been accepted, select the > years: > > - 2015 > - 2014 > - 2013 > > ========================================================================== > > What year was your project started? > > 2008 > > ========================================================================== > > Short description of Pharo (166/180) > > Pharo is a pure object-oriented programming language and IDE. We > innovate every part of the development experience to come up with the > best way to work with software. > > ========================================================================== > > Long description of Pharo (1401/2000) > > Pharo is a pure object-oriented programming languagea and IDE. > Pharo's goal is to minify the gap between the state of your mind and > the functionality of your application. Whether you are writing code, > debugging it, inspecting an object, hacking the runtime or tweaking > the IDE there should be nothing that stops you from engaging the > action with ease and grace. > > We work both on improving Pharo itself and on developing end user > applications in Pharo. Below you will see the highlights of most > prominent Pharo features. > > ### Simple & powerful language > No constructors, no types declaration, no interfaces, no primitive > types. Yet a powerful and elegant language with a full syntax fitting > in one postcard! Pharo is objects and messages all the way down. > > ### Feel a live environment > Feel the joy of having immediate feedback at any moment of your > development: Developing, testing, debugging. Even in production > environments, you will never be stuck in compiling and deploying steps > again! > > ### Amazing debugging experience > The Pharo environment includes a debugger unlike anything you've seen > before. It allows you to step through code, restart the execution of > methods, create methods on the fly, and much more! > > ### Pharo is yours > Pharo is made by an incredible community, with more than 80 > contributors for the last revision of the platform and hundreds of > people contributing constantly with frameworks and libraries. > > ========================================================================== > > Guidance for students on how to apply to your organization. Should > include any prerequisites or requirements. You may wish to include a > template or tips for their proposals. > > (0/1500) > > TBD > > ========================================================================== > > - > > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
