User login

Being Agaric

You have to want to do amazing things with Drupal. You have to be dreaming big.

Forget Drupal (OK, not really). An Agaric has passion for doing what is right for the web, and for the collective, for the people of the world off the web, too.

Building a company is a lot of work; building a collective company may be harder. None of us want to knock ourselves out only so someone can make money. That's great but if that's your primary goal, there are lots of opportunities out there in Drupal right now.

(This has my own notes and my notes on others thoughts -- Kathleen and Dan so far -- which, sadly, filtered through my ears, brain, and fingers, become even more scattered.)

Someone we work with becomes an Agaric, a member of the collective, when?

unbilled hours at the meetings and whatnot
taking steps to make Agaric better

we could have agaric e-mails [be a marker of being a member of the Agaric collective until the formal organizational structure reflects it, we're thinking vote in by supermajority, maybe we'll be sold on consensus, but one important aspect of our collective model is that you don't have to be sold on living in a cubicle with someone]

Based on Kathleen Murtagh's notes and questions, What does it mean to be "An Agaric"?:

  • What does it mean to work with Agaric? What does it mean to be on the Agaric team?
  • Voting rights for the direction of the company? Who can make suggestions and be on the discussion, or not be involved at all? What would a "voting right" mean? How do we decide who has it, voting ourselves in?
  • Should a consultant get an email address? Or is branding as an Agaric part of being on the team? Or would not giving out email addresses be confusing to clients and branding as one face to them?
    • should be obvious
      if someone's constantly working with us, bringing us business- why don't you have an Agaric e-mail?
  • Would we have two e-mail and IRC channels -- one each for internal business and one for everyone involved? Or would someone who is involved at all be able to hear our discussions and put in their two cents?
    • Seems like we will need both. The default, "all", everyone connected to Agaric willing to receive communication gets to see in and weigh in when feeling like it. We'll also need "collective" so that there's a standard, set way of communicating with the Agaric core.
  • Should we have "veto" capabilities where one person can deny someone else joining? Or should it be completely organic, and we group and coalesce at will?
  • Should we appraise a person's personality and ensure they are the type that will promote the Agaric ideals? What are those traits? A strong desire to make the web a better place... a strong feeling of teamwork... a good work ethic... seeing it is all more than the money, but doing what is right.... How would we agree a person has these traits?

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Syntax highlight code surrounded by the {syntaxhighlighter SPEC}...{/syntaxhighlighter} tags, where SPEC is a Syntaxhighlighter options string or "class="OPTIONS" title="the title".
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.