On Saturday, October 7, 2017 at 8:34:06 PM UTC+8, Mark Waser wrote: > > > The **worst** thing for me is when the publicly available repo cannot be > immediately compiled and run due to missing/incomplete instructions or > errors. > > > > While this is nearly unavoidable once in a blue moon, it is certainly > unacceptable when it happens on a regular basis. It shows an incredible > lack of professionalism -- much less a tremendous lack of respect for the > time and effort of others. At work, it is a termination offense. > > > > I’ve read this mailing list for years. It seems that the repo being > broken is far, far more common than not. >
I found this equally frustrating at the beginning. That is until, I asked the same questions and found the whys behind the reasons. Also, having worked a few months recently in the same room as most of the core OpenCog Hong Kong team I can say that Ben is aware of the shortcomings of OpenCog at any point in time, and the high-level steps required to make things right. We've been talking about some of these issues for several years. I've seen a rationale ongoing effort and several attempts that worked for a while and fizzled because there wasn't someone in those roles. Building something hard is a game of stamina more than one of being right in all ways at the beginning. To keep going you need to keep the bills paid and people happy. So you can look at OpenCog for what it is today, and has been... a research platform for a small cadre of AGI researchers working on world-class-hard problems that solves the basic architectural problems of AI suitable for hardcore programmers with some time on their hands... Or you can think about what OpenCog will be... after a transition to the next level up with production level quality, documentation, and product management in service to the larger world community building benevolent intelligence. I've been choosing to jump in and help with the ongoing upgrade. It sounds like you have a lot of experience here. Want to help us build the team to take OpenCog to the next level? Point good people Ben's way and he'll recognize them... There is no doubt we can improve the interfaces and greatly improve the experience for anyone approaching OpenCog anew. I've got some points on these issues I'll continue in the other part of this thread... -- 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/075cf101-b445-4f28-950e-dcf73852a1ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
