We maintain and improve our edgeryders.eu website. Join if you care about our home on the web, and you would like to help!

We need many different contributions, so there is something for everybody: from testing to documentation writing, visual design, Drupal backend tasks, CSS tweaking and Drupal development.

Currently coordinated by Matt. Everybody welcome, just click "Subscribe to Group" and "Follow".

Our most important content:

  • How to join the edgeryders.eu developers. Step by step intro on how to start contributing to the site's infrastructure.
  • Taskmanager for Dev & Testing. If you want to help us with the site, look no further. Includes tasks for newcomers and a way to subscribe to tasks and manage them.
  • Issue Reports and Feature Requests. Go the Taskmanager and use the search string to make sure that someone else has not already submitted the same issue. Done this, create a task to add a bug or feature request.
  • User Manual. All documentation for readers, content creators and moderators on edgeryders.eu.
  • Developer Manual. All documentation for edgeryders.eu backend admins, maintainers and programmers.
  • Long-term Plans. Idea collections what to do with this platform in the long run.
  • Changelog. All the completed tasks, documenting our recent changes to the platform software.
  • Team. All the friendly people who want to contribute to the edgeryders.eu site's development.
like5

On the importance of a weblayout checkup

Hi, since ER is the platform for OpenCare and related OpenAndChange I think the issues of Responsiveness and Accessibility (as of W3C) should be taken very serious.

I know that US instituions are OBLIGED to adhere to Accessibility requirements, it would be a pitty risk 100M grant on such a detail.

If I can ill be happy to contribute

Heads up: new Ethnographer role, content managers and site admins can no longer see and add annotations

Alberto's picture

OpenEthnographer introduces a long delay in loading pages (only for users with the relevant privileges). While we wait for a more permanent solution, we have adopted a workaround. Its implications are that users with content manager and site admin privileges can no longer see or create OE annotations, and can not see the OE sidebar. 

Still missing|: newsletter sign up in the menu alsobutton for switching languages has vanished

I can't remember what happened with the newsletter signup that was to be embedded in the menu. Any chance we wil/can see this? Social media is something it would be nice to move away from and so mailing list is impt. Also for some reason language switching button disappeared.

On the importance of a weblayout checkup

Hi, since ER is the platform for OpenCare and related OpenAndChange I think the issues of Responsiveness and Accessibility (as of W3C) should be taken very serious.

I know that US instituions are OBLIGED to adhere to Accessibility requirements, it would be a pitty risk 100M grant on such a detail.

If I can ill be happy to contribute

Fix that the first opencare challenge now leads to the open&change application process

From here: https://edgeryders.eu/en/op3ncare/helping-one-another-to-discover-what-is

Clicking on the ongoing challenge, "how do you give or receive care?", you are taken here: https://edgeryders.eu/en/how-do-you-give-and-recieve-care

Notice the openandchange application chain on top of the page. 

Clicking on any other challenge obtains the same result. 

 

Heads up: reforming the Edgeryders menu structure

Now that we have a shiny new navigation system, we can tidy up our navigation. Nadia thinks this is better done sooner than later, given that our new clients will be checking in.

We have noticed that we constantly find ourselves having to explain that Edgeryders is both a community and a company. So, I propose we reform the menu as follows. We will have only three top-level items (+ featured projects).

Fully automated development environment setup for new contributors

I am new to Edgeryders and having a look at its technical setup. I am currently working through the "Web-based Development Setup for Drupal Developers" in order to create a local development environment. As I'm going through it, I'm finding that there are a number of steps marked "TODO" in that list, and the whole setup could probably streamlined quite a bit.

Heads up: new Ethnographer role, content managers and site admins can no longer see and add annotations

Alberto's picture

OpenEthnographer introduces a long delay in loading pages (only for users with the relevant privileges). While we wait for a more permanent solution, we have adopted a workaround. Its implications are that users with content manager and site admin privileges can no longer see or create OE annotations, and can not see the OE sidebar. 

Do Challenge Responses break the data model?

Alberto's picture

I noticed that the new content type Challenge Response is not attributed to any groups. 

This is inconsistent with the Drupal Commons data model. Aparts from "cleanliness", I see a potential disadvantage when doin research. 

Example. When we do any ethnographic work, the first thing to do is to parse the content in Edgeryders into two parts: content to be coded by the ethnographers (it is pertinent to the present research) and content not to be coded (it is not pertinent). So far, it worked like this: 

No documents have been added to this group.

Upgrade to latest upstream (3.32)

Site is running commons-7.x-3.12, while the latest commons on BOA is 7.x-3.32. It is desirable to bring it to this level and revert the features to the extent possible, so that there is a clean starting point for further developments. Feature overrides are need to be made for needed features that have been reverted. These have been aggregated into the edgerrides feature (with some exceptions which are not supported, such as nodes panelizer settings)

Theming and navigation

As part of the improvements on the Edgeryders community site, the theming of the site was simplified, especially through:

  • a subtheme of commons_origin > commons_edge
  • the navbar as the central module for rendering themeable, modern and responsive navigation

The commons_origins module is based on adaptivetheme.
There are several CSS customizations made at the UI level using the CSS Injector module.

Project Ark – saving Edgeryders from the email notification deluge. Making a newsletter + digest

The Newsletter + Daily Digest is meant to be sent dailt (d'oh) and consist of two parts:

  1. an editorialized part with interesting or featured content (like #countonme list)
  2. a digest of new content created in groups the user follows.

The editorialized part is implemented with the following components:

Edgeryder 2.0 Development Session

This document records the outcome of the session on developing the new Edgeryders platform held at LOTE2. The idea was to learn from the ER experience in 2011-2012 and get move on. 

Part 1: Feature Collection

One list what you would like to see. Add a percentage that represents the priority (like this German hacker touch)

Alberto:

Creating edgeryders.eu e-mail addresses

We can create e-mail addresses of the form address@edgeryders.eu. This is used for communications of the Edgeryders company (our social enterprise), but we can also provide such addresses for community projects which are in some way officially backed and supported by the Edgeryders social enterprise.

Here's how to create such addresses.

Recent activity in this group

Wed, 22/02/2017 - 10:57
Wed, 22/02/2017 - 08:35
Tue, 21/02/2017 - 21:29
Tue, 21/02/2017 - 19:09

Group contributors

Organizers

Contributors