Re: MISP Issues on github

[Christophe Vandeplas]

(now to MISP developers <misp-...@googlegroups.com>)

On 8 May 2015 at 12:08, AD <elh...@gmail.com> wrote:
> Just FYI I tagged nearly all the issues, closed some and opened additional
> ones based on discussions started in some.
>
> For tagging I tried to make a distinction between "enhancement" and
> "functionality" with my understanding being enhancement is small/incremental
> change, and functionality being a whole new thingie.
>
> I have also tagged a number of issues with "support" (
> https://github.com/MISP/MISP/labels/support ) and it seems we have not
> answered to some of them. I will try to work on that, please check if there
> is anything you think you can already answer on.

Thank you very much David,
The next step we'll need to do is to try mapping all the issues to
specific releases.

Currently the roadmap for v2.4 is 'Releasable to' model.
Andras: could you give us an idea of the target date for this release?

v2.5 is meant to have the modular import/export system. Considering
this is a big change, we should perhaps try to incorporate some
smaller changes/fixes in releases in between? v2.4.x for example. What
do you think?

Also I noticed the issues list contains a lot of requests for
integration with other tools / import/export. I added an additional
tag called 'import/export' and started tagging events. Feel free to
fill the gaps that I missed.
Import/export plugins are a great for new developers to get acquainted
with MISP, categorising them will hopefully give more visibility into
that. (How to contribute documentation issue assigned to me:
https://github.com/MISP/MISP/issues/483)

Those are definitely things to talk about during our next conf call. !

Grtz
Christophe

[Andras Iklody]

Sounds good,

As for 2.5: The modularity in itself might not be that big of a change - however, if possible I'd like to do that together with the API rework that we've talked about (getting rid of all the confusing APIs with different filter options and having one main API that takes a unified list of arguments including the desired output format).

For 2.4: The schedule is delayed by a fair bit as I wasn't able to actually get much coding done during my last weeks at NCIRC. Right now I have everything working with the sharing groups on the local instance, and the synchronisation part is partially done. After I finish that it's a matter of writing upgrade scripts / documentation and then finally testing everything. I hope I can finish it all by the end of May.

Best regards,

Andras

Christophe

--
You received this message because you are subscribed to the Google Groups "MISP development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to misp-devel+...@googlegroups.com.
To post to this group, send an email to misp-...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/misp-devel/CACjrQ-UBPTGFXLVHLw%2B_QiRKi99YA6URtqK4%3DeA9CS90f6apWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Richard]

On Sunday, May 10, 2015 at 7:16:40 PM UTC+2, andras.iklody wrote:

For 2.4: The schedule is delayed by a fair bit as I wasn't able to actually get much coding done during my last weeks at NCIRC. Right now I have everything working with the sharing groups on the local instance, and the synchronisation part is partially done. After I finish that it's a matter of writing upgrade scripts / documentation and then finally testing everything. I hope I can finish it all by the end of May.

Great stuff. Do let us know if you need help with testing, etc.

On Sunday, May 10, 2015 at 6:50:11 PM UTC+2, Christophe Vandeplas wrote:

v2.5 is meant to have the modular import/export system. Considering
this is a big change, we should perhaps try to incorporate some
smaller changes/fixes in releases in between? v2.4.x for example. What
do you think?

I think that makes sense, just like we are now at hotfix-2.3.67.

Those are definitely things to talk about during our next conf call. !

Will those calls be announced here? I'd like to join them if possible.

Kind regards,

Richard

[Richard]

On Sunday, May 10, 2015 at 7:16:40 PM UTC+2, andras.iklody wrote:

For 2.4: The schedule is delayed by a fair bit as I wasn't able to actually get much coding done during my last weeks at NCIRC. Right now I have everything working with the sharing groups on the local instance, and the synchronisation part is partially done. After I finish that it's a matter of writing upgrade scripts / documentation and then finally testing everything. I hope I can finish it all by the end of May.

Is there anything we can do to expedite the 2.4 release? I'd gladly do some upgrade tests and documentation work.

Kind regards,

Richard