We need a common repository for Scribunto modules and templates
Open, Stalled, NormalPublic

Description

We need a central repository of Scribunto modules and templates. Currently they are spread all over.

It has been broadly requested/discussed in many places and this is an attempt to have a URL to watch a contribute to this topic.

Scribunto upstream is in mediawiki.org and therefore I think such central repository should also be in mediawiki.org, to satisfy equally Wikimedia and MediaWiki centric projects.

See Also:

Mentioned in discussion below:

Details

Reference
bz50329
bzimport raised the priority of this task from to Normal.
bzimport set Reference to bz50329.
bzimport added a subscriber: Unknown Object (MLST).
Qgil created this task.Jun 27 2013, 11:06 PM
Qgil added a comment.Jul 2 2013, 9:09 PM

What would this central repository need, apart from deciding where will it be?

I mean, mediawiki.org only misses a category for Lua based templates and another one for Scribunto modules (very easy) and just a bit of love putting together the documentation and support channels. The rest (e.g. announcing new templates, review processes...) will come or not based on the community activity.

All this is kind of happening at https://en.wikipedia.org/wiki/Wikipedia:Lua but that is really not the right place, so other Wikimedia projects are starting their own Lua corners, and just wait when MediaWiki 3rd party admins start adding to the mix.

We could just tell all these people that mediawiki.org is the right place, their commons place, just like it is for extensions, and the rest would come.

PS: I know it's not that simple, but it's not that complicated either. The more time we let this pass the more difficult it will be to undo changes.

Anomie added a comment.Jul 2 2013, 9:15 PM

(In reply to comment #1)

What would this central repository need, apart from deciding where will it
be?

Support in software so that it would work something like Commons does for media. The idea is that the code would exist in one place and be available to all without it having to be copied and pasted to each one.

Note that Commons itself will not be the place for this; the Commons community doesn't want it, and various others wouldn't want it there either.

greg added a comment.Jul 2 2013, 9:19 PM

In the roadmap, we want to get to this in October of 2013 (as of right now, could change in priority between now and then):
https://www.mediawiki.org/wiki/Roadmap#Lua

To me sharing code cross-project seems rather useful too. Maybe MediaWiki.org? Meta? If we are looking at the grand scheme of things, I would really like it if there were a 'special' place for this, and all modules in this 'special' space would be injected in the mw table. This way, when such modules turn out to be much used and generally useful, they could possibly in time be 'adopted' into the Scribunto core mw tables without breaking existing usage.

Qgil added a comment.Nov 1 2013, 4:35 PM

Do you think that this is a good candidate for an internship program? I'm considering adding it to

https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects

(In reply to comment #6)

Do you think that this is a good candidate for an internship program?

No.

Qgil added a comment.Nov 1 2013, 4:49 PM

Right. :) Do you mind explaining why? If it's too big or complex, could a first phase be split as a research or prototyping project?

I'm just trying to see whether we can get external help starting this project that we all seem to be too busy to kick off. As far as I know there is no roadmap including a plan or a date for this repository.

He7d3r added a comment.Nov 1 2013, 5:40 PM

See also this thread from may 2013:
"[Wikitech-l] Centralized Lua modules for Wikisource (OPW mentor needed)"
http://lists.wikimedia.org/pipermail/wikitech-l/2013-May/069658.html

(In reply to comment #8)

Right. :) Do you mind explaining why? If it's too big or complex, could a
first phase be split as a research or prototyping project?

Not to be rude, but you seem to be exhibiting a lack of research yourself. You're aware of the interwiki transclusion GSoC project and its outcome?

You also seem to have not researched current requests for comment (linked in comment 5) before filing this bug.

Large, abstract, and technically complex projects such as implementing a central code repository are terrible for inexperienced users, in my opinion. Discrete tasks that can be implemented in production are a much better use of resources.

I fail to see how this bug is not a duplicate of bug 39610.

Qgil added a comment.Dec 9 2013, 7:27 PM

(In reply to comment #11)

I fail to see how this bug is not a duplicate of bug 39610.

That bug report says:

"Depending on which model is chosen, additional bugs may need to be filed. In
particular, if a central repository model is chosen, there needs to be a
discussion about where to host such modules (for example, scripts.mediawiki.org
or scripts.wikimedia.org) and what to host alongside them (for example,
JavaScript gadgets)."

This report is about the central repository model.

(In reply to comment #13)

(In reply to comment #11)

I fail to see how this bug is not a duplicate of bug 39610.

That bug report says:

"Depending on which model is chosen, additional bugs may need to be filed. In
particular, if a central repository model is chosen, there needs to be a
discussion about where to host such modules (for example,
scripts.mediawiki.org or scripts.wikimedia.org) and what to host alongside
them (for example, JavaScript gadgets)."

This report is about the central repository model.

The comment you copied and pasted suggests the need for a discussion. This would mean using the mailing list(s) or the wiki(s) to have such a discussion, not Bugzilla. In my view, this bug continues to be a direct duplicate of bug 39610.

Will the repository also include non-Lua templates?

(In reply to comment #15)

Will the repository also include non-Lua templates?

I don't know if this proposal by Quim Gil covers that case, but mine at Comment 12 certainly does.

Reedy added a comment.Apr 25 2014, 1:06 PM
  • Bug 64421 has been marked as a duplicate of this bug. ***

The modules to centralize must speak any language.
To support this evolution, the Module:ControlArgs can:

  • adapt any calling module for international use i18n in argument names, error messages, wikitext and categories.
  • provide to many small wikis the same modules as the main wikis, only by adding translations tables in the sub modules .../I18N.
  • help users, when he/she edit any page, by a documentation panel, like Mediawiki do this for modules. See Bug 51660.
  • help administrators to support wikis in other languages, by translating error messages. See Bug 66051.

See the live demo (in debug phase): https://fr.wikisource.org/wiki/Module:ControlArgs

Rical, please don't spam your pet module on every tangentially-related bug report. Thanks.

Rical added a subscriber: Rical.Dec 12 2014, 8:15 PM
hoo added a subscriber: hoo.Jan 31 2015, 12:11 PM
Qgil updated the task description. (Show Details)Feb 12 2015, 12:36 PM
Qgil set Security to None.
scfc added a subscriber: scfc.Feb 12 2015, 2:25 PM

Seems to be superseded by T66474

Tgr added a subscriber: Tgr.Feb 12 2015, 5:23 PM
Quiddity updated the task description. (Show Details)Feb 12 2015, 8:04 PM
Quiddity added a subscriber: Quiddity.
jayvdb added a subscriber: jayvdb.Feb 14 2015, 7:41 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 3 2015, 3:27 PM
-jem- added a subscriber: -jem-.Aug 10 2015, 4:41 PM
Qgil added a comment.Sep 17 2015, 1:51 PM

I was wondering whether there is an interest to push this discussion in the context of the Wikimedia-Developer-Summit-2016. The goal could be to agree on a basic plan and the best way to bring it to an implementation as part of the 2016-17 annual plan (or something along these lines). The globalization of gadgets seems to be progressing, but the templates/modules could benefit from a coordinated effort.

https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016#Call_for_participation

I was wondering whether there is an interest to push this discussion in the context of the Wikimedia-Developer-Summit-2016. The goal could be to agree on a basic plan and the best way to bring it to an implementation as part of the 2016-17 annual plan (or something along these lines). The globalization of gadgets seems to be progressing, but the templates/modules could benefit from a coordinated effort.

https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016#Call_for_participation

Probably not this task, but T91162.

Qgil changed the task status from Open to Stalled.

OK. Marking this task as Stalled and blocked by T91162: RFC: Shadow namespaces, then.

Jay8g added a subscriber: Jay8g.Sep 19 2015, 6:15 PM
IMPORTANT: If you are a community developer interested in working on this task: The Wikimedia Hackathon 2016 (Jerusalem, March 31 - April 3) focuses on #Community-Wishlist-Survey projects. There is some budget for sponsoring volunteer developers. THE DEADLINE TO REQUEST TRAVEL SPONSORSHIP IS TODAY, JANUARY 21. Exceptions can be made for developers focusing on Community Wishlist projects until the end of Sunday 24, but not beyond. If you or someone you know is interested, please REGISTER NOW.
Restricted Application added a subscriber: JEumerus. · View Herald TranscriptJan 21 2016, 2:53 PM
Meno25 removed a subscriber: Meno25.Feb 22 2016, 5:36 PM
Legoktm changed the status of subtask T91162: RFC: Shadow namespaces from Stalled to Open.Apr 20 2016, 10:35 PM
MarcoAurelio added a subscriber: MarcoAurelio.
robkam awarded a token.Dec 9 2017, 7:58 PM
robkam updated the task description. (Show Details)Feb 13 2018, 12:11 PM
robkam updated the task description. (Show Details)
gpaumier removed a subscriber: gpaumier.Wed, Jul 18, 5:57 PM