Releases:
- 24 Feb
- Swedish, Dutch, Chinese initial support
- Course "delete" functionality for side admins (to control spam)
- Language for courses, challenges,... (preparing for the learn page update)
- Duration for challenges
- 9 Mar
- Chinese fixes
- Swedish Fixes
- Learn Page
- Community Reviewed Groups
- 23 Mar
- OBI integration update (disabled, penindg release at beta.openbadges.org)
- Bagdes can be marked to be available in all challenges
- Scoreboard Improvements
Feb 29
- Status of etherpad migration preparation for this Friday
- email sent to the community mailing list
- http://etherpad.p2pu.org will replace http://pad.p2pu.org (i.e., pad.p2pu.org will serve etherpad litle)
- etherpad.p2pu.org/tech redirects to etherpad.p2pu.org/p/tech so no links get broken (without breaking other url patterns used by etherpad little)
- the /p/ part is harcoded on several places of the code so adding a bit of javascript code to etherpad-litle/node/server.js was a cleanest solution i found
- etherpad little does not has an admin dashboard so at the moment api calls need to be used for most admin stuff including creating groups, creating pads in a group, setting password and visibility of groups pads (https://github.com/Pita/etherpad-lite/wiki/HTTP-API)
- if the creation of password protected pads is only going to happen from time to time I can do it manually
- test at http://etherpad.p2pu.org/g.G9I8LjqVPdvZ1fPl$protected
- no email is involved in the process
- also as far as i have discovered etherpad little only sends email when safeRun.sh restarts the etherpad and 'mail -s' is used for this (not available at the dev server at the moment since we have not installed postfix or exim or ...)
- padsearch.p2pu.org/etherpadsearch.php (searching pads on etherpadlittle) will replace padsearch.p2pu.org (searching pads on the current etherpad) when the migration occurs
- Replaced favicon.ico
- TODO: etherpad embeds?
- Hiring report
- Learn page
- Zuzel implementing mockup
- We've been working on the design for this page, we're basiscally going to stick to the wireframe that we proposed before.
- Spending some time on three different types of pages at P2PU
- Application Pages
- Learn, Contribute, Profile
- The style is a smaller functional header that gets out of your way
- Landing Pages
- Staff, Jobs, About, Get Involved, etc
- The style is a large image heavy header and a simple message with some additional static content
- External Pages
- blog, help
- Inconsistent styles (for now) but would like to bring these closer to the p2pu look in the future
- Community Badge Survey: send to all users, any other items to add?
- who is going to help with the text/cotent of the email (maybe cc. alison and bekka in case there is anything else to share in that email)
- links to blog posts
- categories of newsletter
- the newsletter goes out everyweek -- bekka sends it (throught sendgrid?)
- Hackasaurus: when should we expect a pick in visits to those pages?
- I was going throught the google analytics yesterday
- We don't know who will be comming to the site (small launch followed by bigger launch?)
- Ideas for organinzing content + teams (Cohorts, playlists)
- cohorts (team is a better name): if there is signup, dates, ...
- you have 3 options : open team, by invitation, by application?
- challenges (can we name it course?): content
- Lets refine those wireframes add this idea of "teams">> and send them to list?
- Since we have time, do you want to review my ideas for stealth community badges? http://pad.p2pu.org/communitybadges
Feb 22
- Hackasaurus Challenges (Are we rolling out a major UI update by Monday? - mentioned by Laura during MoFo call on Tuesday)
- No major update. Just adding badges she sent to the challenges/tasks.
- And MoFo people need to recreate the challenges to change the URLs.
- Do we have all the data we need for the new badges?
- Saw laura was including logic descriptions with the badges (are those going to be changed or is a new instance of the logic model with min_votes 3 and min average 2 going to be created?
- Chloe: We are not doing any logic updates for these badges.
- Zuzel and Chloe stay on the call after 11 am to setup badges
- What was said on the MoFo call? Just that - some major update coming ;-)
- Future Updates
- The learn page which is the next big UI update depends on the community review functionality so it will probably not happen by Monday (so it will not affect their challenge launch)
- Thought we could try to have the learn page without the community reviewed filter and add the filter when the community review functionality is ready and we have a good number of courses reviewed (depends on when the design is ready)
- Can someone write this up and share with the community/staff when we launch?
- Any updates on the Aleks/John's designs for the jobs/staff/learn pages?
- Should we move the release for next Friday so there is time to finish the designs/implementation and for the accepting/testing step?
- Should we add a column or color tags for designing stage (i.e., aleks/john's work) on the project pipeline?
- PSDs are pretty much done, will link them on the card today. Aleks is finishing up the Learn page today.
- TODO: John write guide for different featured categories on the new learn page
- Should we start sharing notes from this call to p2pu-dev?
- What's the benefit?
- Be more transparent about what's going on
- Yes / no?
- Chloe: no/ someone needs to edit = extra work
- Philipp: yes/ let's just do minor edits - keep them rough ok for dev list @.@ :)
- Zuzel: If we don't take notes regarding hiring interviews or something that shouldn't go to the list we can send them to the list. I don't think they will be usefull all the time but if people are curious we should send them.
- Gunner: filter for "news I can use" (things that will impact you, where you can help, what you have to know...)
- Decision:
- We all keep good notes during the call (suitable for dev list audience)
- Zuzel reviews and sends to the list after the call
- No discussion / just parking this for now -> Good metrics examples
- http://openmi.ch/-board (dmalicke@umich.edu - Dave Malicke set this up)
- Needs discussion about metrics next steps (not for now)
- Etherpad Lite Next Steps
- Planned migration date: March 2nd
- Shut down pad server so there is no editing that gets lost
- Then migrate
- Then bring back up
- We will try to keep the same URL -> pad.p2pu.org no "/p/" on the new one
- Update search script for new server
- Will email work?
- First question -> can we have private pads in groups in Etherpad Lite?
- Do etherpad little sends emails? If so does the email work?
- If groups are possible -> please make the email work!
- TODO:
- Zuzel to let the community / dev lists know
- OBI status / update:
- TODO: Zuzel email to Brian see if the api is stable now (cc chloe)
- Update avatar images
- Suggestion is to use alison's drawings (stick figures). Yes, let's move ahead ok.
- need to upload the way we interface with gravatar
- send different size images to gravatar as default
- Use Alison's drawings in other places:
Feb 15
- Check with Zuzel regarding spam/"abuse" notifications - what can we do with content flagged as spam?
- In the case of comments, signup answers and others with a deleted field I mark them as deleted (set that field to true) after checking if they are spam or not. -- can be done on the admin site in most cases
- If the user is activelly spamming several courses or users I mark the account as deleted (part of it is setting deleted=True in the profile and the other is setting is_active=False in the django user so they can't login)
- If it is a course we currently change its status to not listed, and archived but soon we will set deleted=True
- If it is a private message I actually delete the message (the model commes from a thrid party app so that is the only choice)
- If the about of the user in their profile is the one reported but the user is not spamming others (the profile appears in their signup answers) we can remore the text that is causing problems.
- Some times the same spam is posted in in different places (e.g. private messages to many users or signup answers to several courses) it is useful to search for that text in the db.
- Rebooting the server -> Only Zuzel, John, Jessy, Nadeem have the power to do it.
- If Zuzel is awake - all reboots go through her
- If Zuzel is not available - John can reboot
- Etherpad migration update
- I don't have any news
- TODO: Zuzel to email Brylie
- Welcome back Zuzel!
- Adwords update (linked accounts) [John]
- http://pad.p2pu.org/adwords
- Has a few tech implications to enable conversion tracking
- Need to set up google analytics "events" on the site
- Linked adwords account to analytics account
- TODO: John adding a card to trello
- The way we use trello not a good way to store / manage small tasks example of sprints here: https://trello.com/board/challenge-fixes-1-1/4ed8ff4175e6467872117dcc
- Moving cards on the pipeline
- What cards go to the implementation column?
- @John -> Which pull requests can be merged?
- John went through all - look perfectly fine.
- Three from john, philipp's, brylie's ok
- not sure about recaptcha, migrations (tech), josmas's changes, and "my groups" drop down feature
- Do any need community review? - no
- What changes are needed to make them ready? - none / zuzel to make the call after review
- Are there tickets from lighthouse that will be included in trello cards?
- Hiring Process
- Which interviews are pending?
- Got update from Philipp yesterday (Paul is doing his review on Friday)
- John is planning to offer summer internships for UPenn students - good response
- Big Blue Button Integration
- Who should I arrange a meeting with? email?
- TODO: Philipp to introduce zuzel
- TODO: John to gauge demand for a P2UP hosted solution for webinars?
- OBI api updates?
- Hackasaurus Launch updates?
- Android app from college students for p2pu lab
- Quick question about metrics etherpad - http://pad.p2pu.org/metrics
- Does M4 cover "all times" or 1nov-1feb?
- Is M3 for IP or "users"
- Editor discussion (on the list) Worth considering a move? TinyMCE?
- -1 for right now but i like tinymce and ckeditor the same so it the users prefer tinymce we can change (will require time to configure and implement the uploads, and embeds custom button for tinymce)
- when I was implementing updloads last summer I started this process (integrating tinymce) thinking that it was going to be easier to use a third party app that works with tinymce for the uploads but the app was not appropiate for our use case so I stopped:
- This is on the roadmap for when we get to discussions
- All of this makes sense - please get back to the community so they understand the history and reasons.
- TODO: (zuzel or john?) Email to community to let them know the backstory on editor issue and that they can work on it. It's scheduled for when we work on the discsusion feature.
- TODO: Make a separate card
- Django Project for developer candidate
Feb 8
- Mockingbird account - can we get rid of the paid version?
- Zuzel: I did not know we were paying for this (it is important for chloe's and john's work maybe they know of an alternative)
- Philipp: Free account is 2 collaborators and up to 10 pages, 1 project - Paid account allows more pages and users
- Todo: cancel it from 1 April onwards (ask Bekka to do this)
- Abuse reports going to help.p2pu.org (clutter, can we get rid of this?) How are we acting on the reports? --who gets these
- FYI -> Nice visualization of dev priorities / roadmap (from Popcorn)
- Process for rebooting servers
- Server went DOWN and UP (according to pingdom) this week but there was no notice
- may not have been off, just unreachable... check linode logs
- confirmed that server didn't go down. could be pingdom report-mistake or server was too busy to reply
- CPU load
- Investigated it - doesn't seem to be an issue
- Hiring progress
- John speccing out a small project for one candidate to produce public code we can review
- Need Zuzel to chime in on this, but otherwise going ahead with the plan
- Working with the community
- Getting volunteers involved - See email about jQuery from Paul
- John talked to him on IRC
- TODO: Since Zuzel is away, John will send an email to the dev list to show that we welcome contributions etc.
- Letting the community know about dev processes (pipeline) - Maria's question
- TODO: John to create knowledge base article (+1) and let Maria know about the trello board and how to get involved
- SoW data report: need some hard data from Zuzel >> ?
- What data? Maybe John or I can help.
- Moving metrics into a separate etherpad -> http://pad.p2pu.org/metrics
- Next steps:
- Chloe to complete first draft (with placeholders for data from Zuzel)
- Rearrange in a way that looks close to the final version, starts with good stuff.
- Philipp and John to review give more feedback
- Complete on Monday when Zuzel is back
Feb 1
- Should we try doing this call in big blue button?
- http://p2pu.bigbluebutton.org
- viewer password: welcome
- P2P University Room - 1
- We've setup dial-in numbers for both rooms.
- Room -1 : dial 613-366-1985 (toll free:1-866-964-7085) and enter conference ID: 87190.
- On firefox and chromium (ubuntu lastest version) the microphone/camera access dialog does not respond (clicking allow does not do anything)
- On OSX/chrome the chat window required scrolling in order to get to the text input field
- dialing is working (does not play any music while you are waiting for somebody else to join)
- what has being the feedback from people in p2pu that have ask us about big blue button for courses and test it?
- Make it a card on the pipeline?
- Chloe offline today: traveling back to Europe
- How hard is it to update the "logic" on Learn page?
- Probably not a programming challenge, but an algorithm challenge?
- Answered Wrong Question: I will not call it with neither of those terms: big change will be more appropriate (i.e., if you explit it in smaller pieces it takes time to go through all of them)
- Among those pieces the "sorting by activity and popularity" and the "setup jquery for loading elements on demand in the list that has filters and sorting" are likely to be the harder ones (not mentioning tags filters because they are probably not going to be implemented as in the mockup -- se notes on the card)
- Wait for update of Learn page
- Hackasaurus Challenges - Update from Laura:
- DML is March 1 to 3, so we're planning on a February 27 launch (Monday of that week) of the Hacktivity Kit Challenges. Just wanted to mention that if all the functional stuff is implemented than other than launch support, we'll just be looking for feedback on the curriculum from p2pu side
- Any updates to the Project Pipeline?
- Cards that need to be moved?
- Need a new card for community review (next phase) - actually move the old card back because it has a lot of details
- @John: Please check which of the pull requests in github can be merged.
- @John: If time permits please take a look at the 41 tickets at:
- No tech call next week?
- Question: Any server performance issues after downgrade?
- Philipp: Looks fine from my side. John: No problems. +1
- Etherpad Lite update - Brylie
- [3:58:57 PM EDT] Brylie Oxley: Should I try backing up and migrating the db?
- [3:59:04 PM EDT] Brylie Oxley: Or should we start from scratch?
- [3:59:13 PM EDT] Brylie Oxley: (leaving the old pad in place)
- http://dev.p2pu.org:9001/p/testing
- Philipp -> Migrate
- Next steps:
- Test with community
- Ask Brylie to investigate search (this is not a blocker)
- After Zuzel comes back, migrate
Jan 25
- Dev process transparency
- Public release schedule
- Add dates to existing tickets/cards
- Discuss process going forward - who owns?
- Adding dev priorities to community call
- Why?
- Staff feels disconnected from development progress (and nervous about asking, because tech team is "too busy")
- Hard to know when to expect a feature someone is waiting on
- Did you ask if apart from the dates the card in the trello board match what they care about or are waiting for?
- Complicated to fit everything into dates if the cards have different "sizes" (some take 2 weeks, some take 6 weeks)
- Next steps:
- Each week in this call we discuss priotities and review the dates
- Try to design cards to be 2 week development "chunks"
- Update on Community Reviewed Groups - there is no wireframe / description attached to the trello card
- I added a link to the discussion of this functionality on community list.
- Review how the google analytics tracking of pages is working (see last week)
- Hackasaurus / School of Webcraft updates?
- Hackasaurus -> Hacktivity Kit instead of Interactive challenges > release end of Feb
- Will have first version next week (just waiting for the content)
- School of Webcraft -> No news, waiting for a meeting2
- Status of webmaking 101 mentors
- Mentoring overall
- John is working with Alex in NY to develop a better mentor project
- Willing to bring his 20 or so mentors and facilitate all of them
- Conversation rate from sign up -> mentor is VERY low
- Need to find out why.
- Needs to connect John and Alex with Tara Tiger
- What about the adopters? there are 89 "adopters" in the webmaking 101 - excellent point, we can turn them into mentors
- Mentors & Badges
- Is the "mentor" status implemented in the site? Mentors have more power in awarding badges.
- No, only links to google forms for recruiting mentors, mentees for the schools
- There is this http://p2pu.org/en/badges/mentor/ and this http://p2pu.org/en/badges/adopter/ but they are manually adopted and have no power it turns out :/ Problem with assigning mentorship status across p2pu, what happens when you are a mentor for one Challenge but don't qualify for another one? you should not be able to have that 3 times vote.
- Email from Tara - she submitted her details, but got no reply. Could be that this happened while John was offline. (there should be a bot email, that says "we ll get back to you soon or some something") +1 Yes
- TODO @John - set up emails from the spreadsheet
- How to connect help requests to the community?
- Emails to dev list?
- Add more volunteers?
- Note: Any p2pu user that logins into the help desk can change their notification preferences on help.p2pu.org to be notified when a new discussion is created. This will not include private discussions but those should only be available to people we trust and list on the help.p2pu.org as support staff.
- Added to community list
- Conversation with Big Blue Button (Fred Dixon)
- Goal is a prototype integration
- They are willing to host a server we can use
- We would build a very lightweight integration, so course organizers can schedule sessions on that server from within the P2PU course
- They will help us with the logic / design, but we would have to build it (dev resources)
- Estimate that it will take roughly 4 hours (they have Python libraries)
- P2PU -> Initial idea is to focus on SoSI
- API http://code.google.com/p/bigbluebutton/wiki/API
- Next steps
- Discuss at P2PU
- Try the demo server
- Contact Fred again in mid February
- Test server
- In the meantime - something for us to try p2pu.bigbluebutton.org
- Moderator pw: p2pm
- Student: student
- 1-800 number for US is coming
- TODO @John get community response / ideas on this
- Message to p2pu users and community:
- "We're having to do some work under the hood of our servers on the weekend of the 27th and 28th of January. This work is essential to keep p2pu.org running smoothly, and we apologise in advance for any hassles this may cause you. The site will be unavailable from *** time to *** time
, but we promise that all your personal information, course materials, discussions and challenge work will be safely kept, and fully restored as quickly as possible. And hey, why not use the downtime to lie in a hammock and read a book. tell a friend about P2PU? All the best, the P2PU team" - email to users, email to community list, blog post
- Hiring update
- Abe out
- Julio out -- Update Julio (talk to Paul?) ok
- John: contact Chris, Abe
- Philipp: update Brylie
Jan 18
- Hiring (interns) update
- Zuzel and Philipp to set up calls with Abe
- Zuzel check availability of Julio Carlos []
- Philipp sent email to Joseph
- Etherpad emails - need ability to use a password protected etherpad for board meeting (and requires email sending to work)
- Could a google doc be an alternative? - Yes, but sluggish in comparison.
- Can't promise I will be able to find/fix the problem - Ok, will keep google doc as backup solution
- When is the meeting? - On Monday 23 Jan
- Will send you and update on Friday - Perfecto!
Review how the google analytics tracking of pages is working (see last week) [moves to next week after the relase]- OBI integration still scheduled for early Feb? (Make sure it's in the project pipeline)
- Early february zuzel is going to portugal
- Chloe will
We should contact Brian (confirm that the new OBI api was released) and schedule it for late february // done
- Brylei / Chat
- Did not get a reply from him about working on this
- Hackasaurus / School of Webcraft updates?
- added it to next week agenda
- we will ask Erin/Jessica for an ET of launch
Jan 11
- Zuzel's tooth operation
- The worst part so far has being the initial bledding and my stomach which did not seem to like the sedation. The analgesics are working. Phew!
- I am starting to feel better today (fortunatedly I am not looking like a potato :D) so I will continue working towards a release at the end of this week. See how it goes! If you need to rest, please do!
- Hackasaurus Status
- The launch deadline was postponed so the people preparing content and checking that things are working will have more time
- On the other side this could mean Mozilla could expect that more changes are implemented which is not in our schedule for the next two weeks
- Please flag this immediately if it comes up. I think we should stick to the original plan - roll out what we agreed - and move on to other things in our pipeline. +1
- Also, they have a meeting this week to discuss how it went and what plans they have. I expect that we will set up another call with everyone (us and them) to agree on the plan forward.
- The three new features (challenge sets, badge applications from task, postMessage integration with external interactive tasks) from the Hackasaurus board are ready.
- Applause! This is great. (note, this is NOT 100% interactive- it is just a temporary solution till Atul has time to work on a more integrated solution - if they still want that) key is that they are happy with this in the interim
- Appart from the new pages tracked inside lernanta, I included more flexibility to integrate with google analitics
- Next monday we can check if the google analytics tracking of particular pages (e.g, home page of an specific school, home page of an specific challenge set, and home page and tasks pages of an specific challenge) in its own account is working
- Cool, let's add to next week's call.
- It also has the logged_in variable
- It will allow us to only report details about visits to the hackasaurus related pages
- Inside p2pu we can only count the number of IP addreeses so using google analytics will give us a better stimate of the first metric in https://etherpad.mozilla.org/Metrics
- Still missing some commits to have the Challenge Fixes 1.0 ready for release.
which ones? let's mark them on the board.
- Chloe and Zuzel had a call this week to organize the https://trello.com/board/challenge-fixes-1-1/4ed8ff4175e6467872117dcc
- Chloe: check we move any dev card from the hackasaurus board backlog to here (at least the OBI one is duplicated) will do
- Dev todo list for the next two weeks sprint:
- Downgrading p2pu linode this weekend or just after the release.
- Pick next cards from ready to implement column on Trello board:
- Community review of Courses
- Profile
- Planing Release of this on January 27th
- Metrics -> Mentoring (John)
- Has already collected testimonials from individuals in the past
- Goal: "capturing stories"
- Qualitative analysis -- Since you have their stories it can be done
- What they mentioned as possitive negatives experiences
- Added this into the metrics etherpad
- Future of Webcraft
- Different scenarios:
- Hackasaurus type / working with individual MoFo projects
- Same as before (Main MoFo initiatives)
- P2PU takes ownership
- Does it make sense to organize SoW workshop?
- Check where have people joined this month -- http://p2pu.org/en/admin/projects/participation/?joined_on__month=1&joined_on__year=2012
- So we have a good answer about from were the joing in the metrics board is comming
- I have being seeing a good bunch of spanish challenges
- # 1 Introduce Yourself -> 37
- # 2 -> 46
- Elige el Nombre the tu Sitio Web challenge -> 24 -- http://p2pu.org/en/groups/elegir-el-nombre-de-un-sitio-web/
- Should we help badges support to outstanding challenges?
- Who will take care of adding challenges/courses to school of webcraft many are just listed on p2pu but not in webcraft. good question. How much work is this? How difficult is it? Who can do this at the moment?
- Chloe will do for the workshop badges (we need better process for future)
- (Volunteer) Potential leaders for SoW:
- Planning for workshop for webcraft challenges
- Ask participants to review existing entry level challenges, and come up with ideas for challenges they want to develop
- Ask them to create accounts beforehand (?)
- @John -> Email 3 webmakers for NYC cc Chloe
- Workflow for pull request https://github.com/p2pu/lernanta/pulls related to lighthouse tickets?
- Which of the current pull request we want to merge
- What should be the procedure for next ones?
- John to review value of "feature"
- If needs community review, John to share with community
- If we want to include it, Zuzel reviews quality of "code" and merge
- What's the process of pushing some of the really nice design from three alphas
- http://alpha.p2pu.org -> Staging server for next release (features ready for production)
- http://alpha.p2pu.org:8091 -> Frontend / styling - lots of little things that haven't been merged
- http://alpha.p2pu.org:8093 -> Frontend / styling - lots of little things that haven't been merged
- Features are split across alphas
- we can try to tie much of it width cards related to improvements or changes in p2pu like what we are doing with the ones related width badges and challenges
- some can be used as starting point on the UI for cards like improving user registration/login pages
- Alrton and I had a chat yesterday and we desided to use a full diff of his forks and the main lernanta to chatch most of the changes that are not yet merged (in some weeks when we fill we finished and send him an email he will check the site to see if he notices something was overlook)
- Real-time chat
- Brylie sent an email about adding real time chat to Chloe. Put a lot of thinking into it and made mock-ups.
- Shared on the list and lots of other people jumped in. There seems to be a lot of interest and support.
- John: Good idea but lots of other issues with the site that we should address first. +1 (PS) +1 (Chloe? You said you agree ;-) Just copying from the chat. I agree
- P: Can we make this a volunteer project? what would be next steps then if it is a volunteer time project?
- Identify a feature owner (Brylie/Eif?)
- If they take it on, ask them to follow the project pipeline methodology
- Share wireframes with community list
- Listen to feedback, make changes to design
- Build prototype and get final community review
- Test reliability, then ask Zuzel to merge
- Zuzel to Send email [done]
- News about hiring and onboarding
- Philipp (Friday) and Zuzel (Monday) are having calls with one applicant who passed Paul tech screen (so far only 1 of 3 made it through Paul's screen).
- Zuzel scheduled for next Monday (wanted to be sure I was not going to have problems speaking so did not tried to do the call this week)
- Zuzel schedule call width Brylie before we send it to Paul.
- Getting him to work on the chat thing might be a great way to test his skills
- Chloe wants to send questionnaire to School of Webcraft challenge-takers asking them about badges. How do I contact them? through the list? directly is possible?
- I could get the list for you ok, thanks [Send through sendgrid - otherwise you might hit email quota] or the email provider we used for the webmaking 101 list
- To do a survey, we used surveymonkey in the past - works well. We have an account I think. Depending on the questions you want to ask, it's more powerful than Google Forms. If you share the draft questions, I can give feedback on which tool is most appropriate. Ok, I will share the questions, Phillip have you done this before for the previous badge pilot - are there questions already? Please check with Erin. She has something. will do
- Zuzel: Send email to chloe with the emails from Erin from when she sent the email to the participants of the badges pilot. [done]
Jan 4
- Chloe is sick :(
- Status challenges
- Included school, challenge set, and challenge home pages in lernanta's page view tracking for hackasaurus metrics report.
- Code - I am waiting reply from Atul on interactivity integration
- Code - I am working on commiting code for challenge 1.0 board - Goal is to release Wed/Thu 11/12 Jan
- Content - Waiting on description and image for challenge sets (image for home page of the challenge set) and 1 sentence description, and 1 paragraph descriptions ... also images for each challenge
- Challenge sets require a small configuration made by Zuzel or Chloe (can't be made through the general user interface right now)
- Todo - PS to email Stephanie with general update
- Job interviews for developer
- Paul is helping with technical screening
- Etherpad server email/smtp
Dec 28 (Jan?)
- Status OBI
- Before for the alpha OBI https://github.com/zuzelvp/django-obi
- Based on information received from Brian:
- The issuing API is going to change fairly drastically, fairly soon. Right now issuance is done via a server-to-server POST request (read: no user interaction necessary, which is bad). Brian is changing that – He is writing a JS library that provides an async method which takes badges and a callback and launches a process that shows the user what data the issuer is trying to share with the OBI. More or less based on the https://browserid.org/ model.
- What is not changing at the moment is the metadata requirements for badges: https://github.com/brianlovesdata/openbadges/wiki/Assertions. So once P2PU is hosting valid assertions, we are 80% of the way to issuing badges.
- Unless it's unwaveringly necessary to issue badges right now, Brian recommend us to wait for the new issuing method rather than implementing the backchannel POST method. He is hoping to get that locked down by early/mid January.
- Badge issuing should work retroactively (for existing P2PU badges).
- Milestones: Brian early/mid January.
- Expected amount of work: 3-5 days (could use help from Brian)
- Question / Concern: Amount of maintenance work required as OBI API changes
- February could be a good time to try to integrate again p2pu with the OBI.
- Hackasaurus Dev Status:
- Inline badge submissions in tasks and Challenge sets implemented, commited and available for testing on alpha.p2pu.org
- Need images, one sentence and one paragraph descriptions for the first two challenge set (left note on the board cards).
- Zuzel to send email to Chloe (cc Laura/Jess)
- Currently splitting into smaller pieces and committing the badges db model changes I implemented for the challenge 1.0 board.
- Still waiting on confirmation from Atul regarding "Interactivity" integration
- 21 Dec note on trello: "Hi! We are still figuring out exactly how much interactivity we'll need, and we'll be doing that in the next few days by quickly prototyping our activities using HTML/CSS/JS. That should give us a good idea of what kinds of interactivity is necessary, and whether that can be accomplished through this postMessage-based solution, or would better be done by actually committing Hackasaurus-related code to lernanta (Zuzel mentioned this as a possibility--having server-side "plugins" that contain vetted code she's reviewed).
- Does that sound okay?"
- 2 Jan - Zuzel to send email follow up
- Planning to look at metrics and make sure we are in fact tracking the relevant data
Dec 21
- "Unsticking"
- Tasks mentioned by Laura as outstanding in her email
- Challenge creation process
- Doesn't affect more than 2 users right now
- Important in the long-run and want to fix, but distraction right now
- And -> not related to metrics
- Decision was made during the HackJam by Chloe, Laura, Zuzel
- Reported this back on the first day (to Steph, Mark, etc.) but maybe there was misunderstanding
- Hackasaurus asked us to focus on three things
- Interactivity inside tasks (iFrames etc..)
- integration of badges inside tasks
- ability to group into sets of challenges
- there was 3 developers so we ended up
- Other things that came up during hackjam;
- Challenge Set Landing Page (UX ready)
- Export to OBI (in progress)
- Ability to assign Mentor status (solved)
- No discussion of "next steps" during the Hack Jam which may have caused this
- Deadlines where not adjusted based on how specifications growed
- We had to make improvements because the challenge UI was still buggy/new
- Irrelevant to this project:
- Moving forward here are some suggestions for framing collaborations with Mozilla or other partners;
- Work directly with project stakeholders unless the project involves more than 6 people.
- If a project manager is hired as an external contractor to work directly with p2pu, we should be involved in the hiring process.
- Agree on goals for the project from the beginning. Rule of thump, if those involve more than 2 major platform updates we ask for dev assist.
- Have our own agenda for improvements that is independent of what we develop for Mozilla. Always check with the priorities in that agenda to make sure we are not getting sidetracked.
- Suggest deadlines rather than accept them. This is tricky, but would put us in a better place.
- Decide deadlines as a team in the dev call before we accept deadlines individually.
- December Progress (what have we shipped in december?)
- 100% of dev time has gone to badges/challenge improvements and hackasaurus
- this should be pretty clear from the project pipeline board, projects too big
- challenge filxes has been at the top of implementation all month, now hackasaurus challeneges is there
- Shipped:
- Style changes at badge pages
- Other badges you can ap Carousel
- At bug fixing/finishing up stage (i.e., have worked on implementation but it is not ready for production):
- Simplified badges db models (+ associated UX changes):
- Including submission based community badges
- Facilitating filtering of submissions (awarded, pending)
- 5 Kinds of Badges / Logic: http://pastie.org/3052285
- (challenges hackaton) Jquery-based Inline Link Submission to Task Discussion and Tasks' Badges
- Skill Badges associated to and listed in tasks
- Jquery Wizard to mark task as completed, submit link and provide explanation associated to each badge application.
- Task page updated in each step without need to reloas (form validation, making the new comment in the task discussion area appear, updating apply/submitted/awarded link under the badges list in tasks)
- (challenges hackaton) Sets of Challenges created by site admins.
- List of Challenge Sets Displayed on SoW homepage
- Individual Challenge Set Page under the associated school
- See http://alpha.p2pu.org:8091/en/groups/ -- Now contains a section that looks like the design of the individual page for a challenge set (i know, I think ARlton placed it there by accident / just pinged him, he will change it)
- January Priorities / Planning
- General P2PU -- Promotional Cycles (community review) -- Subpart of Learn Page / Sitewide Group Discovery
- John can use Arlton as a resource for next week to help with UX on above if needed (Challenge UX is wrapping up this week)
- Badges + SoW -- Hackasaurus (features and metrics)
- Update OBI export; Hackasaurus will need issued badges to be exported to OBI
- If OBI API is stable and there is useful functionality ready for the users after the badges get into the OBI:
- want to avoid enabling this functionality before the OBI is ready to use (e.g. users can get OBI badges and post them in their blogs)
- and stable for badge issuers (e.g. there is no big API changes coming that will make all the badges the user sent dissapear and the integration stop working)
- We need to reconnect with Brian to sync up (Chloe already contacted Brian)
- Hackasaurus Interactive Tasks
- Pros and Cons of different Ideas for how to support it have being considered
- Ideas discarted before coding them:
- adding javascript into our database (we pushed back on this one)
- iframes with urls whitelisted by partners (decided not to use it because in the hackasaurus challenges users have to work with the html iframe src url which does not appear in the page source)
- (challenges hackaton) 0.001 version was coded and discarted
- A [widget:<non-white-listed url>] tag that users can add and gets replaced for a button that opens this url in another window so that the other window can post messages back to p2pu
- Pros: Easy to Implement
- Cons: Non-embeded and easy to cheat to get the badge
- Current Specification:
- Provide pluging functionality so modules consisting of html+js+css can be added to the lernanta's github
- each module will correspond to a tag the users can add to the task body which gets replaced by an html section (+ css/js) in the task page.
- Next step: Zuzel to confirm that our plan to move forward is also what MoFo expects (Atul, Steph, Laura)
- Also check that Atul will contribute development time to make this work
- Staff -- Interviews for the Dev Job Posting
- John is reviewing all resumes and removing "obvious" ones
- John will ask us to review those that made it into 2nd round / schedule interviews
- John does overall screening
- Zuzel does tech screening
- Philipp does post screening interviews
- Then we have a final list
- May have additional interviews with other P2PU staff
- Final decision is made in the group (like when we hired Zuzel ;-)
- Can we have a set of questions / points that we look at? +1
- Passionate
- Competent
- Trust / Moral fabric (!) :)
- Team Player
- Comfortable working with non programmers
- Organized
- Comfortable receiving feedback
- Comments we should add to the tasks:
- Question we what to ask them.
- Thinks that look strange.
- Things we think are their strong points.
- Follow up email with kind rejection
Notes:
- Plan for immediate future development
- 1 week
- Move everything from Challenges 101 that was completed into production
- 1 week
- Prepare a demo for Hackasaurus integration
- 1 week
- Future planning
- Be as specific as possible in project specs
- Involve John and Zuzel in project specs to set dev milestones
- Break dev into 2 week blocks / releases
Dec 19
- Planning future release roadmap (see Karen's email about rolling out mini-school-of ed version)
Dec 14
Dec 12
- Update on Hackasaurus / ChallengeJam
- Worth participating (or not right for tech group)?
- Agree on position for online payment options for donations
- Lots of options on the mailing list
- Can we add dates to some tasks in trello boards?
- Hand-over process for challenges / badges -> product management
- Opportunities in badge space (Erin's email)
Dec 7
- This week we have being working on:
- Challenge 1.0 badges board (will keep working on it this week)
- Created a new board Challenge 1.1 to specify a new set of UX improvements for badges
- The other challenge board was renamed to Hackasaurus Challenges as we talked last week
- Sent anonymized school of ed csv metric files to Chloe for June
- Spam short term measures?
- Make organizers able to delete comments/signup answers from others?
- Future: Akismet support or something similar?
- Add a Testing Section to the project pipeline so we ask the community to test the new features and check if there are small changes to make things to fix.
Nov 30
- Discussion on iFrames support
- http://pad.p2pu.org/iframes
- Make a decision
- Communicate decision
- Set expectations
- Is there a connection to the Hackasaurus conversation?
- TODO: Send next steps to the -dev mailing list [John w/ Zuzel for input]
- https://etherpad.mozilla.org/challenges-evaluation-goals
- Maybe push back (we have a call with Steph/ Laura tomorrow - and I'm trying very hard to reduce the list of metrics they want)
- Moving forward on challenges / badges work
- To prepare:
- List of things we commit to rolling into production by 14 Dec
- List of things we will work on beyond that
- Let's move obvious things/ bug fixes into the development column on the pipeline board
- Most of the work can't be classified as bug fixes
- Clarify scope for challenges UX / bugs work
- Zuzel had a call with Chloe this Monday in which the tasks at the Challenge Fixes 1.0 board were clarified
- Laura requested this to be implemented by the end of the week
- cv > we should discuss this, we could postpone the deadline
- I will try to finish it as soon as possible (and work during the weekend if it is not complete on Friday)
- ps > don't kill yourself for this!
- Make sure to go through community feedback process
- If the deadlines are not moved there is no time for much feedback
- However if we start sending emails now about things from the Challenge 1.0 board that I will need to start implementing next week so we can have it in production by Dec 14 it will help clarifying requirements.
- So then the deadlines where for specification not implementation acording to Chloe explanation. yes.
- Specific asks can really help
- John please read through the Challenge 1.0 board
- There are bullets like challenge creation that need to work ok with the rest of the site +1 (if that is not in scope right now then we should revisit as a priority)
- If I have time I will add questions of things I need clarification for as well
- https://etherpad.mozilla.org/challenges-plan
- Note deadlines and reflect into the projects pipiline
- I will need to be working fulltime on challenges/badges during the next two weeks
- Django Developer - Job Description
- Google Analytics for Webcraft/Mozilla
- This is time that we can spend on other things, if it's the priority then we can push other things it's not that hard but also not just
- (zuzel)?
- Have a distinction already to control styles
- Possible to add future data by adding a tracking code
- reports are easier... and it keeps our code simpler.
Nov 23
- Who can access http://p2pu.org/en/metrics/scoreboard ?
- The people that received my email about it. (is_staff=True not necessarily site admins but currently all the users with is_staff=True are site admins also)
- Chloe, Ali, Bekka, John, Zuzel, Philipp
- Update on finding developer (next steps)
- John sent a tweet (is there a spec?)
- Would like to discuss with this group what is the right focus?
- Frontend focus?
- Work with a volunteer UX group
- + Design appreciation (think Brian Brennan)
- + Django developer
- + Familiar with basic Bash/Shell
- + Familiar with Github/Version control
- i.e., Someone that can mostly or completely work in paralell with Zuzel so we can implement things faster
- Next steps:
- Job description (John)
- Jobs page on site (John)
- Spec out design work that is needed in addition (John)
- Guidelines for general review / feedback process
- How many days for review by community?
- When can we close off discussion?
- The process is an "art rather than science"
- Provide detail on the "why" you designed things in a certain way
- Include clear questions if you have questions about particular features
- Ok to have issues that cannot be resolved
- Add dates!!!
- Get bug fixes for badges and challenges into pipeline
- Need update from Jessica to move forward on badges / challenges work
- Chloe hasn't heard from Jessica ... not sure where we stand
- Trello board with bugs -> https://trello.com/board/challenge-fixes-1-0/4ea1b6d5147920a55e037013
- All cards have been specced and discussed with Jessica
- Some pressure to fix the most pressing bugs to support the work with Mozilla
- Either Chloe to follow up or Zuzel (whatever is easiest / fastest)
- Next steps;
- Call on Monday at 10am Eastern
- Zuzel/Chloe/Jessica to talk through the cards
- Zuzel will start investigating and post comments / questions
- Arlton already made some improvements - need to push out to the site
- Confirm that Zuzel has all the info she needs
- Can start on this today -- got ok from chloe and the code is at github.org/arlton2/lernanta
- Archiving old web properties (to redirect or just include a banner)
- Tracker - shut it down / redirect
- QA - shut down / redirect
- qa.p2pu.org and tracker completedly down
- Including arbitrary JavaScript
- Working with Hackasaurus - they were wondering if users could post JavaScript as comments
- Next steps: John/ Zuzel to work with Mozilla to get a concrete example to work through it
- Site admin/metrics (Laura, June)
- Loop Chloe in and have her discuss with Laura
- June to get a screenshot of analytics dashboard and one spreadsheet of exported data (and chloe can talk him through the details)
- anonymized or not? preference anonymous
- figure out our policy going forward and share [Philipp]
- John's workload:
- After the workshop he has more responsabilities so I am wondering if things are ok, or there is something that could be better
- https://etherpad.mozilla.org/challenges-plan
Wed Nov 16
Priorities from workshop:
Dev Process going forward: (This is on the Project Pipeline bord in trello -- https://trello.com/p2pu)
https://trello.com/board/project-pipeline/4ec0f020c137ff072a5d8afa
- Project proposed - goes into backlog
- Community prioritization of next three projects
- Brainstorm / Specwork before dev
- On completion moved to dev
TODO: John send Zuzel screenshot of similar metrics dashboard
Hiring a Developer
- John to create p2pu.org/jobs
- Post a description (checked by zuzel, philipp & community list)
- Share description + budget (probably not included on posting)
- collect resumes for 1 week
- start interviewing next
Wed November 2
(no meeting)???
Mon October 31
- (time confusion due to time change)
- John done: for Mozilla festival, challenges UX updates
- John doing: updates to challenge content, mozfest, profile page
- Chloe done: ux badges for profile page, bugs in badge pages, assessment design gudelines, mozillafest planning
- Chloe doing: keep working on badge profile UX with Jessica (implementation) , copy for badge pages with Arlton, p2puworkshop planning
- Chloe pasted a link to the board: http://bit.ly/oWfCmN
- Jessica blocked: getting local instance of lernata working
- Zuzel: more bug fixes incoming: http://pad.p2pu.org/ux-bugs
Wed October 26
- Looks like all is well for badging going live
- Next steps:
- Make sure copy is consistent and helpful
- Backlog: Mentorship badges, filtering badges (view badge page), filtering submissions (view submissions page), carousel of badges on view badge page, ____
- Arlton and Chloe working on profile page
- Sticking to current functionality + badges, more profile page functionality coming in the future
- difference between pilot and current badge system
- mockups coming
- old badges: http://p2pu.org/en/jessica/
- old system: http://badges.p2pu.org/
- Do we drop pilot badges? Different system and a different way to get them? What to do if they were skill-based with work?
- We could add them to the backpack and only show them if the user has them.
- How will the future iterations of badges be dealt with?
- Can we pull in old pilot badges? Probably not cause they're so different.
- @Zuzel - Do you need anything from Arlton/John on challenge ux changes?
- I contacted her last night and she didn't need anything.
- Trello: Add Arlton to it ... anyone else?John? http://bit.ly/oWfCmN
- On time for release? Probably. Github says all's well.
- Make sure 'need your review' on challenge home page links to submissions page
- What the challenge page looks like http://alpha.p2pu.org:8091/en/groups/new-group/
- Social media tie-in: signing in to P2pu with Facebook connect? share work on facebook? populate profile with facebook stuff (image, etc)
- Twitter?
- G+ like buttons and such? Getting more social.
- Maybe will fall in assessment/badging realm!
- IE: make work for it
- Locations: get from browser or have folks fill it in -- map
- Prioritizing? Zuzel?
- When go live, ping Arlton and Chloe for going through to look for text consistency
- Discussion area for challenges: UX ideation
- AJAX for comments will affect metrics -- need to make sure organizers know that the stats are changing but will be more correct
Mon 24
- We got a response from paul about iframes security concerns -- have to contact Michael for more feedback.
- We have the mockup for the ux changes we talked about last time
- alrton have being working on https://github.com/arlton/lernanta -- see demo at http://alpha.p2pu.org:8091/en/groups/new-group/
- can fordward UI screenshots from jledbetter if wanted
- About IE issues: we can start using the free accounts provided by https://saucelabs.com/pricing . In talis the developers use this free accounts and just have one paid account for automated tests (which we don't have at the moment).
Oct 19
- Clarify Dev meetings schedule - format - communication channels
- I saw an email abut it let me paste:
- Next Release:
- Badges
- Backend for skills badges and peer badges in place largely
- Jessica is working on building UI/UX around that
- Need to create the actual badges (Zuzel to ping Chloe)
- UX stuff to schedule
- Challenges Home Page - Tasks need a "3 comments in the last week" style
- Logic:
- if more than X [define threshold] activities in last day, then show: X comments in last day
- if not by day then try week, months (X comments last week, etc.)
- if no activity - don't show anything
- Display:
- just text
- link to task discussion
- placement: same area where it says view/discuss? we could have it all the way to the right? Use your judgement I think
- so on the challenges home page and one for each tasks - yes!
- will ask arlton for ideas (in case there is no much space to put it)
- maybe we can put the number in green and the text in hover
- Challenges Home Page - Move SoW Mentorship block to sidebar (data hierarchy problem)
- The sidebar is going to have badge stuff (above or bellow badges?)
- Put above badge stuff - doesn't need much space
- Call for mentorship is not really related to the challenge column
- Check logic on peers taking a challenge vs completed\
- maybe a bug
- complete = all tasks marked as comple (ted
- on the challenge = have not leave challenge and thus will receive notifications and can stay in the disscusions (could be stilll working on skill badges)
- Navigation between "Discuss Challenge" and "Tasks List"
- Currently implementation (button in left column not user friendly)
- Proposal to create a toggle at the top of the task list area - allow switching between discussion and task lists (consider implementing as AJAX request)
- Will add them to the todo list for the next release
- What to do about dev server, stats.p2pu.org, etc.
- What's running currently (what can we remove):
- dev server: etherpad, alpha's -- etherpad it probably the main hard one to move and the alpha's can maybe go into a smaller linode
- open atrium - it's a drupal application (will search for it on the server to turn this out)
- iFrames - implications of supporting iFrames more fully
- [John] Ask Paul Osman for input on this
- (Implementation likely needs to be more sophisticated than simply adding <iframe> as one of the allowed tags)
- If no security issue - Jessica will have a look at the exact request (consider design implications) and make a recommendation
- If no security issue, and Jessica signs off on the design, then we she will spec out implementation, and ask for volunteers to send a pull request
- IE Support
- What do we need to either install VMs in which we can install different IE versions to test things or using a service that gave us this.
- Could ask Nadeem to lend us a hand with this (he's got a sophisticated system for this) - maybe he (or one of his developers) can build a slightly simpler version
- http://www.browserstack.com/ (paid service)
- We could also have a message that encourages the users to update their browsers?
- +1
- upsell firefox & offer to install chrome frame for ie users? might not be able to install. -- there is a ve. some institutions (mine included) doesn't allow random folks to be admins of their machinesrsion that
- chrome frame doesn't need admin rights.
- there are already things built, like this - http://www.browser-update.org/
- IE Accounts for 10.5% of traffic to p2pu.org
- But possibly more important users than 10% indicates (and also most likely to be a community that will grow as webcraft share goes down)
- Set up a policy for browser support
- Functional support (not 100% design) +1
- Spell out which browsers we support
October 12
- Zuzel
- Done: Major changes to site (about to roll out release)
- Doing: Push out release, lots of badges functionality will make it to alpha.p2pu.org (but keeping them out of production for now)
- Blocked:
need publishing badge image from Chloe : done
- John
- Done: Challenge content updated, SoW home page content ready, new challenges images, reached out to mentors (info email)
- Doing: More broad call for mentors / communications once we launch, update link to mentor / mentee forms once release has been pushed
- Blocked: none
- Chloe
- Done: beta tester badge image (fun)
- Doing: connect with Arlton on UX for badge issuing (for peer badges etc.), work on view all submissions page with Jessica
- Blocked: none
- Jessica
- Philipp
- Done: Communication (but just raw materials for others)
- Arlton to work with Chloe and Jessica (email sent)
- Launch Plan
- Release today/tomorrow
- Sanity checking
- webmaking 101 preview launch on friday (p2pu & mozilla lists, blogs)
- wait a week, fix things see how it's going
- big announcement 24 october
October 5th
- Daily standups (15 minutes through launch)
- I prefer emails -- can it be at the end of the day? 9am is subway time
- I'm fine with a call - either way
- Quick IM chat for disscusions that need further talk (I do that with arlton and jessica)
- Decision -> Daily chat at 10am (IRC p2pu-dev)
- If people can't make it, how do we get our stuff in the standup if it's irc? email it to p2pu-dev? put it on this pad?
- Release today? - doing one release
- Waiting for reply from John to 'Badges: status' thread.
- up to zuzel, whichever is easier
- If there is a relase, I will not create/associate any badges to the challenges yet (as suggested by Erin) so all badges come together in the following release (next week or before)
- the problems is more that for arlton it is usefull to have more details of any design disscusions we have because he has to implement + mockup stuff
- I cann't heard you ok
- Weekly call moved to 10am (US East) Wednesdays
- Zuzel to update Google Calendar event
- Does that mean that the p2pu-dev developer weekly meetings have moved too? Does the daily standup replace that?
- TODO (next week release):
- Merge Arlton lastest changes [zuzel] -- http://alpha.p2pu.org:8091/en/groups/new-group/content/this-is-task-1/
- Users can give badges to each others (wave, .... badges) -- link below user gravatar on comments [zuzel].
- User can submit work, review work and get skill badges [jessica]
- Badge page with different functionality depending on the type of badge (to be linked from challenge groups), evidence page for the award of a badge to a user (to be linked from users profile) [jessica]
- Do we have all the images we need? Default badge image. I see challenges below.
- Webmaking 101 content:
- Bekka will be editing the contribute page.
- Chloe is already an organizer of the first six challenges so she can make edits to them.
- admin challenge / edit task
- John: Do we have a link to a form for mentees to signup as mentees? I saw one for mentors but don't know if there is one already for mentees too. Check http://alpha.p2pu.org/en/schools/school-of-webcraft/edit/mentorship/
- right now no, but we can make one using google docs. info to collect:
- p2pu username
- email
- what do you need help with
- ... add more here... yes!!!
- Challenges do not have images yet. -- who is working on this?
- @arlton - can you make one image that we can use across the challenges
- yes, does it need to be generic?
- no, doesn't need to be generic (but saves time if you can re-use)
September 28
- Load planning for high traffic on Webmaking 101 (what do we do if we get a lot of users? need a plan)
- Philipp specifically asked about this, not how we're going to respond but if we think high traffic will be an issue.
- We haven't had any load issues that I know of for quite a while, last I remember is when Mashable ran the story about us.
- Other than been ready to give more resources to the linode or restart it I am not sure which other solutions we can give to load issues at the moment.
- Important to let everyone know when some article or news is published around webmaking 101 so we can be more alert in the following hours
- is it possible to configure multiple web nodes (probably unnecessary, but eventually we will have to do it) -- yes, I think that was the next point/url is about
- I think we should do it as soon as we get this problem more frequently
- Future: http://www.linode.com/nodebalancers/
- This is meant as a technical point, will the load take the server offline? What is our plan to prevent that.
- How many users/visitors are you expecting? -- We have not experience a down time for this reason before but what steps do you recommend:
- We should monitor the site (in particular)
- embedly use
- page views table
- email notifications
- linode graphs
- ...
- What direct support do we need to offer? -- probably better to discuse on the community call
- Mentors matching
- Typical user support (what alison does for other groups)
- Answer to direct messages and comments (challenge & tasks disscusions)
- Monitor badge awarding (peer-reviews, ...)
- Challenges & Badges content status:
- Badges
- JL: Will we be ready for Tuesday?
- Which kinds of badges are we going to support on this release?
- peer and self. Chloe's working on imaging.
- Need to pull in Brian for the serving to OBI part. This release or next? (voting for next)
- Release:
- Release features will have to be frozen on the (early) morning of next Tuesday
- That's fine. I'll be in a different timezone so not available most of Tuesday day. Can check in in the evening though if there are issues. (And email always ok and checkable.)
- Website update will happen on Tuesday afternoon.
September 21
- Sync up Badges
- Arlton: https://gomockingbird.com/mockingbird/#m5ase18/kYNa9Y
- Good news -> Completed Task UX# 2 is almost identical to what Jessica is building (I think) yes
- Instead of "I'm done. Ready to submit my work" it could also say - "I want the badge"
- Jessica: http://pad.p2pu.org/badge-implementation
- http://alpha.p2pu.org/en/groups/webmaking-101-introduce-yourself/ -- Example of how a challenge looks like right now in p2pu.
- There is a section on the challenge sidebar linking to related badges that could work as entry point for skill badges.
- Questions:
- What's the flow: Users states that they finished all tasks
- Pop-up (the nice kind):
- "Congrats, you completed and earned a piece of your Webmaking 101 badge (self-assessment)"
- You have unlocked the ability to challenge for skills badges. Go here and challenge for peer-assessed skills badge(s) if you want to and "review the work of some other peeps"? give this "badge" to one of your peers? (another type of badge that might be rolled into the badge task)
- Go on to the next challenge
- Challenge to bring enough people into the peer review process (original idea was activity wall)
- Send notifications to "adopt-a-challenge" people and mentors? - doesn't work if too many submissions (Question: does that go in a queue? What do you mean? I meant it's too many emails.)They could be a queue of notifications in your P2PU profile? Yes - that's possible, but people don't use their profiles (they use the challenge home page as the dashboard) ok, gotya. ;-)
- Can we show something on the challenge home-page?
- "35 people are waiting to be badged (vote on their work)"
- Click takes you to the badge peer review page
- How much of Erin/Chloe's concept has been built already by Jessica? Is there code?
- She is just mapping it out here: http://pad.p2pu.org/badge-implementation, don't think there is code yet Right. Coding tonight hopefully.
- Jessica: will you be able to complete? Define "complete"? let me see how a couple days go :)
- :-) Can people get a badge (through peer-review/voting) when we launch the challenges? there are several peer based badges(majority) - everything is essentially peer based (some peer-2-peer issued and some peer assessed) except for maybe 1 stealth badge and the self-assessed webmaking101 badge (that you get for completion of challenges)
- What happens after you have received the badge.
- Shows up in your profile, maybe you get some notification that says you earned it?
- JB: How do we move from a completed challenge to the next
- JL will be doing the assess me/badge creation part and John/Arlton will be doing the flow part. Should be ok doing at same time. Will be committing and pushing lots. (to master/branch?)
- CV: Can you give badges from the activity wall to a submission? It will be a link so can just follow the link and fill out the assessment (so basically links to the challenge)
- What's the UX for peer badges? Arlton? :) [I thought Jessica was working on that.] [Ok, Jessica will. Saw various UX things so figured it was coming from there.]
- Badge Step Wireframes: Chloe (with input from Jessica)
- submit
- assessors review with rubric
- peer-to-peer where no rubric
- Flow: Arlton and John
September 15
- Main question -> Will we be able to launch the challenges week of 26 Sep?
- Tasks can be completed (done)
- Challenges at p2pu.org
- Badges -- I am taking metrics todos from Jessica's hands so she can work with this (we have Chloe on board as well) -- related to http://pad.p2pu.org/badge-implementation
- Etc.
- Update on / discuss contributor agreements / code ownership
- The last thing I saw was an email to the lawyer asking about the possiblity of implementing some feedback we got.
- Feedback from the lawyers is that we need to have the back-and-forth exchange between us and the contributors to constitute an agreement. All contributors need to transfer ownership of the code to P2PU (we commit to licensing all code openly so we are not placing any restrictions on their use)
- Can we come back to this after the september deadlines?
- Question about password storage (are they hashed)?
- Yes (of course), we are using sha512 and got some md5 passwords imported from the drupal site (they are changed to sha512 when the user logins on the new site)
- Ha - I was sure they would be, but wanted to double-check (our lawyer asked me if they were) - zuzel is totally on top of this :)
- Status Updates:
- Zuzel:
- Release 1.4 -- don't think I will have time before the meeting to write the change list but I can give a quick overview of the features that went into production
- John:
- following up with user tests
- second iteration on challenge type
- expose activity in challenges
- Jessica:
- Learning analytics for School of Ed.
- Next: badges and some learning analytics tweaks
- Philipp:
- worked with John on webcraft UX
- worked on badges concepts
- This week priorities (to pick from metrics, badges, sow ux/challenges dev & content, uci):
- Possible plan for this week (to be changed based on feedback an status updates):
- Jessica: Work on Badges (with Chloe, Carla, Jamie) -- It looks like the badges stuff has reached its 'finish design and lest start implementing' point (http://pad.p2pu.org/badge-implementation) so I think Jessica should be focusing on this.
- Almost. Hopefully within a day or two.
- Zuzel: Focus on profiling/optimizations/... for csv metrics report downloads (do a quick release after we have the performance issues solved) and write change list for the last release. There will be probably stuff to work on for webmaning 101 after a couple of days. If time permits work on UCI quizzes support (sending auth token so they know who came to their site).
- Arlton: I am giving him back to John to work on what is left/next steps of the sow/challenges ux (ping me if there is something important ready for merge/finishing)
- John: edit SoW home page. Work with Arlton, Jamie, Jessica ... in the next steps for Webmaking 101.
- Jamie: move webmaking 101 content to p2pu (adapt when neccesary) -- http://lists.p2pu.org/pipermail/p2pu-dev/2011-September/001834.html -- Start testing challenge groups on p2pu.
- Philipp: Reply to Larrie's email to explain why UCI features are not implemented yet, maybe talk about postponing deadlines? [Thanks for assigning the best job to me ;-)]
September 7:
Last Week Status Report:
- check metrics UI:
- user-3 password
- TODO: Jessica will send email to Karen/dev list to alpha
- decide when the release will happen
- development of new UX needs to be more transparent
- Todo:
- Communicate to John - Prioritize SoW over home page UX changes
- Footer might be quick and easy, but main navigation / home page content on hold
- Zuzel:
- Finished and merged changes to SoW homepage
- Waiting to get ok from Arlton to finish implementing merging other UX changes (on home page, groups, ....)
- Waiting to hear back from the SoW and Badges team (erin, james, jessica, john) about features to implement for supporting challenges/badges in p2pu
- Agreed to implement a few things on the community call (can feature under development courses, can "delete" spam courses) -- scheduled for the last days of this week.
- Jessica:
- Merged part of the metrics UI to master, waiting for CVS download which could happen before tomorrow's meeting.
- Karen's looked at the metrics overview on http://alpha.p2pu.org:8092
- Most of CVS export is done. Still need to test some odd quirks I saw this morning and fix those. Plus need to do "non participant" data and the totals. Keeping a running log of where I am here: http://pad.p2pu.org/jessica
- Met with Chloe about an overview of P2PU and such
- Larry:
- The UCI courses have not been created yet (no links from UCI to p2pu yet)
- Anya:
- The personal learning plan groups started (no features were implemented for this)
- Can we roll "complete the task" feature into these courses?
- Arlton:
- Answered questions from Zuzel about SoW home page.
- Worked on p2pu home page -- according to https://github.com/arlton/lernanta/commits/master/
- The last time Zuzel checked with him (yesterday afternoon) there was nothing ready for completing/merge by Zuzel
- "Currently, I'm working to update the Challenges page from the mockup I showed to Zuzel and John earlier this week. " - email today from him to Zuzel and Jessica
- Stats
- http://stats.p2pu.org is up and running
- all we need to do is include the StatsD class in lernanta then we can measure any action on the website with just one line of code (real time)
- John to file a ticket for zuzel (low prioritiy, after webcraft stuff)
- from where should the class contructor, methods be called? to be disscused on the ticket.
- ... Please add more ....
Discussions:
- When are we scheduling the release (i.e. updating the site)
- Friday September 9?
- People can start using the new features on Monday (September 12)
- Two more days to implement other features
- Monday September 12?
- People can start using the new features on Tuesday September 13
- Three more days to implement other features
- Tuesday September 13?
- People can start using the new features on Wednesday September 14th
- Four more days to implement other features
- What is outdated (if something) at http://pad.p2pu.org/the-list ?
- What has to be implemented and/or merged before the release?
- Disscuse "Courses / Challenges page" and "Create a Course / Challenge form" at http://pad.p2pu.org/p2pu-uxplan
- The disscusion happened on the other pad, Zuzel will send summary to p2pu-dev and start implementing (grab what arlton have done if there is something and do the rest)
- What are we working on after the release?
- Plan Proponsal:
- Zuzel:
- Collect any docs writen by John/Jamie/Arlton ... about challenges features into tickets and emails to p2pu-dev and or community.
- Disscuse "Courses / Challenges page" and "Create a Course / Challenge form" at http://pad.p2pu.org/p2pu-uxplan
- Short description for challenge kind of group.
- How do we use this and what is missing http://alpha.p2pu.org:8091/en/groups/new-group/ ?
- Start implementing/disabling features for Challenge groups.
- Jessica:
- Wrap up metrics UI/download if final touches are necessary.
- Collect any docs writen by Erin/Jamie/John/... about how assesments/badges will work in the context on webmaking 101 challenges
- Start implementing features
August 31:
Plan for 31 Aug - 7 Sep
Proposal for Dev Plan for this week (Please add comments about what you agree, or disagree with respect to the plan and suggest changes):
- Jessica works on metrics UI, and what is missing from the backend
- commits about tracking page visits to tasks and time on those pages were cherrypicked from the course_metrics branch
- UI mockups are yet to be merged to the main branch.
- Try to commit metrics UI stuff to master (on a state ready for production).
- Admins will have access to data (not interface for public/karen)
- http://alpha.p2pu.org:8092
- Zuzel and Arlton work on integrating what has been done of UX changes into the main branch
- Email the community for each feature that needs to be discussed
- Commit the changes approved (or previously requested) by the community in small pieces to the main branch updating backed code when neccesary.
- New UX changes are on hold until next Wednesday or earlier if we manage to go through the above todo list in less time than expected.
- This week Arlton reports directly to Zuzel not to John.
- Rather than ask for feedback on everything, ask for feedback on components
- Community feedback:
- John to send email to community to get feedback on proposed changes
- Put both screenshots (current version -> new version)
- Erin and John and Jessica work on specification for initial assessments/badges functionality and webmaking 101 challenges as a new kind of study group
- http://pad.p2pu.org/webcraft-challenges-badges
- Email p2pu-dev when it is ready.
- Assume we will have less than 8 days (1 full time developer/Zuzel and a part time developer/Jessica) to implement it
- Step by step:
- Design
- Implement new study group type (1.4)
- Implement badges /assessment (1.5)
- Prepare badge images or ask for help from the community to design them.
- Jamie works on finishing content for webmaking 101 tasks.
- No resources this week to work on DIY, UCI
- SoW Social Features
- John working on design this week
- Adopt-a-challenge
- Mentors
- Community space
- Live chat
- Implement for 1.5
August 24
- This coming release (Monday 29 Aug):
- metrics tracking
- Lots of commits in with some placeholder code. Filling out the functionality as I can. Priority is tracking since we can't report on stats we don't have. That is in there but missing the "time on page" part that will just be math and stored in the tracking table. Also need to make sure that it's not a huge performance hit (so far, it's not).
- Continuing tomorrow and Friday around flight schedule. Can be put on alpha for client viewing since I try to have placeholder parts (like the csv) in place before the dynamic part. If that makes sense. :)
- Will be part of the release this weekend.
- http://qa.p2pu.org/questions/151/notifications-on-new-system
- finish uploads (quotes + file types)
- setup ssl certificate on production
- create account on dev for jessica and arlton for setting up demos (sow and metrics visualization/downloads)
- Google Apps non-profit account
- What are the benefits / implications?
August 17
- Release 1.2
- priority courses on home page
- set upload quotas and file types (no .iso etc.)
- SSL certificate
- will be added to next release
- Featured courses
- discuss on the comunity call how to feature (which courses to feature each week) school courses to show on p2pu home page.
- new UX introduction email, dev meetings.
August 10
August 3
Agenda:
- Release
- Assessment Update
- Sending userid violates Google ToS
- We could send course ID (or hashed userid that is not traceable back to individual user) - but need specific user for PD
- Restrict tab/export functionality to Karen at first and see how it goes/grows from there
- Roll out first version only for PD courses (use boolean per course to trigger)
- John update our Privacy Policy?
- [Action] (Jessica) Confirm start date with Karen
- Hosting
- John requested VM from OSUOSL - no response
- Etherpad notifications (ping)
- Joe and Jessica have chatted about this and there is a hack -- probably. Just need to find time. :) Maybe push it upstream.
- UX/Web challenge hiring
- trial work due yesterday; more interviewing
- Webcrafting course (Webmaking 101) - start October
He probably wants to talk about shutting down dev <-----
I moved qa.p2pu.org out of dev
etherpad <--
alpha.p2pu.org <-- though it can me moved to (where? shouldn't be on production, why not? it has its own environment... that just seems like bad form, shouldn't they be separ)ated? what if there's a problem?) (or server updates?) talking about server updates -- we need to schedule one (really old version of ubuntu). -- if we have two servers it is best to have them separated but if we only have one we do not have a choice.
What's the action here? What do we need?
July 20th:
Agenda:
When John starts working as platform lead? (last Friday)- zuzel@p2pu...?
- Talk about development during what is left of the summer -- http://pad.p2pu.org/devsummer
- Discuss Zuzel's email about Teacher PD
News about our Board meeting- Updates on contracts status for assesments, SoW work, PD analytics
- Attemps to recruit voluntary developers/students:
- (pending call with David Humphrey -- I was not able to attend the call when we scheduled for last Friday)
- Plans for local lernanta dev workshop at Toronto on August 6th.
- No reply from ucosp.ca yet.
- http://pad.p2pu.org/stakeholders
Notes:
June 27:
- P2PU Archive TODO:
- Hidde applications like http://archive.p2pu.org/webcraft/application/application-jgittlin
- Fix the course lists on each school section which Charles had to disable due to a views error.
- "Take a course" block: "Start Learning, view our Open Courses List." takes one to the course list with no open courses - do we want this to go to the new site, or is it fine, seeing as this is the archived site?
- Should I remove the IRC "Chat" button on each course page?
- Schools:
- Planning to release features on July 4th.
- SoW got feedback about home page.
- Mojo:
- They are going to register people in an external site/form and requested help from us to manually register them on p2pu as participants
- Any updates on feature request or is everything on pad.p2pu.org/mojo
- Tasks: setup metric script and get some numbers
June 13:
- Migration
- Sign-up process improvements
- Product Manager / Tech Lead
- Metrics
- Migration:
- Message to Jamie (all users) to confirm that we will switch DNS on Saturday (and old site will not be working afterwards) -- copy Pippa, Alison, me ...
- See http://pad.p2pu.org/migration for all detail
Jun 6:
- migration:
- Charles needs to be notified when all courses on the old site are completed. Today was the date when courses should be ending on the old site, so Ali can probably start asking organizers about this, and let us know when we are ready to disable comments, broadcast messages, ... and change domains.
- http://old.p2pu.org/aksdjv%20h
- http://old.p2pu.org/course/list
- 1. types: http://p2pu.org/course/list
- doesn't exist on new site
- check if it exists ("Page not Found"?) on old site
- YES -> redirect to old site
- NO -> show 404
- database copy for metrics:
- badges:
- need to modify osqa-badges/the pilot to authenticate with the new site.
- sent email to John to schedule skype chat.
- Planning todos for early this week: write change list for release 0.7, organize lighthouse (will get some help for this on the dev irc meeting this week), and write roadmap proponsal to get feedback about dev priorities.
- search on the new site:
- google analytics has reports about search functionality on the new site under Content>Site Search
- adds are not displayed on firefox but they are visible on chrome (not sure about other browsers yet) --
May 30
- Server management
- Finding out from John what's the status of OSUOSL hosting
- try to use an etherpad that we are not hosting and copy notes to a wiki?
- What to put on OSUOSL, and what to keep on production and dev?
- Current dev: decommission (remove everything)
- Drupal dev server [will be shut down]
- Production (linode):
- Main web site
- Badges site (OSQA)
- FAQ site (OSQA)
- Drupal web site (archive)
- OSUOSL:
- VM 1 (self-managed, no user or sensitive information)
- Etherpad server
- Staging: alpha.p2pu.org (merge with James' server)
- Shared server: Mailman
- VM 2 - BBB
May 23
May 16
- Zuzel to look into setting up a dev/staging server
May 3
25 April
- Thoughts on migration
- Release 0.4
Migration:
18 April
- Make a decision about moving all courses to new.p2pu.org (only if new site is clearly better than old, and has to be managed carefully)
- Contract update
- Lighthouse and contributions
- Drupal priorities
- Board meeting
Migration
- The list of things todo before 1.0 (i.e. migration point) http://p2pu.lighthouseapp.com/projects/71002-lernanta/tickets/bins/283047.
- If our priority is migrating from to the new site then we should reschedule things to priorize functionality that allows the migration (moving content/users).
- I will prefer not to rush things, but if this will make p2pu users's life better then we should work towards it.
- Possible to move/migrate earlier:
- Release 0.7, 6 June (just after this round of courses ends) Start moving things on the 6th, end on the 20th. So all the features related to migration will have to be implemented by release 0.7.
- Won't have full feature set at 0.7, but enough to move over
- Zuzel to send email to p2pu-dev to let everyone know (sent first email)
- In the meantime, update www.p2pu.org home page with content pointing to new.p2pu.org (link to and update if necessary http://blogs.p2pu.org/blog/2011/03/29/a-new-website-for-p2pu/)
Contract update:
Lighthouse and contributions
Drupal Priorities:
TODO:
- zuzel add a tag for things that should be reviewed, feature request (product manager review). -- Will do this in the first days of the following week, after release 0.4
- zuzel send email to p2pu-dev about migration plans (sent first email)
- zuzel ask bekka to work on www.p2pu.org content pointing to new.p2pu.org (link to blog post about the new site, and any other info people need) + charles
- philipp to complete agreement with mozilla for contracting
- philipp to review things that need review (co-sharing role of product manager with zuzel)
11 April Agenda
- Contract update
- Getting help with design
- Schools Home Page
- Drupal site update / next steps / priorities
- Working groups (not learning) on P2PU site?
- Github issue tracker vs lighthouse
- Update for board meeting on 2 May 2011 (bullet points only!)
- Organizing lighthouse (select tickets for release 0.4)
Design
- Sean has being making some contributions in the design (he was one that replied to my last email a few weeks ago)
- I have to send another email to them, I did not do it this week because the tickets we had (about study groups, schools, ...) were to big so it was hard to let them know of specific things inside those.
- I will send an email probably tomorrow after I finish organizing lighthouse (90 open tickets now)
- Send specific tickets and to see the new site and create new ones.
- I sent a message to the ux/design task force.
- Let Philipp know later this week if we need to bring in additional (for pay) design help (yes, it could help -- see http://p2pu.lighthouseapp.com/projects/71002-lernanta/tickets?q=tagged%3A%22frontend%22 for a list of tasks in wich the additional design help will be working)
Drupal Development priorities
List of courses under development
Working Groups
- Going forward, focus on groups that are for "learning" (not NING like communities)
- Lernanta Dev Course
- Not necessary anymore as there is now a "learning to development on lernanta" course
- Moving release updates to github wiki (done, and lernanta-dev is now a testing sandbox closed for sign-up)
Board Update
- Three main areas (a few bullets for each):
- Overall roadmap until 1.0, and for rest of 2011
- Pick major milestones
- Focus on "state changes" - what can people do?
- Process of involving the community
- Both using community for input and feedback, and also working with volunteer developers
- Areas that need help/ Challenges
- First draft by Friday 15 April??? -- https://github.com/p2pu/lernanta/wiki/Board-Update-April-2011
OVERALL GOALS
provide easy pathways for people to participate…
support social learning online
provide assessment and alternative path to certification
IMMEDIATE GOALS
April 25th Goals
1) streamline the user experience, make it much better/easier
2) support at least some April session of courses
3) make enough progress so we can 100% migrate for july courses and beyond
4) build flexible platform that can grow/adapt to future changes
5) prototype things we are curious about for long term
--breakdown of course model
--badges/assessments
Longer Term Goals
integrate badges and assessments
support new learning models
SF Goals
Wireframes for key pages/experiences for April
Rough sketches for future platform
Wireframes
http://p2pu.lighthouseapp.com/projects/71002/tickets/41-prepare-wireframes#ticket-41-5
(3 links to wireframes)
http://pad.p2pu.org/wireframes
Go through the roadmap
Release 0.2, 0.3, 0.4
http://p2pu.lighthouseapp.com/projects/71002-lernanta/milestones/103702-milestone-2-release-1
Releases every 2 weeks, announcement on mailing list with each release
April courses - some courses on Lernata, some on Drupal
Milestone 0.4 is aligned with first day of April courses - April 25th
New site 100% - July 18th
Release 0.1 - P2PU version of Batucada
Release 0.2 - P2PU specific changes
--DONE: rich text editor, namespacing, rich media support
--TODO: add course content, list of course content, discussion on piece of content, manual addition of people to course, email notification, notifcation settings for users
Release 0.3 - Sign up open for April courses
--TODO: application process*, broadcast messages to users, site appearance, course schedule*, course listing, schools landing page, broadcast to course organizers, course completion*
Release 0.4 - Start of April courses
--TODO: email interaction, wiki like content, profile, course page, leaving a course
*needs more discussion
Ideas for future features:
* Show who is online in your course
Automated course - someone builds it and people take it how ever they want
Or, get people to build out course as part of the sign up tasks
Vision:
- Switch the model: What do you want to learn, versus what do you want to teach -- let people express interests and use that to find people to lead the courses
- Course as a series of projects or content that people are working together at a certain time -- that content could be remixable
- Course creation process leads them through the task model/generation
- Need to build from ground up (help those that want to learn think about how to turn that into a course) and deconstruct from top down (help those that want to lead a course to rethink what that means)
- Task based approach worked through by study groups, short term involvement (2-3 weeks max) the main goal (based on evidence of 2-3 week involvement max)
- Transition out of cycles
- Barriers to entry, ony useful for internal purposes
- April: Last structured round of cycles
- Nomenclature changes
- courses --> study groups
- organizers --> curators (tentative word!)
- participate + follow
- participating requires a sign-up process
- language: tell us more about yourself/goals, study groups are small and not everyone can join. if there's no room the curator will let you know. you can wait for another group to form or start your own (need link/info/pathway)
