AllAccepted answers
Evgeny Shvarov · Mar 26, 2020

And another way to win - to have clear instructions.

Often fantastic applications with bad instructions can loose to poor applications with perfect instructions.

Please make sure that the instructions you have in your README.md really work.

It is always helpful to try to go through your instruction steps by yourself before releasing the application. Or and ask your colleague to do it.

Good luck!

Evgeny Shvarov · Mar 25, 2020

Another thing you may want to add to your OEX and Github README.md - is the Online Contest Github shield!

Here is how it looks like:

Here is the code you can install into your Github README.md

[![Gitter](https://img.shields.io/static/v1?label=Vote%20for%20my%20App&message=InterSystems%20IRIS%20Contest&labelColor=%23333695&color=%2300b2a9)](https://openexchange.intersystems.com/contest/current)

Learn more about Github Shields

Evgeny Shvarov · Mar 24, 2020

Thanks, Dmitriy!

Analysing database, If you mean this:

docker run -it --rm \        -v /opt/some/database/for/test:/db \        -v pwd/out:/out \        daimor/blocksexplorer:iris generate 1 0 0

so this doesn't look very convenient.

Is it possible for me to install your app on a running container (e.g. with ZPM) and request to check one of the mounted databases? This is a more convenient approach, isn't it?

Evgeny Shvarov · Mar 24, 2020

This is a very good question, Ed!

Yes, when you launch a vanilla IRIS CE on docker you have USER namespace and database already. 

But what is the web app? is it REST? do you need the web app at all? 

The infrastructure-as-a-code approach, when the namespace, database, web app, security, BI or Interoperability options, etc is being setup via docker/workflow deployment has the following advantages.

1. Clear understanding, what infrastructure is needed for your app to run on the dev/deployment lifecycle

2. You have the control for the infrastructure - you do not expect USER namespace present or have this or that, you simply set up all your app needs.

3. All the changes to infrastructure are in the repo and you track it.

Evgeny Shvarov · Mar 24, 2020

Ok!

After the first day of the voting we have:

Expert Nomination, Top 3

  1. BlocksExplorer  - 2 
  2. IDP DV - 1
  3. sql-builder - 1

______________

The leaderboard.

Community Nomination, Top 3

  1. sql-builder - 6
  2. isc-generate-db - 4
  3. declarative-objectscript - 3

______________

The leaderboard.

Developers! Support the applications you like!

Participants! Improve and promote your solutions!

Evgeny Shvarov · Mar 24, 2020

Hi Oliver!

It was an issue in %Installer - the Import statement

<Import File="${SourceDir}" Flags="ck" Recurse="1"/>

was inside the Configuration tag started import before Interoperability (Ensemble) enabled in Namespace.

I put it below the configuration and it works.

Thanks @Dmitry Maslennikov for your help.

I sent you a pull request with the fix.

Evgeny Shvarov · Mar 23, 2020

How to test 

According to the requirements, developers should use Docker version of InterSystems IRIS Community edition or InterSystems IRIS Community Edition for Health. 

So every solution could be launched as:

$ git clone https://github.com/repository
$ cd repository
$ docker-compose up -d
$ docker-compose exec iris iris session iris

And then you'll see the IRIS Terminal where you can follow the application instruction to test its functionality.

Winner criteria
Choose the application you like most. But the general criteria are:

  1. Idea and value - the app makes the world a better place or makes the life of a developer better at least;
  2. Functionality and usability - how well and how much the application/library does;
  3. The beauty of code - has a readable and qualitative ObjectScript code.

The post is updated accordingly.