Extension:Chart/專案/最新進展

This page is a translated version of the page Extension:Chart/Project/Updates and the translation is 46% complete.

Charts are now available for mediawiki.org and 3 pilot wikis: Hebrew, Italian, and Swedish Wikipedias. As mentioned in the last update, these will be the only deployments for the time being to provide stability over the holidays and make space for any major issues to be uncovered and addressed before a wider rollout.

Early feedback and upcoming improvements

We’ve heard your feedback about some of the challenges of working with the Data namespace and the limitations of tabular data. In the new year, we’ll be exploring ways to improve this, starting with:

  • Better discoverability of pages in the Data namespace using categories
  • Providing visibility into which wiki pages include a given chart and which charts rely on a given tabular dataset
  • Adding support for specifying which fields from a tabular dataset to use for a given chart in the definition

Thanks for continuing to follow along with the project and providing feedback. We’re looking forward to continuing to improve the extension as we roll out to more wikis.

2024年11月: Production deployment and security review complete

This month we deployed Charts to production, and it is now enabled on Commons and testwiki. You can see a working version at testwiki:Charts. There are a few design tweaks that will come over the next few weeks, mostly to the styling of the hover tooltip.

We also got confirmation from the Wikimedia Foundation Security team that the extension is considered low risk for rollout to pilot wikis in December. We will be taking action on the recommendations from the security review over the coming months as we scale the rollout.

Pilot wiki deployment

We're close to confirming the 3 pilot wikis that will have Charts enabled first, planned for the first week of December. Once we deploy to these wikis, there will be a pause on further deployment until 2025. This is to provide stability over the holidays and make space for any major issues to be uncovered and addressed before a wider rollout. Expect to hear more about this soon!

2024年10月: Working towards production deployment

Throughout September and October, the team has been working on taking the prototype that is currently deployed in the beta cluster and getting it into a production-ready state. The next major milestone we are working towards is deploying the Chart extension to testwiki and testcommons, which we are aiming to do in November. We are simultaneously working towards a security review, which is an important step for the project given security concerns were the reason the Graph extension was ultimately disabled. Following production deployment and security approval, we will begin rolling out to real wikis.

What to expect

The initial version of the Chart extension released to testwiki and testcommons in production will be fully functional, but not yet feature-complete. We've simplified the prototype to focus on the core workflows of creating and embedding charts, in addition to designing a visually accessible reading experience on mobile and desktop devices. Editors will be able to define basic line, area (stacked), bar, and pie charts on testwiki using tabular data stored on testcommons. Documentation for the extension is now available on the extension page, with a working version on beta.

Once we've deployed to production, we'll be adding more features and functionality. Notably, we want to improve the experience of working with tabular datasets and support more customization of the visual presentation of charts (e.g. customizing the colors). We will also be turning our attention towards supporting editors with migrating legacy graphs to charts.

Deployment to real wikis

Soon after deploying to the test wikis, we are planning to deploy the extension to production Commons and real wikis so that we can collect feedback about real-world use and quickly address any high priority issues. Let us know if you'd like your wiki to be one of the first to receive the new extension.

2024年8月:Wikimania回顾和Beta集群部署

Wikimania会议录音
  • Wikimania 总结:。感谢所有参加Wikimania会议或者在产品与技术桌前停下来讨论项目的朋友。通过与大家的交流,我们学到了很多,了解了你们之前创建的图表类型以及未来希望创建的图表类型。我们在Wikimania交流中了解到的一些主要主题已在Phabricator上总结。主要收获是要继续致力于支持最受欢迎的图表模板所启用的核心图表类型,并探索对维基数据等替代数据源的支持。我们还将研究使用Commons作为图表集中存储解决方案时遇到的一些挑战。
  • Beta集群部署
    • 您现在可以在Beta版的Commons中创建图表(示例),并将其嵌入到其他Beta维基上的页面中(示例:英文Beta维基百科德文Beta维基百科)!这让我们更接近于今年秋季在常规维基上进行部署。我们还将开发更多功能,例如支持其他图表类型和视觉自定义。请自行测试这些图表,并告知我们您遇到的任何问题!
    • 一些重要功能仍然缺失。例如,当您在Beta版Commons上编辑图表定义或数据页面,并且该图表在另一个Beta维基的页面上使用时,其外观不会自动更新。要更新图表渲染,您必须清除页面缓存或进行一次空编辑。我们将使其自动更新:T370378

2024年7月:关键决策:库、图表类型、定义存储。加入我们的Wikimania会议

首先,我们很高兴地分享,我们已经就该项目做出了三个关键决策:

  1. 我们已经选定了一个数据可视化库。经过研究和原型设计后,最终考虑的两个选项是Apache eChartsVega(此前用于图表的库),最终决定使用eCharts。不过,我们并未排除未来使用Vega的可能性。想了解更多关于eCharts和Vega的信息,请查看常见问题
  2. 我们还分析了图表模板/模块的使用情况,以确定开始原型设计的图表类型以及其参数。我们将从折线图开始。这些参数也应适用于其他相关的图表类型。折线图之后,我们将转向基于地图的可视化,因为这些图表与其他类型大相径庭,可能需要不同的方法。
  3. 图表定义将存储在Commons上自己的.chart页面中,位于Data:命名空间下。我们希望将图表视为独立的内容类型,而不仅仅是文章的一部分。通过将图表作为链接提供,用户可以轻松地在维基媒体平台之间甚至在其他平台上重用相同的图表。希望将图表嵌入文章中的编辑者可以使用一小段wikitext来实现,类似于从Commons中包含图片,而无需与复杂的模板交互。我们将快速构建原型,以便开始测试我们的假设。 前往常见问题解答了解更多信息。

对于参加Wikimania的人:Chris和Szymon将主持一个会议:“图表,取代Graphs的继任者:一个安全且可扩展的数据可视化工具”(添加到您的收藏夹)。他们将进一步介绍该项目,并预览新扩展的早期原型。主要内容将是如何定义图表以及如何将其嵌入到文章中。请亲自或虚拟参加我们的会议,并注册Wikimania以将会议添加到收藏夹。对于亲自参加的人员,还将设有一个Graphs / Charts展台。欢迎所有不能参加会议或希望进一步交流的人。

2024年7月:專案啟動

我們很高興地宣布,本專案已於7月1日正式啟動。在本月上半月,我們將決定如何使用Chart圖表以及如何建構基礎服務。

最重要的是,我们将选择数据可视化库(T368336)。我们包含了志愿者和工作人员建议的选项。Vega,之前用于图表的库,是其中之一。欢迎提出其他建议,但由于选项众多,我们无法测试所有库。如果您有评估这些库时应考虑的标准,请在我们的讨论页面上写下您的意见!

我们还将筛选优先开发的图表类型。然后,我们会选择一种图表开始开发(T368478)。在此过程中,我们将分析现有图表的使用情况,并考虑志愿者的反馈。随着我们了解哪些图表类型对百科内容最重要以及所选库能实现哪些功能,这个列表会有所调整。

相关地,我们还在探索如何在wikitext中定义图表的语法,或者是否完全不使用wikitext进行定义(T368350)。这还不是最终决定,我们希望尽快推出服务原型。除了考虑语法的易懂性和易用性外,我们还在考虑从现有图表定义转换的难易程度。

一旦我们做出这些早期决策,我们将建立所需的基础设施来创建第一个图表类型。计划是将其作为原型提供,以便志愿者可以开始实验。同时,我们欢迎在讨论页面或Phabricator上提出问题和评论。

我们也鼓励你注册参加Wikimania。我们将在那里介绍这个项目。希望我们能有足够的进展,以便分享有趣的消息。无论是现场还是远程参与,都需要注册。

最后但同样重要的是,我们在考虑使用什么工具来与参与讨论Graph的社区成员保持联系。您希望收到有关新项目更新的通知,还是更倾向于在您的讨论页上收到群发消息?让我们知道如果您有强烈的偏好。谢谢!