Last modified: 2011-07-26 18:58:22 UTC
Enable CustomUserSignup for Hindi Wiki as per 'wmgCustomUserSignup' => array( 'default' => false, 'hiwiki' => true, Local consensus can be found here- http://hi.wikipedia.org/wiki/%E0%A4%B5%E0%A4%BF%E0%A4%95%E0%A4%BF%E0%A4%AA%E0%A5%80%E0%A4%A1%E0%A4%BF%E0%A4%AF%E0%A4%BE:%E0%A4%A8%E0%A4%AF%E0%A5%80_%E0%A4%B8%E0%A5%81%E0%A4%B5%E0%A4%BF%E0%A4%A7%E0%A4%BE%E0%A4%8F%E0%A4%81, Regards Mayur
This would also require wmgClickTracking setting up too I'm also not sure if this is desired/designed (by WMF) to be enabled on other projects There is also no translations for this yet, though, as it's only really the name, and it's description, this is less of an issue
(In reply to comment #1) > This would also require wmgClickTracking setting up too > > I'm also not sure if this is desired/designed (by WMF) to be enabled on other > projects > > There is also no translations for this yet, though, as it's only really the > name, and it's description, this is less of an issue Again translation is not an issue, As soon as this facility is avail to us we will translate this on our project.We have already done that for many new extension which has been installed. BTW this is enabled on english wiki, So i don;t thing Foundation may have any concern regarding this. if wmgClickTracking setting is also desired then also set this. Regards
(In reply to comment #2) > > Again translation is not an issue, As soon as this facility is avail to us we > will translate this on our project.We have already done that for many new > extension which has been installed. > > BTW this is enabled on english wiki, So i don;t thing Foundation may have any > concern regarding this. > > if wmgClickTracking setting is also desired then also set this. > > Regards Translation should occur before it's enabled, besides, having it translated in the beginning, for stuff like UploadWizard, means it is of benefit on Commons etc I wasn't suggesting that it was any sort of a performance issue etc, more that of a policy issue.
(In reply to comment #2) > Again translation is not an issue, As soon as this facility is avail to us we > will translate this on our project.We have already done that for many new > extension which has been installed. > Please note that translations should be made on http://translatewiki.net. Not in your wiki in the MediaWiki namespace alone. Translations made via http://translatewiki.net all Hindi speaking users will profit from it: on Wikimedia Commons, Wikisouce and third party wiki installations as well.
(In reply to comment #4) > (In reply to comment #2) > > > Again translation is not an issue, As soon as this facility is avail to us we > > will translate this on our project.We have already done that for many new > > extension which has been installed. > > > > Please note that translations should be made on http://translatewiki.net. Not > in > your wiki in the MediaWiki namespace alone. > > Translations made via http://translatewiki.net all Hindi speaking users will > profit from it: on Wikimedia Commons, Wikisouce and third party wiki > installations as well. Its easy to to translate an extension after its installation as per ur requirement, Sending it to other hindi Wikimedia project is not a big issue as it can be done by import right on respective project.
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #2) > > > > > Again translation is not an issue, As soon as this facility is avail to us we > > > will translate this on our project.We have already done that for many new > > > extension which has been installed. > > > > > > > Please note that translations should be made on http://translatewiki.net. Not > > in > > your wiki in the MediaWiki namespace alone. > > > > Translations made via http://translatewiki.net all Hindi speaking users will > > profit from it: on Wikimedia Commons, Wikisouce and third party wiki > > installations as well. > > Its easy to to translate an extension after its installation as per ur > requirement, Sending it to other hindi Wikimedia project is not a big issue as > it can be done by import right on respective project. But we do not want to get into the process of having to scrape translations from onwiki. ALL default translations should be made on translatewiki.net. Any customisations beyond that can then be done locally
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > (In reply to comment #2) > > > > > > > Again translation is not an issue, As soon as this facility is avail to us we > > > > will translate this on our project.We have already done that for many new > > > > extension which has been installed. > > > > > > > > > > Please note that translations should be made on http://translatewiki.net. Not > > > in > > > your wiki in the MediaWiki namespace alone. > > > > > > Translations made via http://translatewiki.net all Hindi speaking users will > > > profit from it: on Wikimedia Commons, Wikisouce and third party wiki > > > installations as well. > > > > Its easy to to translate an extension after its installation as per ur > > requirement, Sending it to other hindi Wikimedia project is not a big issue as > > it can be done by import right on respective project. > > But we do not want to get into the process of having to scrape translations > from onwiki. > > ALL default translations should be made on translatewiki.net. Any > customisations beyond that can then be done locally Translation has been done for this extension at translate wiki, now plz feel free to enable this
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > (In reply to comment #4) > > > > (In reply to comment #2) > > > > > > > > > Again translation is not an issue, As soon as this facility is avail to us we > > > > > will translate this on our project.We have already done that for many new > > > > > extension which has been installed. > > > > > > > > > > > > > Please note that translations should be made on http://translatewiki.net. Not > > > > in > > > > your wiki in the MediaWiki namespace alone. > > > > > > > > Translations made via http://translatewiki.net all Hindi speaking users will > > > > profit from it: on Wikimedia Commons, Wikisouce and third party wiki > > > > installations as well. > > > > > > Its easy to to translate an extension after its installation as per ur > > > requirement, Sending it to other hindi Wikimedia project is not a big issue as > > > it can be done by import right on respective project. > > > > But we do not want to get into the process of having to scrape translations > > from onwiki. > > > > ALL default translations should be made on translatewiki.net. Any > > customisations beyond that can then be done locally > > Translation has been done for this extension at translate wiki, now plz feel > free to enable this Need to wait for the daily export now
I don't think CustomUserSignup should be enabled yet. From what I remember, this is related to Lennart Guldbrandsson's "Account Creation Improvement" project and is only used for controlled testing. If that's true, it should not be enabled without talking to him about it. It's generally a good idea not to go fishing around InitialiseSettings.php looking for new toys to enable. :-) Usually, if something should be installed widely, it will be.
I see no concern with this as there is no security issue and this has already deployed on English wiki.So this can be enabled in Hi wiki too.As per reedy suggestion we have also done its translation.
(In reply to comment #10) > I see no concern with this as there is no security issue and this has already > deployed on English wiki.So this can be enabled in Hi wiki too.As per reedy > suggestion we have also done its translation. CustomUserSignup is an extension that the Account Creation Improvement Project used to display custom account creation pages to test a few ideas they had. Why do you even want this extension on hiwiki?
(In reply to comment #11) > (In reply to comment #10) > > I see no concern with this as there is no security issue and this has already > > deployed on English wiki.So this can be enabled in Hi wiki too.As per reedy > > suggestion we have also done its translation. > CustomUserSignup is an extension that the Account Creation Improvement Project > used to display custom account creation pages to test a few ideas they had. Why > do you even want this extension on hiwiki? I am closing this and other bugs as you all developers seem not interested to help hi wiki furthermore.First of all we are denied for Security reasons.if it don't affect it then we are asked for translation of messages on translate wiki without such policy. BTW Thanks for all your help you all made previously for us.
(In reply to comment #9) > I don't think CustomUserSignup should be enabled yet. From what I remember, > this is related to Lennart Guldbrandsson's "Account Creation Improvement" > project and is only used for controlled testing. If that's true, it should not > be enabled without talking to him about it. > > It's generally a good idea not to go fishing around InitialiseSettings.php > looking for new toys to enable. :-) Usually, if something should be installed > widely, it will be. There are many array in InitialiseSettings.php with which we can play, but we wanted only those toys which were useful for us.
(In reply to comment #12) > (In reply to comment #11) > > (In reply to comment #10) > > > I see no concern with this as there is no security issue and this has already > > > deployed on English wiki.So this can be enabled in Hi wiki too.As per reedy > > > suggestion we have also done its translation. > > CustomUserSignup is an extension that the Account Creation Improvement Project > > used to display custom account creation pages to test a few ideas they had. Why > > do you even want this extension on hiwiki? > > I am closing this and other bugs as you all developers seem not interested to > help hi wiki furthermore. We're definitely interested in helping hiwiki, but that doesn't mean that we'll unquestioningly honor every request. > First of all we are denied for Security reasons. Note that all wikis run on the same pool of servers, so a security or performance issue in something that runs on hiwiki only can still affect all of the other 800+ wikis. > if it > don't affect it then we are asked for translation of messages on translate wiki > without such policy. The fact that it's not documented anywhere doesn't mean it's not a policy :) . Sadly that's how things work in the dev/ops community sometimes. Extensions need to be translated into a wiki's content language before they're enabled there, that's true for every extension and every wiki.
Yeah you (In reply to comment #14) > (In reply to comment #12) > > (In reply to comment #11) > > > (In reply to comment #10) > > > > I see no concern with this as there is no security issue and this has already > > > > deployed on English wiki.So this can be enabled in Hi wiki too.As per reedy > > > > suggestion we have also done its translation. > > > CustomUserSignup is an extension that the Account Creation Improvement Project > > > used to display custom account creation pages to test a few ideas they had. Why > > > do you even want this extension on hiwiki? > > > > I am closing this and other bugs as you all developers seem not interested to > > help hi wiki furthermore. > We're definitely interested in helping hiwiki, but that doesn't mean that we'll > unquestioningly honor every request. > > > First of all we are denied for Security reasons. > Note that all wikis run on the same pool of servers, so a security or > performance issue in something that runs on hiwiki only can still affect all of > the other 800+ wikis. > > > if it > > don't affect it then we are asked for translation of messages on translate wiki > > without such policy. > The fact that it's not documented anywhere doesn't mean it's not a policy :) . > Sadly that's how things work in the dev/ops community sometimes. Extensions > need to be translated into a wiki's content language before they're enabled > there, that's true for every extension and every wiki. Asking Questions is not bad but it should be in positive sense, if it is confirmed that a extension can be installed on our wiki then we may try for its translation.But every time we have waisted our time, same in case of uploadwizard for which reedy asked me to do translation we completed its translation and informed about that then suddenly some another developer arise some another concern and finally they succeeded to block this bug for indefinite time as accoring to uploadwizard developer Niel he has 1000 things to do rather than resolving this bug. A wiki like this http://hi.bharatdiscovery.org/india/%E0%A4%AD%E0%A4%BE%E0%A4%B0%E0%A4%A4%E0%A4%95%E0%A5%8B%E0%A4%B6:%E0%A4%B8%E0%A4%B0%E0%A5%8D%E0%A4%B5%E0%A4%BE%E0%A4%A7%E0%A4%BF%E0%A4%95%E0%A4%BE%E0%A4%B0 is using Replace text extension who have no funding and extra resources.But inspite of our vast developer team of Wikimedia foundation we are not able to use this extension on Hindi Wiki that really suck our mind. However I know most of us are volunteer here and we are here to do as best as we can do for our projects.But it is not necessary that if a extension is not installed in english wiki then it would not be delpoyed in any wikimedia project bcoz every wiki has its own need.I hope you all will understand that. Regards
(In reply to comment #15) > A wiki like this > http://hi.bharatdiscovery.org/india/%E0%A4%AD%E0%A4%BE%E0%A4%B0%E0%A4%A4%E0%A4%95%E0%A5%8B%E0%A4%B6:%E0%A4%B8%E0%A4%B0%E0%A5%8D%E0%A4%B5%E0%A4%BE%E0%A4%A7%E0%A4%BF%E0%A4%95%E0%A4%BE%E0%A4%B0 > is using Replace text extension who have no funding and extra resources.But > inspite of our vast developer team of Wikimedia foundation we are not able to > use this extension on Hindi Wiki that really suck our mind. > Wikimedia does not have a "vast developer team", we've got a couple dozen people at most. But with a tiny staff and a tiny server farm (relatively speaking), we do run the world's fifth largest web site. For some extensions, the performance concerns mean they can be enabled on small (few pages, low traffic) wikis but not on large ones (and in many cases, for WMF wikis this means things can't be enabled on any WMF wiki, even smaller ones, because all wikis share the same servers).
(In reply to comment #16) > (In reply to comment #15) > > A wiki like this > > http://hi.bharatdiscovery.org/india/%E0%A4%AD%E0%A4%BE%E0%A4%B0%E0%A4%A4%E0%A4%95%E0%A5%8B%E0%A4%B6:%E0%A4%B8%E0%A4%B0%E0%A5%8D%E0%A4%B5%E0%A4%BE%E0%A4%A7%E0%A4%BF%E0%A4%95%E0%A4%BE%E0%A4%B0 > > is using Replace text extension who have no funding and extra resources.But > > inspite of our vast developer team of Wikimedia foundation we are not able to > > use this extension on Hindi Wiki that really suck our mind. > > > Wikimedia does not have a "vast developer team", we've got a couple dozen > people at most. But with a tiny staff and a tiny server farm (relatively > speaking), we do run the world's fifth largest web site. For some extensions, > the performance concerns mean they can be enabled on small (few pages, low > traffic) wikis but not on large ones (and in many cases, for WMF wikis this > means things can't be enabled on any WMF wiki, even smaller ones, because all > wikis share the same servers). I understand Roan, We all are proud of our Developer team of Wikimedia Foundation.I know you all have lots of stuff to be performed on servers etc..But all our expectations are from developers side only that they would support us and make our problem easy.I think we are getting enough support from our Developer team.We shall rather wait to deploy risky extensions. Thank you & Regards Mayur
