March 2017 - Pharo-users - lists.pharo.org

Fwd: GSoC 2017: Tips on Reviewing Student Proposals

by Serge Stinckwich

Dear all, this is a short update for the Google Summer of Code 2017. The students have to submit your proposals on the Google website before April 3rd. See details below. I dunno exactly who are the students/mentors who are submitting a proposal for Pharo. Can the mentors (or students) send me in private an email about the name of the students/mentors + a title of your project ? Thank you very much. Regards, ---------- Forwarded message ---------- From: Google Summer of Code <summerofcode-noreply(a)google.com> Date: Mon, Mar 20, 2017 at 7:26 PM Subject: GSoC 2017: Tips on Reviewing Student Proposals To: sergestinckwich(a)gmail.com [image: Google Summer of Code] Hi Serge Stinckwich, Thank you for registering to be a GSoC 2017 mentor or organization administrator! We have many new mentors and organizations this year so we wanted to go through some important details to help you understand the process for the next couple of months. Please take the time to reach out to your organization administrator about what is expected of you this year as a mentor. We also encourage you to read the entire Google Summer of Code mentor manual <http://write.flossmanuals.net/gsoc-mentoring/about-this-manual/> and the Roles and Responsibilities doc if you haven't done so already. Both the manual and Roles and Responsibilities doc were written by GSoC veteran Org Admins, Mentors, former students and Google Program Admins. They have helpful information about the program and how to participate successfully at each step in GSoC. *New GSoC Orgs*: the section about participating in your first GSoC has some great tips. To see all emails sent to mentors and org admins visit this page <https://developers.google.com/open-source/gsoc/2017/mentor-oa-announcements> that will continue to be updated throughout the program. Student Proposals As of today, students are able to submit their proposals via the website. Each student may submit up to 5 proposals to the program. They can submit multiple proposals to the same organization for different projects if they wish. Historically, the students with the best proposals reach out to the orgs early to receive feedback before submitting their final proposal. To encourage more students to seek feedback on their proposals we made draft proposals part of the official proposal workflow. Be sure to refresh your dashboard periodically so that you can see when new drafts are ready to review. You will not receive an email. We are encouraging the use of Google Docs for proposals as this will allow you to comment directly on the proposal (if the student sets their sharing settings correctly). Over the next couple of weeks you will be interacting with dozens and in some cases hundreds of students interested in working with your project. We know many of you may become overwhelmed and some students can be impatient, so you may want to have an auto-responder or some sort of canned response to let students know you are looking at their proposals but it could take X days to receive a response. Students *must* submit their final proposal as a PDF through the website. It will be visible to you after the deadline for student applications (April 3 16:00 UTC). You should make your decisions on which students to accept based on the contents of the final PDF proposal and your interactions with the student. Students can delete their proposals and you will not receive an email of the deletion. If a proposal disappears from your list, it is likely because they deleted it. Working with Students All student projects must have at least 1 mentor assigned to the project. We strongly encourage assigning a second mentor as a backup mentor or co-mentor. A mentor should not be the primary mentor for more than one or two students. Mentoring can be a lot of work and we donât want anyone to burn out and become frustrated with the program. Important GSoC 2017 Dates and Deadlines *March 20 - April 3 16:00 UTC*: Mentors and Org Admins review student draft proposals and give students feedback on their proposals. *April 3 - 16:* Review all submitted student proposals with your org and consider how many you want to select and how many you can handle. Decide on the minimum/maximum number of student slots to request. *April 17, 16:00 UTC*: Deadline to submit slot requests (OAs enter requests) *April 19, 16:00 UTC*: Slot allocations are announced by Google *April 19 - 24 16:00 UTC* : Select the proposals to become student projects. At least 1 mentor must be assigned to each project before it can be selected. (OAs enter selections) *April 24 - May 4:* Google Program Admins will do another review of student eligibility *May 4*: Accepted GSoC students/projects are announced *May 4 - 29*: Community Bonding Period *May 30*: Coding begins *June 26-30*: First evaluation period - mentors evaluate students, students evaluate mentors *July 24 - 28*: Second evaluation period - mentors evaluate students, students evaluate mentors *August 21- 29*: Students wrap up their projects and submit final evaluation of their mentor *August 29 - September 5*: Mentors submit final evaluations of students *September 6*: Students passing GSoC 2017 are announced Mentors Mailing List If you want to be included on the GSoC mentors mailing list be sure to opt in on your User Profile page. We will add anyone who has opted in to the list every few days for the next month. And then every couple of weeks throughout the program. You can always opt out once you have been added by unsubscribing using the link on any of the emails. Contact Us Please use the gsoc-support(a)google.com email address for questions so that anyone on our team can answer your question for you. We look forward to working with all of you over these next 6 months! Thanks again for being a mentor for GSoC 2017! Google Open Source Programs Office This email was sent to serge.stinckwich(a)gmail.com. You are receiving this email because of your participation in Google Summer of Code 2017. https://summerofcode.withgoogle.com To leave the program and stop receiving all emails, you can go to your profile <https://summerofcode.withgoogle.com/dashboard/profile/> and request deletion of your program profile. For any questions, please contact gsoc-support(a)google.com. Replies to this message go to an unmonitored mailbox. Â© 2017 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

March 23, 2017

Re: [Pharo-users] Magritte extension

by Diego Lont

> On 22 Mar 2017, at 20:36, phil(a)highoctane.be wrote: > > Magritte is nice but the amount of work is just too much for my taste. Simple forms are better handled with somethibg like Mold. > > And this especially when components interact with a ton of Js. Then I want you to challenge you: try the QCMagritte tutorial. I took me 3 hours, including the time to make some improvements on the tutorial, and please tell me if you still believe it takes a ton of time to make something nice.

March 23, 2017

Re: [Pharo-users] Magritte extension

by Diego Lont

> On 23 Mar 2017, at 04:27, Ben Coman <btc(a)openinworld.com> wrote: > > On Thu, Mar 23, 2017 at 5:25 AM, Diego Lont <diego.lont(a)delware.nl> wrote: >> >>> First of all I want to advertise QCMagritte: This framework is easy to use. >>> It has a seaside like tutorial, that every developer should be able to >>> follow without any significant problems and shows all significant features >>> of both Magritte, Seaside and QCMagritte. Although it lacks documentation on >>> the technical details of the framework, it has documentation included how to >>> use the framework (as a developer). >> >> Shame on me, advertising the tutorial of QCMagritte without checking it actually works. >> >> I fixed the bug that prevented me from starting the first page (rendering a keep alive) of the tutorial this morning, and started trying it out this evening. Along the way I found some typoâs and things that could be explained better, so I made some improvements to the tutorial along the road. I also noticed that some topics are not covered yet in this tutorial â¦ but since no one complained about the tutorial being buggy, not many people have tried the tutorial ?!? > > Can you link the tutorial? > cheers -ben > Maybe including the tutorial in a QCMagritte image was not very obvious â¦ QCMagritte can be found on smalltalk hub ( http://smalltalkhub.com/#!/~DiegoLont/QCMagritte/ ) and pharo CI ( https://ci.inria.fr/pharo-contribution/job/QCMagritte/ ). So download a fresh pharo image, open it and perform the following: Gofer new url: 'http://smalltalkhub.com/mc/DiegoLont/QCMagritte/main'; package: 'ConfigurationOfQCMagritte'; load. ((Smalltalk at: #ConfigurationOfQCMagritte) project version: #'development') load: #( 'All' ). (Smalltalk at: #ZnZincServerAdaptor) startOn: 8080 Doing this should give you a working QC Magritte tutorial hosted on your own pc. You can also download a pre build image from the pharo ci server. When you have an running image with QCMagritte: start a browser on http://localhost:8080/ and the tutorial should pop up.

March 23, 2017

Re: [Pharo-users] Magritte extension

by Ben Coman

On Thu, Mar 23, 2017 at 5:25 AM, Diego Lont <diego.lont(a)delware.nl> wrote: > >> First of all I want to advertise QCMagritte: This framework is easy to use. >> It has a seaside like tutorial, that every developer should be able to >> follow without any significant problems and shows all significant features >> of both Magritte, Seaside and QCMagritte. Although it lacks documentation on >> the technical details of the framework, it has documentation included how to >> use the framework (as a developer). > > Shame on me, advertising the tutorial of QCMagritte without checking it actually works. > > I fixed the bug that prevented me from starting the first page (rendering a keep alive) of the tutorial this morning, and started trying it out this evening. Along the way I found some typoâs and things that could be explained better, so I made some improvements to the tutorial along the road. I also noticed that some topics are not covered yet in this tutorial â¦ but since no one complained about the tutorial being buggy, not many people have tried the tutorial ?!? Can you link the tutorial? cheers -ben

March 23, 2017

Re: [Pharo-users] Magritte extension

by Diego Lont

> First of all I want to advertise QCMagritte: This framework is easy to use. > It has a seaside like tutorial, that every developer should be able to > follow without any significant problems and shows all significant features > of both Magritte, Seaside and QCMagritte. Although it lacks documentation on > the technical details of the framework, it has documentation included how to > use the framework (as a developer). Shame on me, advertising the tutorial of QCMagritte without checking it actually works. I fixed the bug that prevented me from starting the first page (rendering a keep alive) of the tutorial this morning, and started trying it out this evening. Along the way I found some typoâs and things that could be explained better, so I made some improvements to the tutorial along the road. I also noticed that some topics are not covered yet in this tutorial â¦ but since no one complained about the tutorial being buggy, not many people have tried the tutorial ?!?

March 22, 2017

Re: [Pharo-users] [Deploy Application] Where to host using Gemstone/s?

by Dale Henrichs

Sergio, The GsDevKit_home project[1] provides a set of tools for installing and running GemStone/S. There is GsDevKit_ansible[2] built on top of GsDevKit_home that provides a set of Ansible[3] playbooks for deploying a GemStone server, Nginx, daemontools, etc. on Ubuntu. Ansible can be used with AWS or Linode... For additional help, I suggest that you hop over to he GsDevKit/GLASS mailing list and ask additional questions. Dale [1] https://github.com/GsDevKit/GsDevKit_home#open-source-development-kit-for-g… [2] https://github.com/GsDevKit/GsDevKit_ansible [3] https://github.com/GsDevKit/GsDevKit_ansible [4] http://lists.gemtalksystems.com/mailman/listinfo/glass On 03/22/2017 12:35 PM, sergio ruiz wrote: > > I am ready to deploy a live production application, and am exploring > my options.. > > I currently host a bunch of other things over at Digital Ocean. I > would like to use them for this project to, using a new droplet. > > Does anyone know if there is a quick and easy way to install > Gemstone/s on the Digital Ocean server? > > I will also need to port Teapot to Gemstone/s. > > If I need to install Gemtone/s from scratch on the server, which > distro would be the recommended for such a thing> > > Thanks! > > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.Village-Buzz.com <http://www.village-buzz.com/> > http://www.ThoseOptimizeGuys.com <http://www.thoseoptimizeguys.com/> > http://www.coffee-black.com <http://www.coffee-black.com/> > http://www.painlessfrugality.com <http://www.painlessfrugality.com/> > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

March 22, 2017

Re: [Pharo-users] Magritte extension

by phil＠highoctane.be

Magritte is nice but the amount of work is just too much for my taste. Simple forms are better handled with somethibg like Mold. And this especially when components interact with a ton of Js. Phil Le 22 mars 2017 19:53, "Diego Lont" <diego.lont(a)delware.nl> a Ã©crit : > > > On 22 Mar 2017, at 00:46, Ben Coman <btc(a)openInWorld.com> wrote: > > > > On Wed, Mar 22, 2017 at 4:35 AM, DiegoLont <diego.lont(a)delware.nl> > wrote: > >> It has been a while that I was really involved in developing on > (QC)Magritte > >> and doing stuff on the web ... > > > > btw, what does the "QC" represent? > > > QC is a reference back to the company for who the software was originally > written for: http://www.q-software-solutions.de/index.htm. The owner > (Friedrich Dominicus) agreed that I was allowed to make the library part > (QCMagritte) open source. > > Cheers, > Diego > > > >

March 22, 2017

Voyage Timeout

by Hilaire

Hi, When I configure a production image with command st handler as following: pharo myImage st --save --quit configureMyImage.st I notice at image start up, a Socket timeout error. In the configureMyImage.st script, among other things, I open a singleton Voyage repository. I added a 5s delay at the end of this script, just wondering if image was shutdown before Voyage establishes connection with the Mongo DB, but no. Any incompatibility issues to be aware of between st command handler (particularly the --save part) and Voyage repository? Thanks, Hilaire -- Dr. Geo http://drgeo.eu

March 22, 2017

[Deploy Application] Where to host using Gemstone/s?

by sergio ruiz

I am ready to deploy a live production application, and am exploring my options.. I currently host a bunch of other things over at Digital Ocean. I would like to use them for this project to, using a new droplet. Does anyone know if there is a quick and easy way to install Gemstone/s on the Digital Ocean server? I will also need to port Teapot to Gemstone/s. If I need to install Gemtone/s from scratch on the server, which distro would be the recommended for such a thing> Thanks! ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com <http://www.village-buzz.com/> http://www.ThoseOptimizeGuys.com <http://www.thoseoptimizeguys.com/> http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

March 22, 2017

Re: [Pharo-users] Magritte extension

by Diego Lont

> On 22 Mar 2017, at 00:46, Ben Coman <btc(a)openInWorld.com> wrote: > > On Wed, Mar 22, 2017 at 4:35 AM, DiegoLont <diego.lont(a)delware.nl> wrote: >> It has been a while that I was really involved in developing on (QC)Magritte >> and doing stuff on the web ... > > btw, what does the "QC" represent? QC is a reference back to the company for who the software was originally written for: http://www.q-software-solutions.de/index.htm. The owner (Friedrich Dominicus) agreed that I was allowed to make the library part (QCMagritte) open source. Cheers, Diego

March 22, 2017