search

srobo / dev-team-proposal

Proposal for the Dev Team
0 stars 0 forks source link

Add draft dev team proposal #1

Closed trickeydan closed 5 years ago

trickeydan commented 5 years ago

This is the proposal for a Dev Team, based off Andy Busse's original and modified by myself, Tyler and Kajetan.

PeterJCLaw commented 5 years ago

A separate thought has just occurred to me -- we have quite a lot of repos which have their own issue trackers (and in some cases sort-of incumbent maintainers). We should consider how those would interact with the Dev Team.

Do we expect all bug fixes to go via the Dev Team? Would we allow for a continuation of the current setup with maintainers? I'm not sure that this needs to be completely solved now, though we should definitely aim to recognise those already in these roles and not displace them unnecessarily.

Edit: I've moved this into #3 so we can have a threaded conversation there.

PeterJCLaw commented 5 years ago

Another thought (which I've raised as #4, but posting here for visibility, please discuss there): how do we incorporate non-technical changes? For example, we know we'd like to drop media consent forms, but doing so requires considerable investigation into the legal aspects.

RealOrangeOne commented 5 years ago

how do we incorporate non-technical changes

My suggestion is we don't. Not all operational changes need to go through the dev team. The example of the media consent should be added to the tasks repo, and any volunteer pick it up and look into it. It doesn't need the dev team at all.