avatarify-python
avatarify-python copied to clipboard
alievk
New fork of avatarify-python maintained by Kitopvibe1
Forking the project is definitely allowed by the license, and you give attribution, so nothing wrong with that. I wish you good luck with supporting the people who try to run it :)
However, this is still the issue tracker for avatarify-python and not a message board. I'm editing your subject line to better describe the contents of your post. It's still not an issue report for this project so it doesn't really belong here, but I'll leave it up for now.
Btw. you're talking about your "kit-caller" repository, right? A bit confusing since you also have an actual github fork of the project in avatarify-python-1. IMO it would've been better if you continued working on the fork, since it makes it easier to see modifications and merge any upstream changes, if there will be any. You can still move files around in the fork, you don't need to keep the exact file structure if you don't like it, git usually manages to keep track of it. But you do as you like of course.
I don't see why your copy is "upgraded" though. As far as I can see you've only deleted mac/linux files and the manual, and then written a new README.md. Have you got some local changes you haven't pushed yet perhaps?
NOTE: Kitopvibe1's fork is not in any way affiliated with avatarify-python or endorsed by its creators.
Forking the project is definitely allowed by the license, and you give attribution, so nothing wrong with that. I wish you good luck with supporting the people who try to run it :)
However, this is still the issue tracker for avatarify-python and not a message board. I'm editing your subject line to better describe the contents of your post. It's still not an issue report for this project so it doesn't really belong here, but I'll leave it up for now.
Btw. you're talking about your "kit-caller" repository, right? A bit confusing since you also have an actual github fork of the project in avatarify-python-1. IMO it would've been better if you continued working on the fork, since it makes it easier to see modifications and merge any upstream changes, if there will be any. You can still move files around in the fork, you don't need to keep the exact file structure if you don't like it, git usually manages to keep track of it. But you do as you like of course.
I don't see why your copy is "upgraded" though. As far as I can see you've only deleted mac/linux files and the manual, and then written a new README.md. Have you got some local changes you haven't pushed yet perhaps?
NOTE: Kitopvibe1's fork is not in any way affiliated with avatarify-python or endorsed by its creators.
yes, i got some local changes i haven't pushed yet
also i need the pytorch model used in avatarify, can you please help with that?
i'm working upgrading the avatarify completely