User Details
- User Since
- May 8 2015, 5:17 PM (496 w, 1 h)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Resident Mario [ Global Accounts ]
Dec 28 2016
Yes, please do. There is still one thing I want to see, which is what the notification will look like when a new issue is announced.
Dec 27 2016
The technicals look good. I only have one question on this front: will this extension allow cross-wiki notifications? This would be a very important feature for such a tool to have.
Dec 23 2016
Howdy, was wondering if I could get a status update on this from you folks. I remember being involved in some of the original trials (as a test user) way back in mid-2015. I admit I'm surprised this is still in seemingly active development: I expected that the GSoC projection would either complete then and there, or that the feature would eventually disappear into the bugtracker. So my inquiry: realistically speaking, what are the chances that this feature will push by, say, mid-2017?
Jan 15 2016
After re-doing setup it's up again. Hopefully I just missed a step somewhere and didn't realize it.
@valhallasw This is a continuation on the 500-or-404 error that we discussed a week or so ago, do you remember more of the particulars? I don't think either of us filed a bug report for it after everything started working again when I turned debug on and then off again.
According to the cross-filed issue on GitHub this module was intended to be 3 only. This is a bit of an issue on Labs but this is a design specification, not a bug, so I'll close it now.
Jan 12 2016
Thanks, I've gone and done so. Again, apologies, a little unfamiliar with what project maintains these tools.
@Aklapper Apologies, being unfamiliar with the organization of Phabricator tasks (well, with what place this toolset occupies in it) I was unsure of where to place this bug. Thank you!
Jan 11 2016
@Milimetric Can you push this change? It doesn't look like I can create pull requests against the GitHub codebase.
I've clone the code and dug through it a bit and figured out the bug. At line 109 within the article_views definition:
Jan 10 2016
Oct 20 2015
Thanks to some wonderful sleuthing this problem has now be resolved!
Oct 19 2015
Aug 28 2015
See also T3126.
Aug 25 2015
@Qgil Unlike communications interns, tech interns create products that the community has to rely on in the long term. But will the Foundation commit to maintaining this extension in the long term?
Aug 23 2015
I think that Romaine is implicitly criticizing a problem that's plagued the movement for a long time: outside contractors are brought in, write a feature, and then leave. No offense to you, Tinaj, but I highly doubt that say three years from now you will be maintaining this codebase, or even contactable.
Jul 31 2015
I suggest that the best approach would be to have all templates stored on Meta with individual languages' translations stored as subpages using Meta's translation facilities. As here, for example. There could be a new template transclusion prefix ({{iw:Template}} for instance) which returns the appropriate translation subpage based on the language settings of the current wiki.
Jul 6 2015
I tested it a bit. Looking good so far! I do wonder if a short tagline could not be added to the Echo notification (something along the lines of "In this issue: see what really goes in the Phabricator"), but other than that it's already a dream come true.
Jun 19 2015
I suggest that per Amire80, cross-wiki templates be made a blocker bug for this feature.
Jun 12 2015
This task is imho perhaps the most important piece of independent development that could be performed at this point. I'm thinking in particular about the new Graph extension, the rolling-out of which is bound to result, over time, in hundreds of different Lua wrappers on all the hundreds of different Wikipedias. Surely it would be better and more expedient to have one set of commonly agreed-upon and styled wrappers hosted on Meta accessible to all?
Jun 11 2015
Indeed---be very careful about scope creep.
Jun 9 2015
Hi, here from the Signpost editorial board. You asked for our feedback on the proposed technical features, and here is what I have to say on the topic of newspaper delivery: