Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

switching to a neutral indicator for missing tracking issue #59

Closed
wants to merge 1 commit into from

Conversation

oodbur
Copy link

@oodbur oodbur commented May 6, 2017

at least to me, the motivation for calling a missing feature request in a ticket tracker a sad thing is a little mysterious. i guess a software project could be organized without using an issue tracker and still do a good job. or someone could send a patch without first opening an issue...
so here i propose switching to something neutral for that.

@bascht
Copy link
Owner

bascht commented May 8, 2017

I disagree. No matter if it's a closed source or FLOSS project, I think it is sad if progress / current implementation work on OMEMO isn't documented anywhere for users to track progress / find a time line. I think what could also work, would be a ❓ Emoji. Wdyt?

(And I think we could even add a 😭 smiley for Coy.im: coyim/coyim#233 (comment))

@bascht
Copy link
Owner

bascht commented Jun 1, 2017

@oodbur *bump*

@tdemin
Copy link
Contributor

tdemin commented Aug 22, 2017

Tracking can be done with something other than issues, e.g. "What's New" section on Play Store. If we speak of tracking, we should replace "Tracking Issue" with just "Tracking" or something.

@bascht
Copy link
Owner

bascht commented Aug 22, 2017

@tdemin Makes sense. It worked for the first few OSS clients, but not every client has a public issue tracker. The link should point to what ever URL answers the question »What's the current progress for this client«.

@ReneVolution
Copy link
Collaborator

Sorry for being late to the party here. From my point of view, the 😢 is more of an indicator that we were not able to find that information and so absolutely on point. As we want to provide this information to our users, it is sad for us being unable to provide these.

@nogweii
Copy link
Contributor

nogweii commented Oct 7, 2017

IMHO, I think using ❓ for when we couldn't find an issue and 😢 for when the developers have decided against it makes the most sense. (Maybe even 🎉 once a client is at 100%?)

@tdemin
Copy link
Contributor

tdemin commented Oct 7, 2017

Agree with @evaryont. Not implementing OMEMO because of stuff is a thing that makes us sad. 😢

@bascht bascht closed this in #103 Apr 13, 2018
bascht pushed a commit that referenced this pull request Apr 13, 2018
Now clients will show 1 of 4 different symbols depending on the
situation:
- OMEMO support is completed
- OMEMO support is in progress
- We don't know what the state is (missing public tracker)
- The client has decided to *not* implement OMEMO (?!?!)

Expands on the completion and declined states in a full sentence in the
client details page.

Adds a Coy.im client file both to record the situation and demonstrate
the new crying logic.

Closes #59, #96, #106, #83.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants