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

Make separate repository on Github for Blender add-on #3025

Closed
Symbian9 opened this Issue Nov 8, 2017 · 15 comments

Comments

Projects
None yet
8 participants
@Symbian9

Symbian9 commented Nov 8, 2017

Please, make separate repository that will include code only of Blender addon

Here is current location of this addon

@Benau

This comment has been minimized.

Show comment
Hide comment
@Benau

Benau Nov 8, 2017

Member

any good reason?

Member

Benau commented Nov 8, 2017

any good reason?

@Symbian9

This comment has been minimized.

Show comment
Hide comment
@Symbian9

Symbian9 Nov 8, 2017

@Benau, it's impossible download latest code of addon separatly as single ZIP from SourceForge

If try Download Snapshot button on SourceForge it give me only full snapshot of media tree, where size of this .tar.gz is ~ 1.5 Gbytes (sic!)

If create separate repo on Github for Blender add-on only, then there is easy way for get latest code from master as single ZIP.

Also, near all Blender add-ons' developers, that could help with development of this add-on, hosted on Github, and not use SourceForge anymore.

Symbian9 commented Nov 8, 2017

@Benau, it's impossible download latest code of addon separatly as single ZIP from SourceForge

If try Download Snapshot button on SourceForge it give me only full snapshot of media tree, where size of this .tar.gz is ~ 1.5 Gbytes (sic!)

If create separate repo on Github for Blender add-on only, then there is easy way for get latest code from master as single ZIP.

Also, near all Blender add-ons' developers, that could help with development of this add-on, hosted on Github, and not use SourceForge anymore.

@auriamg

This comment has been minimized.

Show comment
Hide comment
@auriamg

auriamg Nov 8, 2017

Member

@hiker Any opinion?

Member

auriamg commented Nov 8, 2017

@hiker Any opinion?

@MTres19

This comment has been minimized.

Show comment
Hide comment
@MTres19

MTres19 Nov 8, 2017

Contributor

My limited experience with 3D art for STK is that sooner or later you'll want the whole media repo anyway. If not to link library objects into your track, then at least for examples of how to do things in Blender, which is often too complex to describe clearly in documentation.

Edit: also, any particular reason why SF is inherently bad?

Contributor

MTres19 commented Nov 8, 2017

My limited experience with 3D art for STK is that sooner or later you'll want the whole media repo anyway. If not to link library objects into your track, then at least for examples of how to do things in Blender, which is often too complex to describe clearly in documentation.

Edit: also, any particular reason why SF is inherently bad?

@Symbian9

This comment has been minimized.

Show comment
Hide comment
@Symbian9

Symbian9 Nov 8, 2017

sooner or later you'll want the whole media repo anyway

I want download Blender add-on & whole media pack separatly.

I won't download 1.5 Gbyte each time if I only need snapshot of latest Blender add-on code.

Current situation is abnormal for normal user/modder.

P.S.: And about your question, @MTres19

also, any particular reason why SF is inherently bad?

SF made big mistake as platform for open-source

Symbian9 commented Nov 8, 2017

sooner or later you'll want the whole media repo anyway

I want download Blender add-on & whole media pack separatly.

I won't download 1.5 Gbyte each time if I only need snapshot of latest Blender add-on code.

Current situation is abnormal for normal user/modder.

P.S.: And about your question, @MTres19

also, any particular reason why SF is inherently bad?

SF made big mistake as platform for open-source

@MTres19

This comment has been minimized.

Show comment
Hide comment
@MTres19

MTres19 Nov 9, 2017

Contributor

@Symbian9 Just use svn update. It will only fetch the newly changed things. No need to download the entire repo again just to update the scripts.

RE the SourceForge scandal, I'm well aware of that. It happened 2.5 years ago and since then I haven't heard of anything bad from them. Also SF has reliably hosted STK's code and downloads for over a decade without anything serious happening that I know of.

Contributor

MTres19 commented Nov 9, 2017

@Symbian9 Just use svn update. It will only fetch the newly changed things. No need to download the entire repo again just to update the scripts.

RE the SourceForge scandal, I'm well aware of that. It happened 2.5 years ago and since then I haven't heard of anything bad from them. Also SF has reliably hosted STK's code and downloads for over a decade without anything serious happening that I know of.

@hiker

This comment has been minimized.

Show comment
Hide comment
@hiker

hiker Nov 9, 2017

Member

First of all, if you frequently want to update the blender tools, I'd recommend to just use svn - you then have the options to just checkout the blender directory (or checkout all, and only update the blender directory). Afaik sourceforge does not offer a directory-only download (it's all or nothing).

Having said that, I don't object to using git for the blender part - but it means that there are then more instructions/repos people need to clone. Atm we can just say: download this repo, and you have everything. Then it will be: you need to download the media repo using svn from here, and the github version from here. Artists might need to install two different tools, there are two places to update (sometimes the media repo needs to be in synch with assets, e.g. when we switched the file format), which atm we get automatically, then we need to handle this case.

@Symbian9 What is the problem of just using svn? TBH, while I certainly favour git of subversion, for the media repo the setup we use seems to work pretty good.

Member

hiker commented Nov 9, 2017

First of all, if you frequently want to update the blender tools, I'd recommend to just use svn - you then have the options to just checkout the blender directory (or checkout all, and only update the blender directory). Afaik sourceforge does not offer a directory-only download (it's all or nothing).

Having said that, I don't object to using git for the blender part - but it means that there are then more instructions/repos people need to clone. Atm we can just say: download this repo, and you have everything. Then it will be: you need to download the media repo using svn from here, and the github version from here. Artists might need to install two different tools, there are two places to update (sometimes the media repo needs to be in synch with assets, e.g. when we switched the file format), which atm we get automatically, then we need to handle this case.

@Symbian9 What is the problem of just using svn? TBH, while I certainly favour git of subversion, for the media repo the setup we use seems to work pretty good.

@auriamg

This comment has been minimized.

Show comment
Hide comment
@auriamg

auriamg Nov 9, 2017

Member

One thought I just had is that we are more and more moving towards the use of an object library, which is in the media repo, so if you want to make tracks according to our best practices, you will need the media repo anyway to have access to the library

Member

auriamg commented Nov 9, 2017

One thought I just had is that we are more and more moving towards the use of an object library, which is in the media repo, so if you want to make tracks according to our best practices, you will need the media repo anyway to have access to the library

@Symbian9

This comment has been minimized.

Show comment
Hide comment
@Symbian9

Symbian9 Nov 9, 2017

For the record, @leyyin made repo that look similar to what I mean

But this repo not updated for a while.

Current stk-blender add-on look not good, and should be designed according next sheme

  • ./blender/scripts/addons/stk-blender/ - main folder for add-on:
    • ../stk-blender/__init__.py - main script of add-on;
    • ../stk-blender/spm_export.py, ../stk-blender/stk_kart.py, ../stk-blender/stk_material_export.py, ../stk-blender/stk_panel.py, ../stk-blender/stk_track.py - submodule scripts of ../stk-blender/__init__.py;
    • ../stk-blender/stkdata/ - directory with parameters as XML-files (configs) of each submodule script.

Also, need update it to Blender 2.78c (current LTS tree).

Symbian9 commented Nov 9, 2017

For the record, @leyyin made repo that look similar to what I mean

But this repo not updated for a while.

Current stk-blender add-on look not good, and should be designed according next sheme

  • ./blender/scripts/addons/stk-blender/ - main folder for add-on:
    • ../stk-blender/__init__.py - main script of add-on;
    • ../stk-blender/spm_export.py, ../stk-blender/stk_kart.py, ../stk-blender/stk_material_export.py, ../stk-blender/stk_panel.py, ../stk-blender/stk_track.py - submodule scripts of ../stk-blender/__init__.py;
    • ../stk-blender/stkdata/ - directory with parameters as XML-files (configs) of each submodule script.

Also, need update it to Blender 2.78c (current LTS tree).

@hiker

This comment has been minimized.

Show comment
Hide comment
@hiker

hiker Nov 9, 2017

Member

We just discussed this issue on irc. I can't see any advantage of splitting the blender tool into a separate repository:

  • there is no need to download 1.5GB of data, if you are interested in latest development version, use svn.
  • you need a media repo in synch anyway in order to use our objects
  • if a blender developer wants to contribute, it's easy to download the svn version, put it in local git, and send us a patch.
    Yes, I do acknowledge that git is the superior version control system, but the additional work for us (updating all instructions, finding a way to make sure that the exporter version and .blender files are in synch) is just not worth, since I don't see any clear benefit. If you are an artist and want to use our latest (and sometimes experimental/work-in-progress) versions, you need to use svn anyway, if you are a blender developer, feel free to use git and just send us a patch.
    I am therefore closing this issue. If you should have a use case that we did not think of, please reopen!

Cheers,
Joerg

Member

hiker commented Nov 9, 2017

We just discussed this issue on irc. I can't see any advantage of splitting the blender tool into a separate repository:

  • there is no need to download 1.5GB of data, if you are interested in latest development version, use svn.
  • you need a media repo in synch anyway in order to use our objects
  • if a blender developer wants to contribute, it's easy to download the svn version, put it in local git, and send us a patch.
    Yes, I do acknowledge that git is the superior version control system, but the additional work for us (updating all instructions, finding a way to make sure that the exporter version and .blender files are in synch) is just not worth, since I don't see any clear benefit. If you are an artist and want to use our latest (and sometimes experimental/work-in-progress) versions, you need to use svn anyway, if you are a blender developer, feel free to use git and just send us a patch.
    I am therefore closing this issue. If you should have a use case that we did not think of, please reopen!

Cheers,
Joerg

@hiker hiker closed this Nov 9, 2017

@Symbian9

This comment has been minimized.

Show comment
Hide comment
@Symbian9

Symbian9 Nov 9, 2017

Anyway, @leyyin just updated his repo stk-blender

Thank you, @leyyin! Please, keep it fresh!

Symbian9 commented Nov 9, 2017

Anyway, @leyyin just updated his repo stk-blender

Thank you, @leyyin! Please, keep it fresh!

@leyyin

This comment has been minimized.

Show comment
Hide comment
@leyyin

leyyin Nov 9, 2017

Member

Btw @Symbian9 my repo will most likely diverge in the near future and break things, as I am trying to clean things up there, so do not rely on it ;)

Member

leyyin commented Nov 9, 2017

Btw @Symbian9 my repo will most likely diverge in the near future and break things, as I am trying to clean things up there, so do not rely on it ;)

@konstin

This comment has been minimized.

Show comment
Hide comment
@konstin

konstin Nov 9, 2017

Contributor

There's also git-svn, so you can use git with a svn repo.

Contributor

konstin commented Nov 9, 2017

There's also git-svn, so you can use git with a svn repo.

@Symbian9

This comment has been minimized.

Show comment
Hide comment
@Symbian9

Symbian9 Nov 9, 2017

There's also git-svn , so you can use git with a svn repo.

@konstin, this is not what asked and not related to what I mean.

This is what I mean

Symbian9 commented Nov 9, 2017

There's also git-svn , so you can use git with a svn repo.

@konstin, this is not what asked and not related to what I mean.

This is what I mean

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment