Migrate package under the gohugoio GitHub organization

[XhmikosR]

@bep: what do you think about this idea? It would make the package official and you guys could also update it when needed.

[XhmikosR]

@bep: ping

[bep]

I'm a little hesitant as to this, as that would mean taking some kind of maintainership over it. A quick glance at the source and it seems it is no binary file integrity file checking in place, which makes me even more hesitant. It isn't that I don't think this is a good idea, it just isn't something I can put work into right now, which I would have to if we were to make it official.

[XhmikosR]

@bep: you can always just add @satoshun00 with the needed rights to push to the moved repo only. And he can try adding what you are asking for.

I can tell you for sure that making this official would help things. For one, someone could update it when a new release is out without us having to ask for it. Plus thousands if not more, are using npm so this is a huge plus. I have already switched to it for my personal projects and for the Bootstrap branch (which I still wait to hear from @mdo).

[XhmikosR]

OK, we need a way to make the project move faster when there's a new version out. @bep: are you still opposed to moving the project under the gohugo org? This could allow you for example handle members, or publish the release yourself.

Unfortunately, with the current implementation, we can't check the hash beforehand, see #36.

I personally offer to handle any updates since we are going to use this ourselves.

[bep]

@bep: are you still opposed to moving the project under the gohugo org?

Yes.

[XhmikosR]

That's too bad, but OK. You could just update it via a script when you make a new release or something.

[satoshun00]

How about a crawler who check Hugo releases at a certain interval?
https://docs.travis-ci.com/user/cron-jobs/

[XhmikosR]

I think the problem here is that we don't check the checksum. And with the current tools, that's not possible...