Cancelled

JBP-160: Migrate Notion to CharmVerse

Author

Anon

Cycle

22

loading

How to fill out this template.

Title: Migrate Notion Database to CharmVerse
Author: Zom_Bae
Date: 2022-05-05

Thesis:

Switch collaboration platform from Notion to CharmVerse

Abstract:

We will be fully migrating or recreating all relevant Notion content in CharmVerse.

Motivation:

CharmVerse is the first Web3 native, all in one workspace which serves the same function as Notion. In addition, it provides native support for bounty management, token-gated access control, and wallet log-in (no more sharing links to gain access!) Furthermore, it offers better-designed APIs that will integrate with Nance to support the proposal workflow automation.

Unlike Notion, this will also be a no cost solution for Juicebox, as a strategic partner for CharmVerse. The ask in return is to assist in fostering relationships with Charm and new dao’s who utilize the protocol.

The CharmVerse team has been working hand in hand with a few folks from Juicebox (shout out to Jigglyjams, Zeugh, filipv, 0xStvg, gulan) over the last few months to dial in this product to make sure it nails all the necessary functionally and then some, when compared to notion.

Watch CharmVerse in action: https://discord.com/channels/775859454780244028/889560116666441748/972111762633674753

Risks:

CharmVerse is a less mature project compared to Notion. There is a higher risk of defects or potential downtime. Though the CharmVerse team is venture-backed and has been very responsive to our bug reports and feature requests during initial assessments.

Specification:

We will be fully migrating or recreating all relevant Notion content in CharmVerse. Once the transition is over, all new content will be solely created in CharmVerse. DAO members must adapt to the new interface though it is quite similar to the Notion interface.

CharmVerse provides a one-time Notion import function to bring content into CharmVerse. The CharmVerse team has also offered to manually help with the migration. Anticipated time to complete: no more than a day after initial import pending any major bugs.

Rationale:

Having 2 parallel knowledge bases with out-of-sync content would be highly confusing and inefficient. Once the content is migrated and recreated, we must cut over to the new system in full at once.

Timeline:

As soon as proposal passes.

Specific completion times are detailed throughout body of proposal.

Copyright and related rights waived via CC0.