A kitten for you!
Blobaugh 16:52, 12 January 2012 (UTC)
A kitten for you!
You ought to have more then one kitten :)
Hi Chad, I wanted to ask you two favors, if you have the time. You recently created a repository for an extension I developed, called HoverGallery, and named the repository mediawiki/extensions/Hovergallery. Would it be too much trouble to rename it mediawiki/extensions/HoverGallery, just to keep consistency with the rest of the extension? The other favor is that I'm quite new to Git and Gerrit, and I can't seem to find the way to submit my code to the new repo. I can clone the (empty) repo, create a local branch, add and commit the changes, but when I send them for review to Gerrit, they show up in the mediawiki/core project! How can I submit them to the mediawiki/extensions/Hovergallery project? I've been looking and trying for hours, but can't seem to get it right. I'd appreciate your help a lot, really. Thanks for reading!
I had a discussion with Aaron Schulz a while ago and he decided that adding the Azure file backend stuff to core wasn't a good idea after all. Could you go ahead and delete the AzureSDK extension that I had previously requested? It's no longer necessary.
Sorry for the inconvenience.
-- Thai Phan
Why all disallowed? It's not like we are so rich as regards search as to ignore the search engines... I suppose it's because gerrit/gitweb is so slow and crawling would kill it? Isn't throttling possible? Thank you very much,
Gitweb was not made to be indexed--it's an atrocious piece of software that caches nothing. Crawlers were causing the gerrit servers to cry, so we disabled crawling. I don't see us turning it back on for the foreseeable future.
Hi, could you process the requests on Git/New_repositories/Requests? Looks like it's been about 2 weeks since the previous updates. Thanks!
Hello Chad, after  and  I've a bit lost track: what's the current status of branch support/install/upgrade for extensions? See also Version_lifecycle#Extension lifecycle management; Manual:Upgrading#Upgrade extensions should also probably answer such a common question, and Download from Git is not very clear either.
Any extension in Git now has a REL1_19 and REL1_20 branch, like they did in SVN (with REL1_18 and below). Extensions in SVN are no longer supported by ExtensionDistributor, nor are REL1_18 and below (since they are unsupported versions of MediaWiki). We will create REL1_21 branches when 1.21 is released.
So what should one do to update extensions on a wiki? Is the current best practice to download them one by one via ExtensionDistributor? It's not written anywhere.
Extension Distributor works well for most people who want a snapshot of extensions that will work with their supported versions of MediaWiki.
If you want a *lot* of extensions, or to do other developer-esque tasks (switching versions easily, etc), then using Git is probably best.
Hi, thanks for moving the extensions. My developer username is "kipcool". Please add me to the "WikiLexicalData" group.
Regarding the other extensions you mentioned: "Polyglot", I'm just using it, but not contributing to it. "RDFIO" I don't know what it is, the request was not from me.
Ahh, turns out you have an old LDAP account (for SVN) that was never updated for Labs/Gerrit. I can do this for you: what e-mail address do you want to use, and what do you want your labs username to be (this is the username for the labsconsole wiki, as well as logging in to gerrit. Your shell username will remain unchanged)
Hi, (if I got that right) it seems that the "WikiLexicalData" extension is using the "push-for-review" model (since I was not able to do a direct push). Being the only active developer, it means I have to review my own commits, which is not really useful.
Can I change it to a "direct push" model?
We do not allow direct pushing to the master branch for mediawiki extensions. In the very near future, we will be having things like linting of changes for all extensions, which won't be possible if you skip review with a direct push.
In that case, the page http://www.mediawiki.org/wiki/Git/Workflow#Other_MediaWiki_extensions should be changed because it says Every extension author can choose between two choices here: the gated-trunk/push-for-review model, and a straight push model. For any given extension, we will honor the wishes of the person/s listed as the main author on the extension's mediawiki.org page.
Hi Mr Demon,
You posted on my talk page about why I want to create new repos. The FileBackendStore class was changed in MediaWiki 1.20 (and then changed again in 1.21). This broke the WindowsAzureStorage extension that I am trying to replace. I could've patched it to work (which I might do later) but, given my penchant for the latest and greatest, I wanted to make a new one that used Microsoft's Azure SDK rather than the one by REALDOMEN (which was used by WindowsAzureStorage and is deprecated).
I guess I don't understand why there's new repositories for this. It's still Azure, and it's still FileBackend, so it made more sense to keep the same extension (but just rewrite it, since the existing one is now deprecated).
I'm planning on adding my FileBackend extension to mediawiki/core (I have the blessing of Aaron Schulz) so there's no need for me to edit mediawiki/extensions/WindowsAzureStorage. As such it's probably better to keep mediawiki/extensions/WindowsAzureSDK the way it is so people with the older extension can still have access to it.
Furthermore, the project owner for mediawiki/extensions/WindowsAzureStorage also hasn't been active for months so I don't know how long I'll have to wait for my change to come through.
So yeah, I only need a repository for the new Azure SDK.
P.S. I also need one for the AWS SDK.
Hello! Are you still handling migration of extensions to Git? It looks like you were doing this about once a week for a while, but now there haven't been any migrations in a month. Since I put in a request for one of those extensions myself, I was concerned. :-)
Since I am just checking myself: a whole batch has been migrated a few days days ago again.
QUESTION to chad: I am just testing migration of our biowikifarm. One odd thing I noticed is that Extension:Lucene-search is not listed neither migrated. May be on purpose, but should perhaps be documented?
Hi ^demon, over at Extension:SacredText#Get_the_Scripture_data it says, "Due to the size of the SQL scripts that add the scriptures to the database, they are kept on a different SVN repository." Given that WMF has no problem devoting resources to hosting the Holy Bible over at Wikisource (in many different languages, no less!), would it be possible to put that extension in the git repository along with its 5.1 MB bible_kjv_entire.sql? If we wanted to give other Scriptures equal treatment, that probably wouldn't take up too much additional space, because there are not a whole lot of religious texts whose copyrights have expired (the Satanic Bible, for instance, is still under copyright) and most (e.g. the Qu'ran and Book of Mormon) are significantly shorter than the Bible. There doesn't seem to have been much demand for including other Scriptures besides the KJV Bible anyway, although the extension was designed to allow for such expansions.
Probably the only books people would be wanting to use this extension for would be those that have been organized into chapters and verses. The most obvious example would be be sacred texts, although legal statutes could be another possibility, if it weren't for the fact that they change; this is more suited for texts that never need to be updated. That's what leads me to believe that even if it were desired to have an all-inclusive set of those static texts in the public domain that have been organized by chapter and verse, it would not take up much space.
It has little to do with the size of the data, and more the version control system's ability to handle it. The file itself probably isn't a problem in Git, but I'm wondering how well it would behave in Gerrit. At the very least, I know diffs will have problems with such a large amount of text all at once.
you may be the right person to address in this matter.
Recently I ran intro problems while testing skins. There are a couple them available in this spot. I think they should be separated and moved to that spot. Besides, splitting them into separate entities would provide the advantage of being able to author, fix and document them separately. However, this is not the main reason why I am writing:
Even though these skins are authored like extensions, it do not think that it is wise to install them in
/extensions/skins/ instead of
/skins/. Here their status of being a skin should imho have precedence before their status of being an extension providing a skin. I believe we will run into heaps of confusion if it stays like this because they are in very different places of a single MW installation which is not very intuitive, too.
However, this is just a suggestion to consider. Cheers
The skins repo in mediawiki/extensions is a holdover from SVN days. The new skins are going under mediawiki/skins/*. Really though, it doesn't matter much. Skins can work out of the extensions directory. If you want someone to talk to about this more, I'd suggest Daniel Friesen. He does a lot more skins work than I.
Sorry for the mail from Travis CI you (and firstname.lastname@example.org) received. That shouldn't happen again.
is there any problem with creating a repository for "CommonsHelper2" because you didn't create "mediawiki/tools/commonshelper2" in the last round?
No, I just didn't quite finish the list on Friday, I got sidetracked by some other things. I will be finishing them tomorrow.
Actually, I see that you're asking to have this moved from the Toolserver SVN. I don't have access to that to dump the full history properly.
I created a JIRA-request on the Toolserver: https://jira.toolserver.org/browse/TS-1458
DaB has created a dump of the SVN-repo and attached it to the JIRA-request: https://jira.toolserver.org/browse/TS-1458
(Unindenting for legibility) I spoke too soon it seems. After starting, it didn't seem to be doing anything, so when I aborted I ended up getting svnadmin: Malformed dumpfile header. Thoughts?
Hi, I asked a repository for the extension Linkedwiki (yet validate for svn, 6 month ago but I have not the time to deploy). My holidays are almost over (one week...) else it will deploy in october. You are very busy. You think it's possible to create it this week ? else I can wait ;)
A guy from our team tried to request a repository for our project WikiVoteYandex here. Could you please explain what's wrong with our extension? We can provide the source code now - the extension is almost done by now.
Nothing is wrong, I just hadn't gotten to yours yet because I had 2 outstanding questions:
- Was this indeed a new extension and not extra features for the existing Maps extension? This isn't a problem, just need to know for sure!
- Is there existing source code (sounds like there is)?
Since the answers seem to be "yes" and "yes," could you provide a link to the existing code so I can import it into gerrit for you and get you started?
1. Yes, it's currently a separate extension that is dependent on Maps and Semantic Maps but in the future in may be merged with Maps/Semantic Maps. The main reason of separation is that we don't yest fully support all Maps features in our extension and also don't know if many people need Yandex Maps support. 2. Sure it is! Here is the link: https://github.com/vedmaka/WikivoteMapsYandex
Hi! I figured I'd let you know that I've recycled your old enwiki script for custom csd reasons for use crosswiki by Stewards and Global sysops :) It is really, reaaaally nice, been looking for something like this for a while :) It's now over at m:User:Snowolf/GS delete and working quite nicely :)
Hi, it might be related to previous question. I've seen UserFunctions has been migrated https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/UserFunctions.git;a=tree but I'm not able to push any change despite being in the owner group https://gerrit.wikimedia.org/r/#/admin/groups/127,members
[17:09:37][toniher@fartet | ~/remote-work/mediawiki/git/extensions/UserFunctions]$ git push Username: Password: error: The requested URL returned error: 403 while accessing https://gerrit.wikimedia.org/r/p/mediawiki/extensions/UserFunctions.git/info/refs fatal: HTTP request failed
[17:10:43][toniher@fartet | ~/remote-work/mediawiki/git/extensions/UserFunctions]$ git review -s Problem running 'git remote update gerrit' Fetching gerrit fatal: '/mediawiki/Extensions/UserFunctions.git': not a Gerrit project fatal: The remote end hung up unexpectedly error: Could not fetch gerrit
Maybe because there is no .gitreview. Am I doing something wrong? Thanks in advance!
You need to push to the SSH URL
Hi, thanks, after having cloned that way
git clone ssh://email@example.com:29418/mediawiki/extensions/UserFunctions.git, I get the following problem:
[18:03:01][toniher@fartet | ~/remote-work/mediawiki/git/extensions/UserFunctions]$ git push Counting objects: 7, done. Delta compression using up to 8 threads. Compressing objects: 100% (4/4), done. Writing objects: 100% (4/4), 838 bytes, done. Total 4 (delta 3), reused 0 (delta 0) remote: Resolving deltas: 100% (3/3) To ssh://firstname.lastname@example.org:29418/mediawiki/extensions/UserFunctions.git ! [remote rejected] master -> master (can not update the reference as a fast forward) error: failed to push some refs to 'ssh://email@example.com:29418/mediawiki/extensions/UserFunctions.git'
Sorry to bother you but I notice that the newly-moved extensions aren't showing up in Gitweb. (In other words, the list of extensions under git control is out of date)
I'm also asked for a username and password to access the new repositories. That may be intentional, but thusfar I've avoided using a username and password on my internal machines simply because I do utterly stupid things from time to time and shouldn't be trusted with anything more than read-only access :D
Thanks for your time!
Is of the requirement to create a new repository over a page Git/New_repositories/Requests correctly for new git extension repository? I watched that last requirement was checked on 27 February.
Thank you for your reply and link. I do not use IRC. I hope that everything will be fine and soon.
Hi, Could you please take a look at the new entries on Git/New repositories/Requests? Thank you very much.
It is over month, and git repository for AccessControl extension is not created. Why? On page Git/New_repositories/Requests is question about history, but I don't understand it. I want do push existing git repository for AccessControl from my server into MediaWiki official git. It is all.
I've created the repository now. I hadn't created it because I didn't know if there was existing history you wanted to push (it matters when I'm creating the repository). You should be ready to go now.