Release a first version

[wetneb]

People should not have to compile the extension themselves: let them just download it by releasing a first version.

[trnstlntk]

I created a draft for the release. Can anyone besides me see this and help me check if I didn't forget anything? @wetneb 👀 ? https://github.com/OpenRefine/CommonsExtension/releases

[wetneb]

Looks great!

This extension will also install the Wikimedia Commons manifest and the Wikimedia Commons reconciliation service by default.

For now that's done by OpenRefine itself already (more precisely the Wikibase extension)… maybe it would make sense to move it here though?

[wetneb]

Congrats for publishing it! It looks like you did not attach the actual zip file that you generated with mvn package. The two archives that are on the release are those that GitHub generates itself, and those only contain the source code (users will not be able to install the extension by downloading those). You should be able to edit the release and add the zip file.

[trnstlntk]

@wetneb I hope I did everything right (not the best idea to do it on a Friday evening with a headache). I found the tagging a bit challenging, I did it inside GitHub Desktop using these instructions as I've only used Git on the command line once (a year ago). I tried unzipping the file before adding it to the release and loading it as a proper extension in OpenRefine 3.6.2 and it seems to work fine on my end.

I guess I have two questions that are more related to user-friendliness of naming of things:

• The zipfile is automatically named openrefine-commons.zip - can this safely be renamed to a more descriptive filename?
• When unzipped, it unzips as a folder named module which I also find vague and not very reassuring. Can this also be renamed somewhere so that it's clearer for the user that they indeed have the Commons extension here?

[wetneb]

The zipfile is automatically named openrefine-commons.zip - can this safely be renamed to a more descriptive filename?

It can! It would be good to have the version number in there, too.

When unzipped, it unzips as a folder named module which I also find vague and not very reassuring. Can this also be renamed somewhere so that it's clearer for the user that they indeed have the Commons extension here?

Definitely! I think it can be safely renamed.

Both of those things could be fixed in the build system, so you don't have to do it yourself at every release, so worth opening an issue for it.