Treebeard project using Repo2Docker

Special Topics
1

Hi Community/Admins,

I’ve been building a continuous integration product which uses repo2docker to containerise/build projects and would like permission to use your branding when discussing our product.

It’s been a lot of fun working with r2d and a few weeks ago I made the first of hopefully many PRs to contribute back to the project.

Over the next few weeks I’d like to

  1. Open treebeard to a wider audience which involves distributing docs, potentially directing users to information about the config files r2d works with
  2. Distribute some marketing material for our project, calling out some of the great open source projects we are built on (including r2d) to alleviate concerns of vendor lock in
  3. Open source our core, including CLI, buildtime, and runtime functionality for running a CI service for scientific applications

keen to discuss here or over email on alex@treebeard.io

Big thanks

2

Hey,

while I can’t give you a definitive answer: all the code (and for better or worse documentation) is covered by https://github.com/jupyter/repo2docker/blob/070e4a9c80f7f00a1f224eeee317c1558e8e7b9a/LICENSE which explains the rights and obligations (modifying, redistribution, endorsement, including the copyright and license in derived copyrights, etc.)

I think (but you’d need a lawyer) that using the name repo2docker and its logo to refer to repo2docker itself is also unproblematic. For example “Our service is built on repo2docker.” or “Configuration files are compatible with repo2docker.”

Does this answer your questions?

3

Interesting! In case others are curious, I found this website: https://treebeard.io/ I guess that is correct @alex-treebeard?

My understanding is that the copyright to the “Jupyter” name is held by NumFocus, but I don’t know whether other things like repo2docker fall under the same category. Either way, I assume it is OK because tons of people use the word “Jupyter” in their products (in the way that tim has described above).

edit: here’s the jupyter trademarks guidelines: https://github.com/jupyter/governance/blob/f36f46e88ebf09467cb31c7b51d90859aaed65e7/trademarks.md

It would also be awesome to see some upstream improvements to repo2docker! :slight_smile:

4

Thanks a lot for the clarification @betatim and @choldgraf just wanted to double check!

Apologies for the slow reply, we are indeed treebeard.io, it’s probs better to check out the repo though https://github.com/treebeardtech/treebeard

Right now the service is part open source, part managed but we’re working on making it possible self-host.

Edit: If you’re reading this a glance at this would be appreciated https://github.com/jupyter/repo2docker/pull/857

1 Like