How to Get Involved with Scicloj

Scicloj is a community platform for building data-science and scientific-computing tools in Clojure, and it offers four concrete entry points: following its events, using its data-science stack, joining study groups and workshops, and getting open-source mentoring. The right starting point depends on whether you want to learn, build, or contribute — newcomers who want guidance should start with mentoring and study groups, while experienced Clojurians can plug into a dev group or the tooling work directly.

What Scicloj actually is

Scicloj describes itself as "helping Clojure grow in new fields." Its work falls into four areas:

• A data science stack — tools and libraries for data-science and scientific computing in Clojure.
• Learning resources — study groups, workshops, and materials aimed in both directions: Clojurians interested in data science, and data scientists interested in Clojure.
• Dev groups — a platform for open-source dev groups to meet, collaborate, and create joint knowledge.
• Open-source mentoring — encouraging newcomers to join open-source projects and supporting them along the way.

That structure matters for getting involved: each area has a different commitment level and a different audience.

Choose your entry point

Step by step: from observer to contributor

1. Follow the events feed. Scicloj points people to its events through the Clojure Events Calendar feed. Subscribing is the lowest-effort step and tells you when study groups, workshops, or dev-group meetings are coming up.
2. Pick a learning track based on your gap. If your gap is Clojure, join a study group aimed at data scientists; if your gap is data science, work through the stack with the learning resources. The site frames both audiences explicitly, so you don't have to guess which track fits.
3. Try the stack on a small task. Take one concrete job — for example, loading a dataset and computing summary statistics — and see how far the Scicloj libraries take you. This gives you something specific to ask about in a group.
4. Ask for mentoring before you ask for a task. The mentoring program exists precisely to help newcomers join open-source projects. Use it to get oriented in a codebase rather than to cold-ask for assignments.
5. Join or form a dev group once you have context. Dev groups are where collaboration and shared knowledge happen; they work best after you understand the tools and have a project or topic in mind.

How to verify it's working: you should be able to name the next event on the calendar, the specific library or resource you're working through, and the person or group you've been in contact with. If any of those is missing after a few weeks, move to the next step — the mentoring route is designed for exactly that stuck point.

Common sticking points

• Waiting to "be ready" before contacting mentoring. The program is described as helping newcomers throughout their journey, so early contact is the intended use, not a last resort.
• Treating the stack as a finished product. Scicloj frames its tools as something it is building. Expect work in progress and treat gaps as contribution opportunities.
• Skipping the events feed. Study groups and workshops are announced through events; without following them you'll miss the main low-friction way in.
• Joining a dev group with no topic. These groups exist to collaborate and create joint knowledge, so arrive with a question, a project, or a dataset.

A realistic first month

Follow the events feed in week one. In week two, pick one learning resource matching your gap and complete a small data task with the stack. In week three, reach out through open-source mentoring with a specific question about a project. By week four, attend an event or dev-group meeting and decide whether to keep learning, start contributing, or both. That sequence uses every entry point Scicloj advertises, in increasing order of commitment.