The easy way: through feedback and sharing
- Drop me a message/comment somewhere: just saying “Hi” or “Thank you dude” would already be great!
- Share your feedbacks: the best place (atm) might be BakeMyScan’s thread on blenderartists.org
- Cite BakeMyScan, although you don’t have to (something like Made with BakeMyScan or #BakeMyScan would be perfect)
- Spread the word. You know, the more the merrier ;)
- Retweet the releases announcement I’ll make on Twitter if you think they are worth it.
- If you find a bug, look for issues on the github repository, and if it is not referenced yet, just open an issue with the relevant information !
- I’ll also soon lose my free “PRO” account on Sketchfab (2019/01/07), so if you happen to think about opening an account, contact me somehow so that I can send you an invitation link: I’m sure I can still have a few more months of “PRO” added to my account with this system :)
The hard way: improve the code
I am not ready to accept external collaborators into my hobby project. Yet.
But as my “secret goal” is to turn BakeMyScan into some kind of “ultimate” addon for asset optimization, while still keeping it free, I will definitely need some help.
In order to make it into a “true” Open Source and collaborative project, I’ll have to open up to other contributors. And I want to do so, I’m just not sure exactly how yet ;).
As of right now and for the next few weeks, here are a few ways you could try to help me:
- Share with me your original tips and tricks related to the “optimization” workflow: sequences of operators you use, python scripts you have developed…
- Share your references to Open Source command-line software that could be interfaced with BakeMyScan: I think we desesperately need a powerful UV packer and other remeshing tools for instance. I’ll keep my “findings” in this github issue for now.
- Share your tips concerning the environment of such a project, the communication, the website… keeping in mind that I need everything to stay simple as can be
Of course, I’ll also try to accept pull requests, but that will 100% depend on the first weeks/months of feedback! I’ll adjust my plans later ;)
About giving credit
What you can do
The code is licensed under GNU GPL v3. So make sure to respect the implications of this licensing scheme if you wish to re-use or re-adapt BakeMyScan.
And although you don’t have to, I would appreciate if you could make a reference to BakeMyScan in the description of assets or applications you create thanks to it. That is the only way such a project can become viable in the long-run, by making sure to give credit to the original content creators.
What I plan to do
I am not trying to implement a “I’ll give you money to have my name on your page” scheme here, but I’ll always try my best to give appropriate credit to anyone helping me improve BakeMyScan.
Whether you made a donation, good general suggestions that I’ll follow, or shared some awesome relevant scripts, you’ll most probably have - if you wish to - a clear mention somewhere. Probably on a dedicated “Thanks to” page, or in the footer of the website as I feel this is often done by creators. Keep in mind that I won’t create a “premium” category, the idea being to thank and give credit. Not to rob you ;)
I’m thinking about something along the lines of:
- (Name + social) gave a tip to support BakeMyScan. Kudos!
- (Name + social) has made (this algorithm) possible by sharing his cool workflow trick. See this blog post where he explained the method.
- (Name + social) has shared his script on …, which is implemented in …
- (Name + social) has helped me to interface (this software) into BakeMyScan
- (Name + social) has 100% implemented the functions allowing to …
- … etc.
I guess that this could be a really cool and elegant way to make sure that I am not the one taking credit for someone else’s work!