On Mon, Oct 2, 2017 at 2:32 AM, Mark Nuzz <[email protected]> wrote:

> Hi,
>
>
> On Sun, Oct 1, 2017 at 9:30 AM, Linas Vepstas <[email protected]>
> wrote:
>
>
> > I mean, how do I tell people "this code compiles but probably doesn't
> work
> > and no one uses it" vs. "this code is the bedrock foundation that we
> > jelously protect from damage"
>
> The way I see it handled most often is to only allow
> production-quality, working code in the master branch.


Yes, but this is the opposite of what we do. I've had this argument with
Ben, and he wants anyone to contribute any thing at any time, no matter
what the quality is. Everyone gets write permissions always. He doesn't
want me or anyone to be a gatekeeper or project manager. He's very
anti-project-management.

The current split is that the atomspace is core code, and is more tightly
policed, while the opencog repo is the wild-west of random parts.


> But didn't the
> project try to enforce that with CircleCI (I think) and you had an
> issue with that?


CircleCI was great, but the integration with github was terrible. It made
checking in code very hard.  It was an instrument of torture and pain.

Anyway, that is besides the point: Although passing unit tests is
important, it is not enough to ensure high-quality code.   There's more to
it than that.

> >
>
> It might just be my anti-C++ bias talking.


I don't particularly love C++. I don't hate it either. It is what it is.

But focusing on this misses the point of opencog.  Don't write C++ code!!
Not you and mostly not anyone, except for a few core maintainers.

You should think of opencog as a domain-specific language.  Actually,
several domain-specific languages. We've created half a dozen of those,
program in those.   For example, our newest one is "ghost". Program in
ghost, that's what you should use, and not C++.

--linas

-- 
*"The problem is not that artificial intelligence will get too smart and
take over the world," computer scientist Pedro Domingos writes, "the
problem is that it's too stupid and already has." *

-- 
You received this message because you are subscribed to the Google Groups 
"opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/opencog.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/opencog/CAHrUA35hkNbRAmu_Via5dOtJD3Xn21yQW%3DZ7ubvq62XtTkOj%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to