Project Statement

About Us

Huntsville Hobby Network is an open project started and maintained by Greggory L., who is a US licensed ham radio hobbyist with a passion for weather photography. The project started as a small idea of having some kind of portable kit that could easily be transported from site to site and capture pictures, all while being remotely accessed using off-the-shelf wifi radio gear. Now, seeing what is possible with this project, it has kinda turned into a much bigger project that aims to offer the weather camera’s photography abilities as a service to the town.

Why The Name

Simple really, the project is based in Huntsville and aims to provide access to weather imagery and research data services to the people of Huntsville.

Are You “Organized”

No, currently the Huntsville Hobby Network is not an organized entity and we do not plan on becoming one. Everything we do is done out of our own pockets and everything is non-commercial. All services provided by the project are done so without cost to any end users. Anyone can step up and propose an idea to the project staff, anyone can offer to add equipment to the project, and anyone can step up to maintain a certain part of the project. The project is driven by those who wish to make it work. Simple as that.

What About Membership

Well, the project is an open platform so to speak. Anyone can join simply by having the correct radio gear to access the network. There are no membership fees because there is no entity so to say. We are just a group of hobbyist doing what we enjoy. The only roster that we have is our registry, which simply allows folks to see who has what devices registered to avoid network conflicts.

Okay, How Do You Govern the Project

The governing body is made up of five people currently. Greggory L. (Ghericoan) is the project chair; providing oversight and upkeep for the equipment officially deployed by the project itself; Drew B. (SkullyDog) is the Public Relations Officer, maintaining public relations with members of the public who have an interest in the project and helps guide the project as it grows and matures. Cheyenne C. (Eli) is the media director; she collects the weather imagery and chooses how to compile them and display them on our website. We currently do not have a project secretary, seeing as our previous board member has been removed from the project for inactivity and radio silence. Aaron D. (ZeMajorNeko) is our ground worker. He handles any loose ends in the project that haven’t been taken care of by other project members, as well as helps deploy field radios and align them. (To those reading this, we are not a registered entity, and as such we do not touch any currency, the terms used above simply describe each person’s role in the project.)

Currently minor changes within each person’s department do not need to be voted upon. Major changes that will impact the project as a whole require a meeting and sixty percent vote to pass. Bringing on new staff will also require a meeting to speak with the applicant and a vote to add them will require sixty percent vote to pass.

The founding members cannot be voted out of the project. However, if a non-founder staff member is causing issues and discontent within the project, a sixty percent vote must occur to vote said member out.

Upgrades or changes to the project’s research network, such as but not limited to things like new access points or increased bandwidth handling, will require an open meeting hosted on our website. Open meetings will allow comments from network users and project staff, as well as hold a vote for proposed changes. Open meetings hosted on our website must remain open for no less than five days.

Meetings

Meetings are to be hosted on the project’s website, https://info.barkshark.net at least once a month to allow for feedback from network users, feedback from project staff, and to propose changes to the project if any are brought to the project’s attention. Meetings can be used to create, alter or remove project bylaws. Approve or deny the addition of project staff. Remove project staff if they are causing discontent. Discuss adding new hardware to the project’s official solution. Things outside the scope presented above should be discussed via email with the project staff. Meeting minutes will require at least a sixty percent vote to pass.

Meetings that create new bylaws, alter existing bylaws, or remove existing bylaws must be openly conducted on the project’s website and the meeting must be open for no less than five days. Bylaw changes will require at least a sixty percent vote to pass.

Dissolution Clause

All projects eventually come to an end. Our project is no different in this regard, which is why we have taken time to outline what will happen when our time comes.
In the event that our project reaches its end of life, we will make an announcement on the website alerting our users of such events and proceed to freeze the website in its current state for six months, after which the website will be brought offline.

Project staff will be asked to retrieve any equipment that they have lent to the project and the project’s official gear will be returned to storage. Any data that was collected by the project will be promptly destroyed. Memory cards are to be overwritten using a Linux machine by using the DD binary with an input device of /dev/urandom. Hard disk are to be formatted and then overwritten using a Linux machine by using the DD binary with an input device of /dev/urandom. All project paperwork is to be filed away for future reference. Once the above operations have been complete, the project is to be considered defunct.