Gus Austin

Recent Activity

Filter 

Friday, March 10 2017

Wednesday, August 17 2016

  • 11:56am

    While the team behind Audience Engine have pushed back their release, we're now using OpenCollective an open source platform that actually provides us with all the functionality we need for collecting/distributing funds, crediting donors and sponsors, and possibly providing some sort of job board. In grand scheme of things, this functionality would be in the form of an Open Collective module that could be used for ourselves and anyone else who uses or develops Drupal. As we're already using and working closely with their team, I think this work would be funded by Open Collective and other stakeholders. 

    Probably a something that could be scoped out and developed on drupal.org.

Monday, July 25 2016

  • 5:21pm

    Per the recent convo in Slack, we have been given the green light to use OpenCollective to collect/distribute funds for a variety of ways including - 

    1. set up OpenProducer collective as a ‘supercollective’ or umbrella org to pool resources for ongoing managment and non-development actvities
    2. set up subcollectives for any projects (openproducer, station, airtime, etc.)
    3. set up subcollectives for regional sprints and meetups where people can build solutions for stations in their community as a way to learn; mentors can get paid (via sponsors) to do that work)

    A main requirement, aside from reading their FAQ, TOS, and supplying a logo/hero image for open producer (if we have), are the names, emails and github/twitter handles of core contributors.

    For the latter, we need to make sure we have goto leads for the roles referenced in the team page

    Based on that, I'd like to circle back to what your desired roles/rate/availability is... and the identify other folks who may be good candidates to fill out the team. My desired role/commitment remains largely unchanged as before.

  • 5:12pm
    Changes to Body
     
     
     
    In addition to the tasks we're already undertaking, here are some additional roles and skills we're seeking collaborators to help with:
     
    In addition to the tasks we're already undertaking, here are some additional roles and skills we're seeking collaborators to help with:
    -
      
    -
    * Project management
      
    -
    * Requirements analysis & information architecture
      
    -
    * Documentation
      
    -
    * QA & testing
      
    -
    * Theming & front-end development
      
    -
    * Design & UX
      
    -
    * Business development
      
    -
    * Mentoring, training, and curriculum development
      
     
     
    Read more
  • 4:34pm
    Too many differences to list. See Revisions for details.
  • 4:23pm

    The technical product manager is responsible for defining market requirements and packaging the features into product releases. This position involves close interaction with development leads, product architects, and key customers.  A strong technical background is required. Job duties include gathering requirements from existing and potential customers as well as recent evaluators, writing market requirements documents or Agile product  backlogs, and monitoring the implementation of each product project.

    Technical Product & Program Manager Tasks

    • Define resources and schedule for project/program implementation.
    • Define requirements and plan project lifecycle deployment.
    • Create strategies for risk mitigation and contingency planning.
    • Run complex projects/programs from design and development to production.
    • Plans and schedule project deliverables, goals and milestones.

  • 4:12pm
    Changes to Title
    -
    Design, UX
    +
    Visual Designer
    Changes to Body
    -
    This person may not know HTML, CSS or JavaScript. They specialize in visual design but with an understanding of the capabilities of Drupal which help them create designs which can be understood and implemented with their team.
    +
    Visual Designers create the look and feel of your site. On larger teams, designers don’t necessarily touch Drupal. However, if they understand The Drupal Way, they will be able to create more efficient designs which are easier to implement.
     
     
    Read more
  • 4:11pm
    Changes to Body
    -
    This person installs and configures modules to create site features. They will be knowledgeable about theming and development, but will mostly use Drupal through its administrative interface.
    +
    There may be multiple people completing the site building tasks on any given project. At the foundation of Drupal skills, site building is the most essential requirement for all development roles. Team members responsible for development should know the configuration of the most popular modules; content types and views; roles and permissions; navigation, menus, taxonomy; actions and workflows. They should be able to compare the best approaches in any given situation.
     
     
    Read more
  • 4:09pm
    Changes to Body
    -
    This person can interpret visual designs into code. They are experienced with the complementary skills of HTML CSS and JavaScript. They can use theme functions and may be able to create custom modules to implement hooks to create displays they need.
    +
    Front-end developers takes the visual designer’s work and turns it into a web page or interface. They program interaction with JavaScript and/or a library such as jQuery, YUI or Prototype. They test cross-browser, cross-platform, and/or cross-device compatibility for inconsistencies.
      +
    Themers are front-end developers with specialist knowledge of the theme layer in Drupal. They create sub-themes on common base themes and may create custom themes. This might not be a distinct role on many teams. Instead, a developer on the team might have this expertise.
     
     
    Read more
  • 4:07pm
    Changes to Title
    -
    Developer
    +
    Back-end developer
    Changes to Body
    -
    This person can code custom modules according to coding standards and best practices. They can test the quality and security of the code they write.
    +
    Back-end developers modify existing code and write new custom code to power the functionality of a Drupal site. A typical Drupal build will have two types of modifications which require custom code changes. Junior developers should be able to handle small changes in markup output. Senior developers will be required where there are integrations or new functionality in custom modules.
     
    An example: http://groups.drupal.org/node/66643
     
    An example: http://groups.drupal.org/node/66643
     
     
    Read more
  • 4:05pm
    Changes to Title
    -
    Technical Leads and Architect
    +
    Technical Leads and Architects
    Read more
  • 4:04pm
    Changes to Title
    -
    System Architect
    +
    Technical Leads and Architect
    Changes to Body
    -
    This person sets up and maintains the system and infrastructure on which Drupal is deployed. They can manage the migration of data and content. They also install and maintain access to the site and version control.
    +
    Technical leads and architects are back-end developers with broad experience with Drupal. They understand how to analyze and set requirements. They establish the high-level development strategy through module selection and configuration. They focus on sitewide concerns such as integration, scalability, performance, and security.
      +
    However, even these highly experienced experts wouldn’t be expected to know everything there is to know about Drupal.
     
    An example: http://groups.drupal.org/node/66638
     
    An example: http://groups.drupal.org/node/66638
     
     
    Read more