You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone! I'm Jialiang Pei, a sophomore who want to participate in GSoC 2018. I am interested in Project:aima-python. I'm a little confused. In addition to guides which has listed in aima-gsoc repo, could I give other PRs even like document errors to enhance the chance that I'm chosen? Is it advisable? Thanks!
I think PRs fixing document errors count points on engagement (e.g. you'll show that you have read the code and have found incremental ways to make it better) and possibly coding (e.g. you'll show you know how to use git), but misses the point on the most relevant skill: design.
So, to answer the question, "yes, it does" but minimally. The highest order bit is your design aesthetics skills and that's best shown with samples of your work.
The text was updated successfully, but these errors were encountered:
From this original thread.
Here is a good breakdown of what we are looking for.
We'll be looking at things in this order:
I think PRs fixing document errors count points on engagement (e.g. you'll show that you have read the code and have found incremental ways to make it better) and possibly coding (e.g. you'll show you know how to use git), but misses the point on the most relevant skill: design.
So, to answer the question, "yes, it does" but minimally. The highest order bit is your design aesthetics skills and that's best shown with samples of your work.
The text was updated successfully, but these errors were encountered: