Add a field about the type of access to an appliance

[julien-duponchelle]

A field with the information:

• this appliance is free to download
• this appliance require a free user account
• this appliance require a trial key
• this appliance require a paid support

I don't know how exactly we should call this field but in order to improve the marketplace on gns3.com ( https://gns3.com/discussions/request-for-organizing-the-appli) or the appliance wizard.

[adosztal]

I'd avoid "license" as it might lead to confusions. How about "availability" or "image-availability"?

[julien-duponchelle]

Availability sound like a good idea.

[adosztal]

Something like this?

    "availability": {
      "enum": ["free", "with-registration", "free-to-try", "service-contract"],
      "title": "About image availability: can be downloaded directly; download requires a free registration; paid but a trial version (time or feature limited) is available; not available publicly"
    },

[julien-duponchelle]

Seem good. What do you think @grossmj ?

[adosztal]

After agreeing on the format, I can make a branch for the updated appliance.json and .gns3a files.

[adosztal]

Here's the suggested solution: https://github.com/adosztal/gns3-registry/commit/2d8c1d4f47ff4e2e384a04761947f0f1340456e3 Keep it / change it / drop it?

[julien-duponchelle]

I just revert the merge because it's break current GNS3 release:

I need to check how we can relax that

[julien-duponchelle]

For me it's sound good and if we want to change we can script the modification.

On Thu, Oct 27, 2016 at 12:06 PM Andras Dosztal [email protected] wrote:

Here's the suggested solution: adosztal@2d8c1d4 https://github.com/adosztal/gns3-registry/commit/2d8c1d4f47ff4e2e384a04761947f0f1340456e3 Keep it / change it / drop it?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-registry/issues/165#issuecomment-256600987, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVFXWsvmUnOtUYa79wrbtkbYLoy-9HPks5q4HeigaJpZM4KedCe .

[grossmj]

This is good, let's use availability.

On Tue, Oct 25, 2016, 23:23 Andras Dosztal [email protected] wrote:

After agreeing on the format, I can make a branch for the updated appliance.json and .gns3a files.

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-registry/issues/165#issuecomment-256294433, or mute the thread https://github.com/notifications/unsubscribe-auth/AEiE5vpLY0D4ANt9biIEzUB9IYix4dj2ks5q3xwDgaJpZM4KedCe .

[adosztal]

@noplay, what if I

• revert my master branch too;
• create a PR for my "availability" branch;
• keep the version updates synchronized between the two branches?

This way you can merge the "availability" branch at a time convenient for you, after fixing the current release.

[julien-duponchelle]

Sound good to me

[adosztal]

Done. Btw, I scripted the modification with this small one. :)

[julien-duponchelle]

Need to wait 1.5.3 before changing appliances files

[adosztal]

That branch conflict appears every time I start committing changes to both. I'll keep the registry v4 files on a local drive; please drop a message here when I can commit them to my master branch, then I'll make the PR. You can delete this one too.

[julien-duponchelle]

I move this to 2.1 because for the moment we need to wait everyone upgrade to compatible client before changing that

[adosztal]

No problem, I'll keep the files updated.

[julien-duponchelle]

Thanks a lot for the help

[julien-duponchelle]

Ok 1.5.3 is shipped we can change the registry now

[julien-duponchelle]

1.5 still create trouble with that... Until user migrate to 2.0 we can't modify the appliances ....

[grossmj]

We will update the appliance files once we release version GNS3 version 2.2

[adosztal]

Ping me before the release and I'll update every appliance.

[grossmj]

This has been implement a while ago ;)