Hi!
> Any day can be Tuesday if you really want.
Thanks to Antoine and Brad for figuring the hhvm crash in
https://phabricator.wikimedia.org/T216689. Finding the cause of random
crashes can be very hard and frustrating, but they figured it out and
resolved it quickly. Thanks!
--
Stas Malys
ave a
comment from a developer within X time" - but unless X is very large, I
think it will be unsatisfactory, since getting "yes, it's a very
important bug, thanks for submitting it" comment without the bug being
fixed is IMHO no better than getting n
quot;WMF is totally wrong in doing this!" is not realistic. Reasonable
people can and do disagree. Reasonable people also can work through
disagreements and find common interests and ways to contribute to mutual
benefit. I think that's what we're trying to do here.
--
Stas Malyshev
smaly
;Need volunteer" tag that I think can be used for that.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
there might be
difference, e.g. for different logged-in users.
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ady found three bugs we totally missed in our code, just by
upgrading to it.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
avoid encouraging bad code.
> Thanks to you all, and again - sorry for the half message.
This looks useful. I think PHPStorm has this check built in, but having
it in sniffs too wouldn't be a bad thing. I've seen such things happen
when refactorin
ust forgot to create a branch.
One useful command for me would be "check out a change and put it in a
branch named after topic of that change, overriding it if it existed".
This allows easy syncing of patches where more than one person
contributes to them.
Thanks,
--
Stas Ma
lesson shouldn't be "let's find somebody to punish". I am
not sure if that was the intent, but it kinda felt this way to me. And I
don't think this is warranted neither in general nor in particular case.
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
__
out moving
it to Review status. Sometimes several people may need to cooperate on
WIP patch before it is ready to go. Of course, one can add reviwer and
then move back to WIP, but it'd be nicer to avoid extra actions.
Thanks!
--
Stas Malyshev
smalys...@wikimedia.org
at highlighting issues that volunteers should concentrate
on is a valid need. But I don't think reusing the same mechanism as
ongoing development tracking is using now is going to be good. It may
get very confusing. We should try to find other way to
asks,
Invalid would be when the task is describing something that can not be
done at all (at least by us), or would not produce any desirable result.
Declined is when it describes a valid task in general, but we are not
going to do it because of reasons.
--
Stas Malyshev
smal
the ones that are part of
the ongoing development. And document it in the lifecycle document.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
erated but automatic, but still this is quality-related data
which is linked to page content (and different for each revision AFAIU).
Currently if I understand right it has its own storage.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailin
about good process, maybe it's because you're guilty" - that's
how this comment sounded to me - is not right.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
s might be good). So I'd say public
record while the ban is active is a must, but after that expunging the
record is fine.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/m
ific? I'm not sure I see where this is public.
I think it's this one:
https://lists.wikimedia.org/pipermail/wikitech-l/2018-August/090490.html
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lis
temp.
banned from date A till date B because of comments incompatible with
CoC" doesn't seem to hurt anyone.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
pecifying it in the same place where the action is described, as per
above. Again, establishing and advertising such place should be
something that CoCC does.
It is clear to me - and I think to anybody seeing the volume of
discussion this generated - that we need improvement here. We can do
better and
me rules around removing
tasks from "High" if it's clear we're not doing it anytime soon.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ly should write the parameter as:
bd:serviceParam mwapi:search "\"goat cheese\"" .
Probably something like this: http://tinyurl.com/y9fdva5w
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
lly CirrusSearch uses some configs without 'wg' prefix, but in
this case it doesn't seem to be an issue.
> Open for review:
> https://gerrit.wikimedia.org/r/#/q/project:operations/mediawiki-config+topic:cleanup+is:open
This one produces 404.
--
Stas Malys
ut you have to inform the user somehow about this.
I think the easiest way would be to change the error message and add a
pointer to a page which describes the issue and how to work around it. I
imagine changing error message in phab shouldn't be too hard?
--
Stas Malyshev
sm
getting more information
Wouldn't it be easy to just log out and read any task (or even use
incognito mode/private browsing in the browser)? It is certainly a small
inconvenience, but I am not sure how it is very important, given a very
simple workaround.
--
Stas Malyshev
smalys...@w
em to be a pressing concern that would
do any harm if not brought into compliance right now. So let's see if we
can reach some consensus here.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
person, etc. But I don't think
special status like that would be very useful or very welcome.
Also note linking one's legal identity to Wiki edits may be very
dangerous in some countries. Requiring people to take that risk to edit
certain pages is not really a good thing.
--
Stas Malyshev
smaly
erging patches
separately probably make it slower than before. If we additionally have
limit of four - which is low even by current historic usage - I am
concerned this will lead to long wait times and a backlog of patches
which might then block other work.
--
Stas Malyshev
smalys...@wikimed
e
same time atomically and scap takes care of nothing ever seeing the
intermediate states) or has to be managed manually, and if so, how?
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
Hi!
> A second advantage, is one can exactly reproduce the build on a local
> computer and even hack code for a fix up.
This is great! CI errors not reproducible locally has been a huge
annoyance and very hard to debug. Thanks for making it easier!
--
Stas Malyshev
smalys...@wikimed
ted until the mythical 8.0 aka
"version where the things can be broken" but for all practical purposes
it should not be used by anybody now and is as dead as anything can be
in 7.x.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mail
a\Assert is likely the way to go for most of MW code.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
his can work in deepcategory
searches - we now have a keyword for it (driven by SPARQL for now) and
what would happen if it is ported to SQL. If we get it on labs db
replicas, we could set up mediawiki so that we could test how good is it
on real data. Thanks for posting about it!
--
Stas Mal
er confusing which set of credentials is
used where, and having good terminology would help that. "Wikimedia
developer account" looks like a good option for this.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia
e or something and can fix it
right there then.
14. All docs are for old UI as it seems. I wonder if there are docs for
PolyGerrit UI?
[1]
https://www.awesomescreenshot.com/image/3174140/0fac7a4a591a59b768f1fe2eadaf66d0
[2]
https://www.awesomescreenshot.com/image/3174139/bf6445a910aa63b2f26433e4
anges, but I doubt it would change anything.
I suspect it has to do with MCR work, but don't know the details. There
might be a need to add some info in the revision for new MCR
information, but not sure.
--
Stas Malyshev
smalys...@wikimedia.org
__
this - is there plan to change it or still use old
hook for now and foreseeable future?
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
lied.
Seems to work ok for me for all roles I've used, except for the issue in
https://phabricator.wikimedia.org/T183306 which is of course still there.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimed
be a good idea anyway :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
would be the best way to improve it?
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
information about anything you think would
be useful for us to know.
What was that page again?
https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Usage
Thanks in advance,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l
Hi!
> haha, awesome!
>
> thanks a lot :-)
Confirming, looks great for me now. And congratulations to the team on
the release of this excellent feature!
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
W
ce, so I did it on another
Likely there's a problem with timeless, see:
https://phabricator.wikimedia.org/T181106
Vector works fine for me though. I guess that's why it's "beta" :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l m
still path components. My reading of the
RFC also seems to be that ";" is a reserved character, and as such
should not be URL-encoded. Indeed, path BNF includes sub-delims without
encoding, which includes ";". However, I am not sure I understand other
part of the patch where it plays with
on the nets. But the processes got better, I think, and
the level of maturity of both discussion and participants increased.
Also, thank you for the kind words, and I'll be glad to help with what I
can if we need something done in PHP core.
--
Stas Malyshev
smalys...@wikimedia.org
t of experience dealing with it,
surely there could be a thing or two we could contribute). Triaging the
bugs (one of the most necessary, thankless, and under-appreciated jobs
in an open-source project). Probably more...
--
Stas Malyshev
smalys...@wikimedia.org
___
find anybody responsible or at least concerned about this sad
state of things.
OK, this came out super-long and kinda ranty (sorry!), so I will stop
for now, but if you have any questions about it, please feel free to
ping me, and I will be glad to discuss it.
--
Stas Malyshev
ulting performance may or may not be
on par or better, but reusing most of the performance work on HHVM in
PHP would not be possible due to completely different engine internals.
So pretty much all that can be taken from HHVM into PHP would be "this
syntax looks like a good idea, let's reimplement it
h) - but it is pretty clear to me that Facebook is in
absolute control over this platform. This is not the case with Zend and PHP.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> PHP 7. I think we need to decide on this pretty much immediately.
Should it be on the TechCom agenda and should we have some public
discussion on IRC in RFC format for this soon?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l m
[3] https://phabricator.wikimedia.org/T165982
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
of course). As for
comparison with hhvm, I heard various reports, but I think spending some
time on seriously testing it (I mean creating proper production setup,
and directing either captured/replayed or real traffic to it) is the
best way to go.
--
Stas Malyshev
smalys...@wiki
icator is now independent from
Facebook, afaik, since it's developers have separate company, Phacility.
[1] https://wiki.mozilla.org/Phabricator
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
some help needed, or there are some
specific issues that are blockers, I think Zend team would be glad to
talk to us. If needed, I could probably help with establishing the
contacts.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mail
d up to
the day we decide to turn the hash off. Starting that day, it'd have to
be generated, but I see no reason to generate one more than once?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://l
adoop storage? I imagine that would
slow down the transition, but not sure if it'd be substantial or not. If
we're using the hash just to compare revisions, we could also use
different hash (maybe non-crypto hash?) which may be faster.
--
Stas Malyshev
for
ex-IE users it may not be an issue).
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
though :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
person is still active in the project under
the same name, it may be easy to track them, but if not, it's mostly
hopeless.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/m
ly
consider Git metadata to be enough in this case, why not in any others?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
potential that
different systems would read different tags (shouldn't make a difference
but might still). Not sure how that would work? If combining @inheritdoc
with other content works as Gergo described, it may be helpful, but
still not sure what exactly it would happen.
lean,
e.g.: http://php.net/stream_set_blocking
But looking into hhvm source, I find this:
https://github.com/facebook/hhvm/pull/7084
Looks like hhvm had a wrong definition of the function.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mai
itive type name.
Not sure why though...
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
y if somebody had pre-WMF +2, they should not lose it just
because they joined and then left the WMF, and this should be automatic
by default. Non-default cases can always be handled on per-case basis.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikite
me]
> links)
That sounds like a good idea :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
or it right now. The way
you want to do it is not supported - yet - but there are many other
ways. Which we are constantly improving. But we can't do everything at
once. Please be patient, please contribute with what you can, and we'll
get there.
--
Stas Malyshev
smalys...@wikimedia.org
___
w hard would it be to add php7/phan to mediawiki-vagrant?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
. Of course, it's a bit
strained analogy, but my point is IRC raw logs are not a very good UI
for many use cases.
Don't have a good solution for this, as IRC is still excellent as
transient quick discussion medium, but much less as a long-term
persistent discussion one. OTOH, maybe that should be done wi
trong caching model embedded and because
there are not too many of them and you need to create them so we can
watch the load carefully). Other pages can gain them - probably via some
kind of Lua functionality - as soon as we figure out what's the right
way to do it, hop
Hi!
> <https://xkcd.com/1770/> seems pretty timely!
Or this one:
https://xkcd.com/1172/ :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
aving people to send their pwds to unknown site and trust
them not to do anything wrong with it :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
to use Phab
for specific task of CfP, which Quim seems to have decided already.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
lp
> you with this. It allows you to consume events, and specify matching rules
> and actions to take based on those rules.
>
> https://www.mediawiki.org/wiki/Change_propagation
I see no mention of ability to consume past events. Is it possib
n T
and N. To know that, I need permanent seekable record of changes. Or
some flag that says when it was last updated, at least.
Unless of course I'm missing the part where you can seek back on
EventBus events, then please point me to the API that allows to do so.
--
Stas Malyshev
smalys...@wiki
wing it now.
Any advice on how to solve this issue?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ill leaves prior revisions in
case of default change broken, but at least current one isn't.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
t sure whether it makes much sense for extensions...
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ooks like a nice solution.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
quot;other". Not ideal, but at least
better than 1780 :)
The list of names is at
https://gist.github.com/smalyshev/dfa72c79d9f750058262b902f47c0130 if
anybody wants to play with it and save time on extracting it :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
thub.io would be an excellent
idea. If somebody would do the design, loading up repos list and
displaying them with a nice structure - given that we actually have
pretty structured names already, so we could start from that - should
not be super-hard?
--
Sta
s, etc.
- it is funny to look at - and we all could use occasional comic relief :)
I'm not sure about production wiki but at least having it in
development/test/beta would be nice I think - e.g. as vagrant role or
something like that maybe?
--
Stas Malyshev
smalys...@wikimed
xed it's good". Agree on -2. I use 0 for just commenting on things
where I do not feel qualified or entitled to review things but still
have something to say, like additional todo items or general discussion.
So, most reviews should be +1/-1.
--
Stas Malyshev
smalys...@wikimedia.org
_
nd
contributing to it, in this particular case it doesn't look like viable
solution to me.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
the refactoring are linked from:
https://phabricator.wikimedia.org/T121430
Pretty version of the same:
https://www.mediawiki.org/wiki/User:Smalyshev_(WMF)/Suggester
If you have questions on this, please contact the Discovery team:
https://www.mediawiki.org/wiki/Wikimedia_Discovery#Communications
--
Stas
d I don't see a lot of reason to mess
with existing working code just to use it.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
eak BC
with older PHP versions? I'm not sure I understand your argument here.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ere and just to be clear, I'm for the gradual approach.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi!
OK, GUI files moved to wikidata/query/gui and patches now have to be
submitted against it. I imagine it will also be easier to set up testing
there given that it's no longer dragging unrelated Java module around.
Please tell me if anything doesn't work.
Thanks,
--
Stas Malyshev
smalys
https://phabricator.wikimedia.org/T113034
aims to improve it.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
the engine that would
be supporting that.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
) and it may be more precise indicator
than just name. Not sure which way is the best to search for it though.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo
to the notes.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
of fear that uneducated
FUD may hurt our reputation does not sound like a winning strategy for me.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech
of these sites are public-facing (and due
to the nature of wikis, many of them, to some measure, are), running
out-of-support software may not be that good an idea.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
you'll encounter one of
them. That could also happen with Test plan - nobody guaranteed it
wouldn't say everything fine, and being +2ed, and still break down.
reviewing it promptly, but typing: Test Plan: I didn't test this patch at
That I have no objections to.
--
Stas Malyshev
smalys
sucks and they have to work around it to be effective.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
/iconv/iconv_prog.c.html. Again,
that would require custom patch for PHP, not sure about hhvm.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
:
http://esr.ibiblio.org/?p=6737
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
, but Facebook,
Twitter, various chat clients, I think several Wordpress plugins, etc.
https://phabricator.wikimedia.org/T8
I wonder if this can somehow be connected to Wikidata's image attribute
(https://www.wikidata.org/wiki/Property:P18).
--
Stas Malyshev
smalys...@wikimedia.org
of time :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
where to contribute and on which condition is entirely yours, but
I *personally* would view such stance as somewhat counterproductive, if
your goal is to contribute to the world's repository of high quality
software that can be accessed to everyone.
--
Stas Malyshev
smalys...@wikimedia.org
1 - 100 of 108 matches
Mail list logo