geo/geo-coop
geo/geo-coop
7
1
Fork 0
Code Issues 55 Pull requests Projects Releases Packages Wiki Activity Actions

Restore disclaimer to blog postings? #74

New issue
Open
opened 2019-10-02 16:05:53 +00:00 by mlncn · 7 comments
mlncn commented 2019-10-02 16:05:53 +00:00 (Migrated from gitlab.com)
Copy link

The old site printed this at the top of every blog:

GEO blogs are part of our mission to provide a platform for co-op practitioners and solidarity economy organizers to share their thoughts and experiences with a wider audience. Any views and opinions expressed are those of the author and do not necessarily reflect the views of the GEO Collective. If you would like to start a blog on GEO, please contact editors@geo.coop. If you would like to make a response to the blog author, we encourage you to do so in the comments section below.

@joshua_davis Should we restore it or a similar disclaimer to somewhere on blog pages?

The old site printed this at the top of every blog: > GEO blogs are part of our mission to provide a platform for co-op practitioners and solidarity economy organizers to share their thoughts and experiences with a wider audience. Any views and opinions expressed are those of the author and do not necessarily reflect the views of the GEO Collective. If you would like to start a blog on GEO, please contact editors@geo.coop. If you would like to make a response to the blog author, we encourage you to do so in the comments section below. @joshua_davis Should we restore it or a similar disclaimer to somewhere on blog pages?
mlncn commented 2019-10-02 16:06:04 +00:00 (Migrated from gitlab.com)
Copy link

(Sorry thought i'd filed this issue a few days ago but had not submitted the form.)

(Sorry thought i'd filed this issue a few days ago but had not submitted the form.)
joshua_davis commented 2019-10-02 16:08:10 +00:00 (Migrated from gitlab.com)
Copy link

Yes please. Good catch. We definitely need the disclaimer so that when I
write something wildly offensive on my blog, the rest of the group can
officially disclaim responsibility. Putting it at the bottom would be
good. Right above the comments, if possible.

Yes please. Good catch. We definitely need the disclaimer so that when I write something wildly offensive on my blog, the rest of the group can officially disclaim responsibility. Putting it at the bottom would be good. Right above the comments, if possible.
FreeScholar commented 2019-10-07 18:05:55 +00:00 (Migrated from gitlab.com)
Copy link

@joshua_davis Should the whole disclaimer text be shown on the bottom of each blog, or a snippet with a more link that goes to a disclaimer page?

@joshua_davis Should the whole disclaimer text be shown on the bottom of each blog, or a snippet with a more link that goes to a disclaimer page?
joshua_davis commented 2019-10-07 18:29:09 +00:00 (Migrated from gitlab.com)
Copy link

The whole thing.

The whole thing.
FreeScholar commented 2019-10-08 17:06:04 +00:00 (Migrated from gitlab.com)
Copy link

Display disclaimer on bottom of each blog.

Display disclaimer on bottom of each blog.
mlncn commented 2019-10-09 20:57:47 +00:00 (Migrated from gitlab.com)
Copy link

@FreeScholar it used to be displayed at the top, should be the bottom?

@FreeScholar it used to be displayed at the top, should be the bottom?
joshua_davis commented 2019-10-09 22:29:43 +00:00 (Migrated from gitlab.com)
Copy link

Yes, that was my request. Thanks for noticing, though!

Yes, that was my request. Thanks for noticing, though!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
drupal10-rebased
drupal10
master
12-comments
old-aug-left-on-local
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).

  
IndieWeb

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

  
Infrastructure

   
Launch Critical

Issue that must be done in time for launch.

  
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.

  
Post-Launch

An issue that needs to be completed, but can happen after launch.

  
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
IndieWeb
Infrastructure
Launch Critical
Marketing
Needs documentation
Post-Launch
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
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: geo/geo-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?