Allow repeat extensions

[marksteward]

For things like the bikeshed (https://london.hackspace.org.uk/storage/26), we want to allow repeat extensions. Each extension should probably be approved by someone who isn't the original owner (or maybe require multiple approvals?), and emails should be sent as usual.

The usual single-extension state should probably also remain, so I suggest a new state, Extended (recurring).

[chixor]

How do you decide who gets reoccurring and who doesn't? Isn't that like
gold membership?

But hey, up to you! :)

On Tuesday, 24 November 2015, Mark Steward notifications@github.com wrote:

For things like the bikeshed (https://london.hackspace.org.uk/storage/26),
we want to allow repeat extensions. Each extension should probably be
approved by someone who isn't the original owner, and emails should be sent
as usual.

The usual single-extension state should probably also remain, so I suggest
a new state, Extended (recurring).

—
Reply to this email directly or view it on GitHub
#124
.

[marksteward]

Was thinking a minimum number of people, rather than privileges. But then I guess that's sort of a popularity contest, so possibly problematic.

[chixor]

Maybe projects which have had 3 previously approved storage requests for
the same thing (based on an identical title and description) qualify for
reoccurring? Essentially it just reduces duplicates in the database but the
process is the same, it still goes up for approval.

On 25 November 2015 at 10:16, Mark Steward notifications@github.com wrote:

Was thinking a minimum number of people, rather than privileges. But then
I guess that's sort of a popularity contest, so possibly problematic.

—
Reply to this email directly or view it on GitHub
#124 (comment)
.