Notes

Reminder : decisions taken at Montpellier's pre-hackathon:

• each gadget has an independent repository on Git
• a bot ships the code to each wiki that has requested the service
• each gadget is translated on translatewiki
• a local configuration is provided for each wiki to setup small changes

Things to take decision on:

• T192228: Request creation of globalgadgets VPS project, now stalled. Question is: why use GitLab instead of Gerrit.
  • Pros:
    • on Gerrit, people will not be able to edit/contribute. A lot of other tools are hosted elsewhere for that.
      • (side note) Release Engineering should be aware of that and be asked if they consider to offer a different tool/interface.
    • More advanced code review features are overkill for a gadget project
    • Possible to get a grant to have a specific server.
  • Cons
    • Gerrit is used on all other projects
    • More advanced code review features
    • What about the Gerrit to GitLab migration?
    • Multiplies the number of used tools
  • To be continued on T192228, with those pros and cons and discuss with the Release Engineering people.
• One repository per gadget or something else?
  • It is possible to use subprojects.
• Use Phabricator instead of GitLab/Gerrit? https://www.mediawiki.org/wiki/Requests_for_comment/Migrate_code_review_and_management_to_Phabricator_from_Gerrit
  • Create a sandbox and try it.
  • We can ask @Aklapper about that.
• @Tgr works on an extension that coordinate central gadgets deployment between Git and the wikis. T187749: Make it possible to use code from an external repository for editor-controlled Javascript/CSS

What about:

• How to convince English Wikipedia to be on the loop?
  • Gadgets and Modules are made by developers, who are aimed to work together.
• Templates?
  • Can be centralized in the same project. That would ease translations.
• How new wikis will be welcomed?
  • During the proof-of-concept time, only one gadget on a few wikis will be available.
  • Other wikis/gadgets/Templates will be progressively added. The taskforce takes all decisions when to open the project to more people/projects.
• Third-party wikis?
  • They can have access to the repository.
  • They can get the bot working for them?

Decisions

• Goal: one gadget centralized before Wikimania as a proof of concept, and deployed on two friendly wikis (ca and fr, probably)

Thank you for hosting your session at WMHack! If you have any notes or slides please add them to the task and then make sure to close the task when there are no more actions. :)