14:58 < lool> salgado-physio, james_w: Thinking about python-hwpack + python-linaro-media-create -> python-linaro-image-tools, I was wondering whether we actually want to make these modules public,
or whether we should have them private instead? The latter would
seem safer, as I don't think we're guaranteeing any API, and all
tools using these modules are in linaro-image-tools itself anyway, right?
15:01 < james_w> lool, we're not guaranteeing anything, but I don't see a point
in preventing people to use them at all
15:01 < james_w> lool, I'd prefer a note stating that the API is not stable
15:06 < lool> james_w: I'm not comfortable with this; first, I don't see where
we'd put the note as to have it easily discoverable; second, I
feel that as soon as third-party scripts will use the API, we
will compelled not to break them; third, the API can still be
used from the private directory
I would also like to make the modules private
14:58 < lool> salgado-physio, james_w: Thinking about python-hwpack +
python- linaro- media-create -> python- linaro- image-tools, I was
wondering whether we actually want to make these modules public,
anyway, right?
or whether we should have them private instead? The latter would
seem safer, as I don't think we're guaranteeing any API, and all
tools using these modules are in linaro-image-tools itself
15:01 < james_w> lool, we're not guaranteeing anything, but I don't see a point
in preventing people to use them at all
15:01 < james_w> lool, I'd prefer a note stating that the API is not stable
15:06 < lool> james_w: I'm not comfortable with this; first, I don't see where
we'd put the note as to have it easily discoverable; second, I
feel that as soon as third-party scripts will use the API, we
will compelled not to break them; third, the API can still be
used from the private directory