search

area515 / Photonic3D

Control software for resin 3D printers
http://photonic3d.com
GNU General Public License v3.0
132 stars 115 forks source link

Branding Changes: CWH --> Photonic3D #177

Closed jmkao closed 8 years ago

jmkao commented 8 years ago

Need to update:

anything else?

kloknibor commented 8 years ago

Maybe also the instal folder (easy to adjust) but maybe even the filenames with cwh in it? Like cwh.log but I suppose there are more ;)!

WesGilster commented 8 years ago

Exciting... What about all of the code?

WesGilster commented 8 years ago

and the entire directory structure where CWH is stored. I'll keep posting here as I encounter more of them... I suppose a repo seach would take care of the vast majority of references.

jmkao commented 8 years ago

At this stage, I think we probably do not need to go below UI and public site-facing strings, so code or log file name changes are probably not necessary. Although Eclipse can probably do many of those renaming changes fairly easily.

WesGilster commented 8 years ago

Makes sense to me, it all depends on how far you want to cut...

jmkao commented 8 years ago

Github automatically creates redirects from the old repo name, so here's one potential plan:

  1. Update HTML and README in WesGilster/CWH
  2. Push to area515/CWH
  3. Rename area515/CWH to area515/Photonic3D
  4. We each update our forks and then start updating the build scripts (which will still work with the old names too, because of the automatic redirects, so step 3 will not break anything)
  5. We do a second pass update with the build files and URLs updated
WesGilster commented 8 years ago

Yep, I was thinking something similar. No migration needed, and you keep backwards compatibility.

jmkao commented 8 years ago

To reduce the amount of work, renaming the zips may not even be necessary. Split this into 3 phases: #203, #204, #205