agaric/agaric-coop
10
1
Fork 0
Code Issues 102 Pull requests Projects Releases Packages Wiki Activity

Decision: Agaric.com vs Agaric.coop for default #74

New issue
Closed
opened 2018-08-18 12:29:09 +00:00 by mlncn · 20 comments
mlncn commented 2018-08-18 12:29:09 +00:00 (Migrated from gitlab.com)
Copy link

I vote Agaric.com (especially since i'm more sure of us holding on to that than Agaric.coop; .com is regulated and all other extensions can get extortionate if they choose. I want to believe in our .coop registrar but i'll note i've never been asked to vote for its directors!

At some point it would be cool to give people entering with agaric.coop a special welcome somehow; probably an extra block on the home page is safer than trying to redirect to a coop-focused page on only the first visit of someone going to agaric.coop directly.

I vote Agaric.com (especially since i'm more sure of us holding on to that than Agaric.coop; .com is regulated and all other extensions can get extortionate if they choose. I want to believe in our .coop registrar but i'll note i've never been asked to vote for its directors! At some point it would be cool to give people entering with agaric.coop a special welcome somehow; probably an extra block on the home page is safer than trying to redirect to a coop-focused page on only the first visit of someone going to agaric.coop directly.
mlncn commented 2018-08-18 12:29:21 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @cedewey

assigned to @cedewey
mlncn commented 2018-08-18 12:36:35 +00:00 (Migrated from gitlab.com)
Copy link

Oh to clarify, i think i meant this as deciding whether to redirect to agaric.coop or to agaric.com. If we decide to brand more strongly as a cooperative we could redirect to agaric.coop. However i don't think we should redirect agaric.coop to agaric.com (but all other domains should) unless we want to hide our coop identity, and have everyone who is cooperative-friendly know we're trying to hide our coop identity. Which i don't think we want. The status quo and probably best decision here is to simply not redirect agaric.coop to agaric.com, nor vice versa. And branding as Agaric.com.

Oh to clarify, i think i meant this as deciding whether to redirect to agaric.coop or to agaric.com. If we decide to brand more strongly as a cooperative we could redirect to agaric.coop. However i don't think we should redirect agaric.coop to agaric.com (but all other domains should) unless we want to hide our coop identity, and have everyone who is cooperative-friendly *know* we're trying to hide our coop identity. Which i don't think we want. The status quo and probably best decision here is to simply not redirect agaric.coop to agaric.com, nor vice versa. And branding as Agaric.com.
cedewey commented 2018-08-20 15:29:57 +00:00 (Migrated from gitlab.com)
Copy link

I think we should be loud and proud about being a coop, so redirect .com to .coop

I think we should be loud and proud about being a coop, so redirect .com to .coop
mlncn commented 2018-09-06 20:48:12 +00:00 (Migrated from gitlab.com)
Copy link

marked this issue as related to #64

marked this issue as related to #64
cedewey commented 2018-09-26 16:05:54 +00:00 (Migrated from gitlab.com)
Copy link

changed milestone to %3

changed milestone to %3
cedewey commented 2018-09-26 16:07:13 +00:00 (Migrated from gitlab.com)
Copy link

@dinarcon @wolcen @gnuget @FreeScholar ,

What do y'all think? Should we have all aliases redirect to agaric.coop or have agaric.com and agaric.coop each work on their own (and not redirect to the other)?

@dinarcon @wolcen @gnuget @FreeScholar , What do y'all think? Should we have all aliases redirect to agaric.coop or have agaric.com and agaric.coop each work on their own (and not redirect to the other)?
cedewey commented 2018-09-26 16:07:21 +00:00 (Migrated from gitlab.com)
Copy link

unassigned @cedewey

unassigned @cedewey
cedewey commented 2018-09-26 16:07:37 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @wolcen, @dinarcon, @FreeScholar, and @gnuget

assigned to @wolcen, @dinarcon, @FreeScholar, and @gnuget
dinarcon commented 2018-09-26 16:20:49 +00:00 (Migrated from gitlab.com)
Copy link

I vote .com being our canonical home and .coop redirect to .com I recommend against both domain serving the same (duplicate) content. And we do not produce enough material for two separate websites.

I vote .com being our canonical home and .coop redirect to .com I recommend against both domain serving the same (duplicate) content. And we do not produce enough material for two separate websites.
gnuget commented 2018-09-26 16:31:42 +00:00 (Migrated from gitlab.com)
Copy link

Currently we mention that we are a cooperative and it is a important part of Agaric.

So, if we want to continue with that then we should use the coop domain and redirect the com to .coop.

But if the new home is more focused on sales, maybe we can use the .com and dedicate a page to talk about the cooperative (and redirect the coop to the com)

Currently we mention that we are a cooperative and it is a important part of Agaric. So, if we want to continue with that then we should use the coop domain and redirect the com to .coop. But if the new home is more focused on sales, maybe we can use the .com and dedicate a page to talk about the cooperative (and redirect the coop to the com)
mlncn commented 2018-10-12 05:59:47 +00:00 (Migrated from gitlab.com)
Copy link

Having canonical meta tags will prevent there from being any duplicate content penalty.

And i admit it's a spineless dodge, but it's nice to be able to send co-op people a .coop link and have it stay that way, and .com for everyone else.

Having canonical meta tags will prevent there from being any duplicate content penalty. And i admit it's a spineless dodge, but it's nice to be able to send co-op people a .coop link and have it stay that way, and .com for everyone else.
cedewey commented 2018-10-12 18:29:35 +00:00 (Migrated from gitlab.com)
Copy link

I think we should use .coop as the canonical TLD for two reasons:

  • Being a cooperative is a way we can differentiate ourselves from other agencies, being a coop is especially attractive for nonprofits (especially ones operating in the economic justice sphere)
  • I want us to be more vocal about being a coop and how others should be too. In an age of increasing wealth disparity and erosion of workplace rights, it's time for coops to be more proactive in helping the coop movement grow

I agree with David that we need information on the website explain what a cooperative is.

I think we should use .coop as the canonical TLD for two reasons: * Being a cooperative is a way we can differentiate ourselves from other agencies, being a coop is especially attractive for nonprofits (especially ones operating in the economic justice sphere) * I want us to be more vocal about being a coop and how others should be too. In an age of increasing wealth disparity and erosion of workplace rights, it's time for coops to be more proactive in helping the coop movement grow I agree with David that we need information on the website explain what a cooperative is.
FreeScholar commented 2018-10-14 02:50:14 +00:00 (Migrated from gitlab.com)
Copy link

Totally agree on all this.

Totally agree on all this.
mlncn commented 2018-10-19 16:08:19 +00:00 (Migrated from gitlab.com)
Copy link

@FreeScholar we have quite a dispute going on, which part do you totally agree with? Clayton's most recent comment? (Also @cedewey i've seen you do conversation threads in GitLab; how do you do that?)

As long as we set canonical URL we don't get any penalty from search engines, and it can definitely help us reconcile our separate opinions here. Search engines will start sending people to the one we choose, though, so it's still consequential.

David's point is right on: we need to draft a super positive (and sales-y) "why a coop" intro linked from the front page, if we have our primary domain be .coop.

That's my preference, that we differentiate ourselves as a coop, but i'd say that switching to .coop as primary is dependent on us getting that copy written.

@FreeScholar we have quite a dispute going on, which part do you totally agree with? Clayton's most recent comment? (Also @cedewey i've seen you do conversation threads in GitLab; how do you do that?) As long as we set canonical URL we don't get any penalty from search engines, and it can definitely help us reconcile our separate opinions here. Search engines will start sending people to the one we choose, though, so it's still consequential. David's point is right on: we need to draft a super positive (and sales-y) "why a coop" intro linked from the front page, if we have our primary domain be .coop. That's my preference, that we differentiate ourselves as a coop, but i'd say that switching to .coop as primary is dependent on us getting that copy written.
cedewey commented 2018-11-28 19:30:33 +00:00 (Migrated from gitlab.com)
Copy link

changed milestone to %7

changed milestone to %7
cedewey commented 2018-12-31 19:06:55 +00:00 (Migrated from gitlab.com)
Copy link

We've decided to make agaric.coop the canonical url and redirect to it. We can change this at a later date if need be.

We've decided to make agaric.coop the canonical url and redirect to it. We can change this at a later date if need be.
cedewey commented 2018-12-31 19:06:55 +00:00 (Migrated from gitlab.com)
Copy link

closed

closed
mlncn commented 2019-01-02 15:03:59 +00:00 (Migrated from gitlab.com)
Copy link

reopened

reopened
mlncn commented 2019-01-02 15:10:32 +00:00 (Migrated from gitlab.com)
Copy link

Sorry. Thought for a second we had to tell Drupal somewhere what the canonical URL was. But our redirecting seems to be enough:

<link rel="shortlink" href="https://agaric.coop/" />
<link rel="canonical" href="https://agaric.coop/" />
Sorry. Thought for a second we had to tell Drupal somewhere what the canonical URL was. But our redirecting seems to be enough: ``` <link rel="shortlink" href="https://agaric.coop/" /> <link rel="canonical" href="https://agaric.coop/" /> ```
mlncn commented 2019-01-02 15:10:32 +00:00 (Migrated from gitlab.com)
Copy link

closed

closed
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
bbb-test
D9-upgrade
drush-9-aliases
provision-dewey
No results found.
Labels
Clear labels   
A11y

Accessibility-related issues

  
Automated Testing

   
Contributable

Issues with work that can (potentially) be contributed back to Drupal or other FLOSS projects.

  
Contributed

Tag issues where we have contributed work back to FLOSS projects (replace Contributable tag; the Contributed tag can be removed once the contribution is recorded in a blog or something.

  
Decision

An issue that requires a decision be made.

  
Design

Issues that should include a UX/design work or review.

  
Development

   
Drutopia

Issues related to Drutopia features or infrastructure, or are potential Drutopia enhancements (with tag Contributable).

  
Feature Request

   
IndieWeb

Anything related to interlinking web sites in a broadly IndieWeb fashion, see https://indieweb.org/

  
Infrastructure

   
Marketing

   
Needs documentation

When an issue has uncovered something that should be documented in a user guide or the project wiki or anywhere else outside the issue queue.

  
status::Abandoned

An issue that has been abandoned and will not be completed.

  
status::Blocked

An issue that is blocked for a reason outside Agaric's control.

  
status::Deploy

An issue that has been tested and is ready to be deployed.

  
status::Doing

   
status::Done

   
status::In Review

An issue that has been completed and is ready for a code and/or design review.

  
status::Needs Clarification

   
status::Test

An issue that has been completed and is ready to be tested.

  
status::To Do

An issue that is an agreed priority and has all information needed to be completed.

  
type::Bug

   
type::Task

   
type::User Story
No labels
A11y
Automated Testing
Contributable
Contributed
Decision
Design
Development
Drutopia
Feature Request
IndieWeb
Infrastructure
Marketing
Needs documentation
status::Abandoned
status::Blocked
status::Deploy
status::Doing
status::Done
status::In Review
status::Needs Clarification
status::Test
status::To Do
type::Bug
type::Task
type::User Story
Milestone
Clear milestone
No items
No milestone
Site Launch
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: agaric/agaric-coop#74
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?