FlyWire Principles

By the use of, you agree to be bound by these Principles and by the website Terms of Service.

Community principles

Openness. All results of proofreading are immediately available to all members of the FlyWire community. All researchers in fly neurobiology laboratories are welcome to apply.

Fairness. Before using previously unpublished reconstructions in a presentation or scientific publication, users must obtain agreement from every principal investigator whose lab identified those neurons or contributed more than 10% of the edits on those reconstructions. This applies to FlyWire neurons themselves and also to the use of FlyWire data for any purpose. (For example, this applies to neurons reconstructed in other EM software platforms using FlyWire data for guidance.) When contacting FlyWire users to seek their agreement for the use of neurons they contributed to, a lack of response within one month may be taken as agreement. Contributors may request co-authorship or acknowledgments, or may agree to share their work freely. The directors of FlyWire may provide arbitration but encourage early and active collaboration between users to prevent disputes.

Communication. Labs are encouraged to communicate with each other through chat, email, and other channels. Coordination of reconstruction and analysis activities will increase the pace of discovery. Members may not share information with any individual who has not been granted access or agreed to these Principles. All active members and their PIs must sign onto the FlyWire Forum frequently to check for announcements and collaborative communications from other members.

Mutual respect. We should all respect each others’ efforts to achieve the common goal of understanding the fly nervous system. Mutual respect fosters a win-win situation, and generates synergy that lifts everybody up.

Design principles

Wikipedia-style crowd wisdom. Anyone is permitted to edit anything. We believe this approach will yield accuracy, once we find the appropriate checks and balances.

Social before technological solutions. Prototyping of workflows should focus on getting the human element correct, using “low-tech” means like Google Docs and Sheets for coordination. Later on, workflows will be implemented by the engineering team as integrated features of the FlyWire site.

Cultural norms over formal laws. The FlyWire community should establish a good culture from the outset. Formal laws will be introduced when necessary but ideally will be kept to a minimum.