Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: Show constitution #2192

Closed
mochet opened this issue Feb 27, 2022 · 6 comments
Closed

Idea: Show constitution #2192

mochet opened this issue Feb 27, 2022 · 6 comments
Labels
design idea Idea for a new feature mainnet Mainnet scope pending-triage Requires triage before any work can begin priority:low

Comments

@mochet
Copy link
Contributor

mochet commented Feb 27, 2022

This doesn't seem to have been discussed or mentioned on this repo at all, it has been suggested via this issue: #2191

TLDR: Atlas should show the constitution, or maybe the particular area of it dealing with content and moderation policies.

┆Issue is synchronized with this Asana task by Unito

@mochet mochet added idea Idea for a new feature pending-triage Requires triage before any work can begin labels Feb 27, 2022
@dmtrjsg
Copy link

dmtrjsg commented Jul 1, 2022

Thank you for raising. This could potentially be handled via these two tickets. tbc

@dmtrjsg dmtrjsg added design mainnet Mainnet scope labels Jul 1, 2022
@bedeho
Copy link
Member

bedeho commented Jul 18, 2022

I disagree, Atlas is about content only, and it is a consumer interface, the constitution will be a very complex document describing all sorts of policies.

@dmtrjsg
Copy link

dmtrjsg commented Jul 22, 2022

@bedeho While I do not have a strong view on this, just to clarify, would it not make sense to even include a link to it in the footer of the side nav? Would constitution or relevant parts from it be cited in Terms of Service or Content Policy which are already added there?

Screenshot 2022-07-22 at 15 35 36

@bedeho
Copy link
Member

bedeho commented Jul 22, 2022

While I do not have a strong view on this, just to clarify, would it not make sense to even include a link to it in the footer of the side nav? Would constitution or relevant parts from it be cited in Terms of Service or Content Policy which are already added there?

the only thing I see that could make sense would be some backlink to the project itself, because I assume more and more people will just directly land in some instance of Atlas, not even hosted by Jsgenesis, and getting some sort of contextual way to find out or find out about Joystream makes sense, the consitution is multiple layers out of context, and may have very limited relevance to the actual Atlas app.

@bedeho bedeho closed this as completed Jul 22, 2022
@dmtrjsg
Copy link

dmtrjsg commented Jul 25, 2022

The link to Joystream would be from the logo / Atlas re-branding. With "powered by Joystream" badge. Tagging @toiletgranny so we pick it up in the relevant ticket or add here if the decision will be taken to go in a diff direction.

@toiletgranny
Copy link
Contributor

Hey @dmtrjsg, thanks for tagging! I'm afraid it's unclear to me exactly how I can help at this point, though.

  1. The link to Joystream would be from the logo / Atlas re-branding.

    Which logo? Atlas? Do you mean linking to Joystream.org by clicking on the Atlas logo?

  2. With "powered by Joystream" badge.

    The word badge implies adding something visual somewhere, but I'm afraid I can't remember we talked about this before. Apologies if it's my memory, but could I ask you to elaborate on this idea or point to an issue where it's described? 😅

I'm happy to discuss this over tomorrow's tech/design sync call if you prefer! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design idea Idea for a new feature mainnet Mainnet scope pending-triage Requires triage before any work can begin priority:low
Projects
None yet
Development

No branches or pull requests

4 participants