#Trademark

1 messages · Page 1 of 1 (latest)

lost loom
#

cc @subtle sun

It depends on what you call it 😉

#

But I am excited to hear more

subtle sun
#

Happy to chat more about this! Feel free to DM 🙏

gray radish
#

obv, you would call it blade. 😛

empty egret
#

@harsh wedge like Lev said:

  1. License: the Dagger Engine is open source, so there are no restrictions in how you use the code. We appreciate contributions, and love learning about how you use it, but you are legally not required to contribute or share anything. We have no plans to change that in the future.

  2. Trademark: if you use the Dagger name or logo in association with your product, there are rules you need to follow. The guidelines are published on our website, and in doubt you can always contact us to chat about it live. It's nothing crazy. Mostly we want to make sure that if you see the "Dagger" label on a product, it's going to give you the real Dagger experience. Not a modified or crippled one. And we also want to avoid confusion about who made the product. Our guideline is pretty similar to the Red Hat guideline, for example.

harsh wedge
#

Thanks folks! We are developing a tool that extends the capabilities of the native tools to develop apps for Android and Apple platforms, and we’d like to offer a CI solution as part of that. I thought about using Dagger pipelines for that instead of coming up with a new language for declaring the pipelines, and wanted to make sure that wouldn’t be in conflict with anything.

#

As part of that I want to develop the Swift and Kotlin SDKs for Dagger so that those communities can define the pipelines in the languages are familiar with.

#

In the case of Swift, I’d need Dagger to support running commands directly in the host because developers usually run tools like xcodebuild that are not available on Linux