What is the best way to manage existing ractives?

[nachocab]

Adding new ractives to inst/examples is not sustainable. Perhaps we need a separate repository ("clickme_ractives") to upload them.

We would also need a way to list, sort, rank, and describe them (wiki page?)

I'm open for suggestions

[tbates]

maybe a beta_ractives folder that people can submit to, and then if they prove popular, the ractive might move to inst/core_ractives

that way there's not a great barrier to new ractives, and the core set can grow over time.

[nachocab]

I like the idea of having a set of ractives already installed, but I'm not sure how I feel about adding a ton of ractives that might not be relevant. I'm thinking of using a clickme_ractives repo where anyone can upload their ractives (sort of like the homebrew people, and making the process of installation and discovery easier. I'm shooting for some time next week. If you have any further comments, I'm all ears.

[timelyportfolio]

runGist in shiny is very nice, and I think helps overcome the learning curve or intimidation factor. However, I don't think gist allows the nested folder structure, so probably needs to be Git. I agree that a comprehensive set of all ractives included in the main package is not a good idea. Some sort of library similar to d3.js would be nice. If we are ambitious enough, we could fork all the examples in the gallery and translate each to a ractive.