-
Notifications
You must be signed in to change notification settings - Fork 0
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
Profile Management #1
Comments
@tantek does proposed by @dissolve alternative version takes care of your objections? |
This revised version takes care of the questions / objections I originally noted, however since our telcon discussion 2015-03-31, it became clear that we don't actually need any kind of profile management in v1 of an API, thus I'd -1 the whole user story with the explanation, can postpone from v1, open to reconsideration for a v2 API. |
-1 to V2 +1 to the original user story The original user story got We've already implemented V1 in SoLiD and demoed it live at the F2F "Twitter doesnt do X" should not be a deal breaker for our user stories. |
@melvincarvalho, read @tantek's previous post on this thread. Also. API V1 is meant to be a minimum set of needed functionality to get an API out which means ideally focusing on cross section of all sites. As stated several times before the # of +1 votes does not matter. The idea is to get full consensus, not majority rule. |
Well what is clear is that there was a VERY strong consensus for this user story. We are unclear what v1 and v2 are, elf has raised this on IRC. The consistent message is that implementations count. This user story is now implemented and demoed. Also I beleive this is one of the ONLY user stories actually implemented and demonstrated live. So together with the very strong initial consensus, I think that is an important data point. |
original: https://www.w3.org/wiki/Socialwg/Social_API/User_stories#User_profile_management
proposed alternative: by @evanp https://www.w3.org/wiki/Socialwg/Social_API/More_user_stories#User_profile_management_V2 by @dissolve
The text was updated successfully, but these errors were encountered: