Decide on a project name

[atc0005]

Currently we're using ezproxy-blockuser as the shortname with atc0005/ezproxy-blockuser as the fully-qualified project name.

Before flipping this repo public I plan to:

1. Have something worth sharing (working prototype)
2. Add any required and/or suggested trademark notices to make clear this isn't an official project of the EZproxy developers, OCLC and that there is no association between this project and their services/products (aside from complimenting EZproxy server usage)

While there is definitely a strong benefit from associating this application's purpose with EZproxy, this application stands to have a much broader use than that one application. It is probably worth going with a more generic name, both to avoid any unintentional association (with its obvious legal ramifications) and mind-share "lock-in" that could result in having the vendor's product be in this project's name.

As an example of the potential generic nature of this app, let's go with the assumption that we use templates for generating the output flat-file. Using templates,, we could have one template for EZproxy format, another template for another format and so on. This is on top of the support planned for #9 where a user can be added to a LDAP group (which any number of apps could use for their logic/decision making).

The end results is that we achieve our original goal of automatically blocking problematic EZproxy user accounts, but that we also have a project name that doesn't lock us into only that one function.

[atc0005]

Not sure if I mentioned it yet, but a short name is preferable, ideally one word only.

---

First idea: brick

• brick wall
  • tends to put a stop to further progress
  • or, builds things up (e.g., adding user to a LDAP group)

Second idea: block

• same "building block" association
• "road block"
• "block user"

[atc0005]

First idea: brick

Going with this if for no other reason than it gets things moving.