Re: ML-Policy and tesseract-ocr

2019-08-14 Thread Paul Wise
On Wed, 2019-08-14 at 17:44 -0700, Mo Zhou wrote: > * For a source package that produce binary package containing ML models, > it's encouraged to write a "reproduce-original-model" that may e.g. > download a dataset from internet and redo the same procedure to > produce the original model.

Re: ML-Policy and tesseract-ocr

2019-08-14 Thread Mo Zhou
On 2019-08-13 01:00, Paul Wise wrote: > On Tue, Aug 13, 2019 at 8:45 AM Sam Hartman wrote: > >> In cases where the model is not recreated, but where software in Debian >> could create the model, I think a README file is better than a package >> relationship. > > Personally, I'd like to see

Re: ML-Policy and tesseract-ocr

2019-08-14 Thread Mo Zhou
On 2019-08-13 00:44, Sam Hartman wrote: >> "Mo" == Mo Zhou writes: > > > >> (result of running the training program with specific input data, > >> if I understand correctly?) > > Mo> Yes, correct. > > >> The source package would need to Build-Depend on the training >

Re: ML-Policy and tesseract-ocr

2019-08-12 Thread Marvin Renich
[Debian list policy is to reply to list without CC to individuals, except where the individual has asked for a CC.] For the rest of your reply, I agree with Sam's response (i.e. no Suggests is necessary). ...Marvin * Mo Zhou [190812 20:29]: > > The source package would need to Build-Depend on

Re: ML-Policy and tesseract-ocr

2019-08-12 Thread Paul Wise
On Tue, Aug 13, 2019 at 8:45 AM Sam Hartman wrote: > In cases where the model is not recreated, but where software in Debian > could create the model, I think a README file is better than a package > relationship. Personally, I'd like to see Policy specify a standard mechanism that people could

Re: ML-Policy and tesseract-ocr

2019-08-12 Thread Sam Hartman
> "Mo" == Mo Zhou writes: >> (result of running the training program with specific input data, >> if I understand correctly?) Mo> Yes, correct. >> The source package would need to Build-Depend on the training >> program and its inputs, but in general there would not

Re: ML-Policy and tesseract-ocr

2019-08-12 Thread Mo Zhou
Hi Marvin, On 2019-08-12 18:35, Marvin Renich wrote: > * Mo Zhou [190812 10:31]: >> To this end, I wrote the policy #5 [3]: >> >>A package that includes a machine learning model, must also include >>the corresponding training program, or depend on the package that >> provides >>the

Re: ML-Policy and tesseract-ocr

2019-08-12 Thread Marvin Renich
* Mo Zhou [190812 10:31]: > To this end, I wrote the policy #5 [3]: > >A package that includes a machine learning model, must also include >the corresponding training program, or depend on the package that > provides >the corresponding training program. > > Does that make sense? If

ML-Policy and tesseract-ocr

2019-08-12 Thread Mo Zhou
Hi -devel, src:tesseract-ocr has two concrete bugs that are associated to ML-Policy[1]. Let's discuss about the possible solution. BTW, today I drew a diagram[2] for the ML-Policy. Those who don't bother to read the full text could have a look at the diagram. -- #933878: training files are