<div dir="ltr">Hi<div><br></div><div>Aerogear team is looking for name for our jenkins node.js client.</div><div>Names are important to avoid confusion between different generations of the build farm</div><div>and also to simplify documentation etc.</div><div><b><br></b></div><div><b><font size="4">My recommendation:</font></b></div><div>- Keep simple name and use it (or parts of it) as repo name, npm package name, executable name, project name or in documentation etc. to avoid confusion</div><div>- Avoid '-', '_' characters in executable name (this is mostly command line client)</div><div><br></div><div><b><font size="4">Suggestions:</font></b></div><div><b>digkins-node</b> for repository name</div><div><b>digkins</b> as executable name</div><div><br></div><div>Use digkins everywhere needed to denote that this would mean "node.js command line client"</div><div><b><br></b></div><div><b><font size="4">What we have at the moment</font></b></div><div><br><b>Repo</b>: <a href="https://github.com/aerogear/digger-node">https://github.com/aerogear/digger-node</a></div><div><br></div><div>It's not denoting in the name that we talking here about new version of the digger so better to change it or add some number etc.</div><div><br></div><div><b>Executable</b>: digkins (digger + jenkins) <br clear="all"><div><br></div><div>PS: Please check if name is available on npm</div><div><br></div><div> Sprint :P</div>-- <br><div class="gmail_signature"><div dir="ltr"><div dir="ltr"><div style="font-size:12.8px"><span style="color:rgb(153,153,153);font-size:small">Wojciech Trocki</span></div><div><div><div style="font-size:small"><br></div><div style="font-size:small"><img src="cid:1deff70600823b9ebf187fa9e94df6ff10966d4e@zimbra"></div></div></div></div></div></div>
</div></div>