PLEASE COMMENT: Should this project be forked for continued development?

[elarroba]

No description provided.

[Eyap53]

Well, there was no activity from @Fantomas42 for the last past year and a half (last activity was on March 2020 for a few commits, and other changes one more year ago).
If we want the project to continue, let's do that. There are a lot of interesting stuff, so it would be a waste to just stop it.

I did make a fork for my own use (https://github.com/Eyap53/django-blog-zinnia), but didn't do much more. I will have some time to review / manage a project, but not much for developing (well, time will tell), so I can provide some help.
If you are motivated, I will follow your call :) (either you create a fork, use mine or whatever, it's up to you !)

[elarroba]

Would be nice to hear from @Fantomas42 and see if he is willing to transfer the project, or at least give permission to other developers to commit and/or review PRs. I agree this project has so much work into it and would be a waste to stop it.
I can dedicate some time to review and manage as well and develop as needed.

@Fantomas42 your input would be greatly appreciated.

[elarroba]

I reached out to @Fantomas42 via email regarding the project. Hoping to get a response. I would hate this project to go on a fork since it already has a lot of visibility with GitHub stars. My organization can absorb the project for further maintenance and development, but ideally it would need to be transferred.

Let's wait and see.

[elarroba]

No word yet from @Fantomas42. Ideally this project needs to be transferred to an organization willing to manage and/or maintain it. My organization is willing to do that but unfortunately transfer would need to be approved by @Fantomas42. Otherwise, we would need to fork.

[elarroba]

@Eyap53 I have created a fork for v0.3-alpha and I will start hosting the project documentation on djangoblogzinnia.com soon.

https://github.com/arrobalytics/django-blog-zinnia

However, in my opinion this project will need to live on under a different name and obviously give credit to the original authors. I will be creating a new project team to manage the project and will be adding you @Eyap53 if interested.

I've tried to reach out to @Fantomas42 many times though multiple channels and he's nowhere to be found. It's a shame to leave this project behind. My organization is willing to maintain and continue the development of this project if @Fantomas42 is willing to transfer.

[Eyap53]

Here is a few thoughts about that :

• Well first you got the wrong version number IMHO. Last version was 0.20, so next version should be 0.21. The 0.3 was already a version a long time ago (although the tag is not present in this directory anymore).
• As I said, I am interested in pursuing the development of this django blog. Though I don't really know what is exactly implied by having your organization manage that. I'll see later.
• I don't think rebranding is a good idea as of now. Maybe later when the projects is more advanced compared to the current state -> Time will tell if it's necessary or not.

[elarroba]

By organization I mean my GitHub organization, where we could create a GitHub Team of developers with different roles and permissions that can contribute to the project, including you.

If we are both interested in the development of this project, there is no need to go separate ways. That would be a waste of our time.

I understand your concern about re-branding and honestly is not my preference. But keeping the same name will be a problem for SEO purposes and there will be confusion as to which project is the most current. Although Zinnia with 2,000+ stars will always get more attention, so any efforts we make to move the project forward will be a waste.

Also, django-blog-zinnia is already taken on pypi, so it would need to be packaged as djangoblogzinnia? Again, more confusion.

If we send pull requests to this repo, it will be a waste as well because @Fantomas42 would need to review and approve. And we all know he's obviously no longer interested in participating. Without @Fantomas42 collaborating with us, there's very little we can do to keep the Zinnia name. It would at least help if he could add a deprecation notice and point to the new repo, but not even that is possible.

Anyway, the ideal solution would be to move this project to a space where more developers can contribute, including @Fantomas42, while still keeping the reputation and exposure of the django-blog-zinnia repo. That can only happen under a different more collaborative setup.

[elarroba]

@Eyap53

I just created a fork of this project and updated the code to work with modern versions of Django (including 4.0+).

Please visit https://github.com/arrobalytics/django-blog-zinnia if you want to contribute. Don't forget to star the project to show your support.

Visit the new site https://www.djangoblogzinnia.com for documentation, demo and other resources.