Plugin packaging about oh-my-fish

[rominf]

Of course, README.md should contain only description. I'm against copy-pasing text like:

to install write:
...
to uninstall write:
...

I think that:

For more information on `oh-my-fish` visit ...

would be enough. This text is easy to append automatically by script to all plugins.

[derekstavis]

I'd prefer using git tags instead of branches, this way plugins can be versioned using semver.

[derekstavis]

But I definitely like omf info command and your proposed output!!

[rominf]

I'd prefer using git tags instead of branches, this way plugins can be versioned using semver.

You are right. I meant tags, not branches. I'll fix it.

[bpinto]

I believe I didn't understand the proposal for the README file. Could you try explaining again?

[rominf]

@bpinto
Well. Printing markdown to a console output is not a very good idea.

I actually vote for self-documented code, so I think that after implementation of fish-shell/fish-shell#478 we can just simply build README files from the help. So, for now, I would leave README files as they are.

BTW, it's possible to extract repository description from .git/description file.

I've changed proposal again.

[bpinto]

I can see this working as it was proposed, might be interesting to see what current plugins would output.

[jeremiejig]

See also git describe to generate a version, which relies on annotated tag.

[derekstavis]

I usually use git describe --tags --always HEAD

[bpinto]

@rominf are you working on a PR for this?

[rominf]

@bpinto, no.

[sagebind]

This will be marked as solved as part of the effort in #427.

[sagebind]

#427 is merged. Packages can now be grouped, be more discoverable, and have metadata using the new package repository system built on top of Git. Closing as solved.