User talk:Varnent
|
||||||||
|
Welcome to Varnent's talk page
on MediaWiki's wiki, a wiki for development and usage of MediaWiki - comprehensive wiki software which powers wikis as large as Wikipedia |
||||||||
Note:
|
||||||||
|
||||||||
A barnstar for you! [edit]
|
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Giving gifts + extension developer support | 1 | 17:04, 12 January 2013 |
| Invited to join MediaWiki Group Promotion | 3 | 18:44, 11 January 2013 |
| Automatic updates of Extension infoboxes | 0 | 07:37, 23 November 2012 |
| Start Point Extension Candidate: MultiUpload | 0 | 17:31, 30 July 2012 |
| AddThis doesn't show on Safari | 0 | 21:23, 19 July 2012 |
| help please | 0 | 07:07, 12 July 2012 |
| 2012_Q1_Extension_Page_Review_Drive | 0 | 13:41, 31 May 2012 |
| Did my first template for the page review | 0 | 22:01, 14 May 2012 |
| AddThis bar collapased by default | 1 | 14:13, 15 April 2012 |
| Wikipedia Stories Project | 0 | 00:41, 12 April 2012 |
| Automatic taxobox | 1 | 04:17, 29 March 2012 |
| Extension 'addthis' stop working on firefox | 2 | 14:13, 15 March 2012 |
| Subversion trunk locked | 2 | 20:39, 5 March 2012 |
| Extensions for corporate wikis | 0 | 14:40, 17 February 2012 |
| Page drive | 2 | 23:47, 25 January 2012 |
| why "third-party" | 3 | 23:29, 30 December 2011 |
| Thank you for the wafels | 4 | 00:08, 22 December 2011 |
| Help from WP | 4 | 07:09, 6 December 2011 |
It has been a while, so revisit this when you get the chance: User:Badon#Giving gifts to Project?
Yeah - I think enough time has passed and enough ideas have been discussed that we can safely do something and not worry too much about backlash. :) I think it would be appropriate to add a page to the Extensions WikiProject are outlining how to request donations and including the info about Amazon wish lists, etc. Maybe add an area to the Extensions template for a donation link - ideally to a section on that page with donation info. My hunch is that if we take this approach, it will not be perceived as official WMF action and we can avoid the headaches of them appearing to be sanctioning the services that developers use to solicit donations. Maybe add a "disclaimer" somewhere stating that these are specific to each developer and not coordinated by or through WMF - or something along those lines that helps address any concerns of "did WMF know that PayPal does XYZ bad thing and now they're using it to solicit developer donations - damn them!" or whatever related hubbub folks prone to complain may find. :)
Thank you for all your work promoting MediaWiki in various forms. You are invited to join the MediaWiki Group Promotion (proposed, waiting for official approval). We are just starting, your questions or feedback about the group itself are priceless. :)
Thank you for thinking of me and for the invite. I would be happy to both help and join as a promoter. I added myself to the members list - feel free to move it to promoters if you think you need help in that area. I love the idea - so anything I can do to help - just let me know. Thanks!
Greetings;
This request is for a specific extension to be inducted as the official start point extension for the 2012 Q2 Extension Page Review Drive.
The extension, Extension:MultiUpload does meet outstanding criterion to be used as a candidate for completion extension for 2012 Q2 Extension Page Review Drive inclusion into the GIT repository and default MW install program. In fairness to other candidate nominees, a vote amongst all standing participants of the Page Drive project should be considered.
Argument In Favor
The aforementioned extension is presently not maintained and has various attributes that are vital to the core MW program. Using it as a start point would allow multiple authors the opportunity to participate in its clean up campaign and help to create a permanent kernel rating for future candidates to emulate.
With all due respects, this proposed extension should be targeted for at least a 2012 Q2/Q3 Extension Page Review Drive passing qualification rating and final code execution submitted to GIT repository by the conclusion of the Q2/Q3 session.
This is an official solicitation to nominate an extension. Your response is requested.
Hello,
AddThis doesn't show the "addthis bar" in Safari (only Share link). On FireFox, the addthis bar is shown but the HeaderTabs extension doesn't run (Only the first tab is shown). Indeed, on IE, Safari, the tabs generated by Headertabs extension are shown. You can see the result on www.wikideb.org.
Best regards.
Pascal Beaujeant Pascal.Beaujeant@uclouvain.be
Hi,
I am ahmed. I made a very simple extenstion. I really don't know what next is. I don't know what tests I should do to make it something better than experimental. And the message about writing the code in the page. if you don't mind, I need some help please.
Hi, The bar is collapsed by default and I need to click on "Share" to access the addthis full links page, then go forward and this time, the bar is expanded... Isn't there any option/trick to change this default behavior? Thank you so much for your support.
That's a good idea! I'll add that to the upcoming features list. :)
Hi!
My name is Victor and I'm a storyteller with the Wikimedia Foundation. I'm chronicling the inspiring stories of the Wikipedia community around the world, including those from readers, editors, and donors. Stories are absolutely essential for any non-profit to persuade people to support the cause, and we know the vast network of people who make and use Wikipedia have so much to share.
Rob Lanphier suggested that I speak with you about the development side of Wikipedia.
I'd very much like the opportunity to interview you to tell your story, with the possibility of using it in our materials, on our community websites, or as part of this year’s fundraiser to encourage others to support Wikipedia. Please let me know if you're inclined to take part in the Wikipedia Stories Project.
Thank you for your time,
Victor Grigas
vgrigas@wikimedia.org
I have a doubt regarding the taxobox. The thing is should it be developed using only Javascript?
We can design maybe a small app using python and django to a major extent.
Cheers, Ashwin
What would be the best approach for the creation of a widget?
Hi,
svn: Working copy '/mnt/upload6/private/ExtensionDistributor/mw-snapshot/trunk/extensions' locked
I wanted to help with the extension review, but this is killing it for me...
Don't bother with ExtensionDistributor. Even when it's not locked, it's usually out of date. Try checking out a copy of the extension from SVN instead.
Exactly. :)
Hi! On the IRC channel #Mediawiki sumanah told me to contact you since I'm writing an extension for my department wiki. I'll tell you more if you are interested, just E-mail me.
Hi Varnent, I have already started to tidy up some extensions pages and make them more comprehensive/appealing. However I just realise that I am the only one. Is the official start still to take place? Cheers
I'm out of town for a conference until next week and plan on pushing a "launch" of it then. Although I'm still contemplating the best ways to do that. Any input would be appreciated. :)
Not a big deal I guess but why "third-party wikis" - I have my own wiki, isn't that a "second-party wiki"? I'm not sure this is really that much clearer than "non-Wikimedia Foundation wikis" which seemed pretty clear to me. Just wondering why you're making this change.
There was a lot of IRC discussion on how to refer to non-WMF wikis. I'm of the mindset that we need to be consistent in our use of terminology across the manual for ease of reading. The Manual:Glossary#Third-party definition references the chats where "third-party wiki" was discussed as the most commonly used existing term by WMF and core developers. While I'm not personally convinced "third-party" is the best possible term, I've conceded it makes the most sense at this point. I also tend to feel that any term with "WMF" is both longer and too "WMF-centric" - which is a complaint I've heard from folks and have made myself about MW documentation.
As to why third-party over second-party - the IRC transcript has a good excerpt by Ryan Lane: "wmf is a first party user. we create the software. everyone else that uses it is third party". Basically a reference to the technical terminology of third party that any non-orginal owner (WMF) or primary consumer (enWP, etc.) is then third-party (non-WMF wikis). Also consistent with how we refer to "third-party extensions" in the documentation and home page.
I'm certainly open to feedback on better terms to use - but do think there should be consistent use of the terms and for now, "third-party wiki" seems to be it.
Thanks for the reply - makes (some) sense. ;-) I'm good with it for now - so long as we keep the redirects in place, I don't really care (there are incoming links from meta). Hmm, this e-mail link worked the one on Project:support didn't, these LQT links are inconsistent. :-\
Tasty, aren't they?! Cheers
lol - indeed - although I just noticed the WikiLove extension doesn't seem to like the LiquidThreads...hmmmm
I guess this will be fixed with LQTv3.0 whenever this may come to reality. I am touching wood.
Amusingly enough, it's apparently more complex than that - lol: https://bugzilla.wikimedia.org/show_bug.cgi?id=33260
Hi, do you know that everything in our Help namespace must be PD, while the WP content you're importing is CC-BY-SA?
I'm not a copyright lawyer - does it qualify for PD once its trimmed and references to WP related areas are removed? Seems like a waste to have to write all help documents from stretch when there is a good base of wording available to be tweaked.
No, the text has to be completely rewritten, see w:Wikipedia:Close paraphrasing. Sorry, I'm deleting all these pages.
That's a rather annoying hassle. No wonder the help section is so stagnant. Can they be placed in the Project namespace or somewhere to help folks using this wiki? Or outreach to the original authors of the help page to seek permission to release into PD? Seems like a waste of time to duplicate work already done elsewhere and using a similar free license.
Ah well - either way I'll maybe come back to those later - not sure how eager I am to reinvent the wheel. :) Thank you for catching it so quick.
