Hi, On 6/6/07, Brianna Laugher <brianna.laugher(a)gmail.com> wrote: MW gets $ from the New World Order organization - they don't need our puny donations;) NWO wants to control the whole world and one way to accomplish it is to control the people minds - wiki is the idea, MW is the software. ;) MediaWiki is pretty lucky to have the WMF to lean on for development Now serious. I've had similar idea some time ago. There was a job offer on this mailing list and a info "I haven't found any info on the MW where to post job offers..." - so I have suggested to create a new page (sorry don't remember the address right now). Well maybe females are better in promoting such ideas;) I wish you good luck. cheers, Regards, Aretai _______________________________________________ _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Maybe sth like this - http://www.mediawiki.org/wiki/Jobs? Regards, Aretai

Hi, It seems to me on the whole of mediawiki.org there is not a single piece of info about how you can donate to support the software development... true? MediaWiki is pretty lucky to have the WMF to lean on for development funds, but IMO it could generate some donations on its own merits. So many corps using MW for intranets, surely they could be encouraged to give something back.

And I guess there would also be interest in a jobs.mediawiki.org listing. (cf. Twiki's http://twiki.org/cgi-bin/view/Codev/ConsultantsForHire & http://twiki.org/cgi-bin/view/Codev/CodersForHire ) why let companies pay to list such jobs elswhere ( http://www.opensourcexperts.com/Jobs/index_html/MediaWiki/index.html ) when they could be listed right here...

In a single function, branch on the tag name to use the appropriate SqlServer object, and pass it to a single, general function

Jim Wilson writes: require called, right? True, but I am trying to write some highly reusable/maintainable code where the tag name is just input data, since the MediaWiki programming model to "statically map tags to parser functions" doesn't seem optimal for our situation. Here's the scoop. At my company, we have many database servers. For each server, we have a separate wiki tag, <server name here>, that allows adhoc queries to that database server. All these wiki tags have the same implementation, but direct the operation to the named database server. We could have done this instead with a single tag, e.g., <sql server="server1">...</sql>, but for convenience of our wiki users (as well as legacy reasons), we have one tag per server. Right now, whenever we add wiki support for a new database server, we have to modify several pieces of code by hand to add the wiki tag: 1. Create the parser function (very short, just a wrapper that calls a more general function using the specific server's connection string) 2. Create a new setHook call 3. Append the tag name to the $wgExtensionCredits 'description' entry 4. Possibly create a bunch more parser functions & setHook calls in the future, for new purposes This is for EACH server we add. It is a maintenance pain as the number of servers grows, and requests for new kinds of database functionality are growing too. So I want to refactor things to abstract away the servers, make things completely data driven, and stop adding code. In the new model, I simply maintain a collection of "SqlServer" objects that represent the servers. To add support for a new server, I'd just add it to the SqlServer collection and be done. No other code-writing involved. All the above 4 steps go away. But in order to do this, I need to detect the tag name which invoked the extension, so I can do the following: - Get the tag name - Generate all the necessary setHook call(s) - In a single function, branch on the tag name to use the appropriate SqlServer object, and pass it to a single, general function I hope this explanation makes sense. DanB --------------------- Confidentiality note The information in this email and any attachment may contain confidential and proprietary information of VistaPrint and/or its affiliates and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may cause liability. In case you have received this message due to an error in transmission, please notify the sender immediately and delete this email and any attachment from your system. --------------------- _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

It is not about luck! MediaWiki is a wiki software written for Wikipedia, it happens to work for other website too. The main "customer" is still Wikipedia.

Maybe we can add a page somewhere that points to the WMF donation page though.

I think we received "job offers" on the mediawiki-l list, some developers also received private offers to write extensions.

What, so Wikimedia can steal the funds that were directed at development? Aside from some specific projects and our two lead developers, Wikimedia do not contribute a lot of cash to the development team.

I would think it a much better idea if all the core developers established some sort of procedure for accepting donations. If a user likes something we do, e.g. Werdna's cascade-protection feature, or wants to encourage that developer to keep doing things, then they can reward that person directly.

If we can find appropriate software of some description to run on it, http://jobs.mediawiki.org or something (bounties? contracts? some other term? not quite sure I like the term "job" here, as it might not be salaried positions being offered (although I'm sure people could find jobs as MediaWiki development consultants)) sounds great to me, and something worth setting up.