Web Monetization Community

Cassie Tarakajian for p5.js Editor

Posted on

Web Monetization Grant Public Report #3

Project Update

The granting period is now over, and a lot of work has happened to wrap up this project. We were able to post our Terms of Use and Privacy Policy, as well as follow all other GDPR guidelines. We also hired a designer to create the subscription screens and user flows. We fixed more infrastructure security work.

In the last progress report, I wrote about the challenge of communicating about the subscription model. Since then, I have met with community members and colleagues to obtain support and start a communication plan.

In recent months, the Foundation has received a number of very large donations from a 20th anniversary fundraiser that shifted the urgency of monetizing the p5.js Editor. Along with the rest of the team, I made the decision to delay this project and shift priorities. The grant period allowed me to conduct all of the foundational research necessary for future implementation. Monetization of the Editor, grants, and donations allows for our team to create a sustainable, diversified funding and development model. The biggest thing I learned is how much infrastructure it takes to monetize a web application, and how much it changes the perception of an open source tool.

Progress on objectives

I was able to deploy the Terms of Service (ToS), Privacy Policy (PP), and cookie popup. I followed the document provided by New Media Rights to support the ToS and PP, such as following GDPR guidelines and creating a plan to handle privacy inquiries to the Editor. This process includes a system for making future changes to the ToS and PP in a public way. For this system, I decided to publish the documents to GitHub in a separate repository to allow users to comment on the documents and make pull requests to suggest changes. Unfortunately, I doubt any lawyer would be willing to write in Markdown, so I also made some changes to the word documents New Media Rights sent us, so that they are easily exportable to Markdown. In the future, the full workflow would be (1) a lawyer makes changes to the ToS or PP, (2) these changes are exported to Markdown, (3) the documents are published to GitHub, and then (4) the community is able to offer feedback.

I also worked with a designer to work on the visual interface for the subscription model. This work included the screens for users to sign up and features for a subscription-only tier. The most important thing we talked through was how to explain the subscription to users in the context of other ways to support the p5.js project. Through this discussion, I learned we need to improve how we communicate the p5.js Editor as an open source project that needs support and is supported by a larger non-profit organization.

I ran into some major issues that needed to be addressed, due to some phishing reports I was getting. I added the ability to ban users, which will be useful and related to any threats against our PP/ToS. I also had to ban the rendering of full-screen sketches, which users were abusing in phishing scams. While it is frustrating because I’m aware that some users have good intentions to show their artwork full screen, the p5.js team’s bandwidth and capacity makes it difficult to address the dozens of reports we received.

I also started working on a communication plan for the subscription model. I pulled together writings I wanted to reference and I thought about the ways, big and small, to communicate, such as linking to the Processing Foundation from the Editor, to a blog post on the organization’s Medium. I also started NEW INC, which is an incubator for folks working at the intersection of art and technology. With it, I have access to a community of peers, mentors, workshares, and workshops. I spoke with some of the mentors at NEW INC about how to approach this type of writing as well.

Lastly, circling back to the unprecedented amount of donations the Processing Foundation received this past fall, our organization radically shifting and transitioning into a new infrastructure. Whereas a year ago, I was wondering how we would fund the maintenance and development of the p5.js Editor, now the funds exist to create full-time positions with benefits. I made the decision to halt work on creating a subscription model, but I am open to this project happening in the future. The most successful open-source projects have a diversity of income.

Key activities

  • Deployed the Terms of Use, Privacy Policy, and Cookie popup to production. You can see the pull request and the deployed documents.
  • Created designs for the subscription plan.
  • Created a small system for user moderation, with the ability to ban users.
  • Handled issue where users were using the p5.js Editor in phishing scams.
  • Began NEW INC program.

Communications and marketing

We haven’t communicated about the subscription project in public at all. I have gotten support and feedback on it as part of the NEW INC fellowship.

What’s next?

Because of a recent influx of large donations to the Processing Foundation, we have decided to wait on implementing this project. The reason is given less monetary constraint, there are issues with the p5.js Editor that are more urgent to attend to. Some of these are:

  • Addressing technical debt
  • Documentation
  • Leadership/team changes (burnout is very common for open source maintainers)
  • Access (accessibility and inclusion) features

What community support would benefit your project?

At this point, there is not a need for community support, as the needs of the Processing Foundation have wildly shifted over the past few months.

Discussion (0)