Discussion for 1.0

[rasmus]

The 1.0 release focus primarily on

• Standardized use of Microsoft.Extensions packages, kill the custom implementations
• Only support LTS versions of .NET (Core) and removing support .NET Framework.
• Fix missssspellllledddd APIs
• Add missing async/await on critical methods
• Removal of non-async methods
• Do much needed API changes that requires breaking current APIs (hopefully not many)
• Build cleanup

Put any off-topic questions and more comments here.

[Zev-OwitGlobal]

Definitely interested in helping out.

[rasmus]

@Zev-OwitGlobal What kind of stuff do you like doing or what do you see yourself helping out with? More likely to find time to do stuff you like 😄

[nativenolde]

@rasmus I appreciate your ambitious efforts and became a sponsor. hopefully more people will follow... Thank you

[Zev-OwitGlobal]

Pretty much anything, one of my dev teams is using it on their project for a large insurance project - so I can focus on anything needed to get the v1.0 release stable - not sure how much is left but I took a look at the list -- so if you have an area that might help the most, let me know!

---

From: nativenolde @.> Sent: Wednesday, February 16, 2022 3:10 PM To: eventflow/EventFlow @.> Cc: Zev Butler @.>; Mention @.> Subject: Re: [eventflow/EventFlow] Discussion for 1.0 (#843)

This message was sent from outside the company

@rasmushttps://github.com/rasmus I appreciate your ambitious efforts and became a sponsor. hopefully more people will follow... Thank you

— Reply to this email directly, view it on GitHubhttps://github.com/eventflow/EventFlow/issues/843#issuecomment-1042120031, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARN7XSYKZRA2ETR23S4FTADU3QAEXANCNFSM45P5CKCQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

NOTICE: This email – including attachments – is intended solely for the named recipient. It may contain proprietary, confidential, or privileged information. If you are not the intended recipient, please notify the sender immediately, delete this email, and destroy all copies. Additionally, if you are not the intended recipient, you must not copy, distribute, or take action based on the information within the email. Though all efforts are made to safeguard emails, OWIT Global cannot guarantee that attachments are virus free or compatible with your systems, and does not accept liability based on viruses or computer problems resulting from opening this email. The views expressed by the sender do not necessarily represent the official position of OWIT Global, and this email is not contractually binding.

[rasmus]

@nativenolde I cannot thank you enough. That's just awesome, thanks for sponsoring. Nice words go a really long way, but active support says a lot more ❤️

[rasmus]

@Zev-OwitGlobal as I guess you have noticed, my motivation for doing EventFlow comes in waves (though the thought of stopping has never occurred to me). Having support would definitely take some load off and make spending my spare evenings on EventFlow a lot more fun.

I can give a short status

• I think 1.0 is coming along nicely, but I'm very worried regarding the API. There's several key changes and I really want to make sure to nail how the the initial configuration is done for 1.0. So any input there would really be awesome.
• I originally created EventFlow while working for eBay, and they required to be part of the copyrights, even though there's no eBay IP and I'm doing the project 100% in my spare time. Last year my department got sold to Schibsted (the original creators of Varnish) and getting the legal parts of the copyrights sorted out was no fun. eBay gave its part of the copyrights to Schibsted as part of the sale and now I have been working to get the copyrights from Schibsted back to me alone. Its done, just need to create a PR with the updated copyrights. Please note that the copyrights to an MIT license project is basically who's name is on the box (as I understand it). For the users of EventFlow nothing will change, its still MIT (forever!), it will just be my name on top.
• The build for EventFlow is fragile and a bit of a sore spot. I have done a few iterations, but its still not as shiny as I would like it. I even started a new open-source project just to be able to have an easier time of managing build and releases for EventFlow and my other projects. Don't know if I'll go forward on actually using it for EventFlow though as it would make the setup "non-standard" and harder for others to understand
• I have been working on moving documentation for 1.0 to mkdocs with material and was hoping to give the docs a lift as well as move them to GitHub Pages (not pushed anywhere yet, will do shortly).
• I have been considering putting a 1.0 GA release the current parts of EventFlow that are migrated to 1.0 as soon as they are cleaned up and stable instead of waiting for all parts to get migrated. But that would create an awful experience for developers using the parts that haven't been migrated yet. And the developers using EventFlow does come first.

Hope that can shed some light on what's going on, but basically the things I would very much like some help with

• Test the initialization/configuration API for 1.0
• Cleaning up and finishing the documentation for 1.0 (as soon as I push the mkdocs PR)
• Cleaning up the build setup as its current state is a real sore spot

[Zev-OwitGlobal]

Sounds good! I completely understand the "comes in waves" part, believe me 🙂

I will dive in and see what I can do! I will respond in more length (still working 🙁) Looking forward to helping !

Zev

---

From: Rasmus Mikkelsen @.> Sent: Wednesday, February 16, 2022 4:47 PM To: eventflow/EventFlow @.> Cc: Zev Butler @.>; Mention @.> Subject: Re: [eventflow/EventFlow] Discussion for 1.0 (#843)

This message was sent from outside the company

@Zev-OwitGlobalhttps://github.com/Zev-OwitGlobal as I guess you have noticed, my motivation for doing EventFlow comes in waves (though the thought of stopping has never occurred to me). Having support would definitely take some load off and make spending my spare evenings on EventFlow a lot more fun.

I can give a short status

• I think 1.0 is coming along nicely, but I'm very worried regarding the API. There's several key changes and I really want to make sure to nail how the the initial configuration is done for 1.0. So any input there would really be awesome.
• I originally created EventFlow while working for eBay, and they required to be part of the copyrights, even though there's no eBay IP and I'm doing the project 100% in my spare time. Last year my department got sold to Schibstedhttps://schibsted.com/ (the original creators of Varnish) and getting the legal parts of the copyrights sorted out was no fun. eBay gave its part of the copyrights to Schibsted as part of the sale and now I have been working to get the copyrights from Schibsted back to me alone. Its done, just need to create a PR with the updated copyrights. Please note that the copyrights to an MIT license project is basically who's name is on the box (as I understand it). For the users of EventFlow nothing will change, its still MIT (forever!), it will just be my name on top.
• The build for EventFlow is fragile and a bit of a sore spot. I have done a few iterations, but its still not as shiny as I would like it. I even started a new open-source projecthttps://github.com/rasmus/Bake just to be able to have an easier time of managing build and releases for EventFlow and my other projects. Don't know if I'll go forward on actually using it for EventFlow though as it would make the setup "non-standard" and harder for others to understand
• I have been working on moving documentation for 1.0 to mkdocs with materialhttps://squidfunk.github.io/mkdocs-material/ and was hoping to give the docs a lift as well as move them to GitHub Pages (not pushed anywhere yet, will do shortly).
• I have been considering putting a 1.0 GA release the current parts of EventFlow that are migrated to 1.0 as soon as they are cleaned up and stable instead of waiting for all parts to get migrated. But that would create an awful experience for developers using the parts that haven't been migrated yet. And the developers using EventFlow does come first.

Hope that can shed some light on what's going on, but basically the things I would very much like some help with

• Test the initialization/configuration API for 1.0
• Cleaning up and finishing the documentation for 1.0 (as soon as I push the mkdocs PR)
• Cleaning up the build setup as its current state is a real sore spot

— Reply to this email directly, view it on GitHubhttps://github.com/eventflow/EventFlow/issues/843#issuecomment-1042341063, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARN7XS2QAFVFGD4LAP6PUNLU3QLORANCNFSM45P5CKCQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

NOTICE: This email – including attachments – is intended solely for the named recipient. It may contain proprietary, confidential, or privileged information. If you are not the intended recipient, please notify the sender immediately, delete this email, and destroy all copies. Additionally, if you are not the intended recipient, you must not copy, distribute, or take action based on the information within the email. Though all efforts are made to safeguard emails, OWIT Global cannot guarantee that attachments are virus free or compatible with your systems, and does not accept liability based on viruses or computer problems resulting from opening this email. The views expressed by the sender do not necessarily represent the official position of OWIT Global, and this email is not contractually binding.

[CapitanMurloc]

@rasmus like @Zev-OwitGlobal , I would like to support you. In one version I put the AOP concept for some things like cache, logs, telemetry, etc... all with a cloud approach. As I don't usually show much of the code I do, in fact, I felt that I am in front of a titan and that my code would not reach the level you have. But seen from another perspective, I understand that any support I imagine will be well received. I have supported you very little financially, but even if it is little I have done it with my heart and my gratitude.

[github-actions[bot]]

Hello there!

We hope you are doing well. We noticed that this issue has not seen any activity in the past 90 days. We consider this issue to be stale and will be closing it within the next seven days.

If you still require assistance with this issue, please feel free to reopen it or create a new issue.

Thank you for your understanding and cooperation.

Best regards, EventFlow

[github-actions[bot]]

Hello there!

This issue has been closed due to inactivity for seven days. If you believe this issue still needs attention, please feel free to open a new issue or comment on this one to request its reopening.

Thank you for your contribution to this repository.

Best regards, EventFlow