Notice nothing prevent somebody to use githud either way... Richard
On Mon, Mar 27, 2017 at 2:55 PM, Richard Vézina <[email protected] > wrote: > To my understanding issue with web2py slice is that it is base on Mucova ( > https://github.com/rochacbruno/Movuca) which is a web2py based CMS not > maintain anymore. To me, the problem is that web2py slice was more an > effort of social network then a web2py showcase... > > I can understand the reluctance of web2py fiddle approach... > > I think we need a better web2py showcase solution... > > For my part, I am not going to trying each un-maintain github repo to see > what the "slice" look like first to see if it really answer my need then > make sure the code works. I mean a bunch of slice repos without demo will > not be that usefull as you have to work a lot before even know if it works > and suit your needs. > > How can you make sure that all the slice in github are maintained > up-to-date with the latest web2py version? How do you levrage the community > work force (improve/fix slices)? > > I think having a proper showcase, without even have to login to create > slice would be nice to share web2py code snippet js plugins integration > etc. If it was a web2py app you could have a mechanism that let you know > which "slice" stop working after an upgrade of web2py as a kind of > integration tests you can analyse web2py ticket for that and notice author. > > With a bunch of github-slice repo, you don't have authorship, you have to > fork improve PR back the commit you made, then wait the author to accept > the change, who is gonna do that to 30-50 repo that may have the same > syntax typo because some backward unpromise compatibilty issue? > > web2py-fiddle could be integrate as to web2py as welcome app or integrated > to it somehow... > > Richard > > On Mon, Mar 27, 2017 at 7:27 AM, Marlysson Silva <[email protected]> > wrote: > >> And the stackoverflow documentation? >> >> http://stackoverflow.com/documentation/web2py/topics >> >> >> Em terça-feira, 21 de março de 2017 16:53:16 UTC-3, Massimo Di Pierro >> escreveu: >> >>> 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 [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
