Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/AgileVentures/WebsiteOne

A website for Agile Ventures
https://github.com/AgileVentures/WebsiteOne

agile cucumber heroku open-source opensource rspec ruby ruby-on-rails

Last synced: 3 months ago
JSON representation

A website for Agile Ventures

Awesome Lists containing this project

README 

        
# AgileVentures WebSiteOne



[![Maintainability](https://api.codeclimate.com/v1/badges/8bbffaef68e73422ca40/maintainability)](https://codeclimate.com/github/AgileVentures/WebsiteOne/maintainability) [![Test Coverage](https://api.codeclimate.com/v1/badges/8bbffaef68e73422ca40/test_coverage)](https://codeclimate.com/github/AgileVentures/WebsiteOne/test_coverage)



## Legacy code



This [Ruby on Rails](http://rubyonrails.org/) app powers the [AgileVentures main developer site](http://agileventures.org/), showing lists of active [projects](https://www.agileventures.org/projects), [members](https://www.agileventures.org/users), [upcoming events](https://www.agileventures.org/events), [past event recordings](https://www.agileventures.org/scrums), as well as information for how to [get involved](https://www.agileventures.org/membership-plans).



## Installation



See the [Project Setup](docs/project_setup.md) documentation



## Contributing



See our [Contribution guidelines](CONTRIBUTING.md)



## History



in 2011, inspired by Dave Patterson and Armando Fox's UCBerkeley Software Engineering Massive Open Online Class (MOOC),  Sam Joseph had the idea for a global online pairing community where everyone worked together to use the agile development methodology to deliver solutions to IT charities and non-profits.  Thomas Ochman joined as project manager and led the development of the WebSiteOne codebase with Bryan Yap serving as technical lead.  Initialy Sam was the notional "client", not getting involved in the tech development, and many different volunteers contributed code.  During this phase the events, projects and user systems were developed.  There was also a blog like articles system.  Yaro Appletov led a tight integration with Google hangouts to allow recordable hangouts to be launched from the site and report back telemetry.



Later Raoul Diffou joined to take over as project manager as Thomas and Bryan had less and less time for the project.  Sam took over the technical lead role in 2016 and also stared pairing with Raoul as project manager.  Later in 2016 as Raoul had less and less time Sam became the sole project manager.  During the course of 2016 Sam and long time AV contributor Michael revised the events framework, and replaced the articles system with a Premium payments framework intended to help ensure AV was sustainable into the future.  In 2017 Google withdrew their Hangouts API breaking various functionality in the site.  Sam and Lokesh Sharma replaced the API integration with manual updates, and Sam pulled in the agile-bot node microservice so that WSO now communicates directly with Slack to alert members about new online meetings and their recordings.  In 2022 AV contributor Matt Lindsey did some cleanup by replacing the mercury document editor with active text and updated the asset pipeline.



## Approaches



* Agile Development

  * In the past we had regular sprints, offered daily standups, and got regular feedback from end users.  We have discussions on Slack and occasional meetings now.

* Behaviour Driven Development (BDD)

  * We use Cucumber and RSpec testing tools that describe the behaviours of the system and its units

  * We try to work outside in, starting with acceptance tests, dropping to integration tests, then unit tests and then writing application code

  * We do spike application code occasionally to work out what's going on, but then either throw away the spike, or make sure all our tests break before wrapping the application code in tests (by strategically or globally breaking things)

  * Where possible we go for declarative over imperative scenarios in our acceptance tests, trying to boil down the high level features to be easily comprehensible in terms of user intention

* Domain Driven Design (DDD)

  * Sometimes we switch to inside out, trying to adjust the underlying entity schema to better represent the domain model

* Self-documenting code

  * We prefer executable documentation (tests) and relatively short methods where the method and variable names effectively document the code



## Reading material



* [Imperative vs Declarative Cucumber](http://fasteragile.com/blog/2015/01/19/declarative-user-stories-translate-to-good-cucumber-features/)



## Admin rake tasks



```bash

rake fetch_github_last_updates

rake fetch_github_languages

rake fetch_github_content_for_static_pages

rake fetch_github_readme_files

rake fetch_github_commits

rake karma_calculator

rake geocode:all

rake user:create_anonymous

rake vcr_billy_caches:reset

```



Updating the live static pages (like 'About' and 'Getting Started') requires the administrator to run `rake fetch_github:content_for_static_pages.`