Sorry for the late response.  I've been focusing on work lately.

My apologies, as I didn't realize that the crowdmatch code was already
checking for this.  I'm surprised, though, that the decision was made to
hard code the value up front, as I don't think it'd be much more difficult
to add the value to each user in the db, default it to 5, and just access
that variable in the crowdmatch logic.  Even though users wouldn't be able
to change it up front, it would at least set up the framework for the beta
changes.  But, if hardcoding is the way we want to go fine.

I was checking to see if the UI to change the limit has been removed.
Unfortunately, the latest master isn't building, so I can't 100% confirm.
Looking at the template, it appears on quick glance that iko removed it.
Hopefully she did.  If that's the case, then I think this discussion is
wrapped up.

On Sat, Aug 5, 2017 at 10:56 AM, Aaron Wolf <> wrote:

> On 08/05/2017 08:07 AM, Bryan Richter wrote:
> > On Tue, Aug 01, 2017 at 07:37:59AM -0500, Jason Harrer wrote:
> >> Not sure how the dev list got removed, but adding it back in at this
> point.
> >>
> >> It sounds like there was consensus on this overall limit (just not
> project
> >> limits).  That being said, I'm going to open up a ticket on GitLab so
> we on
> >> the Dev team can track adding that in.  This is a requirement before we
> can
> >> get the Dashboard page finished.
> >
> > Can you explain why it's a requirement?
> >
> > As far as I understand it, the page simply has to say that a limit
> > exists.
> >
> > My point, that I'm making here and elsewhere, is that implementing an
> > automatic cutoff is not a necessary step for alpha. The process can
> > remain manual for the time being.
> >
> > There are a lot of other manual things I'd rather automate first.
> >
> >
> I agree with Bryan. The requirement is that the limit actually is
> respected, not that it be in the code per se. Since we face little
> real-world risk of hitting the limit during alpha and will know for sure
> if we're approaching it, we're fine. No extra requirement needed for alpha.
> For beta, it will matter more because people could then pledge to
> multiple projects and thus approach their limit with fewer patrons in
> the system.
> _______________________________________________
> Design mailing list
Design mailing list

Reply via email to