{"action":"created","issue":{"url":"https://api.github.com/repos/tbreloff/Plots.jl/issues/222","repository_url":"https://api.github.com/repos/tbreloff/Plots.jl","labels_url":"https://api.github.com/repos/tbreloff/Plots.jl/issues/222/labels{/name}","comments_url":"https://api.github.com/repos/tbreloff/Plots.jl/issues/222/comments","events_url":"https://api.github.com/repos/tbreloff/Plots.jl/issues/222/events","html_url":"https://github.com/tbreloff/Plots.jl/issues/222","id":153147365,"number":222,"title":"Roadmap -- JuliaPlots","user":{"login":"tbreloff","id":933338,"avatar_url":"https://avatars.githubusercontent.com/u/933338?v=3","gravatar_id":"","url":"https://api.github.com/users/tbreloff","html_url":"https://github.com/tbreloff","followers_url":"https://api.github.com/users/tbreloff/followers","following_url":"https://api.github.com/users/tbreloff/following{/other_user}","gists_url":"https://api.github.com/users/tbreloff/gists{/gist_id}","starred_url":"https://api.github.com/users/tbreloff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tbreloff/subscriptions","organizations_url":"https://api.github.com/users/tbreloff/orgs","repos_url":"https://api.github.com/users/tbreloff/repos","events_url":"https://api.github.com/users/tbreloff/events{/privacy}","received_events_url":"https://api.github.com/users/tbreloff/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":18,"created_at":"2016-05-05T00:47:48Z","updated_at":"2016-05-06T17:54:21Z","closed_at":null,"body":"This issue continues the discussion from https://gitter.im/tbreloff/Plots.jl.  Summarizing, there are a few goals that could be achieved through a repo restructuring into a new organization.\r\n\r\n- Keeping the Plots ecosystem within one account\r\n- Consolidation of Plots recipes across disciplines\r\n- Opportunities for collaboration and spreading of responsibilities\r\n- A first step towards becoming the \"standard library\" plotting package for Julia\r\n\r\nThere exist a couple possibilities of organizations to join, but I would prefer to maintain sole ownership over core Plots.jl for the time being.  To that end, I propose forming the new organization JuliaPlots, of which I am the owner, and creating teams of collaborators for sub-systems of Plots:\r\n\r\n- Plots backends\r\n- Plots recipes: statistics, machine learning, graphs, and whatever else\r\n- Plots themes: ggplot2, solarized, etc\r\n- Plots examples/docs\r\n\r\nMy opinion on what should happen next:\r\n\r\n- [ ] Transfer tbreloff/Plots.jl to JuliaPlots/Plots.jl\r\n- [ ] Update METADATA for Plots (what are the necessary steps??)\r\n- [ ] Create a batman logo for the org!  (or... any other ideas?)\r\n- [ ] Transfer tbreloff/ExamplePlots.jl to JuliaPlots/PlotExamples.jl (or PlotDocs.jl?)\r\n- [ ] Update readthedocs site to point to JuliaPlots/PlotExamples.jl\r\n- [ ] Search for and replace hardcoded references to ExamplePlots\r\n- [ ] Create a team for docs maintenance (just me for now, unless anyone's interested)\r\n- [ ] Create JuliaPlots/PlotBackends.jl repo, and move much of the backend-specific code there.  (over time, possibly move it into the individual backends?)\r\n- [ ] Create a team for maintaining the backends\r\n- [ ] Create JuliaPlots/PlotThemes.jl (@pkofod: or transfer from pkofod/PlotThemes.jl?)\r\n- [ ] Create a team for creating/maintaining themes\r\n- [ ] Create JuliaPlots/PlotRecipes.jl (@Evizero: or transfer JuliaML/MLPlots.jl as the starting point?)\r\n- [ ] Create a team for creating/maintaining recipes\r\n- [ ] Transfer tbreloff/VisualRegressionTests.jl into JuliaPlots\r\n- [ ] Update METADATA for VisualRegressionTests\r\n- [ ] Register the packages with METADATA\r\n- [ ] Submit PRs for http://julialang.org/community/, http://julialang.org/downloads/, and http://julialang.org/downloads/plotting.html\r\n- [ ] Write a blog post about the \"how and why\" of Plots\r\n\r\nAnd there are some things which I think would be good for the long term, but don't need to happen soon:\r\n\r\n- [ ] Remove the JuliaPlot org (which was mainly for discussions last year), and include any pertinent info in the Plots docs or in an issue.\r\n- [ ] Pull out much of the code dealing with colors into a separate repo (@lobingera: maybe ColorMaps.jl?)\r\n- [ ] Move gadfly_shapes.jl into Gadfly\r\n\r\nEveryone, please let me know your thoughts.\r\n\r\ncc: @spencerlyon2 @diegozea @jheinen @Evizero @dlfivefifty @timholy @pkofod @simondanisch"},"comment":{"url":"https://api.github.com/repos/tbreloff/Plots.jl/issues/comments/217513742","html_url":"https://github.com/tbreloff/Plots.jl/issues/222#issuecomment-217513742","issue_url":"https://api.github.com/repos/tbreloff/Plots.jl/issues/222","id":217513742,"user":{"login":"lobingera","id":5199059,"avatar_url":"https://avatars.githubusercontent.com/u/5199059?v=3","gravatar_id":"","url":"https://api.github.com/users/lobingera","html_url":"https://github.com/lobingera","followers_url":"https://api.github.com/users/lobingera/followers","following_url":"https://api.github.com/users/lobingera/following{/other_user}","gists_url":"https://api.github.com/users/lobingera/gists{/gist_id}","starred_url":"https://api.github.com/users/lobingera/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lobingera/subscriptions","organizations_url":"https://api.github.com/users/lobingera/orgs","repos_url":"https://api.github.com/users/lobingera/repos","events_url":"https://api.github.com/users/lobingera/events{/privacy}","received_events_url":"https://api.github.com/users/lobingera/received_events","type":"User","site_admin":false},"created_at":"2016-05-06T17:54:21Z","updated_at":"2016-05-06T17:54:21Z","body":"to pick up from way above...\r\n\r\nYes, i could provide maintenance for a ColorMaps.jl if needed; i'd not claim that i'll be better than other choices, maybe i have a little bit more overview, as i did something similar for a research project once.\r\n\r\nI cannot really see the need for **another** julia graphics/plots/plot organisation as https://github.com/JuliaGraphics/ and https://github.com/JuliaPlot/ already exist (and even that could be converged into 1 organisation only).\r\nIf you (@tbreloff) see problems of other developers interfering with your ideas, the simpler solution is to keep ownership on your account.\r\n\r\nStill (especially now after the ShowOff + Gadfly + Compose incident) i'd rather like to see infrastructure packages (and Plots as mediator between common API and a list of backends is very clearly infrastructure) as shared development. Not only to provide diversity if an owner isn't available for accepting a PR. Diversity is always a source for new inspiration - but this can also be provided by enough github discussion.\r\n\r\n"}}