If we can replace the low-level perl script and Ploticus backend with code that generates SVG directly, it could be a lot easier to create a live editing tool for timeline data. This could be much more pleasant to work with than the edit-preview cycle, and encourage more usage of timelines.
See Also T45115: Create a VisualEditor plugin tool to add/edit Timelines
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| Update fr payments image to listen on non-SSL port too | repos/releng/dev-images!6 | ejegg | paymentsHttp | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T44725 Multimedia file format support (tracking) | |||
| Open | None | T56213 Infographics, graph, chart, diagram, plotting, animation support (tracking) | |||
| Declined | hashar | T29157 Provide a stand-alone interactive visual tool to create and edit EasyTimelines (not in the VisualEditor) | |||
| Declined | None | T29156 EasyTimeline: replace perl script & Ploticus backend with PHP and output via GD or SVG |
I also said this on bug 27156 - but we already generate svg's for every timeline (don't really use them for much though) - http://upload.wikimedia.org/wikipedia/en/timeline/688dde24168b00c8abaea72a41adad6d.svg
I'm rather sure that Erik Z. will not be working on this. James, what would be the best pointers to someone willing to add VisualEditor support for EasyTimeline, or wondering whether it's in the VisualEditor team's roadmap?
"Skills: HTML / JavaScript / jQuery development is required. A good grasp of UX / Web design will make a difference."
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#VisualEditor_plugins
The Facebook Open Academy Program [1] is interested in this project, but we would need a technical mentor.
[1] http://lists.wikimedia.org/pipermail/wikitech-l/2013-November/073226.html
vladjohn2013 wrote:
Hi, this project is still listed at https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#VisualEditor_support_for_EasyTimeline
Should this project be still listed in that page? If not, please remove it. If it still makes sense, then it could be moved to the "Featured projects" section if it has community support and mentors.
Wikimedia will apply to Google Summer of Code and Outreachy on Tuesday, February 17. If you want this task to become a featured project idea, please follow these instructions.
Will this feature be needed after launching Graph extension? Vega could represent any kinds of graphs out of data. E.g. http://trifacta.github.io/vega/editor/?spec=lifelines (and see other examples)
Possibly, but we'd need to come up with a transition plan. Killing EasyTimeline and converting all the old revisions to use the new tool wouldn't be ideal…
Well, unless EasyTimeline provides significant additional value (which it just might - I don't know it well enough), I think we shouldn't duplicate functionality - bigger security attack surface, more bitrot ))) But yes, we could have a gsoc project to write a converter ))
This is a message posted to all tasks under "Re-check in September 2015" at Possible-Tech-Projects. Outreachy-Round-11 is around the corner. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.
This is a message sent to all Possible-Tech-Projects. The new round of Wikimedia Individual Engagement Grants is open until 29 Sep. For the first time, technical projects are within scope, thanks to the feedback received at Wikimania 2015, before, and after (T105414). If someone is interested in obtaining funds to push this task, this might be a good way.
I'd advise against work on this task; see T137291: Transition all use of EasyTimeline to the Graph extension or similar and decommission it from Wikimedia's servers for the likely disposition of the extension.
Removing Possible-Tech - not a good candidate, and I think we should close this outright.
I agree with @Jdforrester-WMF lets focus on Graph instead of EasyTimeline which is really legacy. Prior work would need to be migrated to Graph which is T137291.
Sounds like a WONTFIX. If something was produced which warrants a RESOLVED FIXED, please point out the tool in question.