Skip to content

Migrating jQPlot Plans

Ruben Olsen Lærk edited this page Aug 8, 2015 · 14 revisions

What is this about?

Here's a list of "todos" to migrate jqPlot currently on the original jqplot.com website over to this repo. Actually, we're not just migrating, we're also going to improve the library!

Big Plans list

These are topics I can currently come up with we'll have to take of to bring jQPlot back from being a Zombie;

🍪 Please extend and add your own ideas here

Status Plan Comment
open Documentation on this wiki A better place might be the gh-pages branch. This will also give us website for the proejct - see #10 and #45
open Getting Started and introduction This should also be on in the gh-pages branch, as this is the only way we can show interactive examples.
open Documenting examples This should also be on in the gh-pages branch, as this is the only way we can show interactive examples.
open How to contribute and contact us? Link to the jqPlot Google mailing list
open Make a list of other essential pages.
open Make the API available
open Introduce a real API tool which sums up the possibilities of the code Will require us to add formal commenting to the code. (cf. JSdoc)
open Introduce Coding Guidelines and Style-Guide
open Linting the code either with JSLint or JSHint? will help tracking down bugs
open Enforce the Google JavaScript Code Guidelines or something similar
open Migrate the original BitBucket repository
open Pull Requests 👍
open Issues ❓
open Add informative content to the new jqPlot website
open Release Plans: how will the software be delivered? ❓
open Decide on version system (cf. semver)
open Set up Gitter Instant Messaging for this project: https://gitter.im

Questions

Question Answer
What do we do with Chris Leonello's original license?
What do we do with the <www.jqplot.com> domain?
How do we get people to find us?
How much time can we realistically invest in jqPlot?
Who can we ask to help out with the migration?
How can we inform the current users of the jQplot website, and repository that a updated fork on Github exists

Other Sources of people