<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Mika,<br>
</p>
On 4/25/23 11:28 AM, Mika Silander wrote:<br>
<blockquote type="cite"
cite="mid:231790447.9625670.1682414919766.JavaMail.zimbra@csc.fi">
<pre class="moz-quote-pre" wrap=""> Reading through the IEP in question, I thought I would find reasons or motivations as to why having a library is desired. It's possible I've missed discussions or mails and the reasons have been discussed/documented elsewhere.</pre>
</blockquote>
Thanks for the input, I'll try to find some references from the 3.0
discussions when we first discussed this feature request in more
details, or otherwise expand this section on my own.<br>
<blockquote type="cite"
cite="mid:231790447.9625670.1682414919766.JavaMail.zimbra@csc.fi">
<pre class="moz-quote-pre" wrap=""> If the implementation you choose for IEP is the API-breaking generator one
</pre>
</blockquote>
<p style="color: rgb(14, 16, 26); background: transparent;
margin-top:0pt; margin-bottom:0pt;"><span style="color: rgb(14,
16, 26); background: transparent; margin-top:0pt;
margin-bottom:0pt;;" data-preserver-spaces="true">I think there
was a misunderstanding: It is precisely the </span><em
style="color: rgb(14, 16, 26); background: transparent;
margin-top:0pt; margin-bottom:0pt;"><span style="color: rgb(14,
16, 26); background: transparent; margin-top:0pt;
margin-bottom:0pt;;" data-preserver-spaces="true">question</span></em><span
style="color: rgb(14, 16, 26); background: transparent;
margin-top:0pt; margin-bottom:0pt;;"
data-preserver-spaces="true"> if we also want to address this
topic. It has its pros and cons, whereas the biggest downside is
the API-breaking part with all its implications.</span></p>
<p style="color: rgb(14, 16, 26); background: transparent;
margin-top:0pt; margin-bottom:0pt;"><span style="color: rgb(14,
16, 26); background: transparent; margin-top:0pt;
margin-bottom:0pt;;" data-preserver-spaces="true"><br>
</span></p>
<p style="color: rgb(14, 16, 26); background: transparent;
margin-top:0pt; margin-bottom:0pt;"><span style="color: rgb(14,
16, 26); background: transparent; margin-top:0pt;
margin-bottom:0pt;;" data-preserver-spaces="true">You know that
it was a long and bumpy road towards IntelMQ 3.0, and
accumulating multiple significant development steps in a short
period was challenging (OTOH had the - temporary - development
capacity at that time to make this leap). I'm fully aware that
breaking changes can mean a lot of trouble and I'm all for
small, separated steps (hence this IEP), which allow more
straightforward discussion, review and maintenance. When writing
PoCs for this IEP, I found a similar area for improvement in
IntelMQ which could also be interesting to tackle. It is not up
to me to decide the direction of the IntelMQ roadmap but to the
<i>community</i>. Hence, I posed this question and asked for
comments, and I am very grateful that you are contributing so
actively through code and discussion.</span></p>
<p style="color: rgb(14, 16, 26); background: transparent;
margin-top:0pt; margin-bottom:0pt;"><span style="color: rgb(14,
16, 26); background: transparent; margin-top:0pt;
margin-bottom:0pt;;" data-preserver-spaces="true"><br>
best regards<br>
Sebastian<br>
</span></p>
<p>-- <br>
</p>
<pre class="moz-signature" cols="72">Institute for Common Good Technology
gemeinnütziger Kulturverein - nonprofit cultural society
<a class="moz-txt-link-freetext" href="https://sebix.at/">https://sebix.at/</a>
ZVR 1510673578</pre>
</body>
</html>