| 17 Feb 2021 |
 tgr | justinl: what version of MediaWiki is that? We don't seem to have ever used that option. | 14:39:14 |
| tgr | https://github.com/wikimedia/mediawiki/search?q=CURLPIPE_HTTP1 | 14:39:17 |
 justinl | 1.35.1 | 15:44:44 |
| justinl | https://github.com/wikimedia/mediawiki/blob/REL1_35/includes/libs/http/MultiHttpClient.php#L455 | 15:47:19 |
| justinl | tgr: | 15:48:06 |
| justinl | https://curl.se/libcurl/c/CURLMOPT_PIPELINING.html | 15:49:09 |
| tgr | right, so apparently someone used the integer constant value of CURLPIPE_HTTP1 instead of typing it out. Boo. | 18:29:15 |
| tgr | It's the same on master, you should probably file a bug. | 18:29:36 |
| justinl | Ok, thanks. | 18:49:07 |
| justinl | Hopefully this is good enough for starters: https://phabricator.wikimedia.org/T275064 | 19:03:52 |
| 18 Feb 2021 |
 cicalese | My team is hiring an Associate Engineer! Please feel free to pass this on to any junior developers who are looking for a remote position working with MediaWiki. And please feel free to reach out to me if you have any questions.
https://boards.greenhouse.io/wikimedia/jobs/2897861 | 00:24:41 |
|  Georgios Mavropalias changed their profile picture. | 14:37:56 |
| 23 Feb 2021 |
|  Макс Григор'єв joined the room. | 08:29:55 |
| Макс Григор'єв | We are an IT company and are looking for a documentation system, and therefore would like to know if there in Wikimedia (short answer: yes or no) :
- Sharing and editing?
- Multilevel access system?
- A tree structure with the ability to allocate access to its individual members?
- Versioning changes and the ability to rollback?
- Integration with a versioning system (bitbucket)?
- Do you have a convenient visual text editor?
- Cloud solution with WEB access?
- Is there a mobile application?
- Ability to expand functionality and customization through plugins?
- Ability to create and reuse templates?
- Is it possible to add: diagrams, tables, visual elements?
- Tracker and views counter?
- Ability to split your account into subaccounts?
- Ability to comment?
- API for creating bots, e.g. Q&A?
- Ability to post and view videos directly in the interface?
| 08:30:01 |
| Макс Григор'єв | help me please | 08:57:32 |
 Charly | Well Maxc. Your question has a lot of other question raised to give a good answer, but as a commercial person I would say yes to all your 16 points. Standard MediaWiki can handle 2, 3, 4, 6, 9, 10, 15. All your other points can be done with extensions that already exist or if its really specific a custom made extension ( but that means coding work ).
But I am not the real MediaWiki expert here. | 09:01:52 |
| Charly | * Well Maxc. Your question has a lot of other questions raised to give a good answer, but as a commercial person I would say yes to all your 16 points. Standard MediaWiki can handle 2, 3, 4, 6, 9, 10, 15. All your other points can be done with extensions that already exist or if its really specific a custom made extension ( but that means coding work ).
But I am not the real MediaWiki expert here. | 09:02:03 |
| Charly | * Well Makc. Your question has a lot of other questions raised to give a good answer, but as a commercial person I would say yes to all your 16 points. Standard MediaWiki can handle 2, 3, 4, 6, 9, 10, 15. All your other points can be done with extensions that already exist or if its really specific a custom made extension ( but that means coding work ).
But I am not the real MediaWiki expert here. | 09:13:50 |
 bryandamon | Макс Григор'єв: To expand a bit, I'll take stab and others can correct me:
- Sharing and editing? ➡️ Yes (Out of the box)
- Multilevel access system? ➡️ Kind of (Edit access can be configured to page level. View access is harder, but some people have solutions here.)
- A tree structure with the ability to allocate access to its individual members? ➡️ Not really (MediaWiki pages are "flat", but structure and breadcrumbs can be added to mimic what you are looking for)
- Versioning changes and the ability to rollback? ➡️ Yes (Out of the box)
- Integration with a versioning system (bitbucket)? ➡️ Kind of (Through API, PyWikiBot, or external programming)
- Do you have a convenient visual text editor? ➡️ Yes (Out of the box with MW 1.35)
- Cloud solution with WEB access? ➡️ Yes (Out of the box)
- Is there a mobile application? ➡️ Yes (Extension)
- Ability to expand functionality and customization through plugins? ➡️ Yes (Many extensions already exist and you can create custom extensions)
- Ability to create and reuse templates? ➡️ Yes (Out of the box)
- Is it possible to add: diagrams, tables, visual elements? ➡️ Yes (Some out of the box, others with extensions like this)
- Tracker and views counter? ➡️ Yes (Some out of the box, additional with extensions)
- Ability to split your account into subaccounts? ➡️ Not sure about the question (You can create as many User accounts as you want)
- Ability to comment? ➡️ Yes (Some out of the box via Discussion/Talk pages, additional with extensions)
- API for creating bots, e.g. Q&A? ➡️ Yes (Out of the box)
- Ability to post and view videos directly in the interface? ➡️ Yes (Extension like this one)
| 09:14:05 |
| Макс Григор'єв | Dokuwiki and MediaWiki are the same? | 09:17:05 |
 Marijn van Wezel | Dokuwiki is much simpler | 09:18:05 |
 hexmode | Dokuwiki is not MediaWiki. Much different.
| 16:38:15 |
| hexmode | * Dokuwiki is not MediaWiki. Much different.
| 16:38:23 |
| 24 Feb 2021 |
 SeriousFun01 | In reply to @maxhryhoryev:matrix.org
Dokuwiki and MediaWiki are the same? They both have wiki in the name (and php in the code) but that is where similarities end :-). Dokuwiki is simpler (eg file based, no db backend) | 08:08:22 |
 richardheigl | I think we've touched on this here before: Elasticsearch is changing its licensing system with version 7.11. After that, there will no longer be a recognized open source license for Elasticsearch.
We are monitoring the situation. Amazon and Logz.io have announced forks, but so far there is nothing to be seen.
Is the Wikimedia Foundation already thinking about this? I assume that all MediaWiki organizations will agree on the same solution and that will depend on the WMF. | 11:48:04 |
| cicalese | Yes, they are indeed already thinking about this, but I do not know the current thoughts. I will ask. | 11:54:11 |
| tgr | https://phabricator.wikimedia.org/T272111 | 12:22:27 |
| cicalese | Thank you, @tgr. I was just looking for that! 😁 | 12:27:36 |
| 25 Feb 2021 |
| justinl | Hey all, I'm testing MW 1.35 for an upgrade from 1.34 and running into a Varnish problem. It seems like with 1.35 it's always setting a session cookie named <dbname>mwuser-sessionId, which is causing Varnish to never cache anything since a standard VCL block recommended for MW Varnish config is | 18:05:40 |
| justinl | if (req.http.Authorization || req.http.Cookie ~ "session" || req.http.Cookie ~ "Token") { return (pass); } /* Not cacheable by default */ | 18:05:42 |
