Hi, a legal question. I have created a Google Docs...
# random
i
Hi, a legal question. I have created a Google Docs script that adds an nf-core themed progress bar to presentations. I would like to make it available to others through the Google Docs extension store. I want to use the name "nf-core progress bar". Is this use of the name allowed? Could I also use the logo?
πŸ‘€ 1
j
<!subteam^S016E36N7TQ>
Do you have a screenshot @Igor Trujnara? I wanna see cause that sounds awesome😬
i
This is an example slide, I can prove it is automatically generated
πŸŽ‰ 4
😍 4
😱 4
m
shut up take my money
i
I can give it to you for a fair price of zero
πŸ’Έ 2
m
Add two 0 to it, and you got a deal
i
Sounds like a deal to me
🀝 1
f
I would even pay double that!
j
I think @Phil Ewels likely is closest to legal stuff regarding the name etc, but could always stick 'unofficlal' in the title if you can't wait. But I love it. Only suggestion is to make the the stroke around the station circles a little thicker (but that's me being pedantic)
i
If anyone wants beta access, I will need your Google emails
j
Gimme gimme gimme
r
must have
j
let me in
n
nicolas.vannieuwkerke@gmail.com I was planning on making a new slidedeck tomorrow so I'll give it a go there πŸ˜›
m
please πŸ™‚
i
After an uneven battle against documentation, you should all have it. To use it, you need to click the link in your email and then in the project select Deploy > Test deployments > Install. Let me know if it works as I have zero experience with Google Workspace extensions.
πŸŽ‰ 2
g
Sounds like we’re adopting it as an official nf-core thing πŸ˜„
πŸ˜† 1
i
There seem to be some issues with using it, I'll let you know when it works
p
Love it! πŸ™ŒπŸ»
No problems legal wise.
party parrot 1
j
(legal wise I meant more branding ownership etc btw, not legal legal)
πŸ‘πŸ» 1
m
😞
i
No solution to Marcel's issue (sorry), but figured out how to test it correctly. Follow this instruction and it should hopefully work.
I have verified this works on a random old presentation, so unless Google decides to break things it should do its job now
m
I ran into that error both in Safari and Chrome, just to be clear 😞
i
Looks like publishing those extensions is pretty annoying (you even have to have a published ToS and privacy policy) so I will leave it in testing for the time being and work on this when I have a bit more time
c
Super cool 🀩
j
Yeah instructions for the test doens't work for me it seems 😞 I press 'Save test' but doesnnothing saves. I just see the 'Meksyk' test...
I get the same error when I copy over like Marcel too sadly
i
I have found some mentions of this error online, but unfortunately no signs of a universal solution. Someone mentioned using a private browser window, but that is just a random idea that I cannot verify.
😒 1