Moving tufup development to an organization account

[JessicaTegner]

hi @dennisvang

Since we now have this main repo, and the tufup-example repo, would it make sense to move all tufup related stuff to an organization?
Thinking down the line, if we also will have documentation, plugins (like uploaders), or other things.

Thinking like this, to try to future proof this, in the case that you move away from python, or something else happens.

What's your thoughts on this.

[dennisvang]

[...] would it make sense to move all tufup related stuff to an organization?

Hi @JessicaTegner, that's an excellent idea! :)

What do you think, should we just call the organization tufup as well?

[JessicaTegner]

Hi @dennisvang
yes I do think that "tufup" would be a fitting name for it, since that's the main project name. Then from there we can have

• tufup/tufup - Main repo
• tufup/example - example repo.
• tufup/*-plugin - for any eventual plugins.

And so on.

[dennisvang]

Unfortunately it turns out the name tufup is already taken.

Thinking about an alternative name, I started wondering if it might be better to move the project under the umbrella of an existing organization, such as jazzband, or perhaps theupdateframework, if they would be willing.