Help wanted: Community/Issue manager

[rasmus]

If you have been following the project on GitHub, you will notice that the issues and PRs pile up these days. This is by no means fair to the many companies and developers that use EventFlow every day, but the fact is that the development of 1.0 is taking up what little time I have in the evenings these days.

So, if you are interested in helping supporting EventFlow and its community, let me know.

[Simusharp]

Hi,

Can you provide more details about the help you are looking for?

I will be happy to contribute to this project but I am not sure if I am competent enough.

[rasmus]

In short, help out developers on GitHub (and maybe elsewhere).

In more detail

• Provide early feedback to issues created
• Triage issues and pull request, maybe something automatic

Nice stuff that could be done

• Seek out EventFlow developers and their issues on Reddit or Stack Overflow
• Project management, see if issues can be gather together into milestones that provide value into releases with 1.x bumps
• Update documentation with general useful stuff, e.g. if someone is asking questions, others might have the same, so lets put them in the docs

It seems like there's a community surrounding EventFlow, but getting it together and making it into something that can benefit all users of EventFlow is something I have no idea of how to do.

As time is the main currency of open source, it really depends on how much time you have. For me its trying do chop up the work that I have with EventFlow into smaller pieces and get outside help to do these.

[CapitanMurloc]

Count me in. Assign me a task and I will find the time to carry it out.

De: Rasmus Mikkelsen @.> Enviado el: miércoles, 19 de mayo de 2021 13:17 Para: eventflow/EventFlow @.> CC: Subscribed @.***> Asunto: Re: [eventflow/EventFlow] Help wanted: Community/Issue manager (#838)

In short, help out developers on GitHub (and maybe elsewhere).

In more detail

• Provide early feedback to issues created
• Triage issues and pull request, maybe something automatic

Nice stuff that could be done

• Seek out EventFlow developers and their issues on Reddit or Stack Overflow
• Project management, see if issues can be gather together into milestones that provide value into releases with 1.x bumps
• Update documentation with general useful stuff, e.g. if someone is asking questions, others might have the same, so lets put them in the docs

It seems like there's a community surrounding EventFlow, but getting it together and making it into something that can benefit all users of EventFlow is something I have no idea of how to do.

As time is the main currency of open source, it really depends on how much time you have. For me its trying do chop up the work that I have with EventFlow into smaller pieces and get outside help to do these.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/eventflow/EventFlow/issues/838#issuecomment-844002873 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGHWQZASNPFT5TSNNGBTBLTTOOMY5ANCNFSM44X7IZWA . https://github.com/notifications/beacon/AGHWQZFDSEBZW6JPHWVSLVTTOOMY5A5CNFSM44X7IZWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGJHHMOI.gif

[WardenUnleashed]

Hey @rasmus!

I think you've seen me in a few MRs! I'm happy to help as I am greatly invested in the future of EventFlow and use it in many of my projects!

[rasmus]

Thank you all!

This really means a lot! The amount of work for the has be the cause of some frustration on my part and the amount of time I have spend on EventFlow the last few months have been insignificant.

But, getting support, both real and just kind words, really helps.

I have closed the old 1.0 milestone and created a new one. I really, really want to keep the initial release for 1.0 as simple as possible. Basically only doing framework target cleanups (moving to .NET Core LTS versions), build cleanup and doing some well earned API cleanup (remove spelling mistakes and adding much needed APIs that requires braking changes).

Please if you are up for it, pick one from the 1.0 milestone issues, especially #840. I'll try to do some more writeups and issues to align.

[rasmus]

Link to the 1.0 milestone https://github.com/eventflow/EventFlow/milestone/2

[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