Skip to main content

Blog

See Permissions' Machine Names (and much more) with Xray Module for Drupal 7

With Drupal 7's third and final release candidate unleashed on us all this morning, it is long past time to help the #D7CX movement with a seasonal offering of our own.

+1 to Ending comment-to-subscribe on Drupal.org

As starving authors we at Agaric don't have a lot of cash to burn right now, but we've thrown $25 in the project to make it possible to subscribe to drupal.org issues without commenting. (On top of whatever we donated when this request for funding went out a year and a half ago).

Drupal Work Collectives

Agaric proposes the creation of a new kind of workplace, essentially a Drupal commune, but really more like an open source free software idea & brainstorming commune, kind of along the same lines as an artist's or writer's colony.

We're Writing a Book!

Yes it's true, for the past few months we've been hard at work with a lot of other co-authors on The Definitive Guide to Drupal 7.

Agaric Backs Community Coworking Center in NYC

Thinking it would be a great place to work a day or two while in New York City for clients or DrupalCamps, Agaric dropped a few dollars in the Kickstarter fund for New Work City: Community Coworking Center for Independents in NY.

Agaric Sponsors Modulecraft for the Building of Drupal Shared business, Development, and Training Tools

For community shared business, development, and training tools, Agaric throws a little sponsorship at modulecraft.

Agaric Provides Very Minor Assist in Readying Insert Module for Drupal 7

Benjamin Melançon of Agaric helped with a patch for the Drupal 7 version of Insert module.

A round red capped mushroom with white spots.

Agaric?

What the word agaric means and why Agaric took it for our cooperative's name.

Designed to Life

Functionality designed to your life is the Agaric Design signature. Utilizing open source, free software from around the world, Agaric Design websites are impeccably crafted with a modern, sophisticated and understated spirit.

The Story on Agaric

I've always had a passion for good design and healthy coding, even back in the days of owning a web site cart in downtown Natick. Back then, my business partner and I made all natural HTML roll-up web sites and, as an incentive for customers to wait in line, we baked Drupal into different flavored designs.

Custom Trainings

We can modify any of the above courses to best suit your needs! We are also capable of teaching about many other aspects of Drupal. Look here to get a better idea of our teaching experience and expertise and how we can craft custom trainings for you and your team.

Why Agaric

Clients and colleagues know Agaric developers for taking on the hard tasks when we collaborate on larger teams. We combine this expertise with the desire to raise people up. From our first projects fifteen years ago, our goal has been to make our clients need us as little as possible, to put as much power as possible in our client's hands. That is why we started using content management systems in the first place, and it is a tradition we uphold through developing with free/libre open source software, through writing documentation and blog posts, and above all through providing trainings.

Agaric is active in the Drupal community at-large and has presented at various Drupal Camps. We have also taken initiative in organizing Global Training Days in Nicaragua since 2013.

Building the open web

In preparation for Agaric's migration training at DrupalCon Seattle, we've seen again that getting a development environment suitable for working on Drupal 8 with Composer is a big road block. For that reason, here are instructions for getting it all going, suitable for our training or for working on Drupal in a code sprint, with only one hard requirement: PHP.

Three beach shovels standing up in the sand next to a pail.

Getting a local development going is a problem for everyone, including programmers and people who should be skilled at this. Vagrant and DrupalVM were created to make identical development environments work on any computer. Unfortunately, that's more a pipe dream than a promise, as our own experiences and support requests we've received can attest,

Docker is another attempt to make local development match production environments, and a newer generation of Drupal-adjacent development workflow tools, such as DDEV, Lando, Docksal, and Humpback, build on it. Using an online development environment is also an option, but has too much reliance on working WiFi for conference situations.

The goal is any Drupal development environment—any of the above or anything else—where you can go to your project root directory in a terminal and type, say, composer update and have If you don't have a local development environment of any kind, here is the minimalist approach. All the steps start with opening your terminal.

El Reto

350.org necesitaba su herramienta de mapeo para transmitir la amplitud impresionante de la huelga climática mientras emergían rápidamente eventos cerca de los partidarios. Principalmente a través del poder voluntario, tenían una versión inicial de la herramienta en funcionamiento, pero carecía de las características necesarias para que los organizadores se movilizaran en la escala que exigía el ataque climático.

Trabajamos con el equipo de producto 350.org para refactorizar el Javascript personalizado para usar React.js, un marco popular y fácil de usar, agregar parámetros de código de inserción para los organizadores y mejorar la experiencia del usuario para los huelguistas climáticos. El resultado fue una herramienta que ayudó a sacar a unos 4 millones de personas posiblemente en la acción de justicia climática más grande de la historia.

 

Agaric, as a worker collective, does not have bosses and employees. We have skilled, hard-working teammates coming together to figure out and do ... everything.

We will make an exception to hire an excellent business director, project leader, attention-to-detail-and-the-big-picture person. If you happen to be a front end dev too, then great! If not, well, part of your role will be helping bring on more talent.

In addition to forging grand coalitions and leading amazing projects, we need help keeping track of invoices and payments and doing financial planning, managing people's skills and availability, and writing role descriptions way better than this one.

We want someone who expects within six months of joining us to have helped make things 300% more awesome. As a principal or a hired boss, part of this role will be making the decisions of what to prioritize, and saying no to potential projects that don't fit.

OK we'll just say it: We want someone to be Agaric's Liza Kindred.

Want to be part of something that's bigger than yourself, that works on projects and ideas bigger still?

Agaric's model is Free and Open: free and open standards, free and open work and management, free and open source code, free and open documentation. So be prepared to help us share everything we build, as a collective company and with code, to the Drupal community and beyond.

Agaric is not just about doing web work as a collective. We work on interesting, exciting projects (both client work for solid financial compensation and our own platform-building initiatives for dreams of riches). We then, also collectively, take some of the resources, skills, and connections we gain in this work to help build tools, networks, and open learning projects that change the world for the better. We see tremendous potential for a better world by helping people gain more control over their own lives, and open source free software is both a metaphor and a tool for how we can better lives.

We welcome serious and/or comical inquiries.

As big tech continues to violate our privacy, thwart worker power, collude with militaries and deportation agencies, we need to move to ethical tech tools we can trust.

However, it can be intimidating to make the switch to new, unfamiliar tools.

Micky is leading two workshops to help people make the switch.

“How to Switch to Free Software: Email” 4:45-6:45pm Wednesday, December 4

Micky Metts of Boston’s Agaric Tech Cooperative will help us get out of the fix. The key to regaining security and control of the internet is switching to free software equivalents to proprietary/corporate software for communicating – among many uses.

This first workshop focuses on communications using email and texting software. The moderate inconvenience of switching is worth the privacy of strong encryption and the freedom of a new world of user-controlled communications and organizing. This first workshop in Sala Quetzal focuses on email and texting with encrypted software under user control. Bring your phone.

“How to Switch to Free Software: Browsers Etc” 2-4pm Thursday, December 5

A professional software developer, Micky, will focus on this second workshop, also in Sala Quetzal, on browsing, searching, and virtual meeting software. She will show how free software opens up the world of “platform co-ops” – think of Uber under drivers’ control and AirBnB under homeowners’ control.

Micky will be assisted by at-the-elbow translator/helpers. Bring your laptop and your phone.

""

Upgrade from Drupal 6 or 7 when it is right for you

In the era of modern Drupal, release cycles of major versions have only minor importance

Notes

Slides - https://github.com/fiqus/FIT-talk-en

## FACTTIC - Argentinian Federation of Tech Cooperatives
* Members-only mailing list
* Mattermost (open-source chat)
* Monthly virtual board meeting (any member can attend)
* Annual face to face meetings

## FIT
* A project within FACTTIC where coops share the status of projects they are working on
* Evolved to an area where coops share projects
* To join FIT, you need to be a FACTTIC member
* Monthly virtual meetings
* Mattermost channel for ongoing dialog
* Coops have different skills/services, but when there is overlap, try not to compete with one another and determine the 'needs' of each coop.

### Scenario 1: Project demands more workers than coop has
* When there is a need for help, project is shared in FIT
* Coops can apply to join the project
* Candidates are evaluated and one is chosen
* Client is told and must agree
* Project coordination is led by initial coop
* Commercial agreement is handled only by initial coop

### Scenario 2: Client needs work done, but coop decides not take it
* This might happen because initial coop doesn't have the resources or declines for a strategic reason
* Project is shared with FIT
* If no coops are interested, the client is told no one is available.
* If one coop is interested, that coop's contact is shared with the client.  
* If more than one coop is interested, then we ask, does this project require more than one worker?
  * If it only needs one worker, then the coop who needs it most receives it
  * If it requires more than one worker, then the coops coordinate with one another to complete the work.

## Case Studies

### Betterez
* Canadian client
* Reservations and Ticketing Management Platform
* Technologies: MongoDB, NodeJS, VueJS and Elixir
* Needed more work than Fiqus could provide
* 30 developers with 7 different coops
* Fiqus manages financial questions such as the different rates for different services

### Receptivi
* Canadian client
* Website shows real-time psychological insights of staff
* Had more work, but Fiqus declined to take on the work
* Work was shared in FIT
* 3 developers from 2 coops

### Mall Plaza
* Chilean client
* Mobile app showing mall services
* Tech: React Native, PostgreSQL, Flask

## Onapsis
* Argentinian client
* Web system showing vulnerability alerts on servers
* 2 coops

## International FIT
* Ww want to replicate this model on an international level
1. Share this model with others in order to improve it and spread awareness
  * Presenting at Show and Tell
2. Build trusted relationships
3. Get to know each other in person, spend time together
  * Traveling to the UK, meeting with the federation, COTECH
  * Share experiences after trip

## Questions and Answers:
Q: Have you ever had resistance from a client when handing off work to another coop?
  A: There are times when clients don not understand coops and cooperation among coops. We explain the benefit and share case studies. If there is a deadline that needs to be met, it is faster to bring a team on with prior experience working with the original company than trying to find a completely different company.
Q:  How much do you share about multiple coops working on a project?
  A: If it's only a few hours, it's not worth talking about. However, most of the time it's important to share that information and use it as an educational opportunity to demonstrate the strength of coops working together.
* Once clients see the outcome of cooperation they realize it is a good way to approach work.    
* The simplicity of the process is beautiful.
Q: How do you share business development costs?
  A: The coop sharing the project might lower their rates during the ramp up process.
  * This is an aspect that could be improved.
  * The most important thing is to be transparent and communicate a lot.
  * Keep the spirit of generosity flowing.
* When the cooperation is successful, it builds trust with the client.
* Use a tool to analyze project budgets and progress and forecast availability.
* Cooperation also ensures quality, trusted workers will join the project.