This is the P2PU Archive. If you want the current site, go to www.p2pu.org!
Tokbox link is: http://www.tokbox.com/conf/h6y2mlhwxmsyvtji
A good tool to use for everyone to take notes at the same time is piratepad, I've started a pad here: http://piratepad.net/sxRu1HeLxl - all edits are live so everyone can see and edit each other as we talk & type. At the end of the week, we can paste the contents back on here as permanent records.
--
Sorry about starting the 1st class late :( It has been a whirlwind of a week for me! And also I didn't specify which day is our first video chat so a lot of you weren't sure. Sorry!
We had 6 people showed up. Short intro all around, then we jumped into the #1 question: "How is this course going to proceed?" Here's my take on it:
Next, there were questions on the workflow of getting the codes from Github. Using Git to collaborate with people on one project is a pre-requisite to ... err... collaboration. Knowing how to do this will enable you to join and contribute open source projects. Here's the basic workflow for Open Hippel (so far):
That's the basic workflow, be sure to look at the links on the syllabus's Week 1 section.
One more thing, hippel_kit will be a collection of "drush make" files, which will allow you to easily pull down everything needed to set up Open Hippel! Check out http://drupal.org/project/drush and http://drupal.org/project/drush_make
So, for this week, please set up Drupal along with Open Hippel by forking the repositories on Github. It may be worth doing a few forking, pull requests / merging amongst yourselves as well, so everyone is comfortable with working together on the same code base.
-Nick
Comments
Is there someplace with a
Is there someplace with a list of dev "features" that have been built out on git and which are todo? Do the user stories match one to one with dev features?