Yeah, in terms of using some AI tool here... I haven't had enough hot
caffeinated beverage yet to even think about it. But one thing:
Jarek Potiuk wrote on 2/8/23 7:08 AM:
...snip...
I looked at the proposal and with the CYOA engines, one of the
problems is that you have to script it and investi in defining the
paths/branches
I don't see the scripting being that hard, presuming we have a decent
CYOA language. The end path from the script doesn't have to be the One
Best Project For You, it just needs to be a selection of projects that
might be relevant for you.
So coding languages questions merely add to a list like "user can
program in X,Y,Z". Then at the end, we use that as a filter on
projects.a.o to come up with the potential list of projects we'd show
the user.
Each set of questions is only a filter function based on some general
criteria from project data. At the end show all the projects that meet
the filters.
Obviously we also handle non-coding paths, and may have some standard
"Here's How To Go About Finding A New Bug" help text embedded in the
script, or directly linked, so the person can find other useful
resources along the way.
Does that make sense? I'm obviously hand-waving about the issue that
projects.a.o data may not be complete yet. 8-)
--
- Shane
ComDev PMC
The Apache Software Foundation
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
