-
Notifications
You must be signed in to change notification settings - Fork 56
Populate/launch features voting mechanism #319
Comments
We've got a free-access account on Canny at https://ipfs.canny.io, but we still need to set up and populate the features list for voting. Watch this space! |
nice, would you mind sending me an invite? I'm wondering if we can setup multiple spaces for different projects otherwise |
@cwaring You should have an invite in the email already 😊 |
⏳ |
Admin access should be fixed now -- if you don't have admin access and feel that you should, contact me! |
confirmed, thanks 🙌 |
I've populated https://ipfs.canny.io/docs-features with the features from last quarter's prioritized features list, minus the ones that we know we're already heavily prioritizing. @cwaring @ericronne -- can you please take a look to see if it's complete, and then let's talk about best practices for launch? Thanks! |
Notes from today's WG meeting on launch socialization:
|
Can we swap in this version of the logo (where IPFS isn't obscuring the symbol)? |
@ericronne good call. |
Quick status update on this one -- we don't intend to socialize this until the public beta launch, but in the interim, @cwaring is thinking on if we want a deeper integration of Canny into the docs itself rather than just linking to the external page. (As part of longer-term strategy than just this features prioritization effort, this could be really useful.) |
@cwaring - can you please whatever branch has this in the header, so we can close it out? |
This is now linked from the beta as an MVP, closing for now. |
This issue is part of Epic 2D: Vote on and prioritize docs beta features.
Once the best-fit voting mechanism has been decided upon per #318, populate an instance of it with the features from our features list spreadsheet and launch. This likely won't involve a lot of coding on our end, since it'll use a third-party service; however, may involve some visual design for continuity with our existing design language.
The text was updated successfully, but these errors were encountered: