Review role and use of Events in connection creation and signal transmission

[nest]

Review role and use of Events in connection creation and signal transmission

[terhorstd]

Is this actually an issue, or rather a project or discussion that should be continued somewhere else? What is the actual problem that needs to be solved here to close it?

I'd vote to close it.

[heplesser]

See also ticket 685 in the old trac,

[jessica-mitchell]

@heplesser apologies for leaving this one on the back burner so long. is this something that belongs in developer documentation? how up-to-date is the information, has much changed regarding how events are handled?

[heplesser]

@jessica-mitchell I fear this issue really needs more than just better documentation, rather a full code review and refactoring. I will change the title of the issue—it could probably a hackathon topic.

[github-actions]

Issue automatically marked stale!

[heplesser]

Similar to #556, this issue points at a large refactoring we should should consider to achieve cleaner and more maintainable code. As such, it would be a project of its own. To me, the main question is how we see issues: Should issues only represent relatively compact problems or tasks, or also be used to remind us of and collect discussions on larger changes? If we decided to use issues for relatively narrow scopes only, where would we then remind us about and organise discussion around larger efforts?