HaMakor: Supporting Free Software and Open Source in Israel
The association, the communities around it and the practical work that helps independent activity continue.
עברית
An organization behind community activity
HaMakor describes itself as an Israeli nonprofit society for free software and open-source code. Founded in 2003, it provides an organizational umbrella for activity that can otherwise be spread among informal groups and individuals. That role is different from developing one particular application or representing one programming language.
The distinction is useful when looking at a technical community. A group can exchange ideas without being a formal organization. Once activity involves venues, expenses and continuity, an organizational framework can help people coordinate responsibilities. This is a general explanation of why such a framework matters, rather than a promise that every proposed project receives a particular service.
Free software includes more than the Linux desktop
A community concerned with software freedom can include administrators, application developers, translators, educators and people who improve documentation. They may use different operating systems and work on different projects. The shared question is how people can understand, maintain and contribute to the software they depend on.
This broader view helps avoid reducing participation to a contest over a favorite distribution. A translated interface or an accessible installation guide can remove a barrier that a technically impressive new feature leaves untouched. Community work becomes more useful when it responds to the actual difficulty another person is facing.
August Penguin and meeting across project boundaries
HaMakor identifies August Penguin as its annual community conference. A shared gathering gives people from different projects an opportunity to meet beyond the boundaries of their usual technical group. Its role in this article is to show that an organization can support a place for exchange as well as a particular development activity.
For someone who usually works alone, meeting other maintainers can make a problem easier to describe. A conversation may lead to a documentation improvement, a testing partner or a useful contact for a later question. Those outcomes cannot be guaranteed by attending a conference, but they explain why an in-person community event can have value beyond its list of talks.
A directory that shows the range of communities
The official community directory includes Python activity and groups such as Ma’akaf, Baot and Hackeriot, alongside communities connected to other languages. The directory links people to the relevant groups rather than suggesting that everyone follows one programme. It is a practical starting point for finding the community responsible for a subject.
A directory should be read as a route to the group’s own information. Check the linked page for participation details and for the format of a specific event. Different groups can have different purposes, audiences and ways of organizing work. Treating them as distinct communities respects the people who maintain them and helps a newcomer find a suitable place to begin.
The connection with Python in Israel
HaMakor’s overview explicitly includes the PyCon Israel team among the groups working under its auspices. The directory also points to the wider Python community resources. This provides a concrete link between a language community and a nonprofit organization without making the two the same thing.
Our companion article about Python in Israel looks more closely at PyWeb-IL, PyData Tel Aviv and PyCon. The two articles can be read together: one concerns where technical knowledge is exchanged, while the other concerns an organizational setting that can support community activity. A person may contribute to a technical group without every contribution becoming a project of the association.
Contribution and continuity
Before offering help, identify a concrete task and the people responsible for it. Improving a page, testing instructions or documenting an event can be a manageable first contribution. Explain what you intend to change and leave the result in a form another person can review. Small completed tasks are often easier to maintain than ambitious plans with no clear owner.
Continuity also depends on preserving knowledge. Record why an exception exists, how a recurring task is performed and where the next authorized volunteer can find the necessary information. Do not put passwords or private participant information into public documentation. The goal is to make the work understandable without exposing information that does not belong in the open.
Finding the right point of contact
Use HaMakor’s official overview and community directory to decide whether a question belongs with a particular group or with the association. The overview provides contact information for the board. A useful first message names the subject, describes the request and explains what kind of help or coordination you are seeking.
TUX Network Israel presents these links as an independent community resource. This article does not claim that the blog is a member, a sponsored project or an official representative of HaMakor. Clear attribution lets readers learn about the association while keeping the responsibilities of the different projects understandable.