Activity eligibility

Ideas Crew Input
1

Sub-topic of Club / Crew / Group / Team

The core question here is:
Which activities should apply to the Crew?

The biggest issue to consider is the situation where someone joining the Crew has already completed the city. This would have the most impact on the Crew, overall.
Another aspect (less of an issue, and more of something that needs to be considered while making the decision) to this is that there are different reasons for each Crew to exist - there could be 1-3 people who want to complete their city together, and there could be a big running group in a large city that want this social layer added to their fun.
Yet another aspect to this is that these decisions also affect if/how competition between Crews plays out. For example - If a CrossFit gym and a TRX gym in a city both create a Crew, then the competition between the two might not be as fair unless they both chose the same start date (or if the overall decision I make on how all this works makes that decision for them).

After thinking about it for a while, I’ve come up with these options for deciding which activity data to allow in:

A) Everyone’s full history is applied to the Crew
I like this, theoretically, because it allows for a full history view of a Crew’s accomplishments. None of the other options allow for that. On the other hand, if nobody wants that - if that’s not what people are using Crews for - then it’s not actually a benefit.
If a Crew wanted to do something time-specific, then I could work out Crew-specific Challenges where it’s the Crew that joins as opposed to each person. This feels clunky, though, because the default view would be the full history - this could make it odd/confusing for people joining & thinking they were helping finish a city together.

B) The Crew has a start date field, which sets the earliest activity date for joining members
This has the potential of having all the same problems as A, because the Crew could be created with an early enough start date that would allow for a 100% person to join & ruin all the fun. :laughing:
This would address the likelihood that there are already groups out there who have been tracking themselves manually some other way for some amount of time. I don’t know if I’m making this up, though, so speak up if this sounds like you.

C) Only activities created after the person joins the Crew are applicable (so a Crew could be created today, and someone could join a year from now & that year of activities would not apply to the Crew)
This is pretty clean, and probably the least intense version as far as all of my work is concerned (it removes the possibility that a Crew is created with tons of historic processing to do). I’m unsure if it places late-joining Crew Members at a disadvantage or if it’s a welcome aspect.

D) Only activities created after the date the Crew was created are applicable (so a Crew could be created today, and someone could join a year from now & that year of activities would apply to the Crew)
This is similarly clean, but could be a bit stressful for very active people joining older Crews.

E) Allow each Crew Member to set their own start date & allow Captains/Owners to adjust people’s date (and also lock it, so the member cannot change it back) (I do not want to build this :rofl:)

I’m still kind of in an observation state, not really holding a strong opinion yet, but I kind of think that C might be the best place to start.
:sweat_smile: It does feel like it’s going to be an “all of them” situation, since I imagine many different people will have many different uses/reasons.

Let’s discuss the options … share other options, if you think of any … and after it feels like the options are solidified, I’ll set up a poll to get some solid numbers.

2

I am not completely sure I understand correctly but you’re talking about challenges inside crews? In that case the eligible runs would for me differ on the scale of the challenge. Like running a small town would benefit from a fresh start while a when trying to cooperatively run an entire region, i would prefer the whole history to be accesible. So for me option B would be the best.

3

I’m only referring to Crew-specific Challenges in the first option, where everyone’s full history is automatically processed for the Crew’s overall progress. The reason this “Crew Challenge” would exist is to account for the possibility of someone joining the crew who has already completed the city in question. This “Crew Challenge” feature is not built, so it can go in many directions.
From the perspective of “A Crew is attempting to complete a city by combining the efforts of all its members” the Challenge would provide a start date and city choice, and the stats would be based on the overall efforts of all members.

Yeah, a single-city goal and a multi-city goal are wholly different approaches to how a Crew can be used. In that sense, options B and D are effectively the same from the User’s perspective. Every Crew could have a default start date of whatever “today” is while creating the Crew, with the option to change it to any arbitrary date.

Another aspect to this decision (which I’ll add to the first post) is that these decisions also affect the possibility of competition between Crews.
For example - If a CrossFit gym and a TRX gym in a city both create a Crew, then the competition between the two isn’t fair unless they both chose the same start date (or if the overall decision I make on how all this works makes that decision for them).

4

My idea for creating teams or groups was to make an accumulation of all the streets traveled by all the members.

Speaking of my case, the different members of the sports club are from different cities and together we can accumulate a large number of streets and finish different cities together.

So my idea was more that each group would be like a user in the current statistics. So you can say that your team has jointly traveled X streets, completed X cities, and other Global Rank, Percentile, Regions and Countries data.

That was my original idea. Given the proposal of competition between members of the same group. I would make it simpler, transferring the global ranking only with the group members.

But the idea is to create a certain competitiveness. An option would be to reset every January 1, and each calendar year see which member has traveled the most streets throughout the year. And starting from 0 every year. So that not only the real new streets of the general profile are useful. This could be the generic competition.

Another option is that each team can define their dates to see who completes the most streets in a certain time.

I hope my views are useful.