Hi Damian, Chapel has been participating in Google Summer of Code for several years now. In some aspects, that program is similar to what you describe. The landing page for that program is here if you want to learn more about it:
https://summerofcode.withgoogle.com/ There are typical things that we do for getting mostly undergrad students started with Chapel are: - How to contribute: https://chapel-lang.org/contributing.html - "Good first issues" that can help acclimated to the Chapel ecosystem without being challenging in terms of implementation and/or design: https://github.com/chapel-lang/chapel/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 From the process perspective, we try to follow few things: - Weekly meetings with the student - Close-to-daily communication - Screenshare sessions to get them over specific implementation issues as needed Some general pitfalls that the student can encounter: - Getting bogged down in trying to optimize performance of something specific and losing the focus on the general scope of the project - Subtle and occasional bugs: It is always a good idea to communicate with the mentor and/or the Chapel team if there is an unexpected behavior. It may be due to a misunderstanding of some of the semantics or an actual bug in the implementation. The worst thing that a student can do is to get fixated on the issue in an isolated manner and not seek help. Some of these may not be very applicable in your case and may be too obvious. But I hope this helps. Engin On 6/24/20, 5:37 AM, "Damian McGuckin" <[email protected]> wrote: Chapel-team, Do you have any formal processes you have for managing these? I am thinking of having a summer-break (3 month) intern do a conversion of a Fortran program for a civil engineering application into Chapel. Last year, they were computational fluid dynamics projects looking at only the engineering. I was looking for some guidance on a more programming focused task and the processes one should/might follow to benefit the student and address our aims. It might also help if you had a similar process for final year thesis students, i.e. not PhD. Especially I am interested if you have ways to get undergraduates up to speed on Chapel in a hurry and what background you might expect of them. And a list of stumbles to look for (and help pre-empt) before they get to the point of a fall. Regards - Damian Pacific Engineering Systems International, 277-279 Broadway, Glebe NSW 2037 Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here Views & opinions here are mine and not those of any past or present employer _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
