henrikingo commented on issue #101: URL: https://github.com/apache/otava/issues/101#issuecomment-3617215007
Hey thanks for sharing! I always had various ideas about using e-divisive/otava beyond just performance testing. This is very exciting to see. Thanks! I suggest you should start by suggesting an API that would work for you. Don't limit yourself to anything that otava is today, just think of it as a clean slate and start from your own needs. (If you are following the other pull requests, where we're for example replacing Series and AnalyzedSeries with pydantic classes - #93 - you'll see that we're here to do a proper refresh and modernization. Whether you are the best programmer in the world or not is not important. I am also not, but we will review your submission thoroughly. (And add my and hopefully others input as well.) That said, I disagree with @Gerrrr on the point of documentation: If you prefer to just write in english what you hope a future API would do, that's also welcome. (I call it documentation driven development :- ) But bear in mind that API docs can often be generated from code, so in the end not much might survive from your original writeup. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
