Jump to content

politas

Members
 View Profile  See their activity

  • Posts

    751

  • Joined

  • Last visited

 Content Type 

Everything posted by politas

  1. politas
    Can you check using these instructions?
  2. politas
    For the moment, I'm holding off pointing CKAN to that Spacedock entry. I've pointed the latest release to the dropbox link @SpannerMonkey(smce) pasted, and updated the compatibility to include 1.0.5. If anyone finds it doesn't work after all, please let me know. The zip file is weird. The folders have a recent modification date, but none of the files do.
  3. politas
    Is this one going up on Spacedock, too?
  4. politas
    Hi there! I gather there's a whole team now working on this mod, and I'm wondering whether the Richard_Kerman who "shared" Kerbal Foundries on Spacedock is part of that team. The team list posted earlier doesn't have anyone with that name, but Spacedock names and forum names don't have to match up. It is pointing to the old locked thread, though, which makes me suspicious.
  5. politas
    Realchutes and Tweakscale are both on Github, and KAX is on Curse. Why are you posting this question to the Spacedock thread?
  6. politas
    Thanks for the heads up. That's been fixed, now.
  7. politas
    Critical Temperature Gauge, Telemachus, Vessel View and Field Experience should all be working very soon. @John FX, are you aware of any other mods that have fallen through the cracks? There are going to be a few mods that will just be unavailable until the mod author re-uploads them, unfortunately (those that CKAN says have a "restricted" license.)
  8. politas
    Can you please give links to forum threads? Searching is somewhat unreliable on this forum software. Ok, Vessel View, Telemachus and Field Experience should all be fine once my changes are merged. Critical Temperature Gauge we ought to have a mirror of, since it's GPLed.
  9. politas
    If you tell us which mods are causing you grief, we can fix them for everybody. I'll take a stab in the dark and suggest that your .Net installation is still version 4.0, rather than 4.5, which CKAN requires.
  10. politas
    Any chance of an actual release of this? I'd love to list it in CKAN, but CKAN ignores pre-releases.
  11. politas
    Oh sorry, my bad, that was the wrong command try this one instead: ckan scan You can also run ckan help for more information about the command line options, and see the user guide here.
  12. politas
    Ok, well I've never used Windows 10, but you ought to have a program called "Command Line" or some such in the menu under Accessories? That'll give you a window with what looks like an old DOS prompt. (Maybe that's not a meaningful term for you, though) You'll need to change directories to where your KSP program is installed, then enter ckan clean
  13. politas
    What operating system are you on?
  14. politas
    running "ckan clean" from the command line should find all the manually installed mods that CKAN knows about.
  15. politas
    It depends upon which mod you're trying to download, and what license it is released under. Free Licensed mods should mostly be working now, but restricted ones have to wait until they are manually pointed to a new source.
  16. politas
    Any chance of an upload to Spacedock?
  17. politas
    Something that would be good for Spacedock to implement is a way to actually contact mod authors when there is no forum link. The automated CKAN submissions say "Please direct questions about this pull request to <authorname>" with a link to the author's Spacedock profile page, but there's no way to actually contact the author from their profile page.
  18. politas
    It is very hard for Spacedock or CKAN to control where people ask for support. All either tool can provide is an assurance that someone pretending to be you will be restricted from doing so. Ferram, you put FAR under a GPL 3.0 license. If you didn't understand what you were doing when you did so, I'm sorry. But now, the other contributors also have rights that you granted them. I'm sorry that you feel you're being "screwed over" by the license you chose. I am only aware of one of the scenarios you mention actually happening (packaging errors), and it is something that CKAN makes every attempt to fix as soon as we are made aware of it (because CKAN contributors care about CKAN users).
  19. politas
    It's about the contents of the mod, not the name. As an example, Ferram is pretty down on CKAN, and would rather it wasn't listed there. But FAR has something like 20 authors when you add in all the contributions. Ferram may be the main author, but he can't simply relicense FAR as ARR, because he didn't write it all, so he doesn't own it all. And plenty of mods are in the same situation. People in the forums offer up ModuleManager scripts or slightly tweaked models and scripts, and as soon as the original author includes any of those into their mod, it's stuck with the open source license they started with. That's the reality of open source licences, and it's their great strength, for everyone except the original author.
  20. politas
    (Assuming of course, that you are the author of every bit. If you have included material provided by other authors, that is no longer possible.)
  21. politas
    Or if the listing in some other way breaches the mod's license. A derivative of a No Derivatives CC license, for example, or no attribution.
  22. politas
    I'm sorry that I couldn't give a simpler answer, but I gave a precise answer. It depends on the license.
  23. politas
    And the answer is, if the license the mod author chose gives them that right, then yes. If a mod author chooses to use a Free / Open Source license, then they have irrevocably relinquished some rights. That's the promise they make to their users when they use those licenses. It's also the arrangement under which they accept assistance from others to add to and help build their mod, which stops the mods from being entirely "theirs" from a legal perspective.
  24. politas
    Well, the licence you've used allows forks, but since attribution is required, I don't see what you mean by "hostile" forks. They would have to be labelled as forks, and people could choose whether to use the fork or continue using your originals. Is this something you're particularly concerned about? CKAN is downloading all your mods from github, and even if someone were to load them up to Spaceport (and I've never heard of anyone doing such a thing), we would be unlikely to switch over from github.
  25. politas
    Sorry to take so long replying; I've been out of town. Yes, that would work just fine. The .version file needs to be in a folder that will be instaled, as the SurfaceExperimentPackage folder would be in the layout you specified. Github has a mechanism for doing releases that CKAN understands, and CKAN will only add a full release, not a pre-release, so you can create beta releases for people to test out new features before they are offered to the general CKAN public.
×
×
  • Create New...