So here is an update and also @rodlie thanks a lot for really explaining that we do things slow not because we’re abandoning natron but because we just have lots of other committments. That’s a really important clarification I hope more people understand.
Basically, while I would ideally want to do more fixes/additions to the website, I feel like given me and Hank’s limited time especially with the school year ongoing for me, it would be more realistic to simply push the website as-is with my latest (local) fixes (once I push/PR them). Of course, we would still need to do a review, and any glaring (mission-criticial, so to speak) issues must be fixed. But the rest of the things let’s put on a wishlist. That is, whatever we can go without, let’s go without it for now.
@Shrinks99 and @rodlie I would love to hear your thoughts on this and if you’re ready to go ahead, let me know. I just think it’s probably for the best, we’ve worked for years on this thing and I want to get it out.
News! Thanks to amazing work by Hank we have gotten it all set to launch! Btw Hank is amazing, I couldn’t have done the work on this website project without him. In any case we are ready to go!
The next step, as far as I understand with my (admittedly limited) knowledge, is this:
Have a final review before the go-ahead (although imo the website should be good as-is)
Rename and archive the existing natron website repository, maybe to something like natron-legacy-website
Transfer over the repo from Hank’s GitHub over to Natron’s official Github
So glad this is finally happening! This is going to be great to show that Natron is very much alive and there are fresh contributions!
I’m currently busy with other projects, but will try to be more active moving forward.
That’s completely okay, again, no obligations.
We still need a ok from the core team.
Would appreciate if you could let them know of the website!
btw, I still own natronvfx.com and natronvfx.org if the community want to use them (I can even transfer ownership if needed).
Yes that would be wonderful! Although we would probably want an auto-redirect from the https://natrongithub.github.io site (not sure if github pages does this) so that it doesn’t break any mentions of Natron/any links to the Natron website already on the web.
Or we could keep the website on GitHub pages and redirect from those other domains.
Do we still need to keep those domains? In my opinion, Yes; to prevent someone with malicious intent from posing as the Natron website. This has happened before when someone was distributing malware using a copy of the blender website on a malicious domain (biender_com) iirc.