SSL Everywhere

Warning; technical details ahead: Over the weekend, the entirety of the Commons was switched over to the HTTPS protocol. This has been in the works for a few months now, and took a few key steps.

We first needed to secure all of the content that you share on your site. We accomplished this by shifting all our media content to be served up using an S3 Offloads plugin developed by a company from Nova Scotia named Delicious Brains. For the most part all 200 000+ media items made the shift over to their new home. You might find you need to add your header back to the top of you blog, or if you manually referenced an image or file in a widget on your sidebar, you may need to grab the URL again now that it’s being served from a different server.

The next step was to procure certificates for all our our custom domains. Most of the sites on the site are covered under a wildcard certificate: *.commons.hwdsb.on.ca, but users who have opted for a custom URL aren’t covered by this certificate. We leveraged an exciting new initiative called Let’s Encrypt to secure sites like mrpuley.ca, suedunlop.ca, adunsiger.com, and mrjarbenne.ca. Although these sites comprise a small subsection of the 7097 sites hosted on the Commons, I’m inspired by the work of the Domain of One’s Own project, and would love to eventually see our work extend out to allow students to being building out their own digital cloud, as referenced in that linked article from Wired Magazine:

“Writing for EDUCAUSE Review in 2009, Gardner Campbell took the argument a step further. In A Personal Cyberinfrastructure he argued that learning to build and operate a personal cloud was a life skill students would need and should be taught”

If you don’t see the green lock at the top of the browser bar, you might have “mixed content”. A picture of a browser bar, with the green link indicating an SSL connection.This is caused by elements on the page that aren’t secured, and are still being delivered via http, and not https. In many cases, you can navigate to the post in question, and just add an “s” to the end of the “http” portion of the URL in the embed code (most sites that offer embedded content are secured by SSL. If you use a service that isn’t secure, reach out to them on Twitter and ask them to secure their embeddable content). Mixed content has been an “issue” within the HUB (Desire2Learn/Brightspace) for a few years now, so users who navigate that space will be aware of the issue. There is a movement to secure the web that we heartily support.

We couldn’t have done this without the help of our web-host and WordPress security specialist @boreal321.

As always, if you run into issues, don’t hesitate to comment below, or reach out to your 21CL Consultant via email.

The Commons Experiment

5 years ago, around this time of the year, we sat in the Memorial Building in Ancaster, feeling like perhaps it was too late, and that maybe we should wait to launch until Semester Two. What would become the Commons had just been brought to life on a small server. Most of the summer was spent to ensure we would be ready for September, knowing that if we lost a Semester, we would loose the year.

Today, we accepted our 30 000 user into that “little” blogging community, where we provide a stage for students to publish their work; a window into the classroom so that parents can peer inside; a space for professional dialogue. We provide a means of connecting learners across the board with other learners, with colleagues and parents, and with expertise out in our community.

And somehow through all of that, my avatar looks younger ;).

Here’s to five more years of sharing.

Charity Begins at Home

I’ve been using Github for a couple of years now to connect with our developer on the HWDSB Commons. We post a lot of code there, sharing it with the rest of the WordPress and BuddyPress community. For those of you unfamiliar with Github, this is how they describe their platform:

GitHub is how people build software. With a community of more than 14 million people, developers can discover, use, and contribute to over 35 million projects using a powerful collaborative development workflow.

When we look at trying to do real things in the classroom, and providing students Professortocat_v2with authentic tasks, I think Github has a role to play, particularly in secondary Computer Science classrooms. Github is where many international corporations share their work (Vimeo, Facebook, Twitter, Netflix, Apple, Microsoft, and Google, among others). I don’t think there is another segment of industry that works so transparently, and allows the public to look in on the process of how their product is built. Github also flattens the hierarchy, eliminates corporate silos, and allows anyone with a username to contribute to projects, or fork (create your own copy) and hack/remix existing code projects. A Github profile is now being used out in the software development community to gain employment: it’s more powerful than a resume.

Github offers an educational package, and repositories to help teachers use Github in the classroom. If teachers want to teach Computer Science in authentic ways, they should be investigating Github to share code within their classroom. But using it in the classroom is only the first step. The real learning happens when the students begin to see themselves as contributing members of the software community:

As an example, Bootstrap (a theme initially created at Twitter) is available here on Github. There are just under 400 issues that are open on that repository, and the community around the project is quite active. A student could take on one of those issues by forking (copying) the repository and attempting a fix, and then create a pull request to have their contribution pulled into the main repository (a pull request is a request you make to the author of the code, to have your changes “pulled” into the main repository). React, Angular, jQuery, Nodejs: the projects that run the internet are all available and being collaboratively built on Github. When contributors post code, others comment and help to make that code better: they teach each other. How many expectations within a Computer Science class could be assessed by students solving authentic problems on important open source repositories. Even if they don’t get a pull request accepted, watching developers contribute to projects is a rich learning experience every student interested in coding should be exposed to.

The title of this blog post is Charity Begins at Home, because I think that we can help promote contributing to important projects by having our students — with the ability to code — contribute back locally in ways that can make our infrastructure within the board stronger. Our students potentially have a role to play to help create apps they can use in their classes. They see first hand the problems they might be able to solve collaboratively by building software. They can help build apps to support their own learning, or to help teach students in elementary. They could solve authentic problems that exist within our organization. There is a thriving Hamilton Software community that we have partnered with through the Hamilton Code Clubs initiative. The mentors who are visiting our elementary schools could help to audit code created by secondary students.  Think about how rich the learning is when students are tasked with solving authentic problems, have an authentic audience for their products, can see them being used, and can iterate on their development through user feedback.

What better way for a fledgling coder to say Hello World.

Broadcast Posts

2016-03-29_21-53-15We are deploying a new functionality on the Commons called Broadcast. The Broadcast box at the bottom right of the post edit page will allow you to take a post and cross-post/duplicate/broadcast the post to another blog.

Historically we have always felt that students should have one main blog, on which the post all of their work. We recognize that classrooms and initiatives set up group blogs for a variety of purposes, but we didn’t want students to have numerous blogs established for one grade or one course that would have one or two posts on them, and then would be abandoned, when one of the key features of blogging is the ongoing portfolio of work it provides for a student to look back on. We have attempted to endorse the idea that students could use categories to properly categorize their work, much like I do on my blog, with topics like technology, pedagogy, and the Commons.  This is fine, but it can make it difficult — particularly in secondary (in elementary we find the teacher is usually responsible for multiple subjects and can just Follow the blog) — for a teacher to locate the posts a student has written for History, and Science, and English, if they are using the blog for multiple courses during the same semester.

Broadcast is our attempt to attend to this. If the English teacher creates a group blog for the course (using the Hub Sync functionality to add their students as Authors), then the students can broadcast their posts to that central blog using the new broadcast function. This provides a central location for students to see the work of their classmates. Currently comments left on the group blog sync to the student’s individual blog. The students can set it up so that the links on on the group blog will redirect back to the parent permalink (back to the student’s blog where the post was initially created.)

We are still crushing some bugs, but would love some classrooms to test out this functionality and either email me or comment below with feedback and commentary.

I’ve Broadcast this post over to my personal blog (so meta).