Rawsamples.ch and hosting raw sample files

Meta
5

So hello there.
I’m only in favor of the second option, and i hope it will be clear why, unless i fail to write-up my basic vision of what’s need to be there:

  • Basic structure/list of the samples can be autogenerated from that cameras.xml.
  • As you can see, that file has following entries: <Camera make="$1" model="$2" mode="$3">
    For starters, what we need is: one raw file per "$1 $2 $3" tuple.
    That list can be trivially auto-genenerated.
    $ grep "<Camera " cameras.xml | wc -l tells me that there are 841 (sic!) entries.
    • Also, there are <Alias id="$4">$5</Alias> sub-entries in some <Camera> entries, so actually
      The is a second tuple: "$1 $5 $3" (yes, no typos here.)
      $ grep "<Alias " cameras.xml | wc -l tells me that there are 43 aliases.
      So multiply some portion of 841 by 43. That is, 1000+ samples?
    • As pointed out, there may be need for more than one sample per tuple, e.g. just some random shot for regression testing, and a proper color checker picture, etc.
  • For our continuous integration purposes (hallo, apparently new rawspeed maintainer here speaking), all the samples need to be downloadable as one big tarball. And maybe there should be smaller tarballs, e.g. per-manufacturer, per-camera.
  • License for new sample uploads MUST be well-defined, and accepted before upload.
    I’m proposing to enforce at least the same license as rawsamples.ch uses: CC-BY-NC-SA.
    Otherwise, CC0?
  • There needs to be a very simple and friendly web-ui for sample submission.
  • User selects camera manufacturer ($1), then selects camera model ($2+$5), and is presented with either a message that all samples are present, or with a list of wanted samples.
  • New submissions should not go live immediately, but instead there should probably be some pre-moderation.

This is the very basis of what we need for rawspeed, in my opinion.
I’m not so sure that representing it as a forum will work well :slight_smile:

1 Like