Welcome to the HubDirectory
HubBucket Health Information Technology and Medical Technology Project Directory
We're Building the Future of Data-Driven Healthcare with Open Source Technology
Artificial Intelligence - AI | Machine Learning | Deep Learning | Models and Algorithms | Cloud Computing | Edge Computing | Fog Computing | Serverless Computing | Mesh Computing | Application Programming Interface - APIs | Virtualization Technology | Containers | Big Data Technology | Analytics | Analysis | Informatics | Bioinformatics | Clinical Informatics | Data Visualization | Data Mining | Data Modeling | Data Science | Health Informtion Technology - HealthIT/HIT | Health Technology - HealthTech | Medical Technology - MedTech | Mobile Health Technology - mHealth | Telemedicine / Telehealth | Medical Imaging Technology | Wearable Health Technology | Medical Sesnsors | Healthcare Sensors | Biomedical Sensors | Medical Research Technology | Health Information Exchange | Real-Time Data Streaming Technology | Real-Time Data Analytics | Real-Time Data Analysis | Digitial Twin Technology | Robotic Process Automation - RPA | Automation Technology | and more ...
HubBucket Healthcare Technology Project Directory ("HubDirectory").
Here you can learn about the various projects that we have underway, in addition to the technology being used in the projects. The vast majority of projects use Open Source technology. We also use a wide variety of Cloud-based services from various Cloud Service Providers - CSPs.
HubBucket Healthcare Technology projects, products, and services are compliant with:
- The Health Insurance Portability and Accountability Act - HIPAA
- The Health Information Technology for Economic and Clinical Health Act - HITECH
- The Patient Protection and Affordable Care Act - ACA
- The General Data Protection Regulation - GDPR
- The California Consumer Privacy Act - CCPA
- The New York State Data Privacy Act - NYSDPA
- Fast Healthcare Interoperability Resources - FHIR standards
- Other U.S. and International Healthcare Data Privacy / Protection Laws, Regulations and Standards
The HubBucket Incubator
In order for new projects to be created, HubBucket has modeled The Apache Software Foundation ("The ASF") "Incubator." However, the HubBucket Incubator is for internal projects and for the external Open Source projects we participate in.
Since the Meritocratic rules operate across HubBucket from bottom to top, it is vital for the long-term stability of such a form of government, that the initial set of committers has to know very well the dynamics of such a system, as well as share the same philosophical attitude toward collaboration and openness that HubBucket expects from its projects.
The HubBucket Incubator is responsible for:
- filtering the proposals about the creation of a new project or sub-project
- help the creation of the project and the infrastructure that it needs to operate
- supervise and mentor the incubated community in order for them to reach an Open Meritocratic environment
- evaluate the maturity of the incubated project, either promoting it to official project/ sub-project status or by retiring it, in case of failure.
It must be noted that the HubBucket Incubator (just like the board) does not perform filtering on the basis of technical issues. This is because the HubBucket executive branch respects and suggests a variety of technical approaches. It doesn't fear innovation or even internal confrontation between projects which overlap in functionality.
The HubBucket Incubator filters projects on the basis of the likeliness of them becoming successful Meritocratic Communities.
The basic requirements for HubBucket Incubation are:
a working codebase -- The ASF discovered that over the years and after several of their failures, the foundation came to understand that without an initial working codebase, it is generally hard to bootstrap a community. This is because merit is not well recognized by developers without a working codebase. Also, the friction that is developed during the initial design stage is likely to fragment the community. The lesson learned by The ASF is something we have incorporated into the HubBucket Incubation process.
the intention to assign sufficient intellectual property rights to the software to HubBucket -- this allows the HubBucket to obtain an irrevocable and permanent right to redistribute and work on the code, without fearing lock-in for itself or for its users, while still allowing the original author to maintain their copyright.
a sponsoring HubBucket member or officer -- this person will act as the main mentor, giving directions to the project, helping out in the day-to-day details and keeping contact with the incubator PMC.
The HubBucket Incubation period normally serves to estimate whether or not the project is able to increase the diversity of its committer base and to play with the Meritocratic rules of HubBucket.
It might seem rather easy to achieve, but it must be remembered that in a volunteer and highly selective environment, attracting new committers is not automatic.
Diversity and Inclusion of committers are important for two main reasons:
Diversity and Inclusion give long term stability to the project development: in fact, with all the developers affiliated to the same entity, the chance of seeing all of them moving away from the project at the same time is much greater than with a community of individuals affiliated to unrelated entities This gives a greater variety of technical visions: something that guarantees a better adherence to the environment and user's needs, thus a higher chance of finding real-life use of the software/technology.
When a HubBucket Project Group has analyzed and determind that a person has "earned" the merit to be part of the development community, they granted direct access to the code repository, thus increasing the group and increasing the ability of the group to develop the program, and to maintain and develop it more effectively.
Like The ASF we call this basic principle "meritocracy": literally, government by merit.
This process scales very well without creating friction, because unlike in other situations where power is a scarce and conservative resource, at HubBucket newcomers are seen as volunteers that want to help, rather than people that want to steal a position. After explaining the structure of HubBucket, we will see how the meritocracy relates to the various roles.
The HubBucket Board of Directors ("board")
The board is responsible for management and oversight of the business and affairs of the corporation in accordance with the HubBucket Bylaws. This includes management of the corporate assets (funds, intellectual property, trademarks, and support equipment) and allocation of the corporate resources to projects. However, technical decision-making authority regarding the content and direction of HubBucket projects is assigned to each respective project management committee.
The board members are elected people within HubBucket. The bylaws don't specify the number of officers that the board should have, but historically, this was the number of the first board and it has never changed. The board is elected every year.
The HubBucket Project Management Committees ("PMC")
The HubBucket Project Management Committees are established by resolution of the Board, to be responsible for the active management of one or more communities, which are also identified by resolution of the Board.
Each PMC consists of at least one HubBucket officer, who shall be designated chairperson, and may include one or more other members of HubBucket.
The chair of the PMC is appointed by the Board and is an officer of HubBucket (Vice President). The chair's primary responsibility is to the Board, and has the power to establish rules and procedures for the day to day management of the communities for which the PMC is responsible, including the composition of the PMC itself. See the the further discussion about the role of PMC chair and why chairs are officers.
The HubBucket Bylaws define a PMC and the position of chair.
The role of the PMC from a HubBucket perspectivean is an oversight. The main role of the PMC is not code and not coding - but to ensure that all legal issues are addressed, that procedure is followed, and that each and every release is the product of the community as a whole. That is key to our litigation protection mechanisms.
Secondly, the role of the PMC is to further the long term development and health of the community as a whole and to ensure that balanced and wide-scale peer review and collaboration does happen. Within HubBucket we worry about any community which centers around a few individuals who are working virtually uncontested. We believe that this is detrimental to quality, stability, and robustness of both code and long term social structures.
At HubBucket we firmly believe in hats. A person's role is the one assigned to you personally and is bestowed on you by your peers. It is not tied to your job or current employer or company.
However, those on the PMC are kept to a higher standard. As the PMC, and the chair, in particular, they are the eyes and ears of the HubBucket Board, it is you that we rely on and need to trust to provide legal oversight.
- The board has the faculty to terminate a PMC at any time by resolution.
- The HubBucket Developer Information pages have many more details of how PMCs work.
- A complete list of all HubBucket projects is also available.
- The Officers of HubBucket oversee the day-to-day affairs of the corporation.
- The officers are elected by the Board of Directors.
The Meritocracy typically has various roles within each individual HubBucket project communities:
A user is someone that uses our software/technology. They contribute to HubBucket projects by providing feedback to developers in the form of bug reports and feature suggestions. Users participate in the HubBucket community by helping other users on mailing lists and user support forums.
A developer is a user who contributes to a project in the form of code or documentation. They take extra steps to participate in a project, are active on the developer mailing list, participate in discussions, provide patches, documentation, suggestions, and criticism. Developers are also known as contributors.
A committer is a developer that was given write access to the code repository and has a signed Contributor License Agreement (CLA) on file. They have an hubbucket.xyz mail address. Not needing to depend on other people for the patches, they are actually making short-term decisions for the project. The PMC can (even tacitly) agree and approve it into permanency, or they can reject it. Remember that the PMC makes the decisions, not the individual committers.
A PMC member is a developer or a committer that was elected due to merit for the evolution of the project and demonstration of commitment. They have write access to the code repository, an hubbucket.xyz mail address, the right to vote for the community-related decisions and the right to propose an active user for committers. The PMC as a whole is the entity that controls the project, nobody else. In particular, the PMC must vote on any formal release of their project's software products.
The Chair of a Project Management Committee (PMC) is appointed by the Board from the PMC Members. The PMC as a whole is the entity that controls and leads the project. The Chair is the interface between the Board and the Project. PMC Chairs have specific duties.
A HubBucket Member is a person who was nominated by current members and elected due to merit for the evolution and progress of HubBucket. Members care for HubBucket itself. This is usually demonstrated through the roots of project-related and cross-project activities.
Legally, a member is a "shareholder" of HubBucket, Inc. ("HubBucket"), one of the owners. They have the right to elect the board, to stand as a candidate for the board election and to propose a committer for membership. They also have the right to propose a new project for incubation (we'll see later what this means). The members coordinate their activities through their mailing list and through their annual meeting.