I really don't want to maintain a separate repo of "awesome". How about we take from Jame's link? The projects listed on the home page are "recommended" and then we just have a link to "all projects" in that section. That link would go to an "appendix" of some sort in the reference docs. Is that a good way to deal with it?
On Sun, Mar 13, 2016 at 3:39 AM, James Thornton <[email protected]> wrote: > I've always liked how Redis does it: http://redis.io/clients > > - James > > On Sat, Jan 30, 2016 at 6:22 AM, Stephen Mallette <[email protected]> > wrote: > > > We currently have a list of libraries on the home page that are provider > > implementations, driver implementations and other odds and ends. We try > to > > promote only those libraries there that have some level of polish to them > > (e.g. have a stable release, have some docs, etc). I think that's good, > > but it has the shortcoming that "younger" projects aren't promoted at all > > which has the downside that: > > > > 1. These projects could use some promotion to attract help with their > work > > 2. Users don't know these projects are under development and end up > > building their own which fragments available libraries should work be > > duplicated. > > > > I was thinking that we could add a section to the Developer Docs that > > showcased these "younger" projects. I was thinking that the home page > could > > have a link to this new section somehow. Anyone else think this is a good > > idea? If a good idea, is there a better place to add this and a good name > > for what the section should be called? > > > > > > -- > James Thornton, *http://electricspeed.com <http://electricspeed.com>* >
