[09:27:59] hi [09:28:03] :) [09:32:19] Hi [10:42:12] hi [13:35:19] I have successfully installed mediawiki in localhost and want to commit a patch to core repository my core repository in git is presently ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/core.git but actually I have forked the code in https://github.com/rammanoj/mediawiki so which link I have to set for git remote-v [14:03:39] rammanoj_: Github is only used as a clone of mediwiki repositorys, so you're fine with cloning the code from there. However, afaik there isn't any advantage in fetching from github instead of fetching from gerrit directly. If you want to send code in you need to send it to gerrit. So if "git remote -v" gives you a line saying "origin ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/core.git (push)" your setup is just fine for sending code to [14:03:39] gerrit, you'll just need to "git review". [14:05:52] rammanoj_: You might also want to have a look at https://www.mediawiki.org/wiki/Gerrit/Tutorial [14:28:23] yes I have looked at https://www.mediawiki.org/wiki/Gerrit/Tutorial , but I have downloaded the code from $ git clone ssh://@gerrit.wikimedia.org:29418/mediawiki/core.git as provided in that link above but by keeping origin ssh://rammanoj@gerrit.wikimedia.org:29418/mediawiki/core.git (push) as my core repository when I click git status It gives me [14:28:23] a long list of items which are needed to be updated ? [16:13:18] rammanoj_: What "long list of items to be updated"? [16:13:48] Please don't post the complete list, but what is the actual explanation above or below that list? [16:14:04] If there is some kind of warning or error message, please post it, to make sure we talk about the same things. [17:25:43] !1.17 [17:25:43] Old MediaWiki versions may have bugs and security vulnerabilities, we don't recommend you to use any release older than 1 year. See http://www.mediawiki.org/wiki/Version_lifecycle for details. [18:31:18] Hello [18:34:24] I do like do create a documentation site for several software projects and ecah project may have different version (1.0, 2.0 and do on). I do like to create like a namespace for each project and version but im not sure if this is a good approach [18:39:18] I guess namespaces should be good. They require a sysadmint to set them up but once done they can be filtered on searches and other special pages [18:40:10] Is there a limit for the number of name spaces i can get ? [18:41:29] Because i can endup with a bunch of them at the end [18:41:56] Say i got 5 projects each projects gets 3 dofferent versions [18:42:01] Do the math [18:42:17] 15 namespaces [18:45:15] Im asking this because i dont want my docs to endup like the joomla documentation project. Where all versions are some how shared in the same pages [18:45:43] Well, there's no limit, but having a namespace per version seems too much, I'd go with a namespace per project, and list versions either on the same page, or subpages [18:47:07] And what about sub pages per project and version [18:47:47] Such as myproject/version/content [18:48:24] But i dont want the sub pages names in my title [18:48:44] But that will cause seo problems with dup links [18:48:59] subpages can be created by anyone, which is usually more convenient. It's good also, although in case you want to restrict search to specific namespaces, you won't be able to restrict search results to specific projects. Apart from that it should be practically the same [18:49:18] Hmmm wair a sec is the same problem with namespaces dang....