WikiLove/Idea Log

PUBLIC LAW 104-201—SEPT. 23, 1996 110 STAT. 2519 "3963. Highest grade held satisfactorily: Reserve enlisted members reduced in grade not as a result of the member's misconduct.". (b) NAVY AND MARINE CORPS. —(1) Chapter 571 of title 10, United States Code, is amended by adding at the end the following new section: §6336. Highest grade held satisfactorily: Reserve enlisted members reduced in grade not as a result of the member's misconduct "(a) A member of the Naval Reserve or Marine Corps Reserve described in subsection (b) who is transferred to the Fleet Reserve or the Fleet Marine Corps Reserve under section 6330 of this title shall be transferred in the highest enlisted grade in which the member served on active duty satisfactorily, as determined by the Secretary of the Navy. "(b) This section applies to a Reserve enlisted member who— Applicability. "(1) at the time of transfer to the Fleet Reserve or Fleet Marine Corps Reserve is serving on active duty in a grade lower than the highest enlisted grade held by the member while on active duty; and "(2) was previously administratively reduced in grade not as a result of the member's own misconduct, as determined by the Secretary of the Navy. "(c) This section applies with respect to enlisted members of Applicability. the Naval Reserve and Marine Corps Reserve who are transferred to the Fleet Reserve or the Fleet Marine Corps Reserve after September 30, 1996.". (2) The table of sections at the beginning of such chapter is amended by adding at the end the following new item: "6336. Highest grade held satisfactorily: Reserve enlisted members reduced in grade not as a result of the member's misconduct.". (c) AIR FORCE.— (1) Chapter 869 of title 10, United States Code, is amended by inserting after section 8962 the following new section: §8963. Highest grade held satisfactorily: Reserve enlisted members reduced in grade not as a result of the member's misconduct "(a) A Reserve enlisted member of the Air Force described in subsection (b) who is retired under section 8914 of this title shall be retired in the highest enlisted grade in which the member served on active duty satisfactorily (or, in the case of a member of the National Guard, in which the member served on full-time National Guard duty satisfactorily), as determined by the Secretary of the Air Force. "(b) This section applies to a Reserve enlisted member who— Applicabihty. "(1) at the time of retirement is serving on active duty (or, in the case of a member of the National Guard, on fulltime National Guard duty) in a grade lower than the highest enlisted grade held by the member while on active duty (or full-time National Guard duty); and "(2) was previously administratively reduced in grade not as a result of the member's own misconduct, as determined by the Secretary of the Air Force. "(c) This section applies with respect to Reserve enlisted mem- Applicability. bers who are retired under section 8914 of this title after September 30, 1996.".

This is the idea log for WikiLove.

High priority

 * Throttle WikiLove (perhaps only for autoconfirmed users)
 * "Slow down, cowboy. Excessive use of WikiLove can be distracting. Did you perhaps mean to leave this user a message?"
 * Since we already know when the last time the user gave wikilove (it's in our tracking tables), we can do a timeout. Alternatively, though, it may just be easier to set an expiring cookie on them and check for the cookie's presence or absence to allow tool use.  Something like "WikiLove_Throttle", expires in 5 minutes.  Saves us a database access call.
 * Justification: If WikiLove becomes associated with spamminess or problematic new user behavior, it'll generally lose some of its appeal. So some basic throttling seems like a good way to mitigate that risk.
 * Anti-justification - people like to do a batch of thanking actions, that's cool too.
 * Improve handling of "self-love"
 * Perhaps friendly indicator that you're sending a public message to yourself, so that users don't assume it's a "Decorate your own page" feature
 * Perhaps easy undo feature if it's doable.
 * Justification: We see lots of this on new user talk pages, which may generally associate the feature with "lack of wiki experience" more than we'd like. Some of it is to be expected, but some of it may be the result of users not realizing that it's a public message, or not knowing how to remove it after they've posted it.

Make Your Own:
 * Parse Commons URLs, not just filenames (user tests show that users try URLs)
 * Justification: This really should work.
 * Add brief explanatory note pointing users to "new section" link to reduce confusion of users who use WikiLove for leaving messages
 * Don't autofill filename for "Make Your Own" (part of the reason we're getting so many trophy messages)

Medium Priority

 * Preference for users that don't want to receive WikiLove (perhaps just use existing pref to disable both sending & receiving)
 * If we do this, we need to still show the heart icon; just disable it (grey it out). Maybe clicking the icon will pop up a small tooltip saying that the user does not wish to receive WikiLove.
 * Justification: Again, one of the main ways to mitigate frustration or annoyance with the feature.


 * Develop some well thought-out "Welcoming" functionality, e.g. with WikiProject invitation or "request my mentorship" support
 * Use a simple category model to organize templates so they don't have to be stuffed into the JS config file?
 * Justification: Very strongly relates to our key priority for this feature (new user engagement). But, somewhat hard to do well (Twinkle already has basic welcoming templating features which are very popular).
 * en:User:Technical 13/Scripts/ACC WikiLove.js may be of interest towards this.

Configuration:
 * Maybe a version of WikiLove could be built for Commons that leaves a barnstar or similar for the creator of a file, without leaving the file page.  -- idea from Sage Ross,foundation-l/2011-August/067301.html
 * Make messages in config localizable

Make Your Own:
 * Gallery-driven version
 * Justification: Could be a quick way to increase the appeal/utility for experienced users.

Low Priority

 * Handling of adding WikiLove to subpages: either allow or let user know with warning/confirmation
 * Suggested text for message box
 * We need to do this with HTML5 placeholder attributes.  Otherwise, the suggested text will nearly always be what is sent.
 * Change previews immediately as you cycle through dropwdowns

Configuration:
 * Create "config packs": GLAM WikiLove, Science WikiLove, Goth WikiLove, etc.
 * ♥! That could be really cool.--Eloquence 01:33, 6 July 2011 (UTC)