GSoC

[|WE-GSoC] - peer review, registration - [|peer evaluation], Oct23-26 - wikimedia, Timothy, mentor guide, ? 2 students, mentoring * open education * Summer of Code 2014 - [|WE-GSoC] - peer review, registration - [|peer evaluation] * Oct 23-26 - wikimedia, Timothy, mentor guide, ? 2 students * [|WE Help]


 * privacy, [|pocket code] catrobat, girls - Android app, [|tutorial]
 * distributed learning -
 * likw wikipedia - best lessons, courses - collboration, improvement
 * edx
 * tim - orlando

[|session] - [|moderator]


 * selecting students - knowledge of the project at time of selection, coding open projects, code management, formal reviews and feedback, schedules / checkpoints,
 * mentoring students - talk to students - what worked, what they need, communication format, schedule, checkpoints, status, help, guidance - teaching students to be mentored
 * mediawiki - course wrapper,
 * google [| open online ed] - [|course builder] - [|learning differences course]
 * k-12, open, mobile, SOLE - self organized learning environment, stem * Tim Jim - SCAN - mobile
 * girls / women - participants, in user population
 * python
 * [|open edx] -
 * google - [|app inventor] - [|mlk app], [|quizly]


 * mozilla [|appMaker] - Appmaker is a free tool for creating personal mobile apps, even if you don't know code! Combine individual bricks to create and share custom mobile apps right in your web browser.

2014.10.28

Google Code-in 2014 / 2015
 * tools for we ?
 * WE educator - secondary students - ideas for projects, encourage applications to program

GSoC and Summit / Reunion 2014 reflection
 * Thanks to Carol Smith and her wonderful team.
 * Looking back on our experience as new mentor organization, we were apprehensive to be joining the amazing group of organization. This was a great honor to be included.
 * Loved the t-shirts and chatkies
 * formulating the initial description of our organization and what we would like to accomplish with the contribution from a student.
 * process of reviewing student proposals - group - hearing how others doing, their questions and responses from Google team and other list contributors
 * selection - seemed best suited - our criteria, student responses, fit
 * concerns - wanted to be selected by some students ? who we wanted vs who selected us - beauty contest

actual experience - time consuming, mentoring
 * student - deliverable, time worked, work process - expectations - implicit, explicit
 * code management, revision, commit weekly, code reviews,
 * summit - compare experiences with organizations that have 20+ students, over 10 years
 * get students to become ongoing volunteer contributors - not happening reliably, need something different, separate GSoC student coding opportunity / recruiting

learning
 * better to have no student than someone who takes too much mentor time, effort for effort
 * money vs effort - fail early and often - not seen as a failing or organization - carol said
 * professional / project practices - students not used to autonomy - need specific assignments, deadlines
 * test applicants - need not proceed if student doesn't pass screen - demonstrate understanding of organization / project, coding / management structure and processes - find errors and provide a patch
 * student projects - r&d - something want to add but not sure how - have student work on this - see what problems they discover - precursor for actual inclusion - not usually part of release code
 * some students never do any work, do nothing after midterm
 * 2 mentors - deliverable / subject, process/admin
 * multiple students - given contact ? communicate
 * irc - active, source of information

summit experience
 * informal - intros, connect in person, sharing - lots of opportunity for informal chatting
 * un-conference sessions - big range of topics and formats - cbb - what is in each room ? post outside, ballroom - centers - identify where meeting ? balloons, numbers
 * great to meet tim and chat - lots of good information about oeru that doesn't come across in other communication

cbb
 * planning - work to do - projects for students - several smaller and do a couple, process - test and/or train, commitment, student knowledge/interest in org ?
 * promote to oeru schools ? priority in selection
 * visibility - lots of interest at summit in ideas,
 * wikimedia folks helpful, interested - lots of installation, don't hear much from users
 * develop more guidelines for us/students - checklists, processes - more specific than FOSS guides

questions
 * ? future of WE for non-oeru educators

2014.10.25
 * carol - 2015, mods
 * wikimedia - education, wikiversity,
 * wikieducator ? collaboration > master courses / oers
 * mentoring - pretest, communication, tracking, process - commits, pro code / student assignments
 * documentation - manage, collect, publish, in-code tutorials

2014.10.23
 * [|WebMaker] - Thimble - Mozilla
 * [|open textbooks] - [|books by subject] - emphasis in WE, promote
 * WE pages > print book - left nav - Print/export, Create a book,    Download as PDF,    Printable version
 * [|Come Fly with Me]
 * mediawiki - [|mobile frontend], [|zero.wikipedia] - supported by select mobile carriers
 * mentoring

Google Summer of Code 2014
 * WikiEducator - course registration, peer evaluation - beta C4L, Tim live fall 2014?
 * other organizations, Summer of Code org - mentoring, coding, quality check, Pass criteria, expectations
 * MediaWiki - code libraries, conventions, releases, shared code


 * candidate screening - what's important to know about candidate - prior knowledge applicable to assignment? what does candidate need to know about organization? what is time consuming and how can that be mitigated?
 * communication during coding? single point of contact?
 * multiple participants - share among themselves, with others working on similar projects - all MediaWiki ?? groups
 * forum, not just real-time or email - google group - 1 student, 4-6 mentors

2014.10.19
 * [|summit schedule]

2014.09.10
 * t-shirt came

2014.07.20 GSoC 2014 in San Jose, CA in October. There are a number of informal and unconference meeting opportunities. Are there any things that we can research, people we can connect with, ideas to be on the look out for, and/or promote the OER Foundation and OERu?
 * One thing that immediately springs to mind would be getting to know the Wikimedia Foundation administrators/mentors. Since our projects share technology and theirs is MUCH bigger and they've been part of GSoC longer, it would be good if they have any insights about what works for them in GSoC.

Do you know if Wikimedia is doing anything like the course outline, or peer evaluations?
 * Their Education Program[1][2] is a little different, targeting students in traditional classes that are working to author credible Wikipedia articles. Wikiversity tends to keep things "in wiki" and isn't bothered by the look. [1] https://en.wikipedia.org/wiki/Wikipedia:Education_program [2] https://www.mediawiki.org/wiki/Extension:EducationProgram

GSofC development - Did you consider and/or use any of the Wikimedia features? https://www.mediawiki.org/wiki/Extension:EducationProgram#Feature_overview
 * The plan was to adapt the EducationProgram extension to improve our course registration workflow and provide a single dashboard that showed the student the courses they had been and were enrolled in. Unfortunately A.. is very far behind schedule, and it is looking unlikely he will complete that part of the project.  http://wikieducator.org/User:Akash_Agarwal/GSOCproposal#Course_registration_and_flow_improvements

[|Mentoring guide] - looking back.. This all looks like reasonable advice. I didn't see anything in the list that you didn't do. Were there any surprises - things you wish you had known at the outset that should have been in this list?
 * I was surprised that NOBODY in the WikiEducator or OERu communities was interested in applying. There was an awful lot of wasted time and effort as students discovered the project after our acceptance in GSoC and then tried to find a way to get accepted for our single student slot. In hindsight I think it was a mistake not to push harder on students already in the community to submit proposals.

Being on the GSofC list brought more interest, inquiries and proposals than I expected. Great for OER Foundation visibility!
 * Yes, I definitely think it has been worthwhile. But the "student application window" process was definitely not fun. I've been peripherally involved with the Mailman (Python) GSoC process in previous years. I suppose since that project is bigger than WikiEducator it is easier to find interested people to devote their summer to improving it, so there is less noise during the applications and more determination to power through to a successful completion.

vt We would have liked provide feedback about the student with the check box question even if we give him a Pass – still very applicable and important information. If it is going to be for everyone, not just Fail, there could be a couple more statements – good as well as bad. Even great students could have good and bad work habits, and basic skills as we discovered, even though they get a Pass at the end.

Separating the pay from Pass/Fail - doing enough to warrant being paid and Fail by criteria set are not mutually exclusive?

Also – strongly suggest pre-training on “open” development be a requirement. Could be a self study, with quizzes and the ability to “test out” of this. Even if this is not something the GSofC pick up, WE and others could set it up and make it a condition for proposal and student acceptance into the program.