So . . . . let me weigh in . . . .
I’ve been a professional developer for 37+ years and am constantly using open source software for both work and personal endeavors. 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. The fact that the project has so many moving pieces is seriously daunting. The fact that you can’t even start analyzing it without repairing it is a total non-starter for me – and I suspect, most others, particularly professionals who *know* how software projects must be run to ensure progress and success. I had great hopes for OpenCog once – but I seems that it has done nothing but spin in circles except for a few (outstanding) one-programmer pieces (that haven’t picked up the traction they deserve because they’ve been anchored down by the rest). I don’t see that changing without a serious upgrade in the engineering management of the project. -- 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/000001d33f68%248e9bf310%24abd3d930%24%40gmail.com. For more options, visit https://groups.google.com/d/optout.
