culture's Introduction

Holiday Extras Coding Culture

Overview

This is a collection of documents that outline Holiday Extras' culture and developer expectations.

Best practices

Process

Templates

Other

Contributing

Anyone associated with Holiday Extras, including our customers and partners, should feel free to create a branch or fork and submit a pull request with additions, updates or deletions. That being said, we do expect anyone contributing to our culture to watch out for a few things.

Edits should attempt to avoid fallacies and cognitive biases when making their cases for inclusion of contributions. We prefer to follow objective data and arguments.
We use Markdown syntax to format these documents.

The PR template in this repository is targeted at code changes, so we'd suggest something simpler if you're looking for something to use when opening a pull request to add documentation here:

# What does this change?
# Why?

Pull requests to this repository are open to input / discussion / agreement by all, there is no requirement of approval by a fixed number of people with specific roles as in the template for code changes.

If an update or addition refers to a process or technology which is, or is to be, implemented by the group, please ensure that the PR includes applicable reviewers from of each part of the group and notify a member of the group tech panel to discuss appropriate handling of the change.

If a PR has been open for several days with no unresolved comments, or it's otherwise clear from comments many people have had the chance to read and agree, we should consider it good to merge; further changes can always be raised through additional followup PRs.

culture's People

Contributors

Stargazers

Watchers

culture's Issues

Raising JIRA's

I was wondering if we should have a document around raising JIRA's. What is required? How to label correctly etc?

Wanted to know thoughts around this.

Should we integrate guilds into our culture repo?

Now that we've implemented guilds across the web team should we have a folder in the culture repo dedicated to guild related documentation? For example, each guild could have it's own markdown document where their current aims and achievements could be listed. We could even have a separate repo. I just want to get some ideas to help give transparency to each guild and allow everyone to get an overview on each guild's focus and progress. Any thoughts?

holidayextras / culture Goto Github PK