Jump to content
Toggle sidebar
Logos
Search
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information
Editing
Community Organizing
(section)
Page
Discussion
English
Read
Edit
View history
More
Read
Edit
View history
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Hacktivation Energy === Every project has what can be called a “hacktivation energy barrier” - the amount of effort and time a newcomer must invest before they can start making meaningful contributions. Just as chemical reactions require an initial energy input to get started, potential contributors need to overcome certain barriers before they can effectively participate in the project. This includes understanding the codebase, development practices, communication channels, and community norms. The lower this hacktivation energy barrier, the more likely it is that new contributors will successfully join and remain active in the project. Projects with high hacktivation energy - for example, those with complex build processes, poor documentation, or unclear contribution guidelines - often struggle to attract and retain new contributors. Even highly motivated newcomers may become discouraged and leave if they cannot make progress after investing significant time. Successful projects actively work to reduce their hacktivation energy barrier through several key practices: maintaining clear, comprehensive documentation; providing easy-to-follow setup instructions; marking “good first issues” that are appropriate for newcomers; offering mentorship; and fostering a welcoming environment where questions are encouraged. The goal is not to eliminate all barriers - some complexity is inherent in any non-trivial project - but rather to ensure the initial effort required is proportional to the value of the contribution and that newcomers can see a clear path to making their first meaningful contribution. Core contributors should regularly examine their project through the eyes of a newcomer to identify and address unnecessary friction points that raise the hacktivation energy barrier. This might involve streamlining development setup, improving documentation, or breaking down complex tasks into more approachable pieces. Remember that what seems obvious to experienced contributors may be a significant obstacle for newcomers. <span id="the-movement-as-an-occupational-community"></span>
Summary:
Please note that all contributions to Logos may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Logos:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)