Split addins into their own repos

[edwardwilson]

The main EventFlow repo has grown large and contains many addin projects. These should be moved to their own git repos where issues and work can be tracked better. Here are some I have identified as good moves to start.

• [ ] Move Elasticsearch to EventFlow.Elasticsearch #307
• [ ] Move Documentation to EventFlow.Documentation #306
• [ ] Move Samples to EventFlow.Examples

[edwardwilson]

@rasmus I do not have permissions to create new repos in EventFlow, if you want to create the repos I can move the code, or add the permissions for me to do this? I don't mind either way.

[edwardwilson]

Consideration about build and deployment to nuget.org will need to be looked at too with these splits

[rasmus]

Before moving everything, I would like a solution for managing build files. So far the best I have come up with is a submodule and make the build.cake more convention based

[edwardwilson]

Yes it would be good to have a standard build, I am curious though why there is a need for a cake build. Can a simple MSBuild combined with the bespoke appveyor.yml per repo work? I feel a submodule would complicate the getting started for newcomers to contribute.

[rasmus]

I'm all for simplifying the build setup, but I prefer Cake to MSBuild configuration. If you have a good idea for simplification, create a pull request, I would love to see it.

I'm off this weekend so my support will be limited, but I hope to be to write to you soon.

On 8 Sep 2017, at 16.47, Edward Wilson [email protected] wrote:

Yes it would be good to have a standard build, I am curious though why there is a need for a cake build. Can a simple MSBuild combined with the bespoke appveyor.yml per repo work? I feel a submodule would complicate the getting started for newcomers to contribute.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[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