I've always used enhancement for this purpose -- does phabricator
actually support this?
On Mon, Jun 8, 2015 at 10:33 AM, Gergo Tisza gti...@wikimedia.org wrote:
Hi all,
I would like to recommend a naming convention that clearly differentiates
between existing and wanted behavior. This is
On 8 jun. 2015, at 19:52, Jon Katz jk...@wikimedia.org wrote:
I think we could go a step further and call out bugs with the prefix bug:
for more clarity.
-J
Please also discuss such a thing with Andre and other Phab people. We only just
got rid of prefixes since we dumped bugzilla. It
Great find! Since we're mentioning similar features, the Google Dictionary
https://chrome.google.com/webstore/detail/google-dictionary-by-goog/mgijmajocgfcbeboacabfgobmjgjcoja
Chromium
/ Chrome extension (by Google) performs a similar function.
[image: Inline image 1]
--stephen
On Mon, Jun 8,
Good call, Gergo, and for calling out crap when you see it. I know I am to
blame on a lot of these (including the above example). I think the
language solution you described is pretty good.
restating suggested rules for those who don't read prose:
- bugs--explain bad state in present tense
On Mon, Jun 8, 2015 at 1:04 AM, S Page sp...@wikimedia.org wrote:
Maybe WMF should offer its own browser- or OS-level integration, pushing
the reading experience way beyond our sites.
https://en.wikipedia.org/wiki/Wikipedia:Tools/Browser_tools lists various
browser addons, such as Lookup
It might be easier to tag enhancements with enh: given that anyone can
create tasks and will not necessarily adhere to our standards. This would
at least solve confusion in whether things are bugs or enhancements.
On Mon, Jun 8, 2015 at 10:52 AM, Jon Katz jk...@wikimedia.org wrote:
Good call,
We made a bug ticket template that clearly asks for both “Actual Results”
and “Expected Results” to help with this.
T98466 https://phabricator.wikimedia.org/T98466
On Mon, Jun 8, 2015 at 2:25 PM, Derk-Jan Hartman
d.j.hartman+wmf...@gmail.com wrote:
On 8 jun. 2015, at 19:52, Jon Katz
+ Kouroush
A summary of ideas:
*WP as destination:*
-Sister projects swipable from cards
-WMF owned OS integration/browser add-ons
*WP as platform:*
-API for 'cards' on topics/JS library
-Make sure API changes aren't breaking experience for: apple, google,
amazon?
-Help kindle optimize their
Cross posting. Please reply directly to Dan or use the wikitech-l list if
responding.
-Adam
-- Forwarded message --
From: Dan Garry dga...@wikimedia.org
Date: Mon, Jun 8, 2015 at 3:54 PM
Subject: [Wikitech-l] Feedback requested on our search APIs
To: Wikimedia developers
