Talk:Developer hub

Links for skins developers
i was noticed that there are two different links on this page that look like links about skin development: --Lig13 13:29, 7 February 2008 (UTC)
 * under "Extending MediaWiki" headline there is "Skins - Change the look and feel of MediaWiki."
 * but under "Help for extension writers" there is "Skins: Manual:Skinning" that is usefull one

Decision-making version of MediaWiki
Dear Sirs,

No doubt MediaWiki is superb platform for collaborative writing and editing. However I am trying to create “decision-making” MediaWiki website to collaborate in resolving social problems on all levels from global to local; a website resembling virtual brain and mind (www.netsmind.org). Doing this I’ve faced two problems: a) incorporation of formal decision-making model (algorithm) to guide collaborative decision-making process and b) set up an option for alternative decisions. (Keep in mind that collaborative decision-making process excludes voting by definition. Voting is an element of collective decision-making process, which is democracy. Opposed opinions are eliminated by voting in favour of majority. In collaborative decision-making process in case of opposed opinions should be elaborated two or three alternative feasible solutions, which will be verified in social practice. So there is no voting mechanism at all).

I’ve incorporated formal decision-making model as contents, instead of template, very unprofessional manor indeed. (I am Psychologist, not Developer or even Webmaster and can’t write templates). The second problem – option for alternative decisions is high above my limited knowledge in this field). Apparently, because of this reason I can’t promote my site.

I hope sooner or later collaborative decision-making platform will be created and could be of interest to your team to write such version of MediaWiki. Perhaps decision-making platform will be new generation of collaborative software, as making-decisions is more complex and complicate process compare with systemising information. I assume writing few specific templates could be the first step to create full such version.

Nevertheless my inquiry is could your team help me referring my case to Developer, who could be interested of creating of decision-making platform and create for me two or three such templates?

Thank you for your time and all you did to create such fantastic platform.

Regards

D. Tchurovsky tchurovsky@gmail.com

Feature?
Hello - I am finding it a bit difficult to find the correct place to drop a technical suggestion: the mediawiki software list the timestamp of any edit in the page history, right? Would it be possible to update the software so that in addition (or maybe as an alternative, selected in preferences), the time is given as "X hours, X minutes, X secondas ago"? Cheers and keep up the good work! Ingolfson 08:49, 5 February 2009 (UTC)
 * The Bugzilla page says: "All bugs in the MediaWiki software should be reported at bugzilla.wikimedia.org. This is also the place to request new features or enhancements to the software." (highlight mine). Good luck with your feature request. -- Jokes Free4Me (talk) 08:49, 7 January 2013 (UTC)

Extension points
It says "There are 5 main extension points" but 6 are listed. I take it integration with S3 is the minor extension point? Perhaps we should say that. Tisane 06:57, 22 March 2010 (UTC)

Extensions & Skins must be GPL?
Apparently Wordpress themes and plug-ins must be liscensed under GPL (see this).. is the same true for Mediawiki? --Frantik 20:58, 22 July 2010 (UTC)
 * Its debatable - see the thread at wikitech-l/2010-July/048436.html . I'd lean towards they don't have to be gpl (based on that thread), but IANAL and don't understand the issues involved very well. Bawolff 17:37, 19 September 2010 (UTC)

Possible?
If one person starts a wiki, can they transfer ownership to another person? --TripleU 06:31, 29 July 2010 (UTC)


 * Sure. To fully transfer ownership, you'd need to transfer control of the domain and the hosting. —Emufarmers(T 19:13, 13 January 2011 (UTC)

Links to consider when improving this page

 * Just a list of links I was keeping in my user discussion page for the day I (or someone else) start working on improving this page.--Qgil (talk) 21:05, 17 December 2012 (UTC)


 * https://meta.wikimedia.org/wiki/Glossary
 * Developers
 * http://workingwithmediawiki.com/
 * http://www.mediawiki.org/wiki/Gerrit
 * http://www.mediawiki.org/wiki/Git/New_repositories
 * https://blog.wikimedia.org/2012/11/21/lead-development-process-product-adviser-manager/
 * http://meta.wikimedia.org/wiki/Wikimedia_Blog
 * How to help with documentation.
 * https://www.mediawiki.org/wiki/Wikimedia_Features_engineering
 * https://www.mediawiki.org/wiki/Wikipedia_Education_Program
 * https://www.mediawiki.org/wiki/MediaWiki_developer_meetings
 * http://www.mediawiki.org/wiki/Mobile_Beta
 * Volunteer coordination and outreach/Training materials
 * Project:WikiProject_Bug_Squad
 * Project:Help
 * https://labsconsole.wikimedia.org/
 * http://www.mediawikiwidgets.org/
 * Category:MediaWiki Introduction

Beyond MediaWiki Core and extensions
If we want to call this a Developer Hub we need to go beyond MediaWiki core and extensions. We could start fixing this integrating an adaptation of the text we had a How to contribute (now cut because that page was getting too long and cluttered):

The MediaWiki community is maintaining more than 5 million lines of code, and counting. Become a MediaWiki developer. Code contributions are welcome!
 * MediaWiki core and extensions. PHP knowledge required. Check How to become a MediaWiki hacker and the Developer hub.
 * Write enhancements in the form of small shareable user scripts and gadgets written in Javascript.
 * Coming soon: write templates and ParserFunctions with Lua scripting.
 * Multimedia developers are very welcome to Media Projects.
 * Mobile developers are welcome to Mobile Projects.

Developer Hub update
After polishing How to contribute, I want to start working on the update of this Developer Hub. Some key ideas:

And probably more, but getting these 3 pillars right the rest will be easy.--Qgil (talk) 18:44, 8 February 2013 (UTC)
 * It needs to reflect all the software development activities and not only MediaWiki core & extensions. In fact there are many better entry points that should be promoted.
 * Gadgets (including userscripts), Mobile, Templates (focusing on the upcoming Lua-based), Bots, Skins, Extensions & Core.
 * It needs to offer language-centric pages to attract developers with certain skills to the right projects.
 * PHP, JavaScript, HTML, CSS, Python, Perl, MySQL, Java... What else?
 * It needs to identify top projects welcoming developer contributions. Being a "top" project is not enough if you are not ready to handle new contributors and patches properly. The list might change based on the current situation and priorities.
 * The mobile apps seems to be good candidates with a good track of welcoming contributors. What else?

Recently a discussion started on wikitech-l about Developer Hub simplification, and it was decided to take it here. Following the main outline of the proposed ideas, we could have:

to send people to appropriate places. Less is more.
 * Developer Hub: a general overview with a very focused selection of links
 * /Get started (or similar name): intro for newcomers with relevant links.
 * /Reference (or similar name): what developers need on a regular basis.

Developer Hub and Get started should be more concise and visually pleasant, satisfying new developers. Reference is for usual suspects, so it could have more beef and links in order to have everything in one place.--Qgil (talk) 18:28, 27 February 2013 (UTC)


 * Just adding that IMO reference docs should have more links not because they can afford to be less user-friendly, but precisely because they're supposed to be index-like material. E.g. Manual:Code. So detailed descriptions (I assume that's what you mean by "beef") don't fit here, as I see it; instead, that should be spread across the specific components linked to from the reference, which would only contain a brief description of each item.
 * Also, I reiterate the question I posed in the wikitech-l thread: how should Manual pages be reconciled with this approach? Currently most of them are pages about specific components (e.g. configuration variables or specific files or classes, such as Manual:LocalSettings.php), several are long, beefy descriptions of complex subsystems (e.g. Manual:Messages API, Manual:Skinning), and only a handful are reference-type indices (e.g. Manual:Code). Personally, I think the second type should be split into smaller pages (perhaps part of the "get started" group?), all interconnected, instead of attempting to describe the whole system. That's what hyperlinks are for :) --Waldir (talk) 21:02, 27 February 2013 (UTC)
 * Ref more links in reference docs yes, this is what I meant (but you said better). I think we can plug Manual pages under Reference, or even make it the same thing (?). Here and now I want to focus on improving Developer hub page and putting together a decent /Get started page. I have no opinion about organizing Manual pages but it is better to keep both discussions separate. Most Manual pages won't be linked from these two pages anyway. If you want to work in that direction be my guest. :) --Qgil (talk) 00:24, 1 March 2013 (UTC)
 * Agreed. I'm more interested in working in the Manual/reference documentation, so I won't pollute this thread with more about that (hopefully the wikitech-l discussion will continue, and in any case I added this as a topic for discussion in the Amsterdam Hackathon. That said, I will of course offer my thoughts and suggestions on the refactoring and "get started" work you or others might do, and help out in small ways if I can. --Waldir (talk) 17:05, 1 March 2013 (UTC)
 * Good! And same here: let me know which page(s) to watch and I will help at least with feedback.--Qgil (talk) 20:54, 1 March 2013 (UTC)
 * For future reference, here's a list of previous discussions regarding the structure of Manual: pages: Project:Manual --Waldir (talk) 21:06, 6 March 2013 (UTC)

With all the diversity and complexity of projects in the Wikimedia /MediaWiki context, a high level overview would be really welcome. Sumana sent this good example: Roadmap for learning Rails.--Qgil (talk) 17:38, 21 March 2013 (UTC)

re: your "Gadgets (including userscripts), Mobile, Templates (focusing on the upcoming Lua-based), Bots, Skins, Extensions & Core.
That's a good way to think about it, but new potential developers don't know what that division means. Maybe this page could offer some leading questions, e.g. (with everything linked):
 * Want to improve the look of wiki pages?
 * Great! Create a wiki account, modify your User CSS to see thechange, join the design mailing list and share your idea. If you're making extensive changes you can package them into a "skin". See category of unsolicited wikipedia redesigns


 * Want to improve the way wiki pages work?
 * You can do a lot in client-side JavaScript code and CSS. Create a wiki account, modify your global.js. All wiki pages load jQuery, there's a JS API with lots of utility functions and the ability to call the MediaWiki Web API. You can share your code with others and turn it into a gadget.


 * Want to fix or improve the code?
 * Create an account so you can create a bug or update an existing one. Install MediaWiki (it's easiest to grab the MediaWiki-Vagrant virtual machine) and start hacking. Get an account on our code review system gerrit and offer your fix for review.


 * Want to add a new feature to MediaWiki?
 * Maybe it's doable in client-side JavaScript, otherwise you're probably looking at writing an extension in PHP. Install MediaWiki (it's easiest to grab the MediaWiki-Vagrant virtual machine), adapt one of the sample extensions, and start hacking. Talk to developers on IRC in #wikimedia-dev


 * Want to automate some wiki maintenance task?
 * You can write a script or bot that interacts with MediaWiki pages. You can develop it in a variety of languages. If it's useful, we provide "tool labs" infrastructure for running some scripts and bots.


 * Want to remix all the information that users have contributed to Wikimedia projects?
 * We have APIs for that, and complete data dumps, and the Wikidata project filled with facts. (But now this is bleeding over into the Web API part of How to contribute)

MW offers so much it's hard not to add too much. Anyway, just "thinking aloud" -- SPage (WMF) (talk) 06:29, 10 January 2015 (UTC)

Problem_in_Lua_Install
hi, i need help in Extension_talk:Lua

Thanks, فلورانس (talk) 22:46, 2 July 2013 (UTC)

Following updates
This page mentions some communication venues, but only in terms of "discussion" and not in terms of "see what's going on" or "join the community" or "follow the last updates" of development, code review and so on. How to become a MediaWiki hacker has even less. Is this information really irrelevant? Is it placed somewhere else? For the last hour or so, I've been looking for a place where to add a notice that on #wikimedia-dev you may not find all the updates you expect, as the discussion and even the bot updates are fragmented to multiple channels (now not only for obscure libraries and repos but also localisation extensions ), but I didn't find any appropriate one. I could just add some pointers from the detailed descriptions of the channel(s). --Nemo 13:50, 2 August 2013 (UTC)
 * Most of the IRC information has been moved to IRC/Channels. I'm not sure that's very clear about how to follow updates, either. It contains phrases such as "Updates from several repositories" for lack of more precise information. We can't really tell people "go read the wikibugs code to find our where stuff happens". It would be useful to come up with a one-sentence summary of where MediaWiki development can in effect be followed. (Bawolff raised this on #wikimedia-tech just yesterday, if I remember correctly.) --Nemo 20:18, 11 June 2018 (UTC)

I need wiki templates code for wikia
I been ask to remove my user page from wikipedia can i get the code for all the templates so that i can see all my work in wikia or other mediawiki wikis?

Itzcoatzin (talk) 01:33, 20 February 2014 (UTC)


 * Special:ExpandTemplates. --Nemo 07:43, 20 February 2014 (UTC)

Future of this Developer Hub in relation to dev.wikimedia.org / Dev namespace
The Engineering Community Team has committed to T101441 Goal: Integrate new Developer hub with mediawiki.org for the next quarter. One of the blockers is T313 Future of the current Developer Hub at mediawiki.org. I have just posted a proposal in that task. Your feedback is welcome, there (preferably) or here. For general background, see dev.wikimedia.org.--Qgil-WMF (talk) 10:38, 11 June 2015 (UTC)

Smart way to recover OST file with Inspire OST to PST Converter tool
Inspire OST to PST Converter software program is simple to recognize tool which is uncommonly meant for non-specialized customers to finish OST to PST Conversion with no system faults. The device is created with slicing aspect calculations to restore, get better the harmed or ruined OST file and moreover convert degenerate OST information into PST file set up. This product is additionally useful to change over OST to mbox, eml, emlx, msg, html, vcard, vcal and html layout. It's underpins window servers ninety five, NT, 98, ME, XP, Vista, 7, 8, and 8.1,10 (32bit and 64bit). This is the ace feature which causes you to get back your misplaced and all the time erased documents and oversee them in a comparable report which includes Emails, inbox, outbox, despatched-matters, erased things, drafts, contacts, logbooks, notes (to, cc, bcc, challenge, date and time) with a hundred% precision.


 * Support MS Outlook 98, 2000, 2002, 2003, 2007, 2010, 2013, 2016 and 2019.
 * It can convert any length of report.
 * Convert encrypted and password included files and paintings even within the absence of MS Outlook.
 * Support Office 365 & Live Exchange Server and provide 30 days
 * You also can be Converted OST file into PST, MBOX, EML, MSG vCard& HTML Formats
 * Support OS Windows ninety five, NT, ninety eight, ME, XP, Vista, 7, eight, and eight.1,10 (32bit & 64bit).
 * Gives lifetime validity license and updates.
 * Converted PST is likewise on hand with MS Outlook.

Know more - https://www.inspiredatacare.com/convert-ost-to-pst.html