halide / Halide

a language for fast, portable data-parallel computation
https://halide-lang.org
Other
5.9k stars 1.07k forks source link

Should we have a "contrib" folder? #786

Open steven-johnson opened 9 years ago

steven-johnson commented 9 years ago

Per a recent discussion on the listserv, it might be useful to have a place for generally-useful-contributions that are part of the Halide library proper. Suggestions given include: -- glue code that interfaces with libtiff to load TIFF into a buffer_t -- library of vetted & tested Generators for common operations (e.g., bilinear image resizer)

Does this sort of thing belong in Halide or elsewhere? If the former, how much structure do we need?

abadams commented 9 years ago

I'd support a contrib folder where each subfolder contained a README explaining what the thing was, and some standard test script that the nightly tests could call.

On Thu, May 7, 2015 at 6:48 PM, Steven Johnson notifications@github.com wrote:

Per a recent discussion on the listserv, it might be useful to have a place for generally-useful-contributions that are part of the Halide library proper. Suggestions given include: -- glue code that interfaces with libtiff to load TIFF into a buffer_t -- library of vetted & tested Generators for common operations (e.g., bilinear image resizer)

Does this sort of thing belong in Halide or elsewhere? If the former, how much structure do we need?

— Reply to this email directly or view it on GitHub https://github.com/halide/Halide/issues/786.