25 July
Progress
- Structure for github repos is set for reports
- everyone who works on it please update local repository
- EP to send email to Bruno, Joao, etc
- Badges got some copy changes
- pull requests from VMG plus some other changes made on the forms
- EP & PS to setup some time in 3/4 weeks to go through small design issues
- Installed new WP plugin to get featured image into RSS (it seems that there is a wait for 24h for plugin actually start sending the right data)
- working on getting Badges
- the schools section will remain static HTML (performance wise is better this way, since is not gonna change all that much)
- is the wait on the plugin side or the task that we are running daily on lernanta?
- Discourse update
- setup by PS on EC2!
- running latest version (0.9.5)
- PS to field any future sysadmin problems :)
- Etherpad-lite
Priorities
- Homepage
- Get blog posts with images from info.p2pu.org
- DU to work on getting featured badges from badges.p2pu.org
- Need to check the responsive design implementation
- setting the right copy for the whole project (will work with VMG or Jane on this)
- PS to update copy for pages
- PS busy sending email to EP with school contacts on copy
- Badges
- char count on badge creation (or lack of it) became somewhat of a pain for users. I am preparing a feature implementation
- more copy fixes are needed (consolidating with VMG on this)
- Python MOOC weekly update
- Etherpad performance trouble
- Tech mailing list footer to point people to discourse
Problems
- Etherpad is unbearably slow still - is there something we can do about it, ideas?
- For me the tech etherpad is waay slower than community call, could it be that it has much more content thus being unresponsive? Shall we try new etherpad and see if it gets better?
Process
- We haven't posted any tech call notes on thepeople.p2pu.org in the last two weeks!
- my fault, I forgot (three times already, bcs this is the number of times I remembered I have to do it)
- EP to post tech call notes to thepeople.p2pu.org and link to topic on tech mailing list
- We should also post community call notes + video link to discourse
18 July
Progress
- Renewed SSL certificate for p2pu.org
- Lernanta now supports single sign-on for disqus
- good job, awesome!
- need to tell the community about it
- School of open multiple headings request
- school organizers can now put any HTML on their school home page
- Default to community featured courses in topnav
- Homepage mockup ( http://p2pu.github.io/p2pu_homepage_mockup/ )
- Badges had some bug fixes
Priorities
- [DU] Merge community featured courses and staff picks
- why don't we just remove staff picks? I think it's usefull having more control over the courses we show on the frontpage
- to discuss in community call now
- Gentle python MOOC status update
- probably not happening this week, but need to confirm with VMG
- [DU] Discourse
- resolve login/signup problems
- switch to master branch
- are we updating it regularly? not at the moment - but switching to master will help with that
- [DU] Etherpad
- Investigate slowness and find possible solution
- [DU] Google grants + adwords
- Dirk is working with Bekka on renewing the agreement
- Bekka will try to recruit an intern to manage the project
- [EP] File structure for github reports
- [EP] Home page roll-out
- soon mockup will be ready for implementation
- mockup is still under development http://p2pu.github.io/p2pu_homepage_mockup/
- need to reach out to Joao and Bruno
- How will we handle navigation for other pages that the home page links to?
- [Bump to next week] CSS framework
- lets get this up to date with the new home page
Problems
- Etherpad is TOO sluggish
- seems like a known issue: https://github.com/ether/etherpad-lite/issues/1763. They say the problem is in all browsers, but the worst in Chrome
- (Hey Dirk! Good morning. i:-) See you in a few min
- (unless it's etherpad minutes, then i'll see you in a few hours)
Process
- Dirk/Erika etherpad - is it useful?
Questions:
- Badges might need a SSL as well
- firefox will make problems on iframe embedding
11 July
Progress
- Moved pad.p2pu.org to EC2
- Fixed redirects so that http://pad.p2pu.org/tech and http://pad.p2pu.org/p/tech will work.
- Pushed a batch of new features and fixes to production on p2pu.org
- Badge integration in with courses
- Cloning courses by course organizer
- Exporting signups for trusted course organizers
- Reworked notification preferences - we migrated previous preferences to the new system
- Fixed twiiter and Google+ links
- Dowloading logs from mailgun for "Gentle introduction to Python"
- hashing the json string for a unique id
- storing log entries in the database on my laptop
- we don't have enough space in db on heroku to do this, how should we persist logs?
- Renew SSL for p2pu.org
- we will need to wait until P is back to do the phone verification in the US
- Second update of activity for "Gentle introduction to Python"
- Mailgun's API doesn't support querying clicks and opens per mailing list by date range :(
- Rewrite links for Mechanical MOOC emails when they are saved
- Home page
- VMG is making wireframe for the "tour" page
- Feeback from VMG was to put more "weight" on community
- Badges
- some bug fixes (responsive design is aligned now and some other stuff)
Priorities
- Home page mockup
- some feedback was given, we work wih it
- next steps are nplementing feedback suggestions *some(
- Renew SSL certificate
- 3rd weekly update
Problems
Process
4 July
Progress
- Updated pad.p2pu.org to run the latest Etherpad Lite code on github (1.2.11)
- Moved pad.p2pu.org to EC2 small instance
- Updated Ansible script for etherpad
- Implemented exporting signups for trusted course organizers
- Course organizers can now clone a course
- Getting everything to do a release tomorrow morning
- Badges integration with lernanta
- some testing needed before anouncment
- 404 page get embedded when I put in the wrong URL(needs testing)
- Home page mockup http://p2pu.github.io/p2pu_homepage_mockup/
- Travis CI first step for the badges was set up (we got a build pass already)
Priorities
- Push latest verions of lernanta to p2pu.org
- Export emails
- Clone courses
- Integrate badges
- Notification unsubscriptions
- Mechanical MOOC
- send out the second update email
- Padsearch not up to date anymore because it uses the etherpad db and etherpad is on a different server now
- Home page
- Lets talk about how we should get feedback
- We will ask for feedback in discourse, and community list, but present the link at the community cal
Process
Problems
27 June
Three special guests today! Very cool!
- Sebastian
- Drew
- Srishti
- Drew & Srishti is working on building tools around hangouts to handle unconferences
- Sebastian is a new volunteer looking to get involved!!
Progress
- Groups created for Mechancial MOOC
- Tech update posted to blog
- Special email for experimental group almost done
Priorities
- shiping badges intergration with lernanta
- HTML mockups for homepage
- Export list of email participants for trusted course facilitators
- Clone an existing course
- Finalize email for experimental groups
- Homepage
- Erika will start working on HTML mockups (link with Joao and Bruno)
- Tech plan -> Build it as a Django app, that is initially part of Lernanta (makes a lot of tech things easier)
Problems
- Mechanical mooc email unsubscribes. Mailgun unsubscribe link implies user to unsubscribe
- Maybe include a place on the mechanical mooc where a user can unsubscribe
- Email account forwarding breaks participation in a group.
- ex. user signed up with user@mail.com. That address forwards to user@anothermail.com which the user actually uses. When replying from this address messages doesn't get sent because the address is not in the mailing list.
- This is a standard problem in mailing lists that allow posting by subscribers only
- Mailgun doesn't keep stats on replies sent in mailing lists. To get the number of messages sent per mailing list, we have to parse the logs :(
- Discourse social logins are BROKEN (either not working at all, or only partially)
- send message to community about
Process
- badges - lernanta integration
20 June
Progress
Priorities
- Mechanical MOOC
- write script to get data required for emails to experimental groups
- Homepage
Problems
- Discourse
- has login problems (Twitter)
Process
13 June
Progress
- Mechanical Mooc
- Fixed some issues with text email formatting
- Updated grouping to do basic grouping ~ according to timezones, waiting for more final dicision about grouping
- Homepage
- Discourse (CE)
- file uploads to Amazon S3
- evaluated OAuth signin and decided that it present to many possible problems when updating discourse in the future
- Feedback from schools (EP)
- P2PU Reports section for Lab Reports
Priorities
- Discourse next steps
- Someone needs to keep an eye on releases / major improvements
- When they release reply-by-email, upgrade to main branch, review hosting decision
- do they have a development roadmap? no, recommendation from discourse is to follow them on github
- Verify that we send emails with right URLs (thepeople.p2pu.org)
- Are we ready to invite the community
- MOOC grouping
- @CE what was the requirements for random selection?
- Will discuss with June today and then decide
- Homepage redesign
- decide on best way to implement and how it looks
- Write a tech blog post about
- Implement course UX feedback from schools
- Integration of badges with courses on p2pu.org
- Reports - last tweaks (see above)
Process
Problems
6 June
Progress
- Partner badges can be created by some specified users
- partner have to approve a badge being awarded
- Notification opt-out for all notifications
- including notifications sent via the API, but will need some attention when we get a new application sending notification through the API
- DNS for discourse http://thepeople.p2pu.org now (almost) points to our discourse (looks like the DNS is still propagating)
- I added in a CNAME and I added the domain in the heroku.com interface
Priorities
- Discourse [Chris]
- write OmniAuth strategy to work with P2PU
- question: i agree that this is something to implement now, but does this make it harder to keep upgrading discourse as they put out bugfixes / new releases?
- (question about how we got here -> why did we set it up on non-free heroku in the first place? was this just a mistake? github branch said it was free. yes it was a mistake, alright)
- Courses feedback and suggestions [Erika/Dirk]
- Improvements to the home page [Dirk -> Get Erika involved as well]
- Grouping for the python MOOC
- Badges Integration with Courses [Erika]
- Do a sync up again on badges work / what's the plan
Problems
- Still not sure how to help user from Nigeria that keeps asking questions on help.p2pu.org
- would be good if we decide on what to do with that
- erika will take this question to the community call for discussion
- Trello Board
- let's do more descriptive tasks in the trello board. yes (same for etherpads)
Process
- Lernanta Fixtures
- is there any possibility for us to make small fixtures to provide to the people who are playing around with lernanta in Vagrant
- it is nice if there is some fake data in there in order to play around with this thing otherwise it can be useless
- before we do -> what's the audience for this, how many people will do this?
- Not sure, but I do think it is not super important (but we do have audience we don't know about I suspect - tim was one of them)
- yes, you are right. but lernanta is not really designed to be self-hosted anyway (it's not huge benefit for us if people self-host instances) and based on our experience with previous efforts to get more people involved in development work, it is a really small group of people - maybe there are other ways to make it easier for them to get involved with P2PU
- you are right, but if there is two people doing this is one to much. And I am talking about really small fixtures with 3-4 courses/challenges/study groups?
- you are right, but ;-)
- Browser support for lernanta, Badges, Mechanical MOOC
- How much do we want to provide browser compatibility (and mobile <- I thought the CSS framework was responsive)
- http://www.browserstack.com is a great engine for testing (it is not free, though)
- I sympathize with the question. In the past, people have used the fact that we don't get a lot of traffic from users with old browsers as the counter argument.
- @Erika - do you have access to the analytics account? (You should)
- RESOLVED --> Can we take out the ads from the mail (I am not sure under what kind of licence we are at google, but I suspect that if even the free version is able to take out hte adds, than everopne can?)
- which ads? which emails?
- the adds in google mails that are aways trying to sell to me something
- which emails though? i don't see any ads.
- I do get adds on the p2pu.org (do you see ads on the web interface for gmail when you access your p2pu account? or are the ads embedded inside emails you receive?) On the interface
- Here is my suggestion:
- We have a sponsored non profit Google Apps account
- You should be a domain admin user (if not, ask Dirk to make you one) - feel free to poke around the cpanel and see if you can turn it off
- O this is cool, I so will!
30 May
Progress
- Upgraded linode running p2pu.org
- Deployed latest changes to mechanicalmooc.org
- we currently have just over 1200 signups!
- API keys for AWS with credit set up, please inform DU & PS before using
- Updated documentation for the Mechanical Mooc: https://github.com/p2pu/mechanical-mooc and https://github.com/p2pu/mechanical-mooc/wiki
- Partner badge requirement will be deployed during the weekend
- EP talked with Vanessa today and we can drop the requirement of feedback, revision flow as long as we implement requirement for the sample project on badge creation
- Search for badges will go up today
Priorities
- Implementation of feedback and suggestions
- Course announcement opt-out
- Homepage, we need to discuss what we want to do
- we need better reflection on homepage about what we do
- Badges
- revise badge creation process to require that badge creator also create a project
- Move discourse away from Heroku
- Digital Ocean - $10
- AWS Small Instance, 1 year provisioned, low utilization - $30 pm + bandwidth costs
- for now lets defer the decision, both give you similar platform
- target Ubuntu 12.04 32-bit Server Edition(LTS)
- use ansible to setup discourse. https://github.com/p2pu/marvin
- next steps: DU to send email to CE and PS summarizing the work and getting feedback on Digital Ocean & AWS
Problems
- Help for the user which is not expressing very well what he would wish in English
- DU suggested a French response for him
- Discourse not possible on free Heroku!
Process
# 23 May
## Progress
- Sent email to previous users of Python Mooc
- had a small problem (100 users * 25 emails = %$#%)
- User on badges can delete badge that does not have any projects
- Other Python MOOC updates?
- Improved the unsubscribe feature (previously, users would unsubscribe from mailgun, but would still be in our local DB / now unsubscribes sync both)
- Discourse
- http://thepeople.p2pu.org (please update DNS)
- Course UX improvements
- Call with School of Open to go through course organizer feedback
- See email from Jane on community list with (excellent) summary
## Priorities
- Upgrading p2pu.org linode
- DU to let community know about planned upgrade and 3h downtime on Monday the 27th
- Plan implementation of feedback from SOO & SOE
- Confirm that single signon with disqus is possible (for free accounts)
- Grouping users for the Python MOOC.
- We need to talk with June about the grouping
- Next steps: DU to send a email to community list, June and VMG about grouping
- Badges partner badge implementation
- there was a wireframe presented today to Vanessa and Dirk
- Get Discourse hosting set-up
- DNS -> http://thepeople.p2pu.org
- [Optional] Set-up P2PU OAuth
- Heroku (explore DB size first, evaluate if move to Digital Ocean or AWS makes sense now)
- Course UX
- Next step: DU to schedule and prioritize the work (tentatively week after June 1st) and inform SOO + community
## Problems
- Email hickup (how can we avoid these in future, can we?)
- For things with high risk, use a second set of eyes
- Better deploy process (Staging servers are needed)
- Let's discuss how much time (cost?) is required to do this, before we set it up
## Process
- How can we improve tech updates in the community call? (People don't know what is cooking)
- Lets try markdown format for tech call notes so that we can copy and paste the notes in discourse
- doing some research about fabric for the Badges testing and deployment
- we could use it instead of ansible (ansible misses a lot of stuff for real production)
- I have some experiences with it, have been using it before
- It would not be time consuming as much bcs I have experience
- Deployment process (too complicated?)
- you have to be sudo user to pull
- after you have to restart apache manualy
- what happens if migration breaks
- all of those are very dangerous operations to do them without testing on staging servers first
16 May
https://plus.google.com/hangouts/_/c40035a0f9c9450e5bb1d04ac062fddfb21ed40e?hl=en
Erika @djangocon Warsaw (internet might be a bit flaky, some really loud airplanes are passing by from time to time)
Parking Lot:
- Hosting updates (Linode upgrade, MOOC hosting, heroku, AWS...)
Progress
- Mechanical MOOC
- swapped in ckeditor for the WYSIHTML5 rich text editor we were using before
- email scheduler finished (you can now create an email and specify a date when it will get sent)
- also supports group emails (sent to the indivdiual groups) and community emails (to everyone)
- we now support running courses multiple times (sequences)
- emails and groups can be assigned to a particular sequence (=round) of a course
- setting up a new round, requires some shell magic
- imported the sign-up data from ruby MOOC
- Defines goals / planning for 3rd phase of badges (rolled out as they get completed)
- See details under priorities below...
Priorities
- Mechanical MOOC
- set up regular backups for data to amazon S3
- handle unsubscribes (currently, users are in stored in two databases - mailgun, and heroku - need to sync)
- Badges
- [2 weeks] Allow partners to issue/ endorse badges (restrict who can issue the badge)
- The 2-step autorization for partner Badges
- We set out to be implemented until June 1st
- Dirk gave Erika task to make an wireframe to present to partners on how will we implwmwnt this
- [1 week] Integrate badges more closely with courses
- for a start this will be a IFrame that you can embed in a course (or anywhere else)
- [1-2 days] Add elemet to the top level navigation where you can see all the badges
- Some bug crushing tasks (Badge not yet awarded but project already published as a project which got the Badge, ...)
- Question: What is the benefits of converting id to uri and back trough out the system?
- not much within a system, but very usefull
- Setting up the integration servers on AWS for testing purposes
- Hosting
- DU to cancel stats.p2pu.org
- AWS API - PS and DU to go throught this next week
Problems
- Running courses multiple times on p2pu.org
- We don't currently support "cloning" courses
- A few courses are running for the second time, and it's not clear to organizers what the best strategy is
- Easiest solution (right now) -> Create a new course, and copy&paste content
- DU to make sure this is one of the topics on our list of feature requests
Process
- Keep better notes on the call so that we understand what we discussed afterwards
- Talk about how do we build the community who would help us build the tools
- Erika wants some advice on how to attract developers to contribute to badges (or/and lernanta, mechanical mooc,...) as an open source projects
9 May
Progress
- lots of traveling - mostly support
- Discourse
- Only internal auth for now (do we plug in social login too)
Priorities
- Next prio for the Badges is the integration with lernanta
- After we try to accomodate Jane with the ability to limit badge awards to the original creator of the badge for some badges
- Support for Gentle Python
- Tracking
- Campaigns for Mooc
- Fix git dependancies for lernanta
Problems
- ckeditor
- is it possible for us to use the front end one (We use it in Badges, but it has been not in use for a long time, so we still are not sure if it will cause any problems in the future) ?
- markup is way easier there is no backend setup
- errors are way easier to find - trough developer tools
- setup is easy (include javascripts in to the project and add class on html markup wherever you want it to be)
- The pip dependencies will be updated (we do no expect any more problems after that -ever :))
Process
2 May
Progress
- Discourse set up - http://p2pu-discourse.herokuapp.com/
- figure out how to test it and see how we could use it
- one idea is to try 1 month usage just for team +1 - Let's start this immediately
- Badges are in production - OBI integrated
- Dirk did a bunch of work (but not sure... follow up when he's back)
- Course notifications?
- Lernanta translations?
- Dirk @ Burning Man (offline)
- Erika @ AWS conference in Berlin
Priorities
- User testing of badges platform (discovery is too hard) and then making improvements
- Follow up with Dirk on his progress (see above)
- (Translation handling)
Problems
- Commenting broke on Lernanta - Last release broke the CK Editor
- We are using a lot of editors (CKEditor for comments with rich text, and badges, Markdown editor for pages, Disqus)
- Goal -> Consolidate and upate (when Dirk is back)
Process
- Plan better for missing tech/community calls -> remind everyone, enter info in etherpad
25 April
Progress
- badges OBI-integration prepared for production - needs testing http://dev.p2pu.org:8199
- need some help with the testing (how do we test this? also ask others during community call) I did last week, got no feedback :(
- please for rapid feedback
- Mechanical MOOC signup
- Made a few small changes which will hopefully fix the lost sign-ups problem
- final push via normal HTTP post
- delay sending of welcome email
- Not easy to test, but tried it for ~1000 sign-ups
- Update of copy to inform user they will receive conformation email
Priorities
- Get ready for 2 May MechMooc launch
- Push out Course notifications to production
- Lernanta Translations - discussed next steps with Erika
- Test and complete OBI integration?
- Just testing, after that I need few minutes to push to production
- There is need to integrate badges with lernanta and iframe script
- this is needed in order badges to be useful
- DU to send instructions on Discourse to CE (Chris to set it up on Monday)
Problems
- Mailgun API
- Email scheduler working? Yes (confusion between AM & PM scheduling)
- is it possible to prevent scheduling in the past all together?
- Google groups tech@p2pu.org, support@p2pu.org, etc
- schoolofopen@p2pu.org had trouble, only users who were members could post
- are we using these? Do they all allow posts from non members?
- Discourse?
- did this drop of our radar? No!
- there is a demo version at http://lcl.p2pu.org
- Sayamindu set it up
- for use that with the Media lab course for now (not P2PU community)
- running on EC2
- very keen to get a version for P2PU as well
- DU will frame in an email and send to Chris
Process
- Plan to upgrade production server (when Dirk is back)
- Communication around Music MOOC - Update to the community on community calls
- Chris is available for tech work on Monday
Non Tech Call
- Music MOOC (-> present to community) / connect with Eric / Peter Gabriel(the sledgehammer)?
18 April
Progress
- Pycharm (Python IDE) licence
- Data expeditions kicked off - basic email composer & scheduler running ( https://github.com/p2pu/mechanical-mooc/ )
- How does the scheduler work?
- Super simple.
- There is a list of emails. For each email you can specify a date/time.
- You can also still send manually.
- Each email is sent only once (manual overrides scheduled)
- Merged updated Swedish translation, new Korean translation and partial Hebrew translation
- Future: Differentiate between "quality" translations and "in progress" translations
- Current bad translations
- DU to reach out to community about translations
- Linode server upgrades (kick self)
- Dev server has been upgraded (runs etherpad server, and also beta.p2pu.org)
- never assume something like this will Simply Work
- always backup, always be cautious, always do it when you have time to deal with resulting problems!!
- DU to reach out to Zack Chase about course running on beta.p2pu.org
- Badges comming along
- a little slower than expected
- Reach out to community to test rich text editor
Priorities
- Badges
- push to OBI
- rich text
- integration with p2pu.org
- Course communication
- course announcements
- disqus notifications, etc
- LRMI blog post
- Music MOOC
Problems
- WYSIHTML5-bootstrap has several problems
- adding links
- making a single word bold
- would be good to have a goto editor for richtext/HTML
- my suggestion is stil CKeditor (clientside) http://ckeditor.com/ . It needs a bit testing before we could use it as default.
- Question about data mail accounts (bounces).
- Goal: Never expose/send-from an email address that bounces
- If we only show the address that bounces during the test mailings, that's fine. If users see the address (or if it is set as reply-to) then we should make sure not to bounce replies)
Process
- Board update was written for geeks (and lots of good stuff wasn't articulated in a way that gets it the attention it deserves) - Have a look at what I did with it (for next time)
Other
4 April
P apologizes for missing the call (Hewlett meeting overlaps)
Progress
- Badges
- Good talk with VMG and Paul Alison at http://edtechtalk.com/ttt
- Phase II functionality prioritized and in the process of being done
- User support for
- technovation - creating old style badges
- school of open courses
- LRMI
- Discourse (emails from Sayamindu)
- Music MOOC
Priorities
- Open learning hackathon
- Schedule work on MOOC email scheduler ("schedule scheduler")
- For Python MOOC next iteration (Is May feasible?)
- Course wide notifications/anouncements
- Badges
- pushing badges to backpack - by next week!
- Music MOOC
- getting some feedback from music students
- incorporate feedback into more formal proposal
Problems
Process
28 March
Progress
- LRMI (released code on server)
- User support for School of Open
- Badges: started planning for phase II / planning 4-6 weeks
- Backup for badges
- Hoping that we can get discourse set up on the dev.p2pu.org (Sayamindu)
- Set up a wordpress site (no content yet) for open learning theme (eventually -> open.media.mit.edu)
Priorities
- DU still need to write blog
- Data expedition planning for School of Open (-> Open Learning hackathon)
- Badges phase II: starting on design & implementation, including things like:
- OBI integration
- Filtering & discovery
- General refinements
- Music MOOC planning
Problems
Process
- Call Time (confusion) -> Call is anchored to 10:15 Eastern Time US
- Do we still use the Project Pipeline trello (link above)? Yes, it's the overview of other trello boards (=projects)
Music MOOC
- Course on production analysis -> Looking at a piece of recorded music, and looking at its components (different perspective on breaking apart a song -> e.g. verse, chorus, bridge / or different sonic elements / etc.)
20 March
Progress
Priorities
- badges.p2pu.org - phase 2
- next steps: Erika and Vanessa to share short summary of phase 2 with the community
- LRMI
- discourse.org - setup server
- initial group is team with a few core volunteers - plan is to replace back channel email
- in two weeks we start using it - looks promissing
- Project plan for Music MOOC
Problems
Process
- Dev process for badges going forward
- Mainly Erika and Vanessa working together
- Responsible - VMG/EP
- Accountable - VMG (it's her hair on the block)
- Consulted - DU/PS
- Informed - Community, people with accounts on badges.p2pu.org
- Getting better at email -> http://hbswk.hbs.edu/archive/4438.html
What happened with mentors.p2pu.org for lcl course? - PS: Nothing, we ended up not using it
7 Mar
Progress
- Badges: http://dev.p2pu.org:5543/en/
- Back channel chat & video integration: http://candy.media.mit.edu (allows you to watch the video and chat in one window now)
- SOO (Done, but not deployed yet) Added links from course page to SOO home page, Edited which lists SOO courses show up in
- Mechanical MOOC: Python MOOC email
Priorities
- SOO launch
- Might get further tech requests from Jane
- Need to push changes to production
- Badges
- DML demo
- Show folks how to create a badge
- Show folks how to award a badge
- Share progress with community and ask for feedback. Mention that we won't be able to implement feedback until after DML.
Process
- Supporting SOO requests - balancing resources with requests is difficult sometimes
Problems
Stuff
- Q for EP: How was the first week?
- EP: The first whatever is usually whatever. This has gone better than expected.
28 Feb
- Erika joining tech call
Progress
Priorities
- badges, badges, badges
- soo launch
- Feature request - List a course in a school, that is not hosted in lernanta (sorry!)
- We can handle this manually/in the database - but no UX
- Image URL (alternatively, an image and we store it)
- URL for the course
- Title
- Description
- Language
- Tags (List)
- LRMI
- Onboarding Erika - https://trello.com/board/onboarding-erika/512a0f5f40f865e46c0084bf
Discussion
Process
++++++++++++++++++++++++++++
21 Feb
- Erika joining tech call
Progress
- Minimal viable product for badges
- Working on mockups with Vanessa
- Elaborating use cases
- Python MechMooc (Django) - https://github.com/p2pu/mechanical-mooc/
- CSS framework
- Some changes to Media Lab course features:
Priorities
- CSS framework
- Badges project spec
- Discuss Shuttleworth project (set up a project call) - Wed 27, 9am EST
- Onboarding for Erika
Problems
- Badges contracting
- Shuttleworth funding 22k less than requested - we have to kill one of our babies
Process
- Mechanical Mooc
- Set up call with CE, PS & DU
14 Feb
Progress
- Lernanta backup to S3
- Setting up P2PU OAuth (code from Paul)
- Learning creative learning MOOC
Priorities
- Pythonic Mechanical MOOC
- Spec out minimum viable product
- Review group management
- Set up a simple grouping default
- Group by timezone
- Max size 20
- Considering to remove self-grouping option for now
- Analytics
- Opens
- Groups activity
- Unsubscribes
- per group & per week/email
- OAuth
- Badges
- CSS github pages (still not done?)
Problems
Process
7 Feb
Progress
Priorities
- Setup backup to S3 (almost done) - https://github.com/dirkcuys/active-memory
- Media lab MOOC
- Course UX bug fixes
- CSS github pages
- Badges Project
- The pythonic Mechanical MOOC
- DU/CE to discuss (a little bit later)
- First -> Just move what we have to Python
- Then -> What are the next features we have to build, and for whom
Problems
- Media Lab MOOC signup problems (we're fixing it manually)
- No reply email - fixed by Philipp
Process
http://beta.p2pu.org/en/courses/27/teaching-and-learning-with-social-media/
31 Jan
- Progress
- getting ready for release
- Media Lab course
- CSS framework almost done (trello board cleared)
- Incl. documentation/how-to use
- Priorities
- Setup staging server
- Update live server
- Release new course ux and CSS
- Media Lab course / grouping script (and manual groupings)
- Documentation for CSS framework
- Amazon Glacier setup
- Media Lab course email troubleshooting
- Philipp to share a set of email addresses with CE/DU
- CE to review if they are in the database
- Update MMOOC Docs to talk about GA tracking code
- Problems
- mailgun emails not sending for ML mooc (flippin annoying)
- CE to get access and help
- PS to send email to CE
- GA code still in MechanicalMOOC
- CE to update documentation
- File management - 3 Categories
- Backups/ short term storage for server data - Amazon glacier FTW!
- Organizational Sharing - Dropbox/Google Drive
- Hosting media for serving asset / media files for lernanta - either s3 w/ cloudfront or rackspace with akamai
- Process
24 Jan
- Progress
- Priorities
- Course UX (29 Jan)
- CSS Framework (29 Jan) - The exact issues on the trello board are #1
- Problems
- Need some graphic design help with CSS
- Process
- Trello boards! - use them more and as work is done!
- If you are working / spending time on something, it *has* to be on the trello board
- Go through the "Project Pipeline"
17 Jan
- Progress
- Check out http://learn.media.mit.edu - look familiar?
- Sysadmin
- removed spam from badges.p2pu.org!
- backed up etherpad lite database
- figured out where the code is for etherpad...
- Course UX
- show "fresh additions" on course listing page
- notifications for new users in courses
- MOOC
- CSS
- Setup seperate project scaffolding and variables
- Make the documentation page look p2pu nice
- lernanta CSS to be finished fo end of month
- Blog posts
- Priorities
- Small tweaks to Mech MOOC software for Media Lab course
- Sysadmin
- moving pad.p2pu.org to same server running stats
- updating p2pu.org OS
- moving badges.p2pu.org to different server from production
- maybe doing it all using Chef
- Course UX
- feedback from community
- support for old courses to list and update on learn page (currently a 1 time export)
- CSS
- Proposals:
- MOOC Maker RoR -> Django
- Mismatch between org tech stack and MOOC
- MOOC Maker will be implemeted in Django
- DU, CE to plan
- Problems
- DONE (removed) -- Still have this in our google groups footer:
- Process
- Trello still underused (is there a MOOC Maker board now?)
- Add a person (who takes the lead) to each Trello card
- this shouldn't substitute communication! (agree!)
10 Jan
- Progress
- Tech plan posted (woot!)
- Course UX - collecting more feedback
- Mechanical MOOC
- Priorities
- DU Dev hiring
- CE Trello board for Mech MOOC
- CE/DU Blog posts (MOOC Maker, Music Hack Day, Google OER workshop, Dev Process)
- DU Course UX
- CE CSS framework (This will be useful for working with Rich. Not sure what the date is/ by when he'd need it, but soon.)
- Cleaning up and documentation
- Top bar breaking (related to responsiveness) - Top Priority
- Make modular
- CE Data MOOC (if that moves forward)
- Problems
- Embedly error causing some problems - fixed
- Process
3 Jan
- Progress
- Tech plan 2013 going out Tuesday 8 Des - please have a look and give feedback before then
- Mech MOOC
- Jan 7 Start of seq 3 - Gentle Intro to Python
- Some changes, incl. confirmation email before course starts (reduce dead-weight), intro email to groups, group size back to
- School of Data MOOC
- Priorities
- Next steps badge dev hiring
- Review dev applications
- Speak with VMG about dev shop NY
- Sat: Mooc Controller discussion / call
- Higher-level planning / goals / features
- Dev process doc
- CSS:
- Cleaning up and documentation
- Fix responsiveness
- Make modular
- MOOController: Documentating :) and blog post (what have we built, where are we going with this)
- Blog post: Music Hackday
- Blog post: Google OER workshop
- Pingdom alerts / performance issues
- Process
- Problems(?)
- New UX rollout getting pushed back
20 Dec
- Progress
- Priorities
- (Jan 2013)
- CSS: Cleaning up and documentation
- CSS: Fix responsiveness
- CSS: Make modular
- MOOController: Documentating :) and blog post (what have we built, where are we going with this)
- Blog post: Music Hackday
- Blog post: Google OER workshop
- New UX roll out
- Process
- Dev Process document to be shared in Jan 2013 (add note about wearing shirts on calls)
- Problems
13 Dec
- CSS
- Progress
- Priorities
- finish before the end of the year
- merge CSS trello board into course UX board
- responsiveness
- Mechanical MOOC
6 Dec
- Progress
- Priorities
- Blog posts
- Music Hackday
- MOOController
- CSS
- Update beta.p2pu.org
- Get framework ready for badges developer
- Combine trello boards and get on top of everything (metaphorically speaking)
- Problems
- Process
- UX/CSS trello boards combined? Todo CE
29 Nov
- Progress
- Course UX
- Discussed OAuth work with PO
- Shouldn't have an direct impact on p2pu.org users
- Could be used to enable signing in to other services (like wordpress) using P2PU credentials
- Is this for sites that we host? So, our wordpress installation? Or other sites?
- API authorization
- Next steps:
- follow up with PO
- find out how long
- define concrete output (lernanta as oath provider + wordpress login)
- Mechanical MOOC
- Grouping for sequence 2
- admin interface for sending email
- is the grouping repeatable?
- is it a problem running the grouping script again before the first email is sent?
- Problems
- Process
- Priorities
- Get feedback on latest CSS updates, including fonts (Chris)
- Google OER conference
- Course feedback
- Mechanical MOOC
- Chris to tar -cjvf email logs for June
22 Nov
- Progress
- Course UX
- New courses show up in profile!
- Tagging new courses
- More activity on beta
- Mechanical Mooc
- CSS
- Problems
- CSS seems a little stuck
- Mech MOOC grouping (could be under Process)
- Priorities
- Process
- Pushing updates to beta, now and once people start using it (how do we let them know?)
- Regularly pushing code to github
- Merge Course UX and CSS boards (+1)
- Setting Priorities for dev team each week
15 Nov
- Course UX
- listing old and new courses now works
- Schools can feature new courses
- haven't had any courses being created yet
- CSS
- focus on "need to do" issues
- MechanicalMooc
- email glitch
- push changes to github
- look into using routes + members only list to send messages to users
8 Nov
- Progress
- Course UX
- beta.p2pu.org up and ready
- waiting for courses to be created
- Mooc
- Updating code for 2 iteration of MechMooc
- Feedback on Mooc proposal
- Priorities
- Course UX
- creating courses
- course index
- Problems
- Process
1 Nov
- Progress
- Course UX
- LRMI
- School of Data
- Not using beta.p2pu.org or p2pu.org for now
- Plan is to build a Mechanical MOOC, and schools features over time
- Another round of feedback for CSS Framework
- Priorities
- Getting beta.p2pu.org up and used (UX, CSS)
- Change main "Create" button to link to new UX creation - already the case on beta
- Hiring more developer resources (LRMI, HTTPS, badges/assessment)
- Problems
- Process
- Dev communication - Standup on Monday, Tech call on Thursday
- Ideas
- MooC Maker - allow people to create a Mech MOOC
- Next step: Try to raise funds through Lab pool / Draft a 1-2 page proposals
- What have we built so far? -> Mech MOOC / Python course
- What is the opportunity? (Benefit)
- What is needed to make it happen?
- What will we learn by doing this?
25 Oct
- Progress
- [DU] Working through Course UX feedback - still a few small things to fix, but getting to the point where we can invite more users to try alpha
- Planning to do more testing, discuss outstanding questions in the all-hands/community call.
- [CE] CSS - Planning to push a release later today and ask for feedback
- DU & CE to go over the update process for alpha
- Outstanding tasks to complete CSS: A few pages are still missing (e.g. badges)
- Courses/Challenges/Groups: Use old CSS
- New course UX: New CSS/bootstrap
- Email verification process (we put in place a quick fix, is that enough?)
- Priorities
- [DU/CE] Beta test of new UX (=CSS)
- Experience won't be completely integrated (requires new user registrations)
- Notifications through disqus (rather than notification module)
- No https problem, no limitations on iframe embedding
- Host on http://schoolofdata.p2pu.org
- Planned beta launch: 1 Nov
- [DU] New data dump for June
- Problems
- We've had problems with http/https content, especially for embedded content from other servers that was sent over http
- Decision: Going to un-https the site (only use https for passwords/sensitive data)
- DU to reach out to Paul
- Process
- Communication about projects
- Next step: talk about this again
- Other:
- LRMI integration - how to add LRMI features into the site
18 Oct
- CSS
- Mech MOOC
- How do we know if someone "drops out"?
- Could we add a badge at the end of the course?
- CE to talk to VMG/ JA about this
- Target group sizes: 3, 9, 27 (invited 9, 27, 40 to cater for non-shows)
- CE to set up Trello board for feature requests
- Schools
- Heroku
- Help hiring/finding more devs
- CE has contact for front-end dev
11 Oct
- Progress
- Courses UX: http://alpha.p2pu.org/en/courses/13/breaking-the-rules-a-poetry-workshop/
- Backend clean-up
- Fixed up some issues with pagedown editor (preview was not the same as the final HTML after saving)
- PS: I want to play with this a bit, but find it confusing at the moment, e.g what's the difference between "Update Content" and "Preview" isn't clear to the user until they click on those
- Disqus
- There were some issues with comments not loading - those were fixed
- PS/QUESTION: Can we put the discussion back underneath the content, rather than on a separate page?
- DU: Still not convinced that Disqus is the best option, but happy to try it out and give it a real chance
- Main benefit is less work for us / less confusing. But has limitations as well (gives us less control over spam.
- PS: You can configure single-sign on, but only in the Pro version (which costs money) - No free non-profit discount for the full version as far as I know ;-(
- DU: How much more work do we want to do before we roll this out for some users?
- PS: Agree. I think we're pretty close. I talked to Bekka about asking a few of our "power users" to create courses in the new UX (when you are ready). I also think everyone who gets paid by P2PU should put up an actual course.
- CSS (where are we with this? what's missing, if anything?)
- Dashboard pages are done
- Fixed up header
- QUESTION/PS:
- Is this page still accurate? Would be useful to see a list of things that still need to be done. http://pad.p2pu.org/p/dirk-chris
- not up to date. everything on that page is 'done' but needs to be cleaned up (can we please have some place where we track this. for someone who is not in the trenches it feels like this is turning into the neverending story ... and would be great to see what we still have to do ... )
- maybe a trello board? https://trello.com/board/css-framework/5076d9cce4b0c2b6650c53f0
- Resolved previous issue with openbadge API over HTTPS
- Mech MOOC
- grouping for MOOC
- groups formed later today
- groups emails being sent out this evening
- CE: "This is going to work!"
- DU: Let's be ready to recover if something goes wrong. Let's get a backup of the heroku database as well.
- Q/DU: How do we handle unsubscribes?
- CE: Mailgun logs the unsubscribe request. Then we run a process to actually remove people from the group databases.
- Priorities
- Mechanical MOOC - CE - until Oct 15
- CSS - CE
- Courses - DU
- Schools - DU/CE
- Problems
- Spam - should be OK for now
- CSS framework
- Old courses/challenges/study groups not 100%
- do we fix it or use old layout/css?
- Where does help link go when you log in?
- Courses
- disqus
- + less effort, notifications, moderation
- - extra login, any registered users can comment per default
- editor - server side preview
- pagedown is nice, but we need to clean up content and the preview should be exactly the same as the final version!
- Schools
- talk now or set up separate call
-------------------------------------------------------------------------------------------------------------
4 Oct
- Progress
- Priorities
- Finishing up backend CSS
- Alpha testing with internal group for "courses UX" and "CSS" separately
- Next steps:
- DU to prepare a demo on alpha with anonymized production db for testing
- Problems
- Messaging / Notifications for course review
-------------------------------------------------------------------------------------------------------------
27 September
- Progress
- Unified course UX is coming along
- CSS
- Mechanical MOOC
- Emails going out
- Need to get back to grouping script in future
- Also need intro/welcome email to groups
- Priorities
- Monday -> push out both unified course and new CSS so we can do testing
- Mechanical MOOC email only
- Problems
- Ran into an interesting problem with CSS - google search box has limited customization options
- Process
-------------------------------------------------------------------------------------------------------------
20 September
- Progress
- Unified course
- CSS framework
- What's left to finish up? HTML on the pages needs to be put into the grid system.
- Progress during last two weeks -> worked on common elements, now moving onto the templates
- Is there a list of pages that need to be updated?
- https://github.com/dirkcuys/lernanta/tree/css-framework
- Priorities
- Unified course
- Goal to have community ready demo next Thursday (27)
- CSS framework
- Goal to complete list of minimal viable pages by next Thursday (27)
- Problems
- Process
- Github check-ins
- Frequent commits
- Keep work in progress in branches so Dirk can start using it early
- Send pull request to master when finished
- Google hangouts work well
- Start regular stand-ups of dev team (only two people right now, but will get bigger)
- Use hip-chat for "hanging out" as a team (and quick feedback when needed)
- Other / Misc:
- School of Data built a really nice wordpress community site at http://schoolofdata.org - we need to figure out how to embed / link courses
13 September
- Progress
- Mechanical Mooc
- Access to mailgun credentials
- Theres now a mailinglist called python-all that we can send email to all python course members.
- Only use for mass-announcements that don't allow replies
- will replies be sent to everyone - no (replies only within the small groups)
- use Read-only group for mass announcements - yes!
- For normal course content emails:
- Use the-machine@mechanicalmooc.org and send bcc to all groups
- Looks like you have to send from authenticated SMTP session. (http://documentation.mailgun.net/user_manual.html#mailing-lists)
- IOW you need to use a mail client like thunderbird
- Grouping script
- a work in progress
- P says, please do extra testing on this as research hinges on correct grouping
- Unified course
- Busy adding comment capabilities
- Release of first prototype pushed back by CSS framework
- CSS framework
- Waiting for Chris to push changes to github
- This is starting to hold up other work
- archive.p2pu.org
- Sent final questions for migration to Charles (either he'll respond or DU will figure out and go ahead)
- Priorities
- Unified Course [Dirk]
- CSS Framework [Chris]
- MechMOOC [Chris, after CSS]
- Problems
- Process
- Unified courses
- Let's discuss a rough roadmap for getting it completed in tech call (Roadmap dates depend on CSS framework completion)
- Launch beta / get feedback / make changes - 20 Sep
- Try out markdown/textile editor?
- Move to production (in parallel to existing) - 4 October
- Switch over - Oct/Nov
6 September
- Progress
- Courses
- Planning to have working prototype by Sep 14, push out before end of Sep
- CSS framework
- Need to figure out how to merge new CSS into trunk (merge with the existing legacy CSS files)
- Plan to deploy new CSS integration page by page (rather than migrate the entire site to new CSS before deploying)
- Next step: Fix major layout elements for key pages
- Targeting 20th of September for releasing css framework
- Migration of archive.p2pu.org
- Charles Tanton is looking into moving the old Drupal instance to Dreamhost hosting (super generous pro bono contribution so far)
- Priorities
- Continue with course unification and CSS framework
- Move on to schools support after CSS
- Problems
- Merging CSS
- Dealing with use of modals (turn some of the current models into actual pages, e.g. create a course process)
- Linode power outage on 1 Sep: "p2pu - (8731497) Lassie initiated boot - Failed Fri, 31 Aug 2012 20:14:03 GMT"
- Linode datacenter had massive power outage
- Request from community to change default editor (email from Jose)
- Can we make this a mini project (funded)? What's the right amount / bounty?
- Challenges switching the editor:
- There is no perfect solution
- It's not as simple to do as it "seems" (as we would like it to be)
- More technical users would prefer markdown, others prefer WYSIWYG
- There is existing content that needs to be migrated (or work in a new editor)
- Process
- Add chris to users who have access to production server so he can help with problems
30 Aug
- Progress
- Course unification
- Sys admin - moving archive.p2pu.org
- CSS
- Release
- Priorities
- Course unification (Target date: ...)
- CSS (Target date: First version 31 Aug, then update in next 2 weeks)
- time to release
- consistency
- ease of use - to create a new site/new functionality (reduce number of elements, avoid defining custom CSS elements as much as reasonable
possible)
- Problems
- We have a lot of things on our plate and will need to add developer(s) -> Schools, Badges, Courses/Challenges functionality (one type)
- Prefer to scope work as projects (start/end date, clearly defined)
- Please start thinking about people we could reach out to
- Process
- Discussion: What do we want the schools "product" to do?
- How to support schools - through widgets, API, better configuration of landing page, separate server, etc.?
- Options
- No school homepages on P2PU (just use tags or categories to group courses)
- Current implementation / Schools homepage (but better / more features / more customization)
- Schools run separate sites (using whatever they are comfortable with) - link to P2PU for courses & badges, etc.
- Current schools client: Some schools want to use the basic offer, others want more flexibility / features
- Discussion / Opinions:
- It's hard to support everything that schools want, because they are very different
- Running separate instances of lernanta comes with big challenges (could diverge)
- What we currently offer maybe enough for some, but not for all
- For those who want to build more ambitious schools, which should offer a way to do that on separate sites
- Schools then use P2PU for courses & badges
- Support minimal feature set on lernanta
- Widgets to let others sites display school relevant content (course thumbnail boxes ...)
22 Aug
- Progress
- Learn page up on dev.p2pu.org
- Priorities:
- Add School of Open to navigation/menus
- Quick fix: add to footer on page
- Long-term: consider adding "Schools" drop-down to header (waiting for switch over to bootstrap)
- Release
- Courses / Challenges
- Server admin
- What are the things we can outsource, or ask Chris to do?
- CSS framework [Chris]
- Problems
- CSS framework is blocking some of the other planned work
- No waves in Durban (update: not a problem anymore!)
- Process
- What do we do with the tech call?
- We like the PPPP structure
- Everyone busy with tech stuff (DU, PO, CE, ?)
- DU: Move to Thursday before community call
- Mechanical MOOC ... what if ... something goes wrong? (queue scary music)
- P sent an email to John to ask for basic documentation
- John has been in touch with DU to explain basic functionality, DU asked John to update wiki page
- DU: follow up on license, and wiki page documentation
- Courses / Challenges
15 Aug
- Progress
- Priorities
- Twitter bootstrap integration [Chris]
- Learn page functionality [Dirk]
- Up next:
- Course/Challenge merge
- Updated design for homepage and learn page
- Problems
- Footer missing from mockup - ask Aleks
- Copy - ask Vanessa
- Process
- Project pipeline needs a little cleanup and thought
- Github is used for small things, but there's some overlap with Trello
11 July
- Progress
- release went out
- incl. reply by email feature, works, but still needs a few updates / fixes
- "out of office" notification loops
- scrub email addresses
- major uqpdate to the install process - it's super easy now, only 4 steps
- mechanical mooc software almost done
- still a few UX tweaks needed, waiting for content / script
- Priorities
- [John] Collapsing courses, study groups, challenges into one model -> "courses"
- [John] Add ability to facilitate cohorts in courses
- [Chris] Revising CSS framework (migrating to twitter bootstrap)
- [Aleks/Chris] Clean up of site design
- [Nadeem/Dirk] Moving forward on metrics, currently reviewing what we have, speccing out what we need
- [Dirk] Add conversion tracking to google analytics
- [Dirk] Course creation
- Problems
- responsive design issues in twitter bootstrap for mechanical mooc
- Process
- Still need a better/clear way to deal with feature requests - how to handle requests coming through github issue tracker?
- Next steps:
- [Chris] update instructions URL
26 June
- Progress
- Notifications
- Reply by email
- reply+kekjhsdfh-2323jj23k4hiuuudsyoaf@reply.p2pu.org
- noreply@p2pu.org
- Possible security issue with people replying to notifications with spoofed "From" address
- Updated email messages
- Metrics
- queries are really slow, moved to background with celery... could be better, will give it more attention later
- Mechanical MOOC
- Started implementation, should be ready with a first version this week for testing
- Got questions for signup from Vanessa
- Priorities
- Mechanical MOOC
- Cohorts
- Call later today with Dirk, John, Vanessa
- For when Chris starts
- Server Admin / Automating Deployment
- CSS Framework / Front-end
- Problems
- Process
- John: Working on documenting prioritization and sending to community so they know what's up
19 June
- Progress
- 18 May release
- P: Congratulations! All went smooth apparently?
- DU: Unfortunately not 100% ;-)
- P: I liked the release notes, but a little more detail may be useful for less technical users
- Metrics trouble
- Performance issues for metrics queries
- Could we just update the data once a day / static results tables?
- Next steps:
- Goal -> Fix it (could mean improving the way the stats are created, or turning it off again)
- Talk to Paul to see if he has some ideas
- Notifications
- Mechanical MOOC Mock-ups, waiting on copy / questions from VMG
- P: You'll get the question copy later today
- Priorities
- Metrics Fix [Dirk]
- Mechanical MOOC [John]
- Getting feedback from others
- Email features
- Prototype this week
- Notifications [Dirk]
- Cohorts [John]
- Problems
- Archiving mailing lists for Mechanical MOOC
- Processes
- Screencasts after new releases
- Only for major new features
- Feature "owner" does the screencast (not Dirk), e.g. Vanessa for badges, Bekka for community review, etc.
- Misc:
- Philipp will miss next week's call (traveling)
June 13
- Progress
- Course creation 'ready' for release
- People who have reviewed / given feedback
- Started work on notifications
- Subject text special characters fix
- Release on 18th
- Priorities ( https://trello.com/board/project-pipeline/4ec0f020c137ff072a5d8afa )
- Notifications
- Clean up code
- Split out into separate notification module (for future improvements)
- Reply by email (where it makes sense)
- Email copy (wording)
- Cohorts
- Firming up idea / getting it ready for development
- Cohort -> A way to group people
- Creator of the group gets to set a few parameters and act as a facilitator (assign others to be co-facilitators)
- Offers discussion functionality (also fixing up threaded discussion in the process of designing cohorts)
- Mechanical MOOC
- John is doing most of the design / implementation work
- Concept review on Friday, then starting to build next week
- Problems
- Processes
- Need a message to community about priority development (how do we decide? what's a priority right now? how can more people get involved?)
- Questions
- What's the status on badges development? Some content on product discussion etherpad
- Waiting for Vanessa to set the direction / then turning dreams into reality ;-)
June 6
- Review pipeline / development process
- How do we set priorities?
- Decide -> Is it a problem that needs to be solved?
- Evaluate -> effort vs benefit
- Funding requirements -> where are these listed? (JB and PS to talk through / put together project plans) (would like to have a page with this info ->adding to next weeks call
- Affected users
- GOAL: Three priorities at a given time
- What's the status of existing mockups (which ones are final?)
- Avoid unfinished projects from going into development
- Example:
- Multi-task edit form <- it's not a problem for users
- Next steps:
- John to review pipeline - pick top priority and get to development stage, hand over to Dirk
- Define "the problem" / "goal" for development tasks - Projects should have clear problem / solution
- Get next projects lined up with priority
- Plan for future calls -> Progress / Priorities / Problems / (Processes)
- Short-term expansion of development resources
- PO - 8 hrs
- Goals:
- Ensure DU has support in technology design / implementation as needed.
- We have ideas for a more modular platform and open interfaces. Help us turn them into conceptual designs, prototypes & developer documentation.
- Helping us get clarity on where we want to go and turn into concrete strategies for implementation.
- Take what we have right now as the starting point, and map out how we get to where we want to go.
- Focus is NOT building from scratch, but growing / improving / iterating based on what we have.
- Primary concern: different parts of P2PU work together more independently, first step towards open architecture and APIs
- Make changes to the backend to enable experimentation
- Help us build momentum in the right direction rather than set a target
- Tasks:
- Provide mentoring to technology lead
- Provide code-review and design input as needed
- Develop conceptual design for modular architecture of core platform
- Define modules and apps and interfaces between them
- Question:
- Is 8 hours enough to drive this (or act in support role)?
- What is our strategy towards developing and exposing APIs?
- CE (pending)
- Goals:
- Improve front-end and UX
- For each of P2PU's core modules, review UX and front-end code, clean up and improve.
- Solve real problems that exist on current site
- Focus on simple solutions (not bells and whistles)
- Improve underlying front-end architecture
- Clean up CSS
- Modularize CSS / CSS framework
- possibly introduce backbone / other frameworks for web interfaces -> make P2PU work more like an app, improve responsiveness
- give preference to established standards / technologies with more longevity, e.g. jQuery
- Sysadmin:
- Explore cost implication of moving lernanta to heroku (incluing redesign of application, hosting cost, etc.)
- Either migrate to heroku or develop scripted / automated deployment of production site onto a clean ubuntu server
- Goals:
- Ability to recover from disaster
- Reduce time for platform releases
- Enable more people to contribute to development (Make it easy for new developers to get their development environment in one step)
- How do we credit contributors?
- What is the background to this?
- https://github.com/p2pu/lernanta/graphs/contributors
- YES to reward contributions
- Mention in release notes
- Mention in blog posts about new release (and mention them with links)
- Thank you emails on dev list
- Next step:
- DU: Add link to github graph to github project home page
- Sysadmin backlog
- What are implication for sysadmin work if CE comes on board?
- Upgrade production to Ubuntu 12.04 (a clean install)
- Move non critical services to different linode
- Passwordless restart for Apache
- Status monitoring for ALL critical services (apache, celery, ?)
- Next steps:
- Move forward with Liam Smit if we can afford it
- Otherwise, we roll this into scoping for CE
- (move to separate call between tech lead and product manager)
- Product/ Platform:
- Challenge creation process
- Notifications and comments
- Need to check up with sendgrid
May 23
- Current Projects
- New course creation - task creation UX
- Server admin
- Investigate updating jQuery
- Server downtime
- Probably caused by script that shut down apache to deal with high traffic (but server couldn't restart because it needed SSL key)
- Dirk disabled the re-start script
- https://p2pu.org/svn/
- Can we move this to github and remove from production server
- PS: Yes - fine to remove from production (may not need to put on github)
- cron.php?
- Andre Truter
- Set up a call and see where / how he can help
- Find someone else to help with release management (or helping to streamline) - maybe Paul Osman
- Ask Andre about performance tuning (both mysql and apache) (also ask Paul Osman about performance)
May 16
- Current Projects
- Finishing up conversion tracking
- Challenge Creation
- Upcoming Projects [are they in order of priority?]
- Cohorts
- CSS Framework
- Badges
- allow users to edit/delete reviews
- badge tab in challenges that allows choosing applicable skill badges
- Improve site messaging/discussion - http://pad.p2pu.org/p/site-messaging
- A more modular P2PU [need a plan for this - conceptual / strategy]
- API
- existing API work
- Identify needed APIs
- users
- badges
- course directory
- activity
- participation
- notification
- use APIs within our own code - modular Lernanta
- Modules
- Core
- Content catalogue
- People
- Groups
- Activity
- Challeneges
- Courses
- Mentorship
- ...
- Test checkbox for challenge/group/course creation
- http://www.flickr.com/photos/79237959@N02/7202714572/
- Other than the creator and course facilitators, who should be able to mark something as a test?
- How should it be done?
- using the django admin interface
- an extra button on the course for above mentioned people?
- Should course creator be able to change a test course to a non test course?
- Managing signal to noise ratios for courses
- allow users to vote for courses / community review
- point users to mailing list as a first point of contact
- don't put big link to challenge creation on landing page
- The above list should be in sync with the trello board (is it?)
- Process of updating the pipeline (John to get involved in future - when there is a discussion on the list)
- Mozilla Persona - worth looking into?
May 9
- How do trello, tender (help.p2pu.org), and lighthouse integrate?
- Two goals:
- Three tools:
- help.p2pu.org
- report bugs, ask for help, single point of contact for our users
- -> keep it the one main point of contact
- Lighthouse
- tracking development tasks
- has a lot of old content (may not be up to date)
- question -> can we replace this with github issue tracker?
- Trello
- community feedback
- dev work
- planning for development
- maybe only use trello for project pipeline and make github replace the other dev boards
- Questions:
- are we using others? github?
- john mentioned that start using github for new bug reports
- what about mailing lists?
- Difference between issue tracker and trello
- Issue tracker -> tracking bug reports ie click this and it doesn't work
- Trello -> stuff we're committed to working on and are currently doing
- Do users log bugs?
- John: No, they submit bugs via help.p2pu.org -> this is the single point of contact
- Moved this down:
Philipp: +1, but right now they also log bugs (there is a link to lighthouse in the footer - see Zuzel's note below) Let's remove that and point to help.p2pu.org +1 - Developers verify the issue (is it really a bug?) and then fix it or log it as a bug to be fixed.
- Should contributors be able to create tickets?
- All contributors / developers should be able to create tickets
- I noticed that users log bugs on lighthouse as well (I thought we had moved all of that to help)
- The 'Found a Bug?' link on the footer points to lighthouse (which can be changed) - should be changed to help --http://help.p2pu.org/discussions/problems#new_topic_form [done]
- However ultimatedly bugs that can not be solved inmediatedly should be moved to lighthouse since they are easier to manage there.
- There is an 'Attach a Lighthouse Ticket' action on the right sidebar when support staff is looking at a discussions
- Are trello and lighthouse in sync?
- I don think we have integrated trello and lighthouse
- trello is beaing used mostly for staff communication (with the exception of the work on the p2pu api)
- lightouse is still easier to use by voluntary contributors and it is integrated with help.p2pu.org
- Whats the difference between help and community mailing list?
- help is help.p2pu.org with is our user support site (with single sign on with p2pu.org)
- the community mailing list is a place to which some organizers, learners and people involved in moving p2pu fordward are subscribed
- Project pipeline vs development trello boards
- Dev board -> https://trello.com/board/development/4f3d1ecc3a1fad867ad57e76
- Project pipeline = high level overview of projects and deadlines (sometimes checklists are used to provide more details about steps and progress)
- Extra boards including dev board, challenge improvements board and p2pu api board go more in detail and can be assoicated with moultiple cards on the project pipeline
- Project pipeline vs lighthouse?
- project pipeline = where staff resources are focussed
- lighthouse is a big repository of TODOs (feedback from p2pu community and users) which can at some point go into trello or could be takled by volunteers or could stay open for a long time
- What about Github issues?
- it integrates with the code
- Simplified setup:
- (1) How P2PU Support Works
- Single point of contact -> help.p2pu.org
- If a support request comes in that is a bug we do this:
- FIX IT -> Done
- or Log it as a bug using the issue tracker that dev wants to use
- report back on help.p2pu.org (or provide the link to the issue so that users can track progress)
- always try to respond to people, even if we can't solve the problem
- If a user sends an email directly to an individual or to a list:
- forward it to help@p2pu.org
- Make sure not to delete headers / edit message so that original authors get replies from the helpdesk
- (2) Managing the development process
- Store bugs and issues that need to be solved on github issue tracker
- Volunteers can grab issues from here
- Bugs
- Trello project pipeline -> Overview of development "chunks" and where they are in the process
- update during weekly tech call
- Trello is where we store agreed specifications for what we build
- Store screenshots, mock-ups
- Link to background discussion on the dev list
- Roadmap on wiki (dreammap? - what we would like to do)
- updated once a month
- higher level than trello
- +1 -- i think that we need to consolidate a little. communication is spread across help, trello, lighthouse, mail, irc, etherpad, github, p2pu, etc
- help - user help / non dev help
- dev list - all dev discussions (like the API discussion currently happening on trello)
- github - tickets/bug reports, code reviews +1
- trello - high level strategy/priorities - does this then need to be synced with roadmap on github wiki
- Next steps:
- Direct every user questions / bug reports to help.p2pu.org
- Dirk/Zuzel -> Clean up lighthouse tasks (only 50 open ones, I'll flag some) to make sure we don't loose important ones
- schedule a call for this (i things at EST 10 - 12 thrusday, 10 on friday) let me know what time works for you
- Dirk -> Investigate moving from lighthouse to github issue tracker
- Are there any features we are losing?
- We may be losing the ability to "send" tickets from help.p2pu.org to the tracker (we can do that for lighthouse). Do we care about this?
- John -> Organize existing project pipeline into roadmap (discuss next week)
- Release management update
- Use google doc and/or etherpad?
- Google doc with technical todo (might contain sensitive info)
- Update release section on http://pad.p2pu.org/p/tech and include with dev notes sent to mailing list
- Good to have one step-by-step guide with all the notes that remains updated
- Maybe prepare a template and reuse it for each release
- Take notes *after* the release (don't let this slow down the actual release)
- Doesn't need to be public (main audience is internal)
- Next step:
- Dirk -> Create a release checklist (link to or replace existing documents)
- Contains a few standard items (same for each release)
- And updated with specifics per release
- Go through list of responsibilities and make sure each has a new owner
- Dev priorities/progress reporting in the community call
- It's a pretty brief update during the community call, try to keep it short.
- zuzel will run this week section
May 2
- Zuzel update (I actually meant something else, but good to hear what you have been up to)
- multiple task edit/create/order in progress -- demo: http://alpha.p2pu.org/en/groups/test01/content/edit/
- user-10/password
- can edit/order tasks on the same page
- included test at apps/content/tests.py for this functionality
- tested and updated lernanta setup instructions with ubuntu 12.04
- improvements to the django admin site -- https://p2pu.org/admin/
- the performance + ui of the admin site is better now
- did not manage to make it simple enough for non-tech people to handle spam
- couple of bug fixes:
- fixed cancel link of new comments page
- fixed next task link
- Next step sysadmin responsibilities
- http://pad.p2pu.org/p/detailed-responsibilities
- dirk and I had a chat yesterday -- http://pad.p2pu.org/p/zuzel_dirk
- next step: meeting tomorrow 1 hour and a half before the community call to talk about the release
- Sysadmin task included here -> http://pad.p2pu.org/p/detailed-responsibilities
- Linode accounts (Dirk)
- Next steps:
- Add Dirk to management interace for our linodes
- Zuzel and Dirk to look at the menus and features together tomorrow
- Backups
- Currently handled by Andre
- Next steps:
- Dirk to talk with Andre about current setup
- Next steps:
- work out who will take responsibility of each sys admin tasks in the future
- identify an "owner" for all responsibilities
- Badges discussion
- Dirk's prototype
- Course-completion-badges
- Create hard one-to-one association between course-badge and course (so no other users / challenges can award the same badge)
- Original design based on Webmaking 101, which is not generalizable
- Badges
- http://pad.p2pu.org/p/new-badges
- Should badges be reviewed before it can be added to a challenge?
- More general question: do we (need to) do quality assurance?
- For courses / challenges - Community featured. Natural selection
- For badges? Maybe a more important question than for courses
- Who should be able to create badges?
- Roadmap
- Dev environment set-up (how hard is it? how can we make it easier?)
- it's fairly straight forward for developers with python and command line skills
- there are detailed instructions that should work for novice developers
- main issue is if people run into problems
- troubleshooting takes a lot of time / complicated
- alternative would be to create a virtual machine template that developers can just download
- will still look into using vagrant for dev environment (uses virtualbox to automatic setup)
- https:// next steps
- google search results require page refresh
- soloved: not, yet
- Next step:
April 25
- Zuzel's list of responsibilities: http://pad.p2pu.org/p/detailed-responsibilities
- I cleaned it up more
- also defined more the sysadmin section
- When is the next release - can we have Dirk manage the next one?
- I am documenting the current release
- I will share the docs with Dirk and get feedback from him about what is clear and what isn't
- I was thinking of involving Dirk in the release planned for May 4th
- We need to schedule the time for the release in advance (so both of us are awake) and collaborate in the pre-release preparations
- Will all of the conversion tracking stuff be deployed with this release?
- adwords, analytics, and chartbeat should be up
- refferer?
- have to figure out how to pass the info between the time the user hits the site with http and the time (s)he logins with https
- @Dirk / Zuzel: Automated Releases?
- Will keep an eye on things that can be automated, would be nice to get this to a single step deploy eventually
- Next steps:
- Schedule chat about release process with Zuzel
- Walk through setup process with Zuzel on the 3rd of May (before community call -- will wake up early and ping you on skype)
- Do release on the 4th of May
- What's needed to resolve https issues?
- logged in users have to refresh page (cookies are secure) - logged in users over http
- (ideal) research if it is possible to put a non-secure cookie (accessible from https and http) that just says (this user is loged in)
- if we can do this then we can redirect users to https when we detect the cookie
- (alternative simpler solution) redirect all our website trafic to https
- direct access to https://www.p2pu.org or other subdomains produces an error
- Next steps:
- John to check DNS records to force redirect / add CNAME for www.p2pu.org to resolve error at https://www.p2pu.org
- Remove wildcard *.p2pu.org record
- Add a CNAME for www.p2pu.org to point to p2pu.org
- John do some research -> Still need a resolution for secure cookies (users get logged out when they switch to http)
- Contributor agreement - do we ask all contributors to assign ownership to P2PU?
- Shared the last version we had through google docs, should we paste it on a pad?
- MPL allows us to use code in proprietary situations. Do we want to re-license?
- Contributing should be as simple as submitting coa pull request - no red tape
- According to our lawyers we need the signed agreement for code contributions
- http://p2pu.lighthouseapp.com/projects/70576/tickets/22-contribution-agreement#ticket-22-10
- Contributions by paid staff and consultants are covered by their respective contracts already.
- Two questions we had in the past:
- Does each contributor need a customized version or can we make one generic version (e.g. signed by me with today's date) that contributors can download and complete?
- Is there a way to make the agreement "implicit" in joining the project? Similar to the checkbox that states you agree "terms and conditions" that most commerce sites use.
- P2PU is based on batucada, ownership of batucada code remains with Mozilla (maybe Paul Osman)
- Key reasons why contributor agreements are useful
- Relicensing - From MPL to LGPL (for example)
- We can't really do this, because MPL is infectious and batucada "infected" lernanta... we're obligated to keep the MPL
- We can do this if we own the code - we'd have to get ownership from Mozilla
- Why will we want to do this?
- Enforcing License
- John: I don't think there's any chance of people using lernanta (as it stands) in a way that we would be unhappy with. We're using the MPL because of Mozilla
- Right now it's not an issue. This would be setting us up for the future.
- Strategic considerations
- We may not "care" about others using our code in ways that the license doesn't permit
- We may not want to put resources into enforcing the law but think the public opinion will againts other people using the code in ways the license doesn't permit
- Weigh up the downside of making contributions harder (red tape) vs. the ability of enforcing the license at some point in the future +1
- Are we even able to get ownership of the underlying batucada code?
- There is little legal risk that others will use the code in ways that MPL does not allow (the MPL may discourage that use in the first place)
- More information http://www.harmonyagreements.org/index.html
- What about SaaS and AGPL, is the MPL like the AGPL?
- https://github.com/p2pu/lernanta/blob/master/LICENSE.txt
- Next steps:
- Philipp to contact Brian how OBI handles this.
- Philipp to sum up and send to lawyers.
April 18
- Process for manual adition of badges
- We are currently hiring a new learning lead. The learning lead support badge creation. While we are in the process of hiring that person we'll log requests for new badges and Zuzel can help create some of them.
- To make the process as easy as possible, here is a template for all the info that is needed for new badges:
- New features that are in development are ready for review on alpha.p2pu.org
- Some features require the user to be logged in as an organizer (use username: administrator / password: password)
- Added a new 'create challenge' tab
- Updated edit summary tab for challenges (labels, placeholder text for some fields are the same as in the challenge creation mockups)
- Updated edit image tab (small change to the layout to be easier to use)
- Updated edit status & duration tab in challenges (input duration like in the challenge creation mockup)
- Comments:
- I think full hours is enough (1 hour, 2 hours, etc.) / would keep it as simple as possible (don't think we need minutes)
- Is confusing the UI
- TODO: remove that functionality
- Rich text content before and bellow courses list on school home pages (http://help.p2pu.org/discussions/questions/63-school-page-layout)
- Included view submissions link on badge page: (previously only displayed a link to submissions if you have made a submission)
- Multiple reviews from different peers to non-unique submission enabled badges
- Deferred loading of the courses' metrics table:
- Improved task title validation so no task is created with an empty title / slug:
- Updated course creation notification message to organizer:
- Z: working on (in progress -- will keep working on it during the next iteration)
- Development priorities
- [Zuzel] Challenge creation process
- [Dirk] Badges - both back-end review of django badger / basic UI for badge creation
- long-term goal is to let anyone create badges and associate them with their challenges
- look at django-badger to make sure the two apps are either meaningfully different or consider extending django-badger
- start by automating creation of badges for a particular challenge (role the organizer of the challenge creates the badges)
- [Dirk] Sanding some rough edges
- Thumbnails etc. - future tasks to be agreed in daily chats with Zuzel
- Other:
- Possible profile improvements. (two cards) [Waiting on details from John]
- URL design [Needs more detail / input from John]
- Sanding some rough edges
- I really like this one as well ;-) [And maybe a good way for Dirk to continue exploring all parts of the code / site?]
- Dirk's notes: http://pad.p2pu.org/p/dirk_thoughts
- List grouped into tech, logical and philosophical :)
- Move information about future releases into github wiki and link to it from the top of this etherpad
- Dialing into London meeting afternoon (tomorrow)
April 11
- Status Report:
- Migration to django 1.4 still on progress
- Setup of google analytics, adwords' conversion tracking moved to next release
- https configured on production
- Background on using https for entire session after log-in:
- In the process of detecting and fixing pages that import non-https resources (images, css, js, ...)
- There was a small problem with missing avatars but fixed
- This causes the https:// on the url bar of chrome to be displayed in red or with an exclamation mark
- Problem with embed.ly - if you embed content through embedly the browser shows that there are non-safe resources on the page
- no solution yet for pages with embed.ly resources because even if the user embeds a video with an https link the code embedly sends has http:// links
- planning to serve files from old drupal site (e.g., images of courses appearing on users profiles) under p2pu.org so they can be included with an https:// url
- todo: automatically redirect admin site to https:// since http:// does not allow login
- some performance improvements rolled out which should improve page loading time when posting comments
- defered a bigger part of the sending and creating of notification emails logic to async celery tasks
- clear improvement
- OBI integration rolled out
- Question: What are we doing about the badges that were issued in the past?
- Users can manually send badges into the OBI (from their badges admin page) https://p2pu.org/en/profile/edit/badges/
- Wait until other OBI UI fixes are rolled out - then consider how to communicate the feature to our users.
- TODO: mark/create the badges that are going to be global to all challenges (neccesary code is on production)
- we decided to go with Helpful Feedback in a past tech call
- Sill on my [Zuzel] TODO list: prepare screencast about lernanta code overview
- Automated tests to be added during this release:
- Test course, study group creation still works as expected
- Test new challenge creation page works ok
- On apps/projects/tests.py and SauceLab tests
- Status report (Dirk)
- Busy changing "Introduction to contributing to Lernanta" course to challenge
- Added two optional tasks:
- Considering adding a task for "Basic linux usage"?
- Rename challenge to "Contribute to Lernanta" - what about "Learn to hack the P2PU code"?
- Merged support for multiple reviews/awards for badges like Supper Blogger given one submission
- multiple reviews, but one badge
- Philipps feedback: check if it works that way. keep it like that
- allow people to add "evidence" to a badge, but keep one badge for now (not multiple badges for the same submission)
- Still busy familiarising myself with the codebase
- Some random notes: http://pad.p2pu.org/p/dirk_thoughts (still have to add a few from my paper notebook)
- Q: what is the state of badges on the live site?
- Only for certain courses or for any course someone creates
- Only certain challenges (badge creation is still manual and UI changes in courses are needed to display badges there)
- Q: Do we have any wireframes/(dont know what to call it) showing how site navigation should work?
- Almost like a user story: home -> badges -> view submissions -> review appropriate -> award badges?
- nope
- may be useful, with the badges I'm not completely certain how someone should work with them?
- Or maybe something showing how the site comes together (like a graph showing possible navigation?)
- where is the mockups Chloe left? - see trello board for challenges
- No badge creation on current mockups to create challenges
- Allowing users to add badges to challenges will be implemented in future (as part of our DML work)
- Next step:
- Badges issuer project
- Next steps:
- Philipp to double-check with DML team to make sure we agree on deliverables
- Zuzel to check with Les Orchard how django apps we are building are different - then make recommendation if we should combine core code
April 4
- Now with additional developer - worth revisiting how we "test" prior to releasing new features?
- What worked and what did not work in terms of 'how we "test" prior to releasing new features' when Jessica and Arlton were onboard?
- What is the current procedure?
- There is setup prepared for adding Unit tests and selenium tests
- Challenge we face is to add more automated testing because our functionality is in flux - focus testing on things that are (semi)permanent
- Grouping Features - Checking the requirements during "testing" phase to make sure what was built matches the requirements
- Idea:
- Announce releases on the list and ask people to check and report issues+1
- releases on the live server or on the alpha server?
- probably alpha server
- Could do something like this (example from open badges infrastructure project)
- Release / testing process (two weeks timeframe):
- Features Spec'd out added to dev sprint (before sprint starts)
- Dev happens (first week and a half -- maybe before last tech call of the sprint?)
- As things get finished, they're pushed out to alpha by Zuzel or Dirk (who ping the feature owner) (before last tech call of the sprint so the demo is available on the tech call)
- Developer who pushes out the code to alpha lets dev list know and invites people to test-drive
- Feature owner verifies developed features (between tech call/email send to lists and Friday)
- Last minute fixes accourding to product owner and bug fixes (also a good point for translators to chime in) (between tech call and Friday)
- Zuzel deploys to production (on the weekend)
- Feature owner community list
- (lots of people are on both lists and dev will likely have an idea of what's going on?) (yes - added email to dev list above)
- Include new features and improvements in next newsletter
- Next steps:
- Update release process as described above (should we store this somewhere? / trello board?)
- I will add a wiki page with it on github
- Zuzel keep an eye on possibility of adding unit tests when needed - Automated Testing
- Get volunteers to be productive developers as efficiently as possible
- Not sure how trello could work for volunteers (note that trello requires people to be members of the boards), but we should at least try to fillhttps://trello.com/board/project-pipeline/4ec0f020c137ff072a5d8afa for future staff onboarding
- Ignore "onboarding" - i just used the trello board as an example for a step-by-step process to get someone up to speed (on any topic)
- But probably best to use a "challenge" ...
- Screencast
- Existing courses
- Next steps:
- Turn study group into challenge and update (Dirk)
- Whatever new resources are made, we should include them on the README for lernanta (everyone who makes new stuff) -- the wiki is better because it does not requires commits to update and contributors can help (the permissions of the wiki to edit are set so people can add content there)
- Dirk to update notes based on his own experience+1
- [If time permits] Maybe promote the lernanta challenge this 18 April+1 (Dirk to send Ali an email with link and short blurb/description)
- Quick / casual screen cast (Zuzel, John can help with tools/set-up)
- Maybe good to use an existing doc as outline... if we have one that describes lernanta otherwise would start with writing an outline of key points.
- Course dashboard (metrics)
- Has potential - but who owns? Next steps?
- we should talk about how this stacks up with other priorities +1
- Dashboard per course has limitations (needs server resources to create dashboard on the fly)
- Who wants this? Who is the user? (Course/challenge creators?)
- The community is the user so we can answer the question if users are "learning" something
- This gives us a per course breakdown (awesome)
- currently displayed in the interface for owners, is that an essential feature? Yes (and it's very simple)
- Its a useful feature for creators/users to see what's going on in their courses
- Original idea was to show this to all participants in each course so people can track their own progress, compare themselves to others, find out if someone else is struggling (and offer to help) ... but got complex and we didn't have time to really make it work
- Cool, we should think about trying to "unbury" this feature (Yay!)
- Next steps:
- Review existing feature and think about where it could go [John]
- Then decide if we make short-term improvements
- When learning lead joins, hand-over to them as owner
- Next dev priority: creation process
- let's follow the release/testing process we outlined
- we are going to use chloe's mockups as specks: https://trello.com/card/create-page/4ec0f020c137ff072a5d8afa/7
- john/zuzel will send more cards/tickets for dirk
- Sign-up
- encouraging profile completion (profile creation... what is currently the dashboard) - Sign up for a new account and you'll see what I mean.
- Small profile enhancements
- URL Design
- need to be spec out.
Mar 28
- FYI -- chat about p2pu api today 7pm BST (London time) on #p2pu-dev
- Hand-over of challenge development work
- Trello board with challenges related work - https://trello.com/board/challenge-development-sprints/4ed8ff4175e6467872117dcc
- Decide which of these John can take over, and which need to go to the new learning person
- For now, John takes over all cards - revisit when we have a learning lead in place
- Backlog of todos, full of stuff that we want to do but were not prioritized
- notes and ideas on cards, color coded by progress
- Badge Submissions form - will summarize feedback on a pad and link it from the card
- How are the sprints divided?
- Roughly grouped into 2-week sprints (Zuzel estimated)
- Many cards cover small-ish changes / improvements to badges and Challenge functionality
- Red lable indicates bigger change
- Are there any cards that are not relevant anymore?
- Most should be relevant still, maybe a few that aren't anymore
- Creation Interface
- Next steps:
- Review cards on board
- make sure they get scheduled
- Schedule upcoming development
- Add more deadlines to the upcoming trello board cards
- Swap cards if we think the specs for them will not be ready on time for the corresponding dev sprint
- What are we going to be working on after 'Conversion Tracking'?
- Challenge Creation - John to get it ready if there's anything left before it goes to zuzel
- Preparations for Dirk
- Dev call time / How can we make Google calendar remember?
- Please go into the detailed view and check which time zone it stores it in (I tried changing to US ET time, but if I check now it shows me South African time again)
- Today's time is correct for me, next week is also correct.
- Can we set all of our meeting times in GMT?
- Google calendar has it's own mind. ;-) It controls you. You will do what it says, when it says to do it.
- Zuzel will own this, everyone goes by what the calendar says.
- Where to add ideas for future improvements (for example, just shipped community review - we are getting some feedback now)?
- Some stuff in pipeline is not dev stuff but will require some development work at some point
- Project Pipeline board should be focused on development -> "Development Pipeline" we called it this before, but changed the name... can change back to be clear. We're not good at naming :( (we're good at iterating ;-) way to put a positive spin on it.
- Global Community Badges
- http://pad.p2pu.org/p/communitybadges
- How do we measure how we change behavior?
- We can easily measure how many people have received a given badge but what kinds of things will change?
- Mostly interested in how badges change behavior / motivation / participation
- We probably can't track this in much detail yet, but would be good to start thinking about it as we launch the badges
- Probably not quantitative, but can get some qualitative questioning of the people who give and receive the badges.
- Collect feedack through an opt-in survey
- We already have low badge issuing, by adding another step we will further discourage people.
- I was thinking of putting it in the site when the action happens. ("we need your feedback on this, click here to take a short survey or use kissmetrics/etc to ask the questions inline")
- Does the survey exists or will it need to be prepared?
- i made one already for the pilot in our survey monkey account
- We can re-use some of the pilot questions, but we make it fewer questions and more specific
- Follow up with me separately - need to involve a few other people in this
- Did we decide on launching 1 badge across the site? Helpful Feedback? Better Name?
- I'm up for as many as you like
- Let's start with 1 - many reasons to be thoughtful
- (ok as long as you guys plan to release some more in the future :))
- it will look lonely on the give a badge dialog but ok
- Is there a card for adding this badge to the site? Global Community Badges https://trello.com/card/global-community-badges/4ed8ff4175e6467872117dcc/25
- Helpful Feedback? Better Name? you guys said that we need a better name
- I like it - do you want to change? (ok, any objections?) one, two , three, sold! KA-CHING!
- ok.....anything else?
Mar 21
- Call time (tie to 10am Eastern) - done
- Useful: http://everytimezone.com/
- Also, there is a widget in google calendar that let's you see different times for a particular event in the sidebar
- FB on Challenge Creation Page https://gomockingbird.com/mockingbird/#m5ase18/wJabLR
- review some of the titles
- pitch it -> create ( or word that conveys excitement ;) (yes, "create" is not great!)
- (not an issue until we have badge feature)
review & publish -> add badges?
- like the idea of more clearly separating work "in progress" from published
- what happens to my challenge > do i have drafts courses on my profile?
- are skills = tags? (just another name, or needs different functionality?) > yes, same thing / in the future
- how do you go back and forth between the steps (e.g. you're at step 3 and want to go back to 2)? > need to look at this
- Next steps > add edits, share with community
- FB on Badge Assessment/Submission forms (send sketches via em)
- Submission
- Like that you show good work
- Embedd video/text when link to work (main thing I see on the screen is the work)
- Show rubrics in submissions - hmm - how about self assessment? (i like that. self-assessment increases reflection / meta learning)
- How do mentors volunteer to be listed? Challenge adopters for now. Mentorship feature has a long way to go.
- Could tie to personal mentor relationships (Paul is Susie's mentor, his avatar shows up)
- Or tie to general willingness to review badge submissions
- Assessment
- General:
- Is there another page for the discussion (back and forth) between the person submitting and assessing? no we need that! (maybe next version? - this is important, would really like to roll into this release - was a problem in earlier version)
- Next steps > create mockups / share with community
- Moving Signup Flow (https://trello.com/card/sign-up-flow/4ec0f020c137ff072a5d8afa/6) in the pipeline. Changes needed before conversion tracking setup (https://trello.com/card/log-people-in-after-successful-sign-up/4f3d1ecc3a1fad867ad57e76/15)
- Just added a checklist item on the https://trello.com/card/conversion-tracking/4ec0f020c137ff072a5d8afa/57 card
- Changes mostly focused on including better tracking (not big changes to sign-up process)
- Should we add easier ways to sign-up (FB, twitter, etc.)? > Something to consider when we review sign-up flow
- Are there opportunities to gather more information on our users (this goes beyond sign-up only)
- We'd like to have more data on our users to understand better how we can provide value to them, but need to be careful about how we collect this data
- Chloe: there is research that shows declaring your gender before a learning experience might result in different results, i.e. african american teens declaring their race, or girls declaring their gender performing worse in math exams versus kids that didnt have to declare that before taking a math exam.
- Next:
- P2PU as a lab - implications for the platform (just discussion for now - not a proposal yet!)
- already spoke with a number of people in the community about both conceiving P2PU as a lab and the implications that has for the site
- big challenge -> messaging (p2pu.org vs. P2PU the community lab)
- want to give more exposure to projects / experiments through the site
- announce jam days, incubators, hackdays etc.
- landing page with links to wikis, google groups, blogs
- aggregate updates (make it feel alive)
- but we won't support collaboration features through lernanta
- set this up as a separate site/application rather than build into lernanta? (with sub-domain?)
- e.g. blog.p2pu.org, mozillalabs.com, etc.
- should we support more independent "spaces" for schools (but run on one instance)?
- we have two examples now of people who want (are considering) to run their own lernanta instances
- does this create possibility to partner with others who could host their own instance? / what are implication of having multiple lernanta intances in diferent servers (not all managed by us)
- single signon + API + move any p2pu specific content that shouldn't be on the other sites to the database or make it optional.
- Think about distingushing p2pu.org from The P2PU "Lab" (P2PU the lab)
- Next step:
- More one-on-one conversations with core community
- Draft proposal for changes and share with community
Mar 14
- Status OBI
- Community focus
- What's the best way of doing this? Google group embed?example of how it looks?
- Community page
- Show RSS feed of latest topics from community list
- Link to subscribe
- Join Mozilla -> Join (the) P2PU (community)
- TODO: John to take forward
- Challenge set metrics - should we show "badges awarded" or "badges that exist"?
- Badges awarded is a "stat", Badges available is a "characteristic"
- >idea: stat=badges awarded i.e. 1025 / under the stats there is a box with the visual of badges
- Ensure that users know they can earn or not earn badges in a particular challenge (maybe use a "badges available" icon - mouse over shows you the badges you can earn)
- Number = skill badges in the challenge +
- Update the label? -> Badges Awarded (Yes - but that means we have to update the logic as well / what's the number we display?) -> or badges available don't update logic :) Let's update the logic (it's a "stat")
- # the badge awards to the participants of this challenges restricted to badge awards of the badges of the challenge
- ana A B*3
- john C D
- I think limit to skill badges for now (those are most closely associated with a particular challenge) otherwise fine
- format for numbers 0-999 in digits 1,000 - 10,000 == 1k - 10k
- TODO:
- Adding 202 challenges to webcraft home page and feature
done- Is there no way to add individual groups that are featured on the webcraft home page? Yes
- We have two more awesome 202 challenges that are almost done
- TODO:
- Zuzel will add a few courses to webcraft home page as featured courses
- Need links of the courses that should be featured.
Chloe to tell Jessy's API course ( programming-101) - done ( emailed Zuzel) - http://p2pu.org/en/groups/programming-101/
- 2 courses made by John's friends
- P2PU API status
- Community Badges for April 11:
- We need to:
- Collect feedback: done, send survey, but only 12 answers - taking into consideration but we make final call.
- (1) Decide on 3-4 badges to roll out across community.
- Which badges?
- Chloe and Philipp to discuss and decide based on experience so far, survey, etc.
- May focus on "role" badges and those awarded by community (not automatic) for now (taking into account the discussion across blogs at the moment)
- (2) Rebrand badges
- do we have any work going on this? there's a card on the design board based on some discsussions with chloe before -> https://trello.com/c/k6dYn1Sr
- i.e. Change images so they don't say mozilla?yes + redesign to fit P2PU branding and not Mozilla branding
- (3) UX improvements to make it easier to get community badges, need FB
- TODO:
- Philipp and Chloe to do (1) and share with community
- Chloe +Aleks? to do (2)
- Chloe to use input from discussion and get on (3)
- Jobs / Staff page on a branch?
- How can we add community members (less separation between team/community) to this in the future?
- jobs page already lists volunteer positions, staff page is about staff. we could include people with prominent contributions that have committed to the project as volunteers and possible change the name of the page from "staff" to "team"
- TODO: zuzel to move code to a branch so John can make changes
- Bugs / Small tasks on development board
- How do you want us to use this?
- This is a place for dev tasks that aren't part of a project with it's own board. Some big projects warrant their own board, but not all.
Mar 7
- STATUS COMMUNITY REVIEW
- demo
- login as administrator/password
- alpha.p2pu.org/en/reviews/pending/
- Fix before release:
- Combine current "Pending" and "Under Review" tabs
- Terminology
- Pending -> New course
- Accepted -> Reviewed (maybe "approved" is a better word, used more commonly in sites) I'm very nervous about terminology like approved or accepted - it implies that by default new courses are not approved, and creates a new power hierarchy -ok, how else to communicate? calling it "Reviewed by the community" or "Listed"
- http://alpha.p2pu.org/en/reviews/projects/test-webmaking-101/review/
- Mark as Accepted. -> Mark as "Reviewed" (also, remove end "." for options)
- Work on after release
- Make this a discussion / public review process that becomes a visible part of the course page
- users have to request review
- add notifications
- STATUS LEARN PAGE
- Push without design updates, if possible. We should have community input on designs upcoming.
- demo: alpha.p2pu.org
- Hidden functionalty:
- append infinite_scroll=on to the url get parameters (e.g. http://alpha.p2pu.org/en/groups/?infinite_scroll=on) to test autoload alternative
- featured=popular and featured=updated -- Popular and Last updated sections not completedly removed yet
- under_development=on, archived=on, closed_signup=on -- courses in this categories are not shown unless this paramenters are passed
- Other details:
- order: from new to old based on course creation date
- links on the site:
- Under development: ajax to avoid reloading page when using the filters
- Fix before release:
- Layout: Avoid "Community Reviewed Only" line break in the Filter
- Happens in Chromium (will be renamed to community reviewed when filters gets renamed to Show Only)
- Make filter button not necessary (checking and unchecking the box will cause the filter to updated)
- "Search Tags" should be more tags, we don't want users to think that this is a search funcitonality. Should be an autocomplete tags dropdown like this:http://cl.ly/12271V3v0G0m0C1G3k2B
- Enable selection of all languages (could be done by adding a checkbox in front of Language)
- Fix after release:
- Bring back the "Popular" option but review the logic/algorithm behind it
- How will users discover under devlopment courses if they want to (most users don't, I presume but don't know)
- Update the categofies of "featured" courses
- Make the "community picks" a *real* community pick, based on some aggregate opinion of the community
- Include a "showcase/highlight" section (which works like the old "featured" option)
- Discussion:
- Will we check if the Tags features is useful?
- google analytics for /groups?tag=something
- Are "Community Picks" really "Community Picks?"
- Not at this point, it's the new name for the previous "featured" courses functionality
- Clarification: Showcase (currently called Staff Favourites in the Demo is the previous featured functionality). Community picks works similar but instead of having a site admin marking courses as community picks we can have reviewers marking them when theydo the community review process.
- Issue with production server
- diagnosis?
- It looks like we were out of RAM.
- Reported to be Slow Yesterday
- John restarted apache and it went back to normal
- django sent a MemoryError report to me at 12:11 AM (UTC) -- http://pastie.org/3541044 at
- linode charts sow a ~0 on the cpu and networks charts between ~22:00 - 05:0
