Create main repository as issue tracker

[codemasher]

Distinction is easy: engine means engine, which is what upstream reflects. To avoid any licensing issues and creating further mess, we can keep anything related to building the full game (such as assets/scripts, that are currently kept in /misc) and its related issues separate. It's only logical to me:

• worldofpadman (full game releases and related assets, building of the aforementioned, may require propriarity license)
  • wop-engine or whatever you want to call it (the ioq3 fork, GPL [for those who try to misinterpret me: CODE])
  • wop-data (the game assets, may require propriarity or a CC license)
  • wop-mapeditor-support (unrelated to the game, but may be included in the full game releases)
  • etc.

Either way, this may require its own issue then.

Originally posted by @codemasher in https://github.com/PadWorld-Entertainment/worldofpadman/issues/14#issuecomment-820348215

[codemasher]

This repo still doesn't contain any assets, not should it. It's only part of "worldofpadman", aka, the full release and that name for this repo is misleading, Not to mention that there have already been issues created that are not relevant to this repo, but rather to the assets (maps, sounds etc.).

I'm creating this issue now as the recent additions of issues add a lot of unrelated noise here.

[kai-li-wop]

I'm sorry to say that neither the asset repository will be visible to others, nor the issue tracker that goes with it. Also, as @robo9k stated, users are not interested in deciding which repository they post bugs and requests to. So we agreed to use the issue tracker of the worldofpadman repo to represent the WoP game and use it for everything, even if we know that might cause some chaos. To keep track of everything, We use the milestone feature where issues are then assigned. Is it possible to group repos like you suggested?

Also, please don't touch the wop-map-support repo as this is already referenced by the NetRadiant build script to include the wop game pack on the fly.

[codemasher]

just fyi: issues can be transferred to another repo if necessary, so it doesn't matter where users would create issues, but at least we could try and keep some order across the different repos.

Edit: Also, projects exist.

[codemasher]

Is it possible to group repos like you suggested?

Grouping is not possible - i just outlined how i imagine the build process for the final installers, that i would do in a separate project, which depends on the several sub-projects. That repo should also be the one where mainly issues should be reported, projects managed etc. - this repo here, the ioq3 fork (engine, gamecode) is just one subproject of it.