Answers about Attack On Code membership, missions, projects, open source, leadership, participation, recognition, conduct and communication.
Attack On Code, or AOC, is a student-led engineering and open-source community where members learn through practical missions, build real projects, collaborate with teams and grow through visible contribution. AOC is designed for students who want to move beyond passive learning and gain practical experience in software development, open source, design, artificial intelligence, competitive programming, game development and related technical fields.
AOC is more than a conventional coding club. It includes coding activities, but its broader purpose is to operate as a structured builder network where members participate in missions, projects, open-source repositories, hackathons, technical discussions, research and community initiatives.
AOC was created to solve a common problem among students: many people learn programming, complete courses and collect certificates, but receive very little exposure to real collaboration, project ownership, code review, documentation, deployment and long-term software development.
Attack On Code was founded by Nayant Srivastava. The long-term vision is to build a serious student-led engineering and open-source ecosystem that can grow beyond a single college, batch or founding team.
No. AOC may begin through local college communities and regional networks, but its long-term vision is to welcome serious builders from different colleges, cities and technical backgrounds.
AOC is open to students, developers, designers, researchers, problem-solvers and technology enthusiasts who are willing to learn, contribute and collaborate.
No. AOC welcomes beginners, intermediate learners and experienced contributors. New members begin as Explorers and can take beginner-level missions while understanding how the community operates.
Yes. AOC is not limited to programmers. Designers, technical writers, researchers, event organisers, product thinkers, community managers and documentation contributors can also play important roles.
Any membership fee, event fee or project-related cost should be clearly communicated before registration. AOC should not introduce hidden charges.
You can join through the official AOC registration or onboarding process. After registering, you may be asked to complete a member profile, select your areas of interest, attend an orientation, choose a technical wing and complete an introductory mission.
After registration, you enter the Explorer stage. During this stage, you will learn how AOC is organised, how missions work, how teams communicate, how projects are managed and how contributions are reviewed.
Yes. Membership is voluntary. Members may leave the community, become temporarily inactive or return later according to the current membership policy.
Yes. AOC is intended to help members understand open-source contribution step by step. Beginner missions may include improving documentation, fixing small issues, testing features, creating examples, reporting bugs or making minor code contributions.
Yes. Missions should be available at different difficulty levels. Beginner contributors may work on smaller, clearly defined tasks before moving to larger systems.
AOC may provide workshops, resources, learning paths and peer support, but it is not designed as a complete replacement for personal study. AOC helps you apply what you learn through missions, collaboration and project work.
AOC does not need to be restricted to one programming language. The technologies used will depend on the needs of each project or wing. Technology choices should be based on project requirements rather than trends alone.
Yes, but members should usually select one primary wing. You may collaborate with other wings when a project requires multiple skills.
A mission is a clearly defined task or objective that produces a meaningful outcome. Each mission should include its requirements, expected deliverables, difficulty and review process.
Members can explore available missions and select one according to their skill level, area of interest, available time, required tools and project needs.
Yes. Members should not be forced to accept work they cannot reasonably complete. However, once you accept a mission, you are expected to communicate properly, make a serious effort and inform the team early if you become blocked.
Failure to complete a mission is not automatically treated as misconduct. The important requirement is communication. You should inform your mission lead, explain the blocker and request help, reassignment or an adjusted deadline.
Most community learning missions may be unpaid. If AOC introduces paid client work, sponsored projects, internships or revenue-generating assignments, compensation terms should be explained separately and transparently before participation.
Yes. Members can propose missions when they identify a useful problem or opportunity. A mission proposal should explain the problem, objective, expected outcome, required skills, estimated effort and why the mission benefits AOC or its users.
AOC may develop open-source tools, educational platforms, productivity software, developer utilities, artificial intelligence applications, web and mobile products, game development projects, research prototypes, community infrastructure and experimental technology.
Yes. Members may submit a project proposal. Not every idea will immediately become an official AOC project. The proposal must be feasible and aligned with the community goals.
Ownership depends on the project type, licence, contributor agreement and whether the project is an official AOC initiative. Ownership expectations should be documented before significant development begins.
Yes. Contributors should receive appropriate credit for meaningful work through repository contribution history, project documentation, release notes, contributor profiles, certificates or letters where appropriate, public recognition and project portfolios.
Open source means that selected projects are developed publicly under a defined software licence. Open source also requires responsible maintenance, documentation, review and community governance.
Not necessarily. Many AOC projects may be open source, but some internal, private, research, sponsored or security-sensitive projects may remain restricted.
Yes, when a repository is public and open to external contribution. External contributors should follow the project contribution guidelines, code of conduct, issue process, coding standards and review requirements.
AOC may include the Founder, Core Council, technical and operational wings, project teams, squads, maintainers, contributors and Explorers. The structure exists to distribute responsibility and create clear paths for contribution and leadership.
Leadership roles are earned through consistent contribution, reliability, technical understanding, communication, project ownership and the ability to support other members.
Yes. Academic year alone should not determine leadership. A beginner may gradually become a leader by showing strong consistency, responsibility, communication and growth.
Major decisions may involve the Founder, Core Council, relevant project leads, maintainers and active contributors. Technical decisions should be guided by evidence, feasibility and project requirements rather than popularity.
Yes. Respectful disagreement is healthy. Members are encouraged to question decisions, identify risks and propose alternatives.
There is no single fixed requirement for every member. The expected time depends on the mission or project you accept. Members should accept responsibilities according to their actual availability.
Attendance requirements may vary for orientation sessions, project meetings, competitions or official events. AOC should prioritise meaningful participation over attendance for its own sake.
Academic responsibilities are important. Members should inform their team in advance and reduce or pause responsibilities during examinations.
Yes. Many missions, projects, reviews and discussions can be completed remotely. Remote contributors should still have meaningful opportunities.
AOC may provide certificates for meaningful participation, project completion, leadership, workshops or specific achievements. However, certificates should not be the primary purpose of joining.
AOC does not guarantee jobs or internships. However, active members may develop stronger portfolios, better GitHub profiles, teamwork experience, project ownership, technical communication and professional connections.
Yes, provided you accurately describe your role and contribution. Do not claim ownership of the entire project if you worked only on a small part.
Recommendation letters may be provided to members who have demonstrated meaningful, verifiable and consistent contribution. They should not be issued automatically to inactive members or based only on registration.
Members are expected to practise respect, professionalism, honesty, accountability, constructive feedback, responsible communication and proper credit for others work.
Plagiarism, contribution fraud and false claims are treated seriously. Depending on the severity, the response may include contribution rejection, removal of recognition, temporary suspension, removal from a project or termination of membership.
AOC should maintain a clear code of conduct. Reports should be reviewed confidentially and fairly by authorised community leaders. Retaliation against someone who reports genuine misconduct should not be tolerated.
Members may share relevant projects, opportunities and achievements in approved spaces. However, excessive promotion, spam, misleading advertising or using the community only for personal marketing may be restricted.
Official communication may occur through the AOC website, community platforms, project management systems, GitHub, email, event channels and approved social platforms.
New opportunities may be published through the Missions Space, member dashboard, official announcements, newsletters, community channels and wing-specific updates.
You may contact your mission lead, project maintainer, wing coordinator, onboarding mentor or an authorised community administrator.
Successful AOC members are usually the people who remain curious, communicate honestly, complete small responsibilities, accept feedback, help teammates, document their work and gradually take ownership. Consistency matters more than appearing impressive.
Before joining, ask yourself whether you are willing to learn through practical work, communicate when blocked, respect other contributors, commit to small but consistent progress and build something that others can use, review or improve.
Join AOC if you want to move from isolated learning to collaborative building. Join if you want to work on real missions, understand how technical teams operate, build public proof of work and grow into a stronger developer, designer, researcher or technical leader.
Contact the Attack On Code team through the official community platform or submit your question through the website. Learn. Build. Contribute. Lead.
