Fri, Nov 17
Yeah, we should really either deploy it to all the remaining ones with specific consensus soon and then follow up with the rest, or just... do them all and be done with it. These waits have probably seemed completely ridiculous to the actual users, and the worst that's happened anywhere so far seems to be header overflows, which just mean Timeless itself looks stupid.
Wed, Nov 8
Oct 17 2017
I submitted another grant proposal regarding getting financial support for Timeless: https://meta.wikimedia.org/wiki/Grants_talk:Project/Isarra/Post-deployment_support
Whenever the window for those wikis winds up being, could someone give me a heads up beforehand so I can be sure to be around to fix stuff? (Note: I'm back in the US now, and only awake this week between 15:30 and 3:30 UTC and I make no guarantees about being coherent or understanding a thing about what's going on even during those hours because I'm still apparently sick, but if stuff happens before then, I can also just deal with it once up, or stuff. If you don't actually need me around, that's great too. Thank you for bearing with me. I would like to stop being sick now.)
Oct 16 2017
Sep 26 2017
If you need me around, I recommend anything that's not US evening. Or next monday/tuesday. Other than that I'm not sure it matters too much.
Sep 12 2017
Yeah, it should appear where the edit link usually does. This is bug.
Aug 28 2017
But I don't want it to get lost, either.
Reopening because there's a bunch of new stuff on this and I don't have time to deal with it all right now.
Aug 25 2017
Unfortunately it might take awhile for me to sort this out, though. Need to actually find an IE10 somewhere, and such. (Maybe one of my vms has it, but this machine isn't even set up for that anymore.)
Wow. That's some impressive not playing nice, there.
Let's rip off bluesky (owl (wikihow))! :D
Aug 22 2017
Perhaps you might just remove the brackets icon while keeping the pencil?
It's based on username length. Too long usernames get replaced with the generic string, except it really doesn't take very much to be too long, so that turned out to be a bit silly.
Echo container issues again. May be related to how I was seeing the exact same thing when we were deploying to the french projects. I could have sworn this was fixed (twice!) but clearly not.
Also note that WMF colours have changed (again), so RGB usage for that may no longer be appropriate. Are we even going for WMFy-ness to begin with?
Alternatives: lose bar entirely, change to single solid colour.
Aug 17 2017
this is intentional design, not a bug.
Yeah, option to just disable the sidebars and use the screen-small layout (the with dropdowns) for all aside from actual mobile. There's precedent.
The problem here is a lot of things can cause stuff like that, and they
all break the header horribly. Ergh. What WOULD be good handling of
The issue with fr.wikt was basically just an on-wiki config thing exacerbating a really stupid general bug (T173525). It's probably not the only one that could use some adjustments, though, so I went ahead and requested global interface editor rights so I can maybe just fix these sorts of things as we go in the future (at least on projects I understand at all).
Make it more like bluesky.
Skin-specific preferences are totally doable - just add them the same way as any other extension. More of an issue is when/how to display them (only show when skin is even enabled, maybe?), not cluttering up the preferences further, the age-old issue of 'should it even exist', etc.
I mean, do fr.wiktionary and all the rest then, +/- dewp.
@matmarex, yeah, we definitely could have deployed it as was; I just totally forgot at the time what was actually causing the problem and was too tired to think it through. So caution. But it's safe to deploy as is, no problem. Would also make the on-wiki config change easier to sort out to actuallly have it there, too.
Aug 15 2017
Well, we could just move where the content wrapper encompasses, except
that all IS the page content, so perhaps not the best idea. If excluding
user-provided content is the idea, though, shouldn't there be a class
specifically for that? Or is that what mw-body-content is for? What if
you have multiple separated blocks of content?
Aug 14 2017
Sadly this was not entirely completed at wikimania, but it did come close.
Aug 13 2017
Coming to wikisources near you: en, fr, he.
Aug 12 2017
recent racist meme
Pepe the Frog
Or we could start with commons for maximum fallout.
Legoktm: Sounds good to me, but it'll be up to Dereckson or whoever to properly announce it. As much as we're surrounded by french speakers here, I'm not sure they'd be quite the right ones for this for the most part.
Aug 11 2017
Appears to be iphone-specific?
Tapping outside menu should close menu. It does not.
Well, there's still a chance it goes horribly wrong. I don't thiiiink it will, but...
Nope, we're doing it now! It's happening now!
Aug 10 2017
Okay, so my local environment is broken. Okay. Now to find out how to even update. Or what it was for to begin with!
I did git pull. Just now. It says it's up-to-date.
Also refreshed, but I don't have all the others downloaded.
Someone asked for a logo.
Aug 9 2017
Copyright holders is whoever edited it. Year is probably original and/or end date of maintenance.
Jul 25 2017
I love you.
Jul 24 2017
This isn't just timeless. I recall shoving jquery mobile into a bunch of skins for better mobile support, and I probably wasn't the only one (I believe I was copying another skin from the start) - do we have any quick way to check which all have this, or a version of this?
Lacking any response I'm just going to close this. The new tasks were all filed, so thanks for the input!
Jul 19 2017
So... are they effectively under MIT license?
Jul 17 2017
Jul 12 2017
Jul 11 2017
Jul 10 2017
How well would this actually work? Would it catch our common issues? Would it react badly to all the bad stuff already present? What about false positives where things are very much intentional/needed that it may not actually like?
Jun 10 2017
If you really want a technical solution to possible copyright misuse, allowing files from commons is probably exactly what you should do. Unlike local projects, they don't have fair use images at all, and you can further narrow down options by only showing in search results files belonging to categories of licenses that are viable.
I disagree with this task as well. Even if you support the CoC in general, it really doesn't make sense to put it in every single repository when the CoC is for the people and the interactive spaces in which they work, not the technical output thereof. We don't even have separate files for the license in every single repository, and that actually is for the code itself.