-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New name for go-ftw #312
Comments
For what it's worth, I think the current name is fine and I've always known what FTW stood for (it's stated on the first line on the front page / readme file of both go-ftw and the original ftw. I wasn't aware this was unknown / an issue. If someone will not read the first line of your project then that's a them problem, not a you problem 😛) But, always happy to make alternative name suggestions 😀 Of the suggestions so far:
waferWeb Application Firewall EvaluatoR Web Application Firewall Evaluation Routine Web Application Firewall Evaluation Runner 😀 ( Web Application Firewall Evaluation Runtime Web Application Firewall ExerciseR 😅 Web Application Firewall Exercise Routine Web Application Firewall Evaluating Robot 🤖 aftApplication Firewall Tester afterApplication Firewall TestER taftThe Application Firewall Tester rafter(The) Reliable Application Firewall TestER 😅 lafterLayer 7 Application Firewall TestER |
These are great, thanks! I had |
raftReal Application Firewall Tester |
Yeah, unfortunately, |
Let me add adding my two cents:
|
Waf Testing Helper: |
Please pronounce phonetically. |
|
|
Still not convinced a new name is needed or necessarily a good idea, but if we just want a new short command to type that isn't 'ftw', and we want to distinguish the old ftw from the "new" ftw, how about: nftwNew FTW / New Framework for Testing WAFs "Not FTW" "Next FTW" Or keep it ambiguous, and the "n" doesn't officially stand for anything: "n" FTW / "n" Framework for Testing WAFs |
We have been thinking about renaming the project. The name
go-ftw
was a quick win to replace the retiredftw
.Our reasons to rename the project are:
go
prefix isn't meaningful to users in any wayftw
is not obvious (it is "framework for testing WAFs")Candidates
Legend:
waft 🚫
Meaning: "WAF tester"
Pros:
Cons:
westy
Meaning: "Web Server Test utilitY"
Pros:
Cons:
waffles, waflz, etc. 🚫
Cons:
wtf
Meaning: "WAF testing framework"
Cons:
The text was updated successfully, but these errors were encountered: