I'm co-admin of for Pharo organization in the context of the Google
Summer of Code.
Maybe some of your students might be interested to join (deadline
before April 3rd).
If I remember correctly, the Vietnamese students will received
something like 2400 USD
if their are successful in their project.
If they are interested they can send me an email.
Please find more details below.
On Wed, Mar 1, 2017 at 7:29 PM, Serge Stinckwich
<[hidden email]> wrote:
> *** Please forward this message to students that might be interested ***
> Heartiest Congratulations !
> Pharo Consortium has been selected as a mentor organisation for Google
> Summer of Code 2017.
> Google Summer of Code is a global program focused on introducing
> students to open source software development.
> Students work on a 3 month programming project with an open source
> organisation during their break from university.
> Read more at https://summerofcode.withgoogle.com/
> Pharo is a pure object-oriented programming language and a powerful
> environment, focused on simplicity and immediate feedback (think IDE
> and OS rolled into one).
> Everything in Pharo is an object. The entire syntax of Pharo fits on a
> postcard coding can be done directly in the debugger. Pharo has super
> cool tools that empower you and make you super efficient. Pharo's goal
> is to deliver a clean, innovative, free and open-source immersive
> environment. By providing a stable and small core system, excellent
> developing tools, and maintained releases, Pharo is an attractive
> platform to build and deploy mission critical applications. Pharo
> fosters a healthy ecosystem of both private and commercial
> contributors who advance and maintain the core system and its external
> More information about Pharo is available here: http://www.pharo.org/
> We invite all the prospective eligible students to code their summer
> away with Pharo Consortium.
> Student Responsibilities
> ...to your Mentor
> - Submit quality work
> - Regularly communicate work completed, what you intend to do next, and blockers
> - Ask for help when something is preventing you from achieving a goal
> - Give indication that you are alive and working daily (GSoC)
> - Re-evaluate work scope when significantly ahead of expectations (GSoC)
> - Communicate with your mentor AND the broader community
> - Inform when work capacity will be reduced, as early as possible
> (e.g., family, health, other work) (GSoC)
> - Listen and respond to feedback
> ...to the Org Admin
> Let them know when there are
> - Interaction issues with any mentor or community member
> - Significant disagreements involving your work or changes to your work plan
> Read more about responsibilities here:
> Hence, we invite enthusiastic student developers contributors to work
> with Pharo Consortium for GSoC 2017.
> 1. A first list of projects are available here :
> http://gsoc.pharo.org/ but more can be found by interacting with
> mentors from the Pharo community.
> 2. Join dedicated channels, #gsoc-students for general interactions
> with students on Pharo slack. In order to get an invitation for
> pharoproject.slack.com visit the URL here:
> Discuss with mentors about the complexity and skills required for the
> different projects.
> 3. Please help fix bugs, open relevant issues, suggest changes,
> additional features, help build a roadmap, and interact with mentors
> on mailing list and/or slack to get a better insight into projects.
> Better the contributions, Better are the chances of selection.
> Before applying:
> * Knowledge about OOP
> * Basic idea about Pharo & Smalltalk syntax and ongoing projects
> * Past experience with Pharo & Smalltalk
> * Interaction with organisation
> You can start with the Pharo MOOC : http://files.pharo.org/mooc/
> Guidelines for Proposal:
> * Introduction: Clearly defined problem. Current state of things.
> Issues you wish to solve and why. Conclude with solution.
> * Project goals: Format it like 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. It is
> better to promise less and deliver more than to promise a lot and then
> fall short.
> * Implementation: Longer and more detailed. Provide technical details,
> show that you understand the technology and illustrate key technical
> elements of your proposed solution.
> * Timeline: Make it weekly. Set goals for each week. Be upfront about
> other commitments, including exams, classes, travel, internships,
> jobs, etc.
> * Benefits to Community: Make your case a benefit to the organization.
> * Related Work: Research and write how the project fits into the
> target organization. Explain related works, similarities &
> * About me: Provide full contact information, email addresses,
> websites, IRC nick, postal address and telephone. Write a few
> sentences about yourself, previous experiences and why you think
> you’re the best for this job.
> Submit your proposal early. Keep it short. Include necessary
> information. Get it reviewed in the mailing list or Slack channel
> before submitting it.
> The deadline for submitting your proposal is March 20th to April 3rd
> on https://summerofcode.withgoogle.com/
> Looking forward to great talent joining our organisation this summer.
> Warm Regards
> Pharo Organisation Admins
> (Alexandre Bergel, Jigyasa Grover, Serge Stinckwich & Yuriy Tymchuk)
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
Smalltalk-vn mailing list
|Free forum by Nabble||Edit this page|