> about this), and the developer-group would be really happy to listen to > ideas, suggestions and practical solutions. Although we can make suggestions we think might work, it really comes down to what works best for the core developers (other than ignoring input... ;) ).
Off the top of my head I came up with two potential suggestions (beyond leaving status quo), neither of which is necessarily optimal, but could work: 1. Non-developers submitting patches would be required to additionally submit a ticket for its inclusion; this gets greater visibility but somewhat sidesteps the whole community review bit that emailing the list has. 2. One of the developers commits to handling public/forward patches (think Andrew Morton) and serves as a developer-side focal point for patch review and inclusion. This puts a larger focus & strain on individuals and reduce their time available for direct development, but could also help improve quality and visibility. > Personally I can only appologize for the long overdue responses and I > will do my best to work towards a better solution. No need for apologies, we just want to help make things better. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
