qhtcp repo still private

[cryobry]

The qhtcp repository is currently private. qhtcp-workflow is deployed on the Hartman Lab server but it is not safe to run on projects until I finish writing the existing project normalization layer. Run qhtcp-workflow --help if you're curious about CLI usage, but the complete documentation is auto-generated shdoc in the qhtcp repo's README and qhtcp-workflow is interactive by default. You can glean it from reading the raw shell file cat $(which qhtcp-workflow). I doubt anyone wants to do this so I will make an announcement when the normalization is done for more testing.

From my earlier email:

The lab's GitHub organization currently contains three repositories:

server (public): contains the lab server manuals for users and admins and many of the scripts I use for managing the server.
qhtcp (temporarily private): contains the qhtcp-workflow project and all associated Q-HTCP software and documentation.
qhtcp-data (public): contains a sample project for qhtcp-workflow development, you can ignore for now.

Eventually I'd like for this to become a collaborative project but understand that not everyone is fluent in collaborative programming yet. Luckily, GitHub makes it fairly trivial to edit documentation and other simple code and generate pull requests within the web interface without a git prerequisite. Each repository also features out-of-repository tools like wikis, threaded discussions (forum), and bug/issue trackers for collaboration outside of the code base. These are good places to share information that's too specific for a general README, personal workflows, workarounds, quick notes, code help, brainstorming and planning, etc.

These features will become more relevant once I deploy qhtcp-workflow (the new Q-HTCP front-end) on the server and open up the "qhtcp" repository for feedback and review. For now I pinned an announcement in the "server" repository that contains a little more information about the state of qhtcp-workflow and what I'm currently working on to get it safely deployed. Typically the "server" repository should be reserved for server-specific discussion/issues, but I will post updates there until the "qhtcp" repo is made public.

In the interim please familiarize yourself with the GitHub interface, and make a GitHub account if you anticipate collaborating on the code or documentation. You shouldn't need accounts to view the public repositories so I will send invites for maintainers once qhtcp-workflow is live.