On 6/6/2022 4:36 PM, Erich Steinböck wrote:
| silence is taken as approval
Rony, I've already said multiple times and in no unclear words that my silence just means I
haven't written an answer and in no way is an approval.
This is what successful open source projects do, otherwise the risk that development stalls is very
high.
Just witness the fate of this particular thread: a month ago (!) it already discussed problems in
"samples\ole\apps" and the question what to do about it. I see these problems each semester when
teaching business administration students (most have no pre programming skills) how to use ooRexx
and OLE to program Windows programs. It is unbelievable how difficult it makes it for them to
realize that ooRexx and OLE on Windows is really a nifty tool, when half of the examples do not work
(ooRexx cannot run them, ooRexx creates errors). Also it is difficult to find the samples they might
be interested in if one can not tell from the file name what its content would be. Let alone having
additional examples for MS Office to help them more with these applications as MSO is so dominant
and important in the Windows world. At the core it is about making it easy for newcomers and
interested programmers to use ooRexx' OLE to program Windows programs and jump start them with
ooRexx OLE programs that demonstrate how easy it is to program MS Word, MS Excel, MS Outlook, MS
Powerpoint.
Since posting this /a month ago /no comments, answers have surfaced! Why is this, Erich, what do you
think? What do you suggest for someone who is volunteering to do the necessary work and gets no
comments, no answers?
Basically there are two possibilities in situations where no answer is given:
* no answer (after a certain while) is taken as "no objections", "no opinion",
"no personal
interest", "o.k.", "agree", and the like, such that one can go on, which is
the /constructive
/way to keep things going and advancing,
* no answer is taken as a veto: this is the /destructive/ way and stalls (and
over time will kill)
every community.
My take has been - having learned that on other very successful open source projects - to go after
the constructive branch.
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
