Dear ONAP Community, ONAP has grown to be quite a big and complicated project and looking for some information is sometimes like searching a needle in a haystack.
The most obvious way to navigate in ONAP source code is to use grep or some indexer built into your IDE. Unfortunately this requires having full ONAP sources on a local machine and sometimes can take quite a lot of time and your loacal. That's why other large open source projects like Open Stack or The Linux Kernel provides a web based code search engine: http://codesearch.openstack.org/ https://elixir.bootlin.com/linux/latest/source/kernel Some time ago we set up in our company Hound instance for ONAP. After using it for quite some time we found it quite useful and faster than grep. We think that if it's beneficial also other people may find it useful. That's why I'd like to ask you, as a community, two questions: 1) Do you think that publicly available code search for ONAP would be useful for you? 2) Do you think that hound is the right tool that we should use or you prefer some other tools(opengrok or other). Please share your opinion and provide argumentation if you prefer other tool Best regards, -- Krzysztof Opasiak Samsung R&D Institute Poland Samsung Electronics -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17199): https://lists.onap.org/g/onap-discuss/message/17199 Mute This Topic: https://lists.onap.org/mt/31724678/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
