Skip to content
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.

CLI-WG project description #4

Merged
merged 1 commit into from Apr 4, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Binary file added static/ferris.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/kevin.jpeg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/kevin.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
14 changes: 14 additions & 0 deletions templates/projects.hbs
Expand Up @@ -78,4 +78,18 @@
</div>
</div>
</div>
<div class="project">
<div class="row">
<div class="description">
<h3>clap-rs</h3>
<p><a href="http://clap.rs/">clap</a> is a fast and configurable argument parsing library for Rust. It is the de-facto standard in the crates ecosystem for handling provided arguments when creating commandline applications. </p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it would be great to add 2 sentences in a paragraph between the description of clap and kevin's bio that states something to the effect of:

  1. good candidates for this project would be people who are excited about learning about.... something something
  2. participants in the project will <briefly describe 1-4 things they'll do>

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not super great talking about myself, but something like:

  1. good candidates for this project would be people who are excited about learning about building robust CLI applications with all the modern niceties and improving CLI UX

For 2, forgive me if I'm catching up late, but do we need to already have a good project for them to build? If no, here is a generic statement I'd use:

  1. participants in the project will focus on CLI design including detailed UX, building robust CLI applications in Rust while avoiding common mistakes and performance pitfalls, learn how to structure a CLI application to as to be maintainable and extensible, and finally learn common considerations when packaging and distributing an application.

If we need an actual project in mind, I'd need to think of one (and I have a few ideas off the top of my head) 😜

Also, here's what I sent to @spacekookie recently:

Kevin is the creator of clap and a member of the CLI Working Group. He is fascinated by all things command line and passionate about building, and teaching others how to build a command line world with better UX and more consistency.

Along with this image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you have an actual project in mind i can tell u from looking at the applications we've already gotten that people really love the more specific projects :) but it's not necessary- really up to you!

<p>Candidates for this project should bring an interest and fascination with the building of commandline interfaces and UX design. They will dive deep into the process of creating CLIs, avoiding common performance and stability pitfalls and creating maintanable and easily distributable tools.</p>
<p>Kevin is the creator of <a href="http://clap.rs/">clap</a> and a member of the CLI Working Group. He is fascinated by all things command line and passionate about building, and teaching others how to build a command line world with better UX and more consistency.</p>
</div>
<div class="partner">
<img src="static/kevin.png"/>
<h4>Kevin Knapp</h4>
</div>
</div>
</div>
</section>