- handbook
- Company
- Company
-
- Board & Investors
- Communications
- Decision making and project management
- Guides
- Organizational Structure
- principles
- Remote Work
- Security
-
- Access Control Policy
- AI Development and Customer Data Policy
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Cryptography Policy
- Data Management Policy
- Hardware Security Policy
- Human Resources Security Policy
- Incident Response Plan
- Information Security Policy and Acceptable Use Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Secure Development Policy
- Third-Party Risk Management Policy
- strategy
- values
- Operations
- Engineering & Design Practices
- Design
- Engineering
- Internal Operations
- People Ops
- Marketing department
- Marketing
- Sales department
- Sales
-
- Commercial Organization
- Customer Success
- Edge Connectivity Sales Process
- Engagements & Pricing
- Forecast Review
- Hubspot
- Legal
- operating-principles
- Partnerships
- Processes
- Professional Services
- Sales Compensation Plan
- Sales Meetings
- Sales Regions
- Self Hosted Dashboard v2 Multi User
- Subscription Agreement 1.5
Node-RED is FlowFuse
We strongly encourage the belief that the Node-RED and FlowFuse communities are the same. Whether you are a FlowFuse community member or an employee, you should treat both community members equally. Remember, the success of FlowFuse lies in the success of Node-RED.
General Guidelines
We recommend reading the Contributor Covenant Code of Conduct to help ensure that our community remains respectful, collaborative, and supportive. These principles are grounded in common sense and shared values. By adhering to them, we can create a welcoming environment for all members and foster a culture of mutual respect and growth.
Community interactions.
As an employee of FlowFuse, when we interact with the OSS Node-RED community we must be mindful of our position. For example, when offering advice on the Node-RED forum or the Node-RED slack, the first answer we offer should be how a solution can be achieved using Node-RED. If a native Node-RED solution is not possible or the user would benefit from the advantages that FlowFuse offers, then, like any other person or company, we can offer FlowFuse as a potential solution.
