A (late) Introduction to the LifterLMS Working Group

Saurabh had an idea

He approached the team sometime in the fall. He wanted us to start a LifterLMS Working Group.

In software development working groups are common. The W3C has several dozen groups which regularly gather to discuss and work on various internet specifications. Without these groups and specifications, we would not have many of the tools and utilities we use daily to power our websites.

WordPress itself doesn’t call them working groups, but if you point your browser to make.wordpress.org you can see another dozen or so teams working on various areas of the WordPress project.

A free and open-source project with a growing community should have it’s own working group, but we don’t.

We’ve always planned features with the interest of the user in the forefront of our minds. We gather feedback and diligently record issues and feature requests. We pivot our focus and goals based on these comments and questions we hear in support conversations and social media posts.

But the issue Saurabh’s idea attempts to resolve is that we did not have an official forum or platform to facilitate the co-creation of LifterLMS. We, the core team, have always remained solely responsible for the actions taken following or as a result of these conversations.

Saurabh’s idea was to gather a new group of stakeholders and meet to organize our collective thoughts about the successes and shortcomings of the project. His idea was to create the platform the project has been lacking.

The First Meeting

In January we organized the first meeting of this working group. We hand-selected a small group of users and contributors. We decided to start with quizzes as our first discussion topic. We checked our issue and request trackers and found when organized by category, quizzes, by far, had the highest number of feature requests.

I had intentions to distill the learnings of this first working group into some ground-breaking document and publish it here on the blog.

I had intentions that something so powerful would be said that it would result somehow instantly in a reconstructed and superior quiz system.

We discussed these things, and we (the core team) recorded more notes and more feedback. A lot of what we talked about has been written down and recorded by us multiple times over. New points were brought to our attention, and some of the issues we’re aware of were given new context.

There’s more work for our team to do on quizzes, and as we approach the second meeting of the working group we have new things to consider.

Improving the Working Group

As we look forward to the next session of the group, we hope to work together to find ways to encourage greater participation from members of the group.

Talk and discussion is not unimportant, but it’s only a small part of what we’ve learned we need from this group. We not only need members with great ideas and strong opinions, we need members who are willing to do work.

The most obvious work is code, but we don’t need to write more code*, we need to draft and create documentation, architectural models, feature concepts, roadmaps, and design specifications.

In simple terms: we need to determine, concretely, the things that LifterLMS needs to do. We need to write these things down and commit to them.

After these concepts and ideas are solidified, then I will work with our core team and contributors to turn these into deployable and useable features.

If we look to the work of the working groups of the W3C, we’ll see that these groups do not write code. They write specifications. These groups may have developers in them but the primary purpose of these groups is to create and design these specifications. The browser vendors and developers working on Chromium or Blink or Mozilla will then interpret these specifications and create the browsers we use.

Moving forward, the LifterLMS Working Group will be creating these specifications, and you’re invited to participate.

* If you’re a developer, we do need to write more code, please join us, please contribute.

Session 2, March 2019: Certificates

On March, 20, 2019 at 9:00am PST we’ll gather for the second session of the LifterLMS Working Group, and we’ll be discussing certificates.

Our choice for this session comes after realizing that our first topic, quizzes, was perhaps too broad a topic. Certificates, while arguably as important as quizzes, we’re hoping will prove to be a topic that’s more digestible in a short period of time.

Bring your ideas, and be prepared to start creating LifterLMS with us.

See the events calendar for meeting details.

1 thought on “A (late) Introduction to the LifterLMS Working Group”

  1. OK, I am in… this is a good idea!

    Excited for the meeting in March because Certificates need a lot of work from the native LifterLMS format and I have personally done a lot to enhance and improve Certificates, including adding many more Merge Codes for Cerificates, changing size up to full A4 Portrait format, adapting certain background issues… and generally helping people out on Lifter’s Facebook Page who struggle with Certificate issues.

    Generally, I think the important issues around Certificates of LifterLMS revolve around saving in HTML format in stead of in PDF format, size and Layout options or limitations and the adaptability of Merge Elements.

Leave a Comment

Your email address will not be published. Required fields are marked *