Skip to content
This repository has been archived by the owner on Apr 29, 2022. It is now read-only.

Revival of original repository / end of life for this repository #97

Closed
Joelius300 opened this issue Sep 30, 2019 · 4 comments
Closed

Comments

@Joelius300
Copy link
Owner

Joelius300 commented Sep 30, 2019

As you might have seen, Marius M. (@mariusmuntean) has resumed work on the original ChartJs.Blazor. Since this repository here has made a lot of progress during the time the other project was abandoned, Marius has agreed on merging all my changes into his repository where all future development will be done.

This means that, after I have merged the remaining few pull request, this repo will not be maintained anymore. The nuget package will be abandoned or removed entirely (if that's even possible). All the issues from here will be moved to the original repo.

The migration is currently taking place and me and Marius are actively working on it. We have a plan and are discussing important decisions and milestones along the way. For this reason I think it's best if people who want to contribute are very careful with what and where they open new issues and pull requests. You can always offer help but please do not rush anything as this is a slow and steady process which requires carefully planned execution.

If you already have bug-reports, new feature ideas or other stuff, please go ahead and open an issue in the original library as the issues here will have to be moved there manually anyway.

I'd like to thank all the contributors who helped me maintain this repo during the last three months.
Special thanks go out to @SeppPenner who has been a great help. I'd also like to give special thanks to Marius himself for being so understanding and helpful concerning this library and the migration to his repository (and of course for making all of this possible in the first place).

I will continue to work on this library alongside Marius in his repo and adress the issues and feature that are still open/missing (either from issues in this repo, issues in the original repo or personal backlogs).
Hope to see you there :)

@Joelius300 Joelius300 pinned this issue Sep 30, 2019
@SeppPenner
Copy link
Contributor

SeppPenner commented Sep 30, 2019

I'd like to thank all the contributors who helped me maintain this repo during the last three months.
Special thanks go out to @SeppPenner who has been a great help. I'd also like to give special thanks to Marius himself for being so understanding and helpful concerning this library and the migration to his repository (and of course for making all of this possible in the first place).

Thank you for the kind words. I really like the library and want to contribute further on the original one from Marius as well 👍

Just some thoughts from my side (I already told you some of them yesterday):

I guess that's all from my side.

@TomaszGrzmilas
Copy link
Contributor

Hi guys !

As I can see nothing is happening on mariusmuntean/ChartJs.Blazor repo. Maybe it was not good idea to kill this repository ? Here project was developing and I think now it will stuck in place :(

What you think ? Maybe we can still doing some work here ?

BR

@mariusmuntean
Copy link

Hi everyone,

I'm almost done with reintegrating the changes in my repo. The work I've done is on the revival branch.
Yesterday I republished the client-side samples on https://www.iloveblazor.com

Today I'll update the README and publish a NuGet package. Afterwards normal development should resume.

@Joelius300
Copy link
Owner Author

The migration is now officially complete 🎉 ❤️

This issue here will be closed but stay pinned for anyone who stumbles upon this repo. I might archive this repo but that's not fixed yet.

I hope to see everyone again back in the original ChartJs.Blazor by marius! 😄

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants