Hmong Software SandBox

Experimental & Highly Unstable

About the HSS Team

The HSS team members are made up of highly-skilled software developers and language experts in their respective fields. The entire team is made up of volunteers who enjoys simple, social networking, to help each other learn and explore new technologies as it relates to improving the Hmong community. No one is in charge, and no one gets paid for their codes or time.

Although the team and projects are done on a volunteer basis, the codes developed are not open-source (unless agreed upon my the project team members) and will not be available for download. If a project arises that can be commercialized, it will be up to the team members to decide what their next steps will be.

This is the SandBox of the HSS Team. They break things that can not be broken.

stacks_image_0408DCB8-144C-4632-B01A-FB91D8C82B9E

Current Experiments

Hmong Text Reader
KuaBot
EtoHT
Learn Hmong X

We are looking for a few volunteers who are seasoned developers (web technologies - especially PHP and JavaSctipt) who are also fluent in Hmong. If you can read and write Hmong and have advanced programming skills, join us! Send us your resumes or show us some samples of your work. You get no pay, but you will feel happy because you will be doing highly experimental stuff - for the Hmong community.

A SandBox

http://en.wikipedia.org/wiki/Sandbox

A sandbox is a testing environment that isolates untested code changes and outright experimentation from the production environment or repository, in the context of software development including Web development and revision control.

Sandboxing protects "live" servers and their data, vetted source code distributions, and other collections of code, data and/or content, proprietary or public, from changes that could be damaging (regardless of the intent of the author of those changes) to a mission-critical system or which could simply be difficult to revert. Sandboxes replicate at least the minimal functionality needed to accurately test the programs or other code under development (e.g. usage of the same environment variables as, or access to an identical database to that used by, the stable prior implementation intended to be modified; there are many other possibilities, as the specific functionality needs vary widely with the nature of the code and the application[s] for which it is intended.)

So they say... ;-)