-
-
Notifications
You must be signed in to change notification settings - Fork 3
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request]: New Name! #2
Comments
we should leave the name as is - better title/brand recognition, that is if we get the permission from the original copyright holder - will ask @dtobi later today.@AtomikkuSan, repo is not ready yet. Have massive amount to do before anything is done to it. Will finish it once I finish prepping GA |
Wouldn't @sarbian be a better person to ask? |
Okay, thanks for the clarification! I really hate the ND clause, it makes mod developing a lot harder, especially on the legal front. |
respecting the original author's wishes, and just general respect in general. yes, it can be a PITA, and many Many MANY mods have died because of this, but at the same time it has kept several key mods alive. experience has taught me to go very carefully with licenses and make sure get the full permission. which we will get. :D |
Which ones stayed alive?
I can't wait! |
Hi guys. What's up? |
Welcome @dtobi ! Just about to shoot an dm to you et al on the KSP forums concerning adopting. With a CC ND 3.0 license must dot i's, cross t's, and zip the zeds. |
@AtomikkuSan just want to verify your forum name so I can include you in the adoption letter. AtomicTech correct? |
@ dtobi - KSP Forum Direct Message sent. Also has my email address. @AtomikkuSan I don't expect you to want to help with all of them - but I suspect you will want to. :D I think I got all of them, all except:
|
OH YES, IT'S (MOD DEVELOPING) SHOWTIME! |
Yep! |
@dtobi can we rename the project to Space Shuttle Engines Reflown and, more or less, rename every part with a more technical sounding names and better descriptions? |
So, which ones do we have? |
Would Klockheed Martian stay as brand name? In general, I’m fine with Space Shuttle Engines Reflown. It would be nice if you would still credit me as original author, though. Otherwise you’re free to rename parts, change code or add new models, of course. |
@dtobi I personally prefer keeping the brand intact - so keeping the wonderful pun Klockheed Martian as manufacturer, agency, and total brand. Changing the name of the add-on is not my first choice because it is disrespectful to you and all the hard graft you put into it in the first place. Changing the name also sends players the wrong message. @dtobi legally can't until we have an answer to the forum's direct message since the license is CC ND. This is because the original source of the files and license comes from the forums and not GitHub. The permission must come from the original source. Just doing the legal due diligence. Mahalo nui loa! |
I'm okay with all the current parts staying under Klockheed Martian, but can I change any of the new parts to be under AtomicTech Inc.? |
@zer0Kerbal, I've updated all the new pull requests to have Klockheed Martian as their manufacterer. |
👍 just waiting on @dtobi to reply to the forum direct message; it's a sticky pickle this conundrum we find ourselves facing, need a pickle jar opener |
nearly in business now. converting this to a discussion. will keep everyone informed also will update here as the repo is prepared, hopefully my schedule will allow me to prioritize this wonderous parts add-on. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Description of the new feature / enhancement
When I was first developing this mod, I originally named it Shuttle Engines Rebuilt and I'd like to name this continuation with something similar. I'd want to rename it to Space Shuttle Engines Reflown.
Proposed technical implementation details
Change the Repo name.
The text was updated successfully, but these errors were encountered: