Skip to main content
Category

Blog

An update on how AMP is served at the OpenJS Foundation

By AMP, Blog, Project Update

When the AMP project moved to the OpenJS Foundation in 2019, our technical governance leaders shared a plan to separate the AMP runtime from the Google AMP Cache, and host the AMP runtime infrastructure at the vendor-neutral OpenJS Foundation. OpenJS is happy to report that this complex task of re-architecting the AMP infrastructure is making tremendous progress thanks to input and guidance from the AMP Technical Steering Committee (TSC) and AMP Advisory Committee, as well as thanks to the AMP Project and OpenJS teams for coming together despite the work and life challenges that were sometimes faced during the pandemic.

About AMP

AMP is a multi-stakeholder open source project used across a broad range of organizations to increase web performance. It’s a web component framework with a collection of complementary technologies that help publishers easily create websites that load quickly and predictably on different networks and devices.

Today AMP powers nearly 10 billion web pages worldwide, and is implemented by Google, Microsoft Bing, Pinterest and Pantheon, among others.

An AMP Cache is a cache of validated AMP documents published to the web, which allows the documents to be served more quickly than if they were generated by the original site each time they were displayed. Two of the largest AMP Caches are operated by Google and Microsoft, each of whom use the foundations developed by the AMP open source project to build their own commercial AMP Cache. This is a similar model to how most commercial products are built today with open source projects such as Linux and other JavaScript technologies such as Electron and Node.js.

Understanding how the AMP runtime will be served moving forward

The AMP runtime is a piece of JavaScript technology that a developer can add to their website to be able to use AMP components for building their website. By using AMP components, their pages become eligible to be hosted by an AMP cache. Some websites may choose to host the AMP runtime files themselves, while others may want to rely upon the AMP runtime soon hosted by the OpenJS Foundation to deliver the latest version of the code on demand. Ultimately, the choice is up to the developer. Please note that  documents served from the Microsoft or Google AMP Caches will still download the runtime from the specific AMP Cache itself.

The AMP runtime itself is developed openly and transparently in the AMP Performance Working Group. This part of AMP will not change, as the goal in moving to the OpenJS Foundation was to ensure this work could continue under a vendor-neutral nonprofit, and this is still a high priority. What’s new is that after disentangling the AMP runtime from the Google AMP Cache, the OpenJS Foundation will manage the servers that deliver the AMP runtime files (the download server and the CDN). As planned, the OpenJS Foundation has been involved in the implementation of hosting the CDN and has been spending additional time to fully understand the technical requirements.

Hosting project infrastructure is a core service of our Foundation – it’s one of many ways we help maintainers manage the stability and delivery of their open source projects. The way OpenJS hosts the AMP runtime infrastructure will be very much like how we support the infrastructure for the popular jQuery CDN, which performs a similar function and distributes 2.2 petabytes of jQuery libraries per month. We are working with Cloudflare to host the AMP runtime CDN. OpenJS Foundation projects benefit from the goodwill of Cloudflare’s contribution to open source through its free Cloudflare Enterprise program, in addition to other CDN providers who support other OpenJS communities. 

As an umbrella organization, the OpenJS Foundation has a governance model that gives a strong voice to its projects. Each of the projects are run independently at the direction of their core maintainers or Technical Steering Committees, as is this case with the AMP TSC. At the same time, OpenJS takes on the non-development aspects of the projects, ranging from infrastructure support to marketing, to help our projects grow and get better every day.

We are thrilled to be making this change to help the open source AMP Project continue to grow and diversify its contributors as they all work to make great experiences for the web.

If you have any questions about OpenJS please reach out to me at rginn@openjsf.org, or on our Slack workspaces: OpenJS Foundation or AMP. If you have any AMP Project specific questions please feel free to reach out via GitHub.

Posted by Robin Ginn, Executive Director, OpenJS Foundation

How Open Governance Influences Open Source & Inner Source at GoDaddy

By Blog, OpenJS World

During the OpenJS World, held virtually in June, we heard from many inspiring people involved in all areas of technology. In this keynote series, we will highlight the key points from the keynote videos. We hope to share highlights of the speakers in a way that allows for people to discover what parts of the talk interest them the most.

In a recent Keynote Speech, Charlie Robbins and Jonathan Keslin talked about how Open Governance at GoDaddy’s organizational structure mirrors their communication structure, known as Conway’s law. GoDaddy supports internal groups in an effort to push the decision process to the engineers and content experts. They only use those outside their field when necessary. 

This technique has been successful for GoDaddy (GD). This process went on for a few years before a pattern emerged. Once they were motivated, volunteers stayed engaged because of interest in the mission of their group.

As GoDaddy’s internal and external communities have grown, so did the need for structure and governance. They created GoDaddy {open}. This is GD’s name for its open governance structure, a nexus of technology and community. It is extensible and repeatable and fostered by leadership. GD {open} groups are bodies meant to drive business outcomes or policies. They are formed across disciplines both technical and non-technical. It gives visibility to other parts of the company through shared goals.

Guilds are another form of open governance used at GoDaddy. Guilds are groups of people formed around a specific topic, such as a programming language. Individuals rally around a technical topic, sharing best practices and forming a community. One thing that guilds are not is a group that talks about standards or infrastructure. They are communities that come together to learn and grow. GoDaddy also participates in trade groups such as OpenJS, Domain Name Association, and Node.js. GD open lets them coordinate these across the company. GoDaddy also is an open-sourced supporter, and have many different projects released to open source and communicate these efforts with their engineering blog. GoDaddy doesn’t have all the answers, but they do support them whenever they can. 

Full link here

Broken down by section:

Conway’s Law 0:44

Open Governance for internal groups 1:10

Application of Open GoDaddy 2:35

GoDaddy Open Governance 3:40

Organizational Structure 4:00

Model of GoDaddy open 4:16

Application of Open Governance Groups 4:54

Guilds 5:40

What is a guild? 6:54

GoDaddy Participation 7:24

Open-source Supporter 7:36

GoDaddy External Support in Open Governance 8:16

Take a Trip through JavaScriptLandia

By Blog, JavaScriptLandia, OpenJS World

During the OpenJS World, Jory Burson and Joe Sepi discussed the OpenJS Foundation’s efforts for getting the community involved in projects by creating collaborative spaces

.

Jory Burson, Community Director at the OpenJS Foundation, spoke with Joe Sepi, an Open Source Engineer at IBM. The discussion started with Sepi explaining how the Cross Project Council (CPC) helps open source projects by providing advice, support and multiple avenues for work collaborations. 

The concept of collaboration spaces was created to provide opportunities for people in the ecosystem outside the project or the foundation to get involved. Burson elaborates that this is a way for the whole community to work together. 

Additionally, the Standards Working Group is another active space where people with all levels of experience are welcome to join. One of the goals this year is to develop a set of resources and a website for developers to get involved in standardization. 

Another key program recently launched by the OpenJS Foundation is JavaScript Landia. This is the individual supporter program, and it gives anyone access to online information where you can support different projects, collect badges, and much more.

In conclusion, Burson and Sepi both encourage viewers to join and become involved in the community by joining Slack, accessing Github and visiting openjsf.org/collaborate. They emphasized that the only requirement to be involved is a passion for JavaScript and a desire to help!

Full video here

Broken down by section:

Speaker introduction 0:02

Cross Project Council (CPC) 0:46

How CPC has helped projects 2:51

Collaboration Spaces 7:49

Open Source 10:44

JavaScript Landia 19:17

Conclusion 24:28

Node-RED 2.0, Project Update

By Blog, Node-RED, Project Update

Node-RED, a hosted project at the OpenJS Foundation, recently shipped its latest version, 2.0.

Node-RED logo

In a blog written by Nick O’Leary, the main focus of Node-RED 2.0 is dropping support for old versions of Node.js that are themselves no longer supported which allows the team to make major dependency updates internally.

The new release also includes first versions of the Node-RED Flow Debugger and Linter. These are optional plugins that really step up the developer experience within the project’s editor.

For all details, check out the Node-RED blog and watch Nick outline the release notes in this video.

OpenJS World: Michael Jennings

By Blog, Event, OpenJS World

OpenJS World Keynote: Michael Jennings, Inclusion Strategy at Netflix

During OpenJS World, which was held virtually June 2-3, we heard from many inspiring people involved in all areas of technology. In this keynote series, we will highlight the key points from the keynote videos. We hope to get a highlight of the speakers in a way that allows for people to hone in on the part of the talk that interests them the most.

What is inclusion? Michael Jennings is the Inclusion Strategy Partner at Netflix and utilizes many of the tools created at OpenJS. He talks about creating an inclusion footprint and why it is conducive to businesses. Inclusion is an extension of companies themselves. Companies tend to market, whether unintentionally or intentionally, based on the people in their company. Jennings says that the greatest innovation you can make is to empower people.

Jennifs covers the importance of asking questions, how best to lead to the answers that you want. He talks about built-in biases, not only in an organization but within each member. He also says there is no quick fix, and that inclusion is a journey to undertake. He makes a great analogy about inclusion and bias as a piece of complex art, that is different for each individual. We need to see not just ethnicity, but different demographics and experiences. 

HR is puzzle work. It’s hard to focus on experiences that meld into your project. Be innovative with people, not just technology.

Jennings talks about self-reflection being paramount to the process. Who do you work well with, who do you not work well with, who do you dislike, who can you not stand? When someone is different at the table, what is your instinct to do? How do you react and why? These are all questions he brings up as being important. 

Ultimately, inclusion is an opportunity for all, not just for our leaders.

Link to full OpenJS World video here

Inclusion footprint 0:54

Asking uncomfortable questions 1:50

What is inclusion? 3:45

Think about yourself 5:31

Dealing with biases 7:11

Innovative with spaces 7:59

Things conducive to self-work 8:35

All of our opportunities, not just leaders 10:20

Sign up for updates on OpenJS Word 2022 happening June 7 and 8 in Austin, TX

Node.js Certified Developer Spotlight: Rahul Kumar Saini

By Blog, Event, OpenJS World

We recently interviewed Rahul Kumar Saini, software engineer at Successive Technologies, about his experience taking the OpenJS Foundation Node.js Application Developer certification. Here’s what we learned.

Why get certified through OpenJS?

The OpenJS Foundation is a well-reputed organization among the JavaScript community, with a history of many successful projects that has a large impact on the javascript echo system. The certification is provided in collaboration with Linux Foundation that encourages me to get certified with OpenJS.

How was the test-taking experience? Compared to vendor-specific certifications, how is a vendor-neutral test different?

The test-taking experience is quite good, the examination platform was user-friendly and easy to use. The pattern of the exam was problem-based not just objective type. In my opinion, vendor-neutral tests add extra trust and security in comparison to vendor-specific certification.

How has the certification helped or added value for you?

It boosts my knowledge since the curriculum of the exam was covering all Node.js core modules/APIs in detail. It helps me to explore the best practices and standards.

What are your career goals and how do you think certification can help in reaching them?

I want to get expertise in Node.js and Javascript ecosystems, and I think this certification is a milestone toward this journey.

Anything else to add?

I like the problem-based exam pattern that also tests your abilities in real-life scenarios instead of just multiple-type objective questions.

Congrats to Rahul for this great accomplishment!

If you are considering taking a Node.js Training or certification exam, now is a great time! Now, through July 9th, you can save 60% on all Node.js offerings with code NODE60. Head over to the Linux Foundation Training and Certification site to snag these savings. 

OpenJS World Keynote Panel: Getting Hired

By Blog, Event, OpenJS World

During OpenJS World, which was held virtually June 2-3, we heard from many inspiring people involved in all areas of technology. In this keynote series, we will highlight the key points from the keynote videos. We hope to get a highlight of the speakers in a way that allows for people to hone in on the part of the talk that interests them the most.

During the OpenJS World Keynote Panel on Getting Hired, Scott Hanselman spoke to leaders in the tech world to hear their insights on best practices for getting hired, especially during a pandemic, for entry-level job seekers and people of diverse backgrounds.

Hanselman spoke to Zainab Ebrahimi, CEO at Flourish, Jerome Hardaway, Executive Developer of Vets Who Code, and Saron Yitbek, Founder of Codenubi. 

Haselman started the discussion by highlighting the impact the pandemic has had on employment. Ebrahimi dove into this topic by sharing an example of how difficult it has gotten for entry-level job seekers to get hired. She explained how she recently saw a job posting for an entry-level position asking for five years of working experience. Yitbek mentioned how a shift from calling the position junior developer to early career developer shows that there is hope and that the industry is slowly becoming more open-minded in the skill levels they are willing to accept. 

Hardaway talked about the importance of upscaling your skillset. The conversation discussed the importance of focusing and investing time in mastering a specific skill. Yitbarek talked about how people often find themselves bouncing around from learning one skill to another; she ties this in with a Hardaway comment about the importance of learning how to plan and be organized.

In their closing thoughts, all the speakers agreed that the barriers to entry for entry level job seekers and for people of diverse backgrounds are high. They all focused on how the community needs to accept people for just being themselves, take them as a whole, allow room for learning from mistakes and invest in being patient and teaching skills. While acknowledging that baby steps are being taken to make it a more welcoming environment, they recognized that a lot more needs to be done to address this wide set of issues.

Full video here

Broken down by section:

Panel introduction 0:24

Flourish and coaching 1:43

Saron talks about helping early-career jobs 2:57

Jerome talks about upscaling the skillset 4:18

Stack you need to create a webpage 8:05

Importance of focusing 10:06

A new way of studying and planning 11:25

Diversity and importance of belonging 15:36

How to create a more welcoming environment 19:03

Does Open source matter on the resume? 23:36

Closing thoughts and call to action 25:19

Sign up for updates on OpenJS Word 2022 happening June 7 and 8 in Austin, TX

OpenJS World: A “Fast” Introduction to Fastify

By Blog, Event, Fastify, OpenJS World

During OpenJS World, which was held virtually in June 2021, we heard from many inspiring people involved in all areas of technology, including Matteo Collina from Fastify. We hope to highlight speakers in a way that allows for people to hone in on the part of the talk that interests them the most.

Open source projects are as good as their communities. Matteo Collina from NearForm provided the OpenJS World audience a great explainer on Fastify. Fastify is a web framework for Node.js. It is open governance, community-first, and shared ownership. They want their users to share, contribute to the project. There is a shared effort to spread the effort among the companies using it, which is key. They have good and lofty technical principles. They have a similar speed to Node.js core, and faster than other methods.

Fastify runs through two different types of plugins, Core and ecosystem. Core is supported by organizations and ecosystem is supported by members of the community. The key difference is that Core plugins work on everything, while ecosystem plugins work on individual problems. They improve performance so much because they implement a horizontal model, where you segregate the complexity into smaller parts. The system is a step towards microservices, as well as a move away from monolith systems.

Matteo goes into the internal parts, and how plugins allow for reusability and encapsulation. This is the part that increases speed. He also talks about a predefined lifecycle, so that only the parts that need to be executed are. These plugins also allow for separation and allow for better organization. There is also out-of-the-box serialization as well as validation through Avj and internal testing.

Full Video here

Broken down by section

Twitter handle 0:30

Importance of community 1:36

What is fastify? 2:45

Core Values 3:40

Why a shared effot? 5:05

Techincal principles of Fastify 6:17

How fast is Fastify? 7:58

Mercurius graphql adapter 9:28

Core vs Exosystem plugins 9:39

Target architecture 10:50

Internals 13:02

Plugin explained 14:06

Request lifecycle and recommended project structure 15:35

Plugin separation visualized 16:35

Serilaization 17:57

Validation and testing 18:24

Live coding 19:42

OpenJS World: Glamorous JavaScript

By Blog, Event, OpenJS World

During the OpenJS World open Keynote discussion, Anna Lytical deconstructs the world around them to create entertaining and educational coding tutorials. Anna Lytical is “a sickeningly entertaining and educational” drag queen specializing in technical education content creation. 

In this conversation, Anna highlights the parallels between a drag makeup look and coding. For example, in code the cost of importing a package could make your applications slower, larger or more confusing to contribute. While in make-up, it can take a lot of physical space to store. Anna uses a diagram of an eye to illustrate the grid and they use this diagram to help make it easier to understand code. In order to explain how the application of purple eyeshadow on the crease can be converted into a more polished look, they help to elucidate this by creating a new function. In this, they take two areas in the function to be their input, and they’ll get their color by adding new strings. The coding on the right side of the video directly corresponds with all the steps needed to create this make-up look.

Additionally, Anna explains what the Learning Ladder is and how they view the path of someone becoming a great engineer as a ladder. They talk about how sometimes the steps seem clear but the rungs seem to be too far apart. Sometimes people don’t always climb the standard ladder to a Computer Science career because they sometimes don’t have all the knowledge needed to take those steps. Anna explains that this is where their content comes in as it helps to bridge those gaps. 

Anna takes something people know, whether it is make-up, drag or JavaScript code and they combine it with something new by drawing connections and making it relatable to the viewers and their experiences. Anna nicely demonstrates how coding can be just as creative as make-up can be.

OpenJS World Full Video Here

Broken down by section:

Introduction 0:01

Understanding Drag 0:33

Cost of importing a package 2:58

The eye 3:18

Completed Make-up look and code 8:03

The Learning Ladder 9:23

Anna Lytical Courses 10:30

Closing comments 12:42

Thank you Anna Lytical for showing us the creative side of coding in a super entertaining way!

OpenJS World: The Roaring Twenties for JavaScript

By Blog, Event, OpenJS World

OpenJS World Keynote Series: The Roaring Twenties for JavaScript

During the OpenJS World Welcome Keynote, Robin Bender Ginn, Executive Director of the OpenJS Foundation, and Todd Moore, Vice President of Open Technology and Developer Advocacy at IBM, discussed JavaScript and the importance of diversity, the effect of the pandemic on the JavaScript ecosystem and gave updates on some of the many the projects hosted by the OpenJS Foundation

Ginn started the Keynote discussion by drawing a parallel to the roaring 1920’s to the 2020’s and highlighted how both were dramatic decades of change. During the conversation, Ginn and Moore shed light on how the presence of systemic bias in the tech industry can be a hindrance in the growth of JavaScript. Both the keynote speakers were hopeful that this bias could be overcome in the years to come. They highlighted OpenJS’ efforts to create a diverse and varied stakeholder community, while also recognizing there is a long way to go and steps like putting more structure around DEI programs helps bridge that gap.

The on-going pandemic has led to a sharp rise in online commerce and the digital delivery of healthcare and education. JavaScript was the key tool behind this. For example, Netflix, an end-user and contributor to the Node.js project, saw a heavier reliance on its IT infrastructure during the pandemic.

In their closing thoughts, both the speakers agreed that Node.js was key to many companies’ growth because its maintainers ensure that it is neutral and diverse in nature. Ginn and Moore also reiterated the importance of the role open-source plays in speeding up innovation and acts as a force for good in global economies. 

OpenJS World Welcome Keynote Full video here
Broken down by section:
Member introduction 0:04
Systemic bias in the tech industry 2:19
Members 3:08
Pandemic and its effect on the 3:51
A closer look at Netflix’s Open Source Software 4:09
Milestones from OpenJS Project Communities 5:06
Project Graduation 7:01
Collaboration Network 8:31
NodeJS Certification Program 10:43
New Individual Supporter Program 11:33
Neutrality and the role foundations play 12:26
Leading Standard Development Orgs 15:00
Why is IBM contributing to the OpenJS Foundation 16:47
Closing thoughts and call to action 17:06