I think it is important that things be marked clearly as: - plugin/app/recipe - production/beta - have a screenshot - be hosted locally or remotely (github/bitbicket/whatever)
On Jan 21, 12:18 pm, Bruno Rocha <rochacbr...@gmail.com> wrote: > 2011/1/21 contatogilson...@gmail.com <contatogilson...@gmail.com> > > > What do you think of having a wiki on the framework and its libraries in > > web2pyslices? > > I don't know if a wiki is needed, in web2pyslices we are planning to have a > follow system, so people will be able to follow slices, and people will be > able to fork slices, Slices can be anything (it is like a post), but it is a > post specifically categorized and with exclusive features for each category. > > We can add the functionality to make a slice public, so anyone can edit a > slice (option-able by the creator of the slice) > > Slices will be connected itself with other slices (slices follows slices), > so we finish having a tree of related stuff. > > Imagine the workflow: > > Enter web2pyslices > Search keyword 'form' > results shows : > 5 last people who recently have 'form' on his actions > 5 latest recipes/tutorials tagged and with 'form' on content > 5 lates plugins related to form > 5 latest slices that follows any other slice related to 'form' > plus: > 5 results from web2py source with the 'form' keyword' > 5 latest google groups threads related to form > and so... > > The idea is ONE PLACE for web2py related stuff.
