I'd like to help maintain it. And I vote for a web2py solution. Not using would let us in a "shoemaker's son always goes barefoot" situation. I think this is embarrassing.
2017-03-22 1:23 GMT-03:00 Kiran Subbaraman <subbaraman.ki...@gmail.com>: > I agree that the managing web2pyslices as issues may be one way to go.A > couple of options that I have in mind > > *Option 1 / bl.ocks.org <http://bl.ocks.org>* > But there is another idea that I have been considering for sometime... > I follow the d3js community once in a while, and they have this nice way > to contribute and expand on the examples created using d3js. These examples > are hosted on http://bl.ocks.org. If an example is created on Gist, and > follows a prescribed template, then it is hosted as an example on > bl.ocks.org. > > The template and process is defined here: https://bl.ocks.org/-/about > > The work that the bl.ocks.org application does, needs to be replicated in > some form by another application in the web2py world (This has similar > problems - hosting, and computation power, etc) > > *Option 2 / Gists, with PR based list* > > - Post a slice on gist > - Raise a PR, with this link - this is similar to the way one raises > PRs to lists such as this - https://github.com/akullpp/awesome-java > - If someone creates a web2pyslices.github.io on this site, then you > have an autogenerated webpage with the curated list of slices. > > > The reason am plugging for Gist based solutions is that it makes > contribution to that Gist, or improvement in code a possibility (however > remote). > > On Wednesday, March 22, 2017 at 1:23:16 AM UTC+5:30, Massimo Di Pierro > wrote: >> >> web2pyslices is becoming hard to maintain. Right now the best solution is >> to create a github repo and move all the recipes into issues. We will >> deprecate by closing them. People with gihub accounts can post and comment >> issues/recipes. Unless you have a better solution, this will be done within >> the next week. >> >> One sideffect is that we will lose some information about authorship of >> the recipes and the comments. We will add a notice "created by {...}" but >> the {...} name will be the web2pyslices username and that may not mean >> anything in the gihub context. >> >> At this I do not have a better solution but please share your thoughts. >> >> -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Carlos J. Costa Cientista da Computação | BS Computer Science Esp. Gestão em Telecom | PgC Telecom Mangement <º))>< -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
