Merge with fork source?

[da4089]

@skarim has successfully transferred ownership of the original vObject repo from Eventable (its former host company) to their own GitHub account. This is a great effort and outcome, and in my own experience of attempting such things, no small achievement.

The question now is what to do next.

The original repo has a large collection of GitHub stars, and is the source of many forks. While this can be viewed basically as a vanity metric, I think it goes beyond that, and conveys a level of maturity and trust in the project that is genuine, and valuable.

So, one option is to:

1. Rename py-vobject/vobject to eg. py-vobject/vobject-fork
2. Transfer skarim/vobject to py-vobject/vobject
3. Merge py-vobject/vobject-fork back into py-vobject/vobject
4. Move forward with development in py-vobject/vobject (and archive py-vobject/vobject-fork)

There'd be some mess to clean up with issues, PRs, discussions, etc. But perhaps that's worthwhile given the stars, etc, from the original repo?

What does everyone think?

[akuker]

sounds like a good plan to me!

[da4089]

@rsb-23 @return42 any feedback on this?

[rsb-23]

This seems the best approach to me.
Additionally, a warning should be added to update/refresh active forks on py-vobject/vobject preferably in contributor.md

• Which release will be merged in step 3, v0.9.7 or 0.9.8?

[da4089]

I think it makes most sense to merge the latest code back?