From c403812389a0bcf921f676bd3afc7a09d363608d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Mon, 31 Jul 2023 10:26:30 +0200 Subject: [PATCH 01/13] edit manifest.mdx - fix typo in caption for consistency - edit filename (URL) for SEO --- .../content/blog/{the-documenso-manifest.mdx => manifest.mdx} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename apps/marketing/content/blog/{the-documenso-manifest.mdx => manifest.mdx} (95%) diff --git a/apps/marketing/content/blog/the-documenso-manifest.mdx b/apps/marketing/content/blog/manifest.mdx similarity index 95% rename from apps/marketing/content/blog/the-documenso-manifest.mdx rename to apps/marketing/content/blog/manifest.mdx index 8cace576d..899bdd26e 100644 --- a/apps/marketing/content/blog/the-documenso-manifest.mdx +++ b/apps/marketing/content/blog/manifest.mdx @@ -18,7 +18,7 @@ tags: />
- Documenso — The DocuSign Open Source Alternative. + Documenso — The Open Source DocuSign Alternative.
From 0bbaa640808ad7ee296413b820f480c1b1bd0213 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Mon, 31 Jul 2023 10:39:05 +0200 Subject: [PATCH 02/13] edit announcing-documenso.mdx - fix typo for consistency in tone and voice - edit filename for SEO --- ... announcing-open-source-docusign-alternative.mdx} | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) rename apps/marketing/content/blog/{announcing-documenso.mdx => announcing-open-source-docusign-alternative.mdx} (65%) diff --git a/apps/marketing/content/blog/announcing-documenso.mdx b/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx similarity index 65% rename from apps/marketing/content/blog/announcing-documenso.mdx rename to apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx index 351690663..65bec3166 100644 --- a/apps/marketing/content/blog/announcing-documenso.mdx +++ b/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx @@ -17,20 +17,20 @@ tags: alt="Documenso announcement blog banner" /> -
Documenso — The DocuSign Open Source Alternative.
+
Documenso — The Open Source DocuSign Alternative.
## TL; DR; -I am launching an open-source document signing tool because trust-based products should be built on openness. The first release will be in 2023. Sign up at documenso.com and get on board. +I'm launching an open source document signing tool because trust-based products should be built on openness. The first release will be in 2023. Sign up at documenso.com and get on board. ## Let’s build the world’s most trusted document-signing tool. -Today I am excited to announce my new Project Documenso. Documenso is an open-source document signing tool you can host yourself and freely build upon because it is, you know, open-source. Before I get more into the details of what and when will be launched I want to take a moment and talk about why. +Today I'm excited to announce my new project Documenso. Documenso is an open source document signing tool you can host yourself and freely build upon because it's, you know, open source. Before I get more into the details of what and when will be launched I want to take a moment and talk about why. ## Digital signing is great -Signing Documents digitally has countless benefits: Less struggle with printing, less wasting paper, faster request delivery, easier changes, easier coordination of people far away, verifiable document integrity, and verifiable signer identity (this is a vast topic, will write more on soon), easier storage and search of signed documents, the list goes on. Digital Signatures take something very old and very trusted like personally signing documents into the digital space, adding the benefits listed above. It also introduces a new party to every signing transaction, the signing tool providers. What was peer to peer transaction before, now goes through an intermediary. While this is not a problem in itself, it should make us think about how we want these providers of trust to work. +Signing Documents digitally has countless benefits: Less struggle with printing, less wasting paper, faster request delivery, easier changes, easier coordination of people far away, verifiable document integrity, and verifiable signer identity (this is a vast topic, will write more on soon), easier storage and search of signed documents, the list goes on. Digital Signatures take something very old and very trusted like personally signing documents into the digital space, adding the benefits listed above. It also introduces a new party to every signing transaction, the signing tool providers. What was peer to peer transaction before, now goes through an intermediary. While this isn't a problem in itself, it should make us think about how we want these providers of trust to work. ## How do we build trusted systems? @@ -38,11 +38,11 @@ While doing research for Documenso I came upon a quote that expresses the curren > Document signing is NOT a technical problem. [Editor’s Note: Because it was solved technically a long time ago] It’s a legal acceptance problem — and everyone KNOWS DocuSign and friends and understands how they’re admissible. Anything else would have to compete with that and people would be suspicious of it for a long time. -While this may sound like a hurdle at first, it immediately gave me a sense of validation for a more open approach to signing. People will and should be suspicious of their tools and demand a high bar when it comes to trust. And the way to earn this trust is by being open. Trusted tools should be the result of thoughtful discussion and reviews. They should be the result of the needs and will of its community. They should be transparent, adaptable, and empowering while using. Open-Source embodies these values very well for software, which makes it a perfect fit for this space and creating a high-trust tool. +While this may sound like a hurdle at first, it immediately gave me a sense of validation for a more open approach to signing. People will and should be suspicious of their tools and demand a high bar when it comes to trust. And the way to earn this trust is by being open. Trusted tools should be the result of thoughtful discussion and reviews. They should be the result of the needs and will of its community. They should be transparent, adaptable, and empowering while using. Open source embodies these values very well for software, which makes it a perfect fit for this space and creating a high-trust tool. ## Next Steps -So, what can you expect from here on out? I have started to build Documenso 0.1 which is scheduled to release in “early” 2023. If you are interested in helping make this happen, let me know via hi@documenso.com. Getting working code into the hands of the perspective Documenso community is currently the #1 goal. Other than that I will be releasing several articles about document signing and what something like Documenso should look like, in my humble opinion. So stay tuned! +So, what can you expect from here on out? I've started to build Documenso 0.1 which is scheduled to release in “early” 2023. If you're interested in helping make this happen, let me know via `hi@documenso.com`. Getting working code into the hands of the perspective Documenso community is currently the #1 goal. Other than that I'll be releasing several articles about document signing and what something like Documenso should look like, in my humble opinion. So stay tuned! If you think Documenso is worthy of support, please share documenso.com with anyone interested, and sign up to be among the first to try out version 0.1 as soon as it launches. From 817569a333365763d79d627f276da28b157aaea8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Mon, 31 Jul 2023 11:26:43 +0200 Subject: [PATCH 03/13] fix typo --- .../blog/announcing-open-source-docusign-alternative.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx b/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx index 65bec3166..37e7901c9 100644 --- a/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx +++ b/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx @@ -38,7 +38,7 @@ While doing research for Documenso I came upon a quote that expresses the curren > Document signing is NOT a technical problem. [Editor’s Note: Because it was solved technically a long time ago] It’s a legal acceptance problem — and everyone KNOWS DocuSign and friends and understands how they’re admissible. Anything else would have to compete with that and people would be suspicious of it for a long time. -While this may sound like a hurdle at first, it immediately gave me a sense of validation for a more open approach to signing. People will and should be suspicious of their tools and demand a high bar when it comes to trust. And the way to earn this trust is by being open. Trusted tools should be the result of thoughtful discussion and reviews. They should be the result of the needs and will of its community. They should be transparent, adaptable, and empowering while using. Open source embodies these values very well for software, which makes it a perfect fit for this space and creating a high-trust tool. +While this may sound like a hurdle at first, it immediately gave me a sense of validation for a more open approach to signing. People will and should be suspicious of their tools and demand a high bar when it comes to trust. And the way to earn this trust is by being open. Trusted tools should be the result of thoughtful discussion and reviews. They should be the result of the needs and will of its community. They should be transparent, adaptable, and empowering while using. Open Source embodies these values very well for software, which makes it a perfect fit for this space and creating a high-trust tool. ## Next Steps From 3cdfde5e0f643b0c8d4cf5f83190fc83d8844030 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Wed, 2 Aug 2023 09:07:34 +0200 Subject: [PATCH 04/13] fix mailto --- .../blog/announcing-open-source-docusign-alternative.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx b/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx index 37e7901c9..73143277f 100644 --- a/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx +++ b/apps/marketing/content/blog/announcing-open-source-docusign-alternative.mdx @@ -42,7 +42,7 @@ While this may sound like a hurdle at first, it immediately gave me a sense of v ## Next Steps -So, what can you expect from here on out? I've started to build Documenso 0.1 which is scheduled to release in “early” 2023. If you're interested in helping make this happen, let me know via `hi@documenso.com`. Getting working code into the hands of the perspective Documenso community is currently the #1 goal. Other than that I'll be releasing several articles about document signing and what something like Documenso should look like, in my humble opinion. So stay tuned! +So, what can you expect from here on out? I've started to build Documenso 0.1 which is scheduled to release in “early” 2023. If you're interested in helping make this happen, let me know via [hi@documenso.com](mailto:hi@documenso.com). Getting working code into the hands of the perspective Documenso community is currently the #1 goal. Other than that I'll be releasing several articles about document signing and what something like Documenso should look like, in my humble opinion. So stay tuned! If you think Documenso is worthy of support, please share documenso.com with anyone interested, and sign up to be among the first to try out version 0.1 as soon as it launches. From 547ed337a6eb21d8ddac8cdf9cceddc2112f746e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Wed, 2 Aug 2023 10:57:29 +0200 Subject: [PATCH 05/13] Add profile picture: Flo --- apps/marketing/public/blog/blog-author-flo.jpeg | Bin 0 -> 2651 bytes 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 apps/marketing/public/blog/blog-author-flo.jpeg diff --git a/apps/marketing/public/blog/blog-author-flo.jpeg b/apps/marketing/public/blog/blog-author-flo.jpeg new file mode 100644 index 0000000000000000000000000000000000000000..a1e84fc83580fbffef68241bb6157dc2aa1021a0 GIT binary patch literal 2651 zcmbV~doi#Q39)SN$d?569wf6(aKYFW;KL?l`^Cz7nMfj6KF@}0S111M; z?V(%K1@=R$|B#Yg#gzVZ;5l?ERy1e!+rb!qJ%AJeya8_rr~(KfK?oA$zXX&8uYiF+ z>_?j*fI<)`Oc*XAiVzbNup|K?5CRc`LSV41Yrts1IRHh%w(r!p6qa&430Db|Hi*mk zT}1WZvj&;tU0>A_{8MY^!&o&((=mcx3%>xF2R5Pi6w}ClKlr4 zQotnyg+ie4EiO=qyakSg!glHlZ?|-WpA3^yF^Ch9KA7?Qvj$OB!{c9Ne8RgBvTE3m z>hoJ@Kgj+&uq*!;+23IQa18>#03yP|aABAT91a&16+wtg|0FIZCN95SN#pig?Al$%l5#$z5z~4`hhv>c ziu7XAS3ZC`VezI?{LsXBD=mETc)F8=wKauERx1s+Wn4d4{ywZCZ8(RJtv04i1zitm<8KTRx%V_}NG1z!){b!pR}LaUTa=(AxK5{@49p zfl)y*qSc3D~^dd?1zqpRyA_J4;k=%FS8c)V5JEmB=FqAG3riU2|I5aJ~7> zkiF{SDj5(}G7LE^)lRC}79H(svf1%C>KjntZ3#W2LM5xy(G!V0qG9_t zs8SlYIMcpM>Fnfh5>96=hj`TD5h}lHoBPI)k$lX2&th5S%3Aqe?|+J(@|cEC_0VNjKgro zB8X+KQnDP=2^mpl;OL#~Pw6ll-Q++Q1RblYle5t@z^s*>i3s$PyZz>agrP$iBA17_ zQn`vwS#3Vsc3${a!~__pAhpySc3~3Q(ny)t;W za_0C*LPl!e#vJNmyMe+&v5Kg;lTJ^HHJCepNA}PHZb%)HPv0?>ePivZ>sb6 z;jCPJZC|tDz2OS(FP32rI+OL$;7C?xGB!2OXY%I}ol#JsB_h_mapr#Tq6^EOYr9@xS!ESH z#DNiD%4{xDEY}RZ;Y?3PDxT|h0*=OHd7lH=M-`o?gB^-;I zde(B8-~9nA7d{=v?Jb%_&X(!Ud7XTSvCmtQnTm3(zS*fG`@BSz=J{yRD23(M6`+g% zwYjpA`v_lQ%4ljpX=F>@>AhVDZ`x}xtunsurkZjYQMQ8Xexc7`Kk<0#@{Fb$+fH

9ckeN!avMQ}E&-hD4G z9Gb4(lhUE74XX;l$4aGtuQ{{tX*e_7SDfduPH^sanRVVld0#Q;iF2q79bbAm#5;X$ zBPud~+IUB}mz9upvd|~rdKryg-jWiFbd;Ik{x+TiU4S18dXlDnv5i@7v#m*iGi#x3 zObSxO#TOk#9lOJB$JBQ`C|FJyUg)OSPTa-U1<1)Y&pwnigTf)ow;ZB_7xo`u6lkl3 zwhx!yqZG;}vAp`(&IMHEz|PnFp7e$R)L?_`<4ZZD8mJC#eq5OoWAx5}w(s1jwRcC$ zVH2l25Ud?JY*nLvJT=Kw%f9tCuQp&?PwzYWQFc;#D1>^&W5yrjntSX)jM^VCf4_(q zO|1OHj}^FZD=mi_J92VjoYU1@7HsGX{REbbydXOpA$CefPRUN`x3u@fI8@N(o0j+T zWhQ##A4haIy_x4>nQi`ArH9#}X!H`}kxgXJhu1;17q<2FRO#~pQwDxy+EyfKw;hKa z@7T)dwd%<$$sHLTyWywXswf?WNFsRJj5!CsqAr@vY3+P6mEl3#NM2NS8u}g?wKvHv z>sgcJHhls^#Gk8K?*kUZa}K`7UFQ)$huWhNA%^yIj#bVVbdXhqE>BXL5ofr5ippx3 za;spHg?RB>)e@Dx>94<%9;%$j5xnwaFP1OMhwl74>Ip>dD@(9I+H>4 z&ODkz52l~VGS)NGK^1cQ2M2s!)Lkum_0XMrQgq- z-ABMvsik`NZ0v{S)~Xk%11;8N@d;`f1o&Aq2-oHQ^~ek7*y;G{i~;VYl2@~K*3qIC zmVamw5+yE2RgzAM7q;sJwxx~ItaOojWsL@iD)amQ4V-wI2mk;8 literal 0 HcmV?d00001 From 90eb54f76887925526e633e62935f38ec7509536 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Wed, 2 Aug 2023 11:11:29 +0200 Subject: [PATCH 06/13] Add blog post: Switching to Discord --- .../blog/switching-from-slack-to-discord | 135 ++++++++++++++++++ 1 file changed, 135 insertions(+) create mode 100644 apps/marketing/content/blog/switching-from-slack-to-discord diff --git a/apps/marketing/content/blog/switching-from-slack-to-discord b/apps/marketing/content/blog/switching-from-slack-to-discord new file mode 100644 index 000000000..fe2fc8379 --- /dev/null +++ b/apps/marketing/content/blog/switching-from-slack-to-discord @@ -0,0 +1,135 @@ +--- +title: Switching to Discord +description: Launching an open-source document signing tool because trusted-based products should be built on openness. The first release will be in 2023. Sign up at documenso.com to be on board. +authorName: 'Flo Merian' +authorImage: '/blog/blog-author-flo.jpeg' +authorRole: 'Go-to-market' +date: 2023-08-02 +tags: + - Announcement + - Community +--- + +We’re switching to Discord. + +Documenso is an open-source DocuSign alternative, built with community and transparency in mind. + +So, when we started working on the project, we quickly set up a Slack workspace to start engaging with community members. + +As the community grows (reached 2K stars on GitHub and 100 community members on Slack), we felt the need to set up a more community-friendly environment. + +The Documenso team is growing, too. [Lucas joined Timur](https://twitter.com/ElTimuro/status/1648608988391514112), then [Ephraim](https://twitter.com/documenso/status/1662418374243041280) and [David](https://github.com/dguyen) recently joined the journey. We want to stay in touch with the community as much as possible and avoid context-switching to focus on work, support, and fun. + +We’re an open-source project and focus on building a great developer experience. So, when we thought of a Slack replacement, community- and developer-friendly, Discord was an obvious choice — not to mention that it would help us keep up with [OSS friends](https://documen.so/oss), too. + +So, we’re switching all conversations, team- and community-wide, to Discord. + +In this post, we won’t debate *why* we’re switching — Slack vs. Discord is a long-lasting debate with pros and cons, and fans on both sides. There are great [stories](https://blog.meilisearch.com/from-slack-to-discord-our-migration/) and [threads](https://twitter.com/McPizza0/status/1655519558600470528) on the topic. We just don’t want to write yet another story here. + +Instead, we’ll focus on *how* we plan to make the switch. + +## ## Who is this story for? + +First, we wrote this post for the team so we’re ready for the switch. Then we post it online because we value transparency and thought it might help the community. + +For community members, this story would help you understand how we plan to make the switch and give you the guidance to fully embrace the new experience. + +For founders and makers who would like to switch too, in one way or another, this story would help you handle the transition with a detailed guide. + +## Switching to Discord + +We’re switching to Discord, step by step. First, we’re moving team conversations, then we’re moving the community with a 15-day buffering. + +The detailed plan goes like this: + +- 2023-07-25 `t=0`: Timur starts setting up the Discord server and sends invites to the team. +- 2023-07-26 `t+1`: The team switches to Discord. The objective is to get used to the product and to customize it to feel at home and, when we’re ready to welcome the community, to make new members feel at home, too. +- 2023-08-02 `t+8`: We announce to the community the upcoming changes in the different channels — GitHub, Twitter, and Slack. + + - **GitHub** + - [ ] Create new Pull Request + - [ ] Add story to the blog + - [ ] Update link to the community + + ``` + https://documen.so/discord + ``` + + - [ ] Start a new Discussion + + ```markdown + Happy Wednesday! + + TL,DR: We’re switching to Discord. [Join the fun!](https://documen.so/discord) + + We want to build a beautiful, open-source DocuSign alternative. As we're growing (reached 2.3K Stars), we feel the need to have a more community- and developer-friendly environment to share ideas, support, and memes. + + Make sure to join the server to keep up to date on all things Documenso. + + Oh and, spoiler alert, there may be some swag there 👀 + + See you there! + Flo + ``` + + - **Twitter** + - [ ] Tweet the announcement + - [ ] Pin Tweet + - [ ] Update link in bio + + ``` + The Open Source DocuSign Alternative. + + http://documen.so/github + http://documen.so/discord + http://documen.so/manifest + ㅤ + ``` + + - **Slack** + - [ ] Post message in `#general` + + ```markdown + Happy Wednesday! + + TL,DR: We’re switching to Discord. [Join the fun!](https://documen.so/discord) + + We want to build a beautiful, open-source DocuSign alternative. As we're growing (reached 2.3K Stars), we feel the need to have a more community- and developer-friendly environment to share ideas, support, and memes. + + Make sure to [join the server](https://documen.so/discord) to keep up to date on all things Documenso. + + Oh and, spoiler alert, there may be some swag there 👀 + + See you there! + Flo + ``` + + - [ ] Pin post + - [ ] Set topic and description + + ``` + We're switching to Discord. Join the fun: https://documen.so/discord + ``` + + - [ ] Archive channels: `#code-review` `#how-to` `#meet-and-greet` `#random-memes` `#self-hosting` `#support` + +- 2023-08-09 `t+15`: 7 days later, we send a reminder on Slack. + - **Slack** + - [ ] Schedule reminder in `#general` (Flo) + + ``` + Friendly reminder: we're switching to Discord and will soon disconnect this Slack workspace. + + Join the fun! https://documen.so/discord + ``` + +- 2023-08-16 `t+22`: 15 days later, we’re making the final edits to the Slack workspace. + - **Slack** + - [ ] [Edit posting permissions](https://app.slack.com/slackhelp/en-US/360004635551) in `#general` + - [ ] Disconnect Slack + +## Final thoughts + +- We’re at the very, early stage on our journey to building a beautiful, open-source DocuSign alternative. We want to build a great developer experience with the open-source community and, switching to Discord, we want to set up the foundations of an open, safe place for community members to get in touch, brainstorm ideas, and have fun. +- It doesn’t mean we won’t ever switch back to Slack. The tools of today aren’t the ones of tomorrow. We don’t delete the Slack workspace, we archive it, and keep the `documenso` handle. May it be just an *au revoir?* +- For now, we’re pushing forward and are eager to welcome you on Discord. Make sure to [join the server](https://documen.so/discord) in order to keep up to date on all things Documenso. See you there! From 84d295e324ce576d0b9129ffd11edd5a15a5d240 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Wed, 2 Aug 2023 11:15:08 +0200 Subject: [PATCH 07/13] Update link to community (Discord) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a7bb44b9f..3330a0e3c 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ Learn more »

- Slack + Discord · Website · @@ -22,7 +22,7 @@

- Join Documenso on Slack + Join Documenso on Discord Github Stars License Commits-per-month From c036858d45325142090cdd7840d5ac793646b296 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Wed, 2 Aug 2023 11:16:04 +0200 Subject: [PATCH 08/13] Update link to community (Discord) --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 46768040d..3309796fa 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -10,7 +10,7 @@ If you plan to contribute to Documenso, please take a moment to feel awesome ✨ ## Developing -The development branch is main. All pull request should be made against this branch. If you need help getting started, [join us on Slack](https://join.slack.com/t/documenso/shared_invite/zt-1qwxxsvli-nDyojjt~wakhgBGl9JRl2w). +The development branch is main. All pull request should be made against this branch. If you need help getting started, [join us on Discord](https://documen.so/discord). 1. [Fork](https://help.github.com/articles/fork-a-repo/) this repository to your own GitHub account and then From 16a703092261500d1df5d8fc3efcb319073c0853 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Wed, 2 Aug 2023 11:27:07 +0200 Subject: [PATCH 09/13] Edit blog post description --- apps/marketing/content/blog/switching-from-slack-to-discord | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/marketing/content/blog/switching-from-slack-to-discord b/apps/marketing/content/blog/switching-from-slack-to-discord index fe2fc8379..3736505be 100644 --- a/apps/marketing/content/blog/switching-from-slack-to-discord +++ b/apps/marketing/content/blog/switching-from-slack-to-discord @@ -1,6 +1,6 @@ --- title: Switching to Discord -description: Launching an open-source document signing tool because trusted-based products should be built on openness. The first release will be in 2023. Sign up at documenso.com to be on board. +description: Join us on documen.so/discord to share ideas, support, and memes. authorName: 'Flo Merian' authorImage: '/blog/blog-author-flo.jpeg' authorRole: 'Go-to-market' From 659af8759235a0764503d23b8d2fe965f9aec329 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Thu, 3 Aug 2023 11:40:00 +0200 Subject: [PATCH 10/13] Edit content --- .../blog/switching-from-slack-to-discord | 30 +++++++++---------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/apps/marketing/content/blog/switching-from-slack-to-discord b/apps/marketing/content/blog/switching-from-slack-to-discord index 3736505be..623682787 100644 --- a/apps/marketing/content/blog/switching-from-slack-to-discord +++ b/apps/marketing/content/blog/switching-from-slack-to-discord @@ -28,7 +28,7 @@ In this post, we won’t debate *why* we’re switching — Slack vs. Discord is Instead, we’ll focus on *how* we plan to make the switch. -## ## Who is this story for? +## Who is this story for? First, we wrote this post for the team so we’re ready for the switch. Then we post it online because we value transparency and thought it might help the community. @@ -47,15 +47,15 @@ The detailed plan goes like this: - 2023-08-02 `t+8`: We announce to the community the upcoming changes in the different channels — GitHub, Twitter, and Slack. - **GitHub** - - [ ] Create new Pull Request - - [ ] Add story to the blog - - [ ] Update link to the community + - Create new Pull Request + - Add story to the blog + - Update link to the community ``` https://documen.so/discord ``` - - [ ] Start a new Discussion + - Start a new Discussion ```markdown Happy Wednesday! @@ -73,9 +73,9 @@ The detailed plan goes like this: ``` - **Twitter** - - [ ] Tweet the announcement - - [ ] Pin Tweet - - [ ] Update link in bio + - [Tweet the announcement](https://twitter.com/documenso/status/1686719482096766977) + - Pin Tweet + - Update link in bio ``` The Open Source DocuSign Alternative. @@ -87,7 +87,7 @@ The detailed plan goes like this: ``` - **Slack** - - [ ] Post message in `#general` + - Post message in `#general` ```markdown Happy Wednesday! @@ -104,18 +104,18 @@ The detailed plan goes like this: Flo ``` - - [ ] Pin post - - [ ] Set topic and description + - Pin post + - Set topic and description ``` We're switching to Discord. Join the fun: https://documen.so/discord ``` - - [ ] Archive channels: `#code-review` `#how-to` `#meet-and-greet` `#random-memes` `#self-hosting` `#support` + - Archive channels: `#code-review` `#how-to` `#meet-and-greet` `#random-memes` `#self-hosting` `#support` - 2023-08-09 `t+15`: 7 days later, we send a reminder on Slack. - **Slack** - - [ ] Schedule reminder in `#general` (Flo) + - Schedule reminder in `#general` ``` Friendly reminder: we're switching to Discord and will soon disconnect this Slack workspace. @@ -125,8 +125,8 @@ The detailed plan goes like this: - 2023-08-16 `t+22`: 15 days later, we’re making the final edits to the Slack workspace. - **Slack** - - [ ] [Edit posting permissions](https://app.slack.com/slackhelp/en-US/360004635551) in `#general` - - [ ] Disconnect Slack + - [Edit posting permissions](https://app.slack.com/slackhelp/en-US/360004635551) in `#general` + - Disconnect Slack ## Final thoughts From 2ec3cebcc962c2ad3a1c4e9f70fe579e0242d4e3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Thu, 3 Aug 2023 12:32:27 +0200 Subject: [PATCH 11/13] Optimize description --- apps/marketing/content/blog/switching-from-slack-to-discord | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/marketing/content/blog/switching-from-slack-to-discord b/apps/marketing/content/blog/switching-from-slack-to-discord index 623682787..82c7ac4d6 100644 --- a/apps/marketing/content/blog/switching-from-slack-to-discord +++ b/apps/marketing/content/blog/switching-from-slack-to-discord @@ -1,6 +1,6 @@ --- title: Switching to Discord -description: Join us on documen.so/discord to share ideas, support, and memes. +description: The Documenso community is growing and we feel the need to have a more community- and developer-friendly environment. We're switching to Discord. authorName: 'Flo Merian' authorImage: '/blog/blog-author-flo.jpeg' authorRole: 'Go-to-market' From 1a31cc321c3eea080b630fdfd81efd529ff0e0c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?fl=C5=8D?= Date: Fri, 4 Aug 2023 08:25:51 +0200 Subject: [PATCH 12/13] fix typo --- ...ack-to-discord => switching-from-slack-to-discord.mdx} | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) rename apps/marketing/content/blog/{switching-from-slack-to-discord => switching-from-slack-to-discord.mdx} (94%) diff --git a/apps/marketing/content/blog/switching-from-slack-to-discord b/apps/marketing/content/blog/switching-from-slack-to-discord.mdx similarity index 94% rename from apps/marketing/content/blog/switching-from-slack-to-discord rename to apps/marketing/content/blog/switching-from-slack-to-discord.mdx index 82c7ac4d6..0e3d0e54d 100644 --- a/apps/marketing/content/blog/switching-from-slack-to-discord +++ b/apps/marketing/content/blog/switching-from-slack-to-discord.mdx @@ -1,13 +1,13 @@ --- title: Switching to Discord -description: The Documenso community is growing and we feel the need to have a more community- and developer-friendly environment. We're switching to Discord. +description: The Documenso community is growing and we feel the need to have a more community and developer-friendly environment. We're switching to Discord. authorName: 'Flo Merian' authorImage: '/blog/blog-author-flo.jpeg' authorRole: 'Go-to-market' date: 2023-08-02 tags: - Announcement - - Community + - Community --- We’re switching to Discord. @@ -20,9 +20,9 @@ As the community grows (reached 2K stars on GitHub and 100 community members on The Documenso team is growing, too. [Lucas joined Timur](https://twitter.com/ElTimuro/status/1648608988391514112), then [Ephraim](https://twitter.com/documenso/status/1662418374243041280) and [David](https://github.com/dguyen) recently joined the journey. We want to stay in touch with the community as much as possible and avoid context-switching to focus on work, support, and fun. -We’re an open-source project and focus on building a great developer experience. So, when we thought of a Slack replacement, community- and developer-friendly, Discord was an obvious choice — not to mention that it would help us keep up with [OSS friends](https://documen.so/oss), too. +We’re an open-source project and focus on building a great developer experience. So, when we thought of a Slack replacement, community and developer-friendly, Discord was an obvious choice — not to mention that it would help us keep up with [OSS friends](https://documen.so/oss), too. -So, we’re switching all conversations, team- and community-wide, to Discord. +So, we’re switching all conversations, team and community-wide, to Discord. In this post, we won’t debate *why* we’re switching — Slack vs. Discord is a long-lasting debate with pros and cons, and fans on both sides. There are great [stories](https://blog.meilisearch.com/from-slack-to-discord-our-migration/) and [threads](https://twitter.com/McPizza0/status/1655519558600470528) on the topic. We just don’t want to write yet another story here. From 9ca84f5ededb85cdc8c7240f1cb5aef8c4b90aa7 Mon Sep 17 00:00:00 2001 From: Mythie Date: Sat, 5 Aug 2023 17:44:39 +1000 Subject: [PATCH 13/13] chore: add contributor license agreement --- CLA.md | 45 +++++++++++++++++++++++++++++++++++++++++++++ CONTRIBUTING.md | 1 + 2 files changed, 46 insertions(+) create mode 100644 CLA.md diff --git a/CLA.md b/CLA.md new file mode 100644 index 000000000..9bdc1bd2b --- /dev/null +++ b/CLA.md @@ -0,0 +1,45 @@ +# Documenso Contributors License Agreement + +This Contributors License Agreement ("CLA") is entered into between the Contributor, and Documenso Inc. ("Documenso"), collectively referred to as the "Parties." + +## Background: + +Documenso is an open-source project aimed at providing an open-source document signing platform for all parties. This CLA governs the rights and contributions made by the Contributor to the Documenso project. + +## Agreement: + +**Contributor Grant of License:** + +By submitting code, documentation, or any other materials (collectively, "Contributions") to the Documenso project, the Contributor grants Documenso a perpetual, worldwide, non-exclusive, royalty-free, sublicensable license to use, modify, distribute, and otherwise exploit the Contributions, including any intellectual property rights therein, for the purposes of the Documenso project. + +**Representation of Ownership and Right to Contribute:** + +The Contributor represents that they have the legal right to grant the license stated in Section 1, and that the Contributions do not infringe upon the intellectual property rights of any third party. The Contributor also represents that they have the authority to submit the Contributions on their own behalf or, if applicable, on behalf of their employer or any other entity. + +**Patent Grant:** + +If the Contributions include any method, process, or apparatus that is covered by a patent, the Contributor agrees to grant Documenso a non-exclusive, worldwide, royalty-free license under any patent claims necessary to use, modify, distribute, and otherwise exploit the Contributions for the purposes of the Documenso project. + +**No Implied Warranties or Support:** + +The Contributor acknowledges that the Contributions are provided "as is," without any warranties or support of any kind. Documenso shall have no obligation to provide maintenance, updates, bug fixes, or support for the Contributions. + +**Retention of Contributor Rights:** + +The Contributor retains all right, title, and interest in and to their Contributions. This CLA does not restrict the Contributor from using their own Contributions for any other purpose. + +**Governing Law:** + +This CLA shall be governed by and construed in accordance with the laws of California (CA), without regard to its conflict of laws principles. + +**Entire Agreement:** + +This CLA constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior and contemporaneous understandings, agreements, representations, and warranties. + +**Acceptance:** + +By submitting Contributions to the Documenso project, the Contributor acknowledges and agrees to the terms and conditions of this CLA. If the Contributor is agreeing to this CLA on behalf of an entity, they represent that they have the necessary authority to bind that entity to these terms. + +**Effective Date:** + +This CLA is effective as of the date of the first Contribution made by the Contributor to the Documenso project. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3309796fa..eca35cd8b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -7,6 +7,7 @@ If you plan to contribute to Documenso, please take a moment to feel awesome ✨ - Before jumping into a PR be sure to search [existing PRs](https://github.com/documenso/documenso/pulls) or [issues](https://github.com/documenso/documenso/issues) for an open or closed item that relates to your submission. - Select and issue from [here](https://github.com/documenso/documenso/issues) or create a new one - Consider the results from the discussion in the issue +- Accept the [Contributor License Agreement](https://documen.so/cla) to ensure we can accept your contributions. ## Developing