[FEATURE] Claim an issue

[sivakumar-kailasam]

• Allow someone to claim an issue for a week
• Reset that if it wasn't resolved (or didn't have a PR pending, haven't worked through those details yet)

[acorncom]

Per discussions with @sivakumar-kailasam we're thinking we'll have this info stored at the following location:

/issues/<issue_id>/contributors

The contributors hash would be an array with the following setup:

contributors: [{
    username: <string>,
    network: <twitter | Ember Slack | github>,
    createdAt: <ISO-8601 date>
}]

This gives folks the ability to say they want to work on an issue but also allows multiple people to work on it together (and to coordinate how to contact each other as well). See my prototyped code here (which also needs cleanup: https://github.com/ember-learn/ember-help-wanted/blob/master/app/models/item.js#L12-L39 😄 )

More details about how to save relationships can be found here: https://www.firebase.com/docs/web/libraries/ember/guide.html#section-relationships

On the backend, we'll end up having a tool that resets this field after a week or so based on the createdAt date ...

[acorncom]

Since the notes were made above, our backend approach has changed. We'll be using a JSON-API compliant backend, so should focus primarily on sending contributor information back to the backend as we add new ones.