unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nathan Dehnel <ncdehnel@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, guix-devel@gnu.org
Subject: Re: Binary descriptors for OpenCV
Date: Thu, 17 Aug 2023 16:57:35 -0500	[thread overview]
Message-ID: <CAEEhgEuuVFR0jqguXAD_GeRCo6xSDs_eZdR2s2kQqe9JS2Br-Q@mail.gmail.com> (raw)
In-Reply-To: <87bkf753m0.fsf@gnu.org>

Yeah, sure, I could offer my input.

On Wed, Aug 16, 2023 at 11:55 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi,
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
> > Nathan Dehnel <ncdehnel@gmail.com> writes:
> >
> >> Perhaps such greyzone objects that can't be fully regenerated should
> >> be put in their own channel so users know where they are and it
> >> doesn't become a mystery how many they have installed on their
> >> systems.
> >
> > I would want put a variant of the opencv package in the guix-science
> > channel if we decide not to include them, because xfeatures2d is useful
> > for feature detection in scientific applications (that’s the only reason
> > why I’m looking into this).
> >
> > However, it would be good to come up with a policy anyway.
>
> Yes, the problem is machine-learning output comes up more and more
> frequently.
>
> I agree we need to come up with a policy (I’m a bit torn on this and not
> too sure what I’d put in there.)  Maybe we should set up a working group
> with interested parties to draft something; who’s in?
>
> Ludo’.


  reply	other threads:[~2023-08-17 21:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  7:21 Binary descriptors for OpenCV Nathan Dehnel
2023-08-01 12:14 ` Ricardo Wurmus
2023-08-16 16:55   ` Ludovic Courtès
2023-08-17 21:57     ` Nathan Dehnel [this message]
2023-08-17 23:18     ` Maxim Cournoyer
2023-08-24 15:08       ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2023-08-01 18:50 Nathan Dehnel
2023-08-01 20:37 ` Saku Laesvuori
2023-08-01 20:58   ` Nathan Dehnel
2023-08-02  4:46     ` Saku Laesvuori
2023-08-02 20:25       ` Nathan Dehnel
2023-08-03  6:18         ` Saku Laesvuori
2023-07-31 13:12 Ricardo Wurmus
2023-08-01 14:02 ` Maxim Cournoyer
2023-08-01 14:39   ` Saku Laesvuori
2023-08-19  9:37 ` Simon Tournier
2023-08-24 15:06   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEEhgEuuVFR0jqguXAD_GeRCo6xSDs_eZdR2s2kQqe9JS2Br-Q@mail.gmail.com \
    --to=ncdehnel@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).