Template:
- Where is your head at? Good life/work balance?
- Check-in
- Product(s)
- Community / Users / Support
- Marketing / Outreach
- Metrics
- Threads to pay attention to:
- Make it easier to go to your own page
- Stian, Alison, Jose UX testing
- Subject "Thoughts about the platform"
2 July
- School of Open update
- Cohorts
- Priorities for July
- Loose ends:
- Dev prioritization process
25 June
School of Data - Cohort feature
- Spec'd out with mockups - input from dirk, philipp, vanessa, and Laura (+Karen Fasimpaur)
Mechanical MOOC
Berlin Planning
Development priorities process on community list, clear flow of how it works
18 June
- Free UX input = User testing / HCI thread on community list
- how do we respond to feedback like this? how to encourage more of it?
- how to turn feedback into suggestions (make it easier to improve based on these results)?
- something is broken -> this is how to fix it (or here is the fix)
- [John] encourage people to take things as far as they can, maybe help them figure out what's next and tell them
- [John] Keep relevant learning with the upcoming projects (ie: feedback about signup can go on the sign up card on trello)
- Development priorities email / update
- [John] to close discussion thread (resolve any remaining issues)
- [John] to let dev and community list know what the process is
- Mechanical MOOC
- Sign up form domain [philipp] - you can use launchrock...but it's kind of spammy, maybe just embed a google form for now
- Wondering why - Newsletter and T-Shirt design tasks not moving forward
- Projects with dev implications
- School of Data - Shuttleworth/Open Society Foundation
- Badges for learning / 21st century skills - Hewlett
- Badge issuer (from courses) - DML
- Mechanical Mooc - Shuttleworth
- Summer projects planning
- "John not updating/sharing"
11 June
- Very quiet (no community email, no response to individual emails, nothing on this pad) - Reasons?
- Process to determine dev priorities (subject "setting and managing development priorities")
- Product discussions (notifications, HCI, finding courses)
- Catching up on all the 100+ threads on the community list
- Dev priorities thread in particular from thursday
- Mechanical MOOC planning - Not a good model for me to assign deadlines
- Philipp set deadlines, I should be planning that stuff
- Original discussion didn't seem to match exactly what came up in the first call with partners
- Not really sure what we're planning and which org is responsible for all the different parts
- P2PU responsibilites
- "DailyLit-type" software
- Sign up form
- Collect email and some other data
- Disclaimer / Terms of Use / CC BY SA
- Ability to re-start (sign-up for next round)
- Group formation
- Run script to assign people to groups - TODO
- Quit group
- Exit form that asks why people quit
- Send emails
- Script emails on etherpad, copy/paste into form to send out
- Default: text email
- Nice to have: HTML formatted emails
- Archive full record of communication
- Relaying email from members
- Limited admin / research features
- "Script" - Content that is sent out every week [Vanessa/Philipp to write]
- School of Data next steps - talk to Laura and develop project plan / implementation / deadlines / priorities
5 June
- Terminology discussion - are we ready to call everything a course?
- Most terms are clear, need to write up usage of "course" with supporting arguments
- Question -> how is dropbox quota for P2PU calculated?
- don't worry about it - so many bits
- Employee status for US staff
- When we get to renewing contracts this summer
- Design work - next steps
- Two parts
- Bekka & Philipp following up on Newsletter & T-Shirt
- Website design - how to make progress
- Let's slate this for first week of Berlin
- P2PU Labs projects design ideas
- Development pipeline / planning:
- define core platform components (for each: status, next steps, key issues / problems)
- Schools
- Notifications
- Challenges / Courses
- Cohorts & Discussion
- Profiles
- Search & Discovery
- Badges
- (Mentoring)
- How should P2PU prioritize?
4 June
- Dev hiring
- Short term gig focused on front end / UX
- investigate creating an automated deploy script
- consider migration from linode -> heroku
- estimate total cost for current load, and estimate future
- what would our system look like (we have some servers we may not be able to migrate to heroku)
- request non-profit discount / free service
- Senior mentor
- Berlin update
- Visa issues (get more developers?)
14 May
- Big picture check-in
- Where is your head at? On safe ground?
- Not sure what's going on / lack of certainty about "lab direction" impact on own work
- Are we making a fundemental change?
- Many people are having a crisis
- Want to focus on things that are relevant long-term
- Your vision / goals <> The Lab. Opportunity to provide leadership?
- Increase programme involvement
- Community in Tech
- need to make changes to the site that don't need community input
- let's move forward on those
- after NY, let's discuss streamlining community review process
- 3rd party apps
- Product / Platform
- Next steps:
- Define core services
- What are the core P2PU Services?
- What are the core ways we allow external modules to extend P2PU?
- Work on lab-platform framing / modular structure
- Review pipeline and adjust priorities if necessary
- Get pipeline in sync with funded programmes
- Ability to support a cohort for School of Data/ School of Open
- NY offline
- Frontload priorities for Dirk
- Dev position hiring
- Other loose threads ...
- Next steps on strategic plan development
- Board meeting report (this Thursday 17 April)
- Task teams (John: lab platform / but out until 3 June)
- Berlin
Parking lot:
- Developer hiring
- School of Data
- Discussion forum
- HTTPS
- Lab - ongoing conversation
- Question > how do we distinguish the site from the lab/organization?
- P2PU has a lab <> P2PU is a lab for social learning and supports projects
- P2PU is run by a community who want to change the way higher education works. We are a lab.
- Dashboard / Metrics
- Add weekly?
- Number of users active at any point during last 7 days = level of activity (looking for growth)
- Number of users active at any point during last 30 days = level of activity (looking for growth)
- Number of users active during last 30 days and during 30 days prior = retention (looking for persistence)
- Lab platform structure
- Project idea -> MIT/Codecademy/OpenStudy mooc, ties in with "let's talk TED talks"
6 May (continued 7 May)
- Check-in on overall status
- Need to define the change/ direction we are going in
- How are we acting as a lab?
- Explore workshops, setting conversation, moving the field forward
- Identify big problems to solve, then lead the community in solving them
- Take care of existing community
- Think about support / curation
- Pragmatic technology solutions that make our users life better
- How will it change our day to day work? (--> platform)
- Central place that holds together
- User accounts, API, learning portfolio/badges, relationships
- Is lernanta holding us back (influences overall experience)?
- How to get there:
- Start thinking modular
- Define interfaces and use them internally
- Big new ideas / projects / initiatives
- Profiles (what I'm looking to learn)
- Lab technology strategy
- Lab web presence
- Mentoring (parked until Berlin?)
- Value proposition in modular architectures
- What's the value to someone using our API
- What's the value to us from someone using our API
- Questions to ask:
- Level of integration with P2PU.org experience
- Is it a strategic investment for us? (Does it require resources)
- Discussion Forum
- Next steps (John):
- Investigate different options (disqus, intense debate, etc.)
- Make a recommendation which one to choose
- Last week catchup:
- Developer hiring
- FlossManuals / Badges
- Strategy to deal with test course spam
- GA
- quick fix -> how to review webcraft
- seminar
- Metrics
- Group creation can be improved (most groups are spam or test)
- Rolling forecast (compare to last 30 days / project for next 30 days)
- Useful metric we don't have at the moment -> sessions
- Active users (logged in number of times)
- Conversions
- Sign-up is the first step
- What's next?
- TODO:
- Create a few statsd queries and store in google doc
- Investigate ways to look at metrics over time
- Put in place easy fixes / improvements to scoreboard
- Groups created
- Rolling (last 7 days) for some of the tables
- Feedback (in research course) on discussion forum
- reply to comments?
- options:
- Contact Disqus about possible free account with API / SSO access
- Lab web presence
1 May
- FT Developer
- Come up with a list of names / people we already know and think could do the job
- Do internal evaluation (make sure we consider hiring them)
- Then take next steps (tech screening, other interviews, etc.)
- Next step:
- John to review trello board and put together short list
- Set up tech-screening for promising candidates
- FlossManuals badges conversation / audacity course
- Candidate for P2PU as badge provider
- What is our offer?
- Start thinking through implications of P2PU issuing badges on behalf of courses / schools
- Design product
- Feature set required to support (without major intervention from us)
- Next steps:
- John to think through offer / product
- Reach out to FM community to better understand the need (and opportunity for P2PU to support)
- Also see -> http://badgepost.com/catalog/
- What can we do to reduce the amount of "test" courses that are created?
- Two things:
- We have too many test courses - need to reduce "clutter"
- Users have an interest to express who they are and what they hope to learn - they currently use "create a course" feature to do that
- Next steps:
- John to come up with a quick fix for clutter
- Longer term development of a better feature that let's users express their interests
- Aleks not on staff list for Berlin
- John didn't ask to send an application
- Use product manager budget
24 April
- Board meeting update
- No input for board report (disconnect?)
- Tech lead vacancy - short-term/ long-term
- Shifting responsibilities within team
- Recent application looks interesting
- Overall check-in on projects
- Product
- Challenge Creation
- Bucketing Dev Projects
- Could we pick a few major pain points and do something about them? (e.g. notifications)
- Community
- Terms - Community Call this week
- Outreach
- Metrics
- Berlin funding (contribution from product manager fund)
- Decided to move 2000 over into berlin budget (need to ask Bekka to do)
- Platforms to review
- Share with list(s) and cc John so it shows up in his inbox
- Feedback from London
- API/Platform discussion - (maybe useful contact) -> http://apievangelist.com/about.php
16 April
- Updates from Philipp
- Goals for London
- Impact of Lab Ideas - Discussion of scenarios
- http://pad.p2pu.org/lab-notes
- Right now the website is one product
- If the lab has multiple projects we focus on - this would have implications on product manager role
- Original goal was to build a place that allows you to find people, connect with them, learn with them
- How does the lab set priorities?
- Status (and send update for board meeting - last 3 months / keypoints)
9 April 2012
- Metrics
- Recs for Alison's group tracking
- When we automate, important to keep historical data as well
- - /scoreboad has all the data, we just need to build a display
- stats.p2pu shows the historical data very easily, just have to look at it and add tracking codes for important things
- Conversions?
- We should think about this like funnels
- Main Funnel: People visit the site
- They join the site
- They do some desired thing
- Creation Funnel:
- Registered user clicks create
- They finish the description
- They add tasks
- they click "publish"
- Design (what are next steps?)
- Review overall brief
- not rebranding or developing corporate brand identity
- refine what we have and build on existing identity
- focus on uniform design across website
- do a few small design projects besides website (t-shirts, newsletter)
- Review group
- Ideas
- first: 1:1 chats
- then: small group
- then: community list for sanity checking?
- by the time we get to the community it might not be as useful of a discussion
- perhaps a solution is to get volunteers from the communtiy to join group (so the small group is actually known)
- Sources of difficulty
- It's hard to get ideas from people who don't draw things or provide examples
- hard to convey ideas without making something
- Adwords update
- Two course organizers are running their own campaigns
- How can we make this available to more people?
- Webmaking 101 "Lean" Example
2 April 2012
- Quick check-in on big picture developments
- some issues in the past few weeks
- we're friends and share a common goal
- let's work through them and come up with resolutions:
- design group, berlin, lab, TNW, badges, and one more
- Confirm time for monthly call tomorrow
- Go back to original framing of these calls:
- Things to call out from past week
- Setting priorities for next week
- Getting unstuck
- [additional] group them by bucket
- Internship application (Srishti and others)
- I responded "will get back next week"
- this is for a volunteer position
- Next steps:
- TODO John: Confirm that all internship applicants are in the Berlin pool (send 4 names to Bekka)
- School of Data
- Certification - test case for paid certificaiton
- school of data section on p2pu.org
- schoolofdata.org landing page
- Buckets -> What about support and metrics? Good to call those out specifically. Marketing less important?
- Moving challenges development forward
- First step: creation
- Package for development pipeline
- Every module should have an owner
26 March 2012
- Berlin
- Applications (no dev yet, but John has a few in the pipeline)
- A few intern developers to apply as well
- Workshop venue (with kitchen) - wikimedia house not moving forward, exploring supermarkt and other alternatives
- Next steps:
- John to kick BB in the loins, and reach out to a few Berlin start-ups about venue
- mooc - massive open online course
- WSGR support on helping our users understand terms of service better (get into pipeline - but not immediate priority)
- federated lernata examples, who else was thinking about it?
- Talked to jessy - the only why she had was to try it out
- "i think that running a standalone instance of lernanta would do more harm that good in trying to kickstart a community around open science efforts"
- are more instances a good thing or a bad thing? neither - will explore going forward
- ask "why?" when people want to set up separate instances
- related to "identity" of schools: https://trello.com/c/kxET5OKW
- London agenda planning
- John, Nadeem, Bekka, Chloe
- 18 April (23rd April Board Meeting)
- Venue (tentative): Mozilla office
- Translate "lab identity" to the web
- what does P2PU.org feel like?
- what's the experience?
- how does the lab character related to the learning platform/community?
- Lab framing catch-up (after letting idea sink in)
- http://pad.p2pu.org/lab (old notes from conversation with allan and others)
- What's different?
- Wow, P2PU is changing the way people learn and I can too. They're even available to help me out.
19 (moved to 20) March 2012
- From the community call notes
- John: "Create standalone groups" Philipp: "(we need groups attached to challenges first - that's the use case we have to support)"
- I think we're saying the same thing.
- Right now challenges are "attached" to groups, we need to add the functionality of a standalone group that can "work on challenges"
- First version:
- 1 challenge / group (future goal: same group can work through multiple challenges)
- Design process - working with small group as agreed
- Involve Philipp in pre-community decisions when requested (or discuss why not necessary)
- annotator thread
- don't have bandwidth to do this "properly" right now - could look at it again in 6 months or so
- Philipp to send email to dev list, otherwise we'll let it go
- weekly calls - try not to let things pile up (yes, but how?)
Unfinished 12 March 2012
- Articulate key goals for Lernanta
- we don't really have a good overall framing for Lernanta
- is it a platform for social learning
- social learning space
- packaging things up as features
- keep notion of lernanta as a tool for partnerships / projects
- and consider that we are influenced by funding
- P2PU as a Lab
- Question of identity (not just messaging)
- Work on wording / messaging to make sure it's clear and compelling to existing community, people we want to join the community, and people who have never heard of P2PU
- Confusion around wording because two things have the same name
- It's not every day that you can step through the door into the community that runs the site
- If we found something we can do that is more effective at making learning awesome than our current site than we would go ahead and do that
- Could be two different messages
- We run p2pu.org - it is a place where you can learn anything, with anyone
- P2PU is a community-operated lab that changes the way people learn online
- Are we like Wikipedia? Most users never see what is going on underneath.
- Are we like Mozilla? Most people only think of Firefox.
- Who do we exist for?
- Implications on the site:
- http://okfn.org/
- http://okfn.org/projects/
- http://okfn.org/wg/
- What do we need to get this started:
- Make it feel more malleable (community owned)
- Collaboration features will not be hosted on p2pu.org / more like entry points to project
- Entry points through p2pu.org
- Content:
- Lab page:
- What are the current projects?
- Assessment
- Badges
- Better courses (learning challenges)
- Open Science (Jessy)
- P2PU Dev / Lernanta
- Next steps:
- Philipp: to contact project leads as about entry points into their projects and a short description / blurb
- Philipp: work on framing of P2PU as a lab (avoid confusion around site / project / community)
- John
- provide images / widgets that they can include in
- Schools feature
- We'll look at this *after* working through other priorities:
- Ideas/ Questions:
- Let anyone create one but "official" schools carry more weight
- Is there a "schools" feature that would be attractive to outsider without requiring interaction?
- Schools feel more like independent "spaces" (you arrive at the schoolofdata.org - and not at p2pu.org)
- Example -> Kickstarter curated pages (require approval)
Decision making- Summer projects curation (tech / non-tech)
- Bekka -> non dev / John -> dev
- Internships vs fellowships (what's the difference?)
- Internships partly virtual
- Interns need funding, they apply for fellowship
- march pace
- 0% users
- +20% comments
- - 6% joins
- - 32% groups
- moved notes from monthly calls to http://pad.p2pu.org/john-monthly
12 March 2012
- sxsw debrief
- London plan
- Challenge Financials
- June & August
- Focus just on July this year
5 March 2012
- Badges Competition update
- NSF proposal udpate
- Make decisions this week
- Learning Lead interview
- Design
- Invoices
- Process
- Separate site-wide interaction from specific ux
- Style Guideline: We do things because we can, the kinds of things a a traditional institution couldn't get away with.
- Challenges Launch
- Challenges / Sets / Courses
- Map to expectations
- Balance informal/web with learning/education
Reading List
27 Feb 2012
- Reading List / Discussion Topics
- MITx
- Stanford AI course
- Udacity (for profit started by AI course instructor)
- Coursera (Stanford owned for-profit)
- Questions:
- What are the key features?
- Huge audiences
- Recorded lectures
- Small quizzes / Automatically graded exams
- How will they scale?
- Build once
- No individual assessments necessary
- How are they different from us
- Content consumption driven
- Using deadlines
- No explicit support for collaboration (yet)
- Linked to traditional academic courses
- Connected to formal "authority"
- Everything I do falls into one of five buckets
- Mostly
- As needed
- Question about partnership / projects - School of Data
- Useful to think about: what are your buckets? What are other staff buckets?
- SocHack Warsaw
- Education Hackathon
- P2PU is a media partner
- Hiring
- Process for setting up schools
- When committed resources hand over to John for planning of product implications
- I saw that you updated the challenges (thank you!) - what were the changes you made? what did you learn about creating a "good" challenge? i think would be super helpful to summarize and share.
- TODO: Started taking notes send to community list
- New users/week for past 10 weeks [protected]
- Communications opportunities around challenges
- "online courses: if they don't suck, they don't scale"
- doing two marketing pushes
- March 7 - A new way of learning online
- --> "take one of our three featured challenges"
- three exemplary challenges
- differnet topics = "challenges work not only for technical topics"
- HTML in the world around you
- DIY U
- Writing for the web
- stories of people
getting badges and using them- why the challenge was "more engaging"
- what they built (learning-by-making)
- Mid April - Everyone can make a challenge
- challenge creation process (Mid April)
- --> make a challenge
20 Feb 2012
- Reading List
- The Management Team - Joel Spolsky
- Staff
- Contract developer candidate
- Try to make a decision on Weds in the tech
- Full time developer candidate
- Try to make a decision on Weds in the tech
- Philipp to talk re: Salary
- Summer Internships in Berlin (application / qualification process)
- If applicant needs/wants travel / accommodations
- Apply to Berlin Fellowship (~first of april)
- Without travel / accommodations - just show up
- TODO Philipp to contact lawyers
- explain "fellowship" idea (covering costs for travel)
- clear that 17 year old is ok for internship
- Note to not confidential info into public calendars
- Proposal on how to tie up the course/challenge/study group discussion
- Primary focus for the week
- Metrics example - http://openmi.ch/-board (dmalicke@umich.edu - Dave Malicke)
- When is the right time to add FB/G+/Twitter buttons?
- I'd like to address sign-up flow issues first so that we can capture as many inbound users as possible
- Put a FB "Like" button on the site (use widget that shows the people who you know who like the page)
- Alex priorities - Should have an overview somewhere (specific question about newsletter)
- UK in April - do we have a final date:
- Webmaking 101 report - artefacts made courses more active/engaged (need proof/stats)
- In John's interviews, people singled out HTML Writing by hand, and HTML hunting as the more engaging
- 5 interviews?
- TODO: John to confirm 5 and make sure we have transcripts somewhere
- Other updates on Webmaking 101
- Amount of Peer learning, what's the quality of the interaction between participants
13 Feb 2012
- Paul Bakulish Email
- Interviews
- Dirk faces Paul
tomorrowFriday - Ricardo waiting on coding challenge (useful work / 100-200 USD)
- Snapshots / qualitative information for Webmaking 101 report
- TODO: 3x picture/screenshot + quote + short description
- tied to interesting findings where possible (even if they're not already in the report)
- before noon tomorrow (aka tonight)
- Update on School of Data
- Relevant for Lernanta/Product:
- Need ability to create groups / cohorts - with facilitation and support
- Sustainability:
- Plan is to experiment with charging some users for facilitated courses (but keep the challenges free)
- Financial transaction handled outside of P2PU
- Questions:
- Private vs public?
- Are cohorts physically separate, or filters of a broader community
- How do we set the price?
- TODO: Brainstorming on Cohorts
- Update on DML Competition
- Chloe UX stuff
- Webmaking 101
- TODO: Three or four problems in challenges and how we addressed them
6 Feb 2012
- Webmaking 101
- 5 of 7 complete, 2 more left
- Lots of activity
- Some badges seem to be a bit hard and need more reviewers
- TODO: See email from Philipp - add content to Chloe's report draft
- John/Philipp Meeting plans for March/April
- 18 April Wed (London or Cambridge)
- Am I going to the UK? Yes please.
- TODO: Book flight
- TODO: Plan 21-22 April - P2PU London Techsprint
- Laurian Gridinoc
- Nadeem
- Rufus Pollock can help us find more (he is not there)
- Can't do 21-22, aiming for 14-15 instead
- Philipp meeting with Albert at SXSW or NYC
- TODO: John Email Philipp and Albert to set date/time
- Hiring:
- Portugal developer (good rate, skill tbd)
- Unless Brian rules him out - we can try him for 3 months
- South Africa developer
- phone interview scheduled
- Discussion / Commenting needs work
- Thoughts on using 3rd party commenting (disqus) with SSO
- What about a django discussion package / app / module?
- Related? Website Editor discussion on mailing list
- TODO: Research Django discussion packages
- shuttleworth question
- Three or four main features of the "product"?
- Kickstart a new learning community
- Learn anything with other people who share your passion
- Get recognition for your achievements
- Find mentors
- Thought: The whole "lab" idea is missing in this story
- Berlin plans
30 Jan 2012
- Webmaking 101 Challenges
- I'm working on this now. I will get it done, especially since I'm not redoing everything.
- It's a small project!
- Mentoring
- Next physical meeting (SF, NYC, London, Other?)
- Let's try to make these roughly quarterly
- TODO: Philipp to check with Chloe and Bekka about meeting in UK
- Hiring Developer
- Did you follow up with Brylie? Yes - told him we needed a little longer
- Call with Abe
- What can we offer him, if anything?
- He's available from May
- If he comes to Berlin we'd cover his costs (transport / accomodation)
- If Google Summer of Code happens, he can also be paid by Google
- Another round of outreach
- More applications (only a few so far)
- Ideas? Sent email to Rufus (OKFN) who said they have too many applicants, and Sunil (friend in India)
- TODO: John to ask some people in Poland
- Scoreboard
- Would be good to expand with "top groups"
- Create a list of high profile challenges
- We think people like challenges and that they are driving traffic
- Let's design some challenges on other interesting topics
- Each staff member creates a challenge with a high-profile collaborator
- Brainstorm:
- Open Governance / Community Building - Jono Bacon/ Seth Godin (Philipp)
- MBA Monday Challenge - Fred Wilson (John)
- Cyberpunk Fiction - Cory Doctorow / China Mievielle (Bekka, Nadeem, Laurian)
- Creative Writing - ... (Jane)
- Food - Gordon Ramsey / Jamie Oliver / Heston Blumenthal (Niels)
- Video
- Travel
9 Jan 2011
- Mentoring (come up with next steps)
- How to track success for Hackasaurus challenges?
- Mentoring blog post -> http://alexkehayias.tumblr.com/post/14267008843/learn-to-code
- Could bring him in as Head of Webcraft Mentoring
- Is mentoring a "feature" at P2PU? Yes!
- Map out a mentoring feature, post to community... MVP style
- Once post is ready, share with Mimi Ito for input
- Share notes on chat with Andy and Albert
- They like us, but pushing for for-profit (not totally though - impact question)
- Hiring update
- Aleks said he'd send the signed contract today (Monday). Will co-sign and return right away.
- 8 interviews (Paul did 3) -> 1 possibly moves forward
- Zuzel/Philipp to talk with him next
- Consolidating Groups
- Proposal coming on Wednesday
- Hypothesis:
- Challenges + mentors (+ a little bit of magic) = everything you can do with courses
- Key differences
- Application process
- Start/End date [Not currently supported]
- Group feature to control who can join
- "Authorship" - you can't see who created the challenge
- Mentoring
- Badges and assessments (built in)
- Meeting with Alan Webb
- Interesting question - how can P2PU support custom development that's not part of our priorities, but does support bigger term vision?
- No problem for features that are suitable for general audience
- Features that are not suitable for general audience - would need be an income opportunity (or resource acquisition opportunity)
- Webmaking 101
- John: "I'm doing it TODAY."
- DML Proposal
- John: "I'm doing this after Webmaking 101." ;-)
- Draft possible Webcraft future scenarios
- Hackasaurus style - more independent brands / communities
- Good model that we could take to others, e.g. JQuery
- Needs less admin/coordination overhead, but also
- Less community (potentially)
- Remains a major Mozilla initiative hosted at P2PU (but need to find someone to lead on content and community)
- Experience of finding someone to run it has been difficult
- Managing relationship with Mozilla complex because requires strong integration at all levels
- P2PU takes over Webcraft (with less Mozilla branding / push)
- It's not our community - P2PU are not "the experts" for web development
- We'd have to find the money in addition to finding the right people
- = > Not really an option
2 Jan 2011
- Logo / Brandbook
- Get fonts into the hands of the people (license) -> dropbox folder
- Version for use on grey background coming later
- Hiring
- Designer Hired
- Contracting next steps
- (Soft) Max of 20 hrs / week -> 80 hrs / mth
- USD 30 / hour
- Can bill more if necessary
- 6 months
- Send monthly invoice with outline tasks
- How to define monthly deliverables / tasks
- John to work directly with Aleks
- Mon: Synch up on overall goals with PS
- JB/AS Weekly call Tuesday
- Wed: Report back to dev call
- Pure design work (wireframing, content, UX has to be done prior to getting to Aleks)
- Community calls
- Join calls when things to present
- Developer Interviews
- Ongoing this week
- Goal set up interviews on weds in dev call with zuzel then philipp then staff
- "Interns" -> Possibly get started with Abe for now, Paul only in summer
- John to figure out how to structure - internship, part-time, etc.?
- Webcraft 2012 post - after webmaking 101 update
- Report on webmaking 101
- Jam packed with stats, and cool stories
- After post goes up -> Set up a call with JB/PS and Mark, Ryan, Erin, Steph(?) to discuss future
- Course / Study Group / Challenge consolidation
- TODO: Post to community [goal for this week]
- Hone in on one key question
- Distill existing notes from calls, add opinion -> develop a proposal
- Share with Philipp ahead of time
- Two steps
- Present current thinking, and get more ideas from community
- could get messy, closed in one week
- Create a proposal based on disucssion and send to community
- Mentoring
- Experience so far
- sent emails to all that requested mentors
- got less than five replies
- scheduled calls, nobody followed through (holidays)
- will schedule again
- Improvements
- It's a compelling offering, but we really need it to be a first class feature for it to be useful
- Low-tech version to test different ideas?
- Next steps
- Move this to next week (unless John has time to think about it ;-)
- Webmaking 101
- Projects Delivered December 2011
Weekly Update - 19 December 2011
- Badge Reviewers Contacted
- Mentorship
- Idea stage for how to structure / support mentorship
- Test out in "simple as possible" ways (as little as possible sw development)
- Job Posted - ~15 applicants
- GSoC
- Q: When do we know if we get it? A: Not for a while (applications not open yet)
- Timeframe: May - August
- Budget 5k / intern
- P2PU Internship
- Paul Kernfeld - potentially bring on part-time now, then move into GSoC or Berlin (or hire if we have more money by then)
- Use John's discretionary funds to get started
- Full-time
- More money?
- John's discresionary budget - 5k USD reserved (will roll over into 2012 if not used)
- Money from events
- Re-purposing salary
- MITx
- Outstanding
- Webcraft 101 content update
- Designer - get formal application from Alex... it's on the way
- Logo Updates / Design
Weekly Update - 12 December
- Webcraft 101 content update
Webmaking 101 updateBadges - recruit volunteers for Webmaking 101 (see my email)TODO: Contact 5 people from webcraft to review badge requestsCaley WoodsJamie CurleJessy Cowan-SharpVanessa Generelli
MentoringMore offers (15) than requests (10)John has contacted all mentees - but no replies yetTODO: Follow up with everyone who has requested a mentor (about 7 people)
Post job description - Django Developer- Designer - get formal application from Alex
On hold: Webcraft position (Challenge designer / community coordinator)
28 November 2011
- UX Contract
TODO: John to follow up directly to see if Arlton can work with Chloe directly on front-end dev for challenges.
Hiring in general (job descriptions)Will post description to staff soon (tomorrow)
Challenges UX work / fixing bugsPotential for overlap between Chloe's work and John'se.g. group creation process
Challenges work needs to hit community list / follow general dev process (pipeline)
Mozilla Challenges ProjectMozilla web making across different projects Why is this important
UX quality assurance - process to catch small bugs / improvementsWhen we send out a release, post to list with areas to test
21 November 2011
- challenges
- update webmaking 101
- John to bucket two days, get feedback and then bucket one more day
- more challenges - jessy / chloe
- haven't done a communications push yet
- webcraft position
- TODO: Job Description - Challenge Designer / Community Manager
- development positions
- design - contract work
- 2000 - 2500 / mth (half time) (may not use the full budget every month)
- ux working group - jose, oliver ding, joao
- 1 FT developer, needs job description
- 50% badges & assessments
50% learning challenges- Django Devleoper + javascript / front-end
- metrics