Skip to content

DOC · governance

Constitution

How the AWS Student Builders Group at Daffodil International Academy is organized and run.

Draft · subject to committee approval

Article 1

Name and affiliation

  1. 1.1The name of the organization is the AWS Student Builders Group at Daffodil International Academy ("AWS SBG", "the Group").
  2. 1.2The Group is a student-led community affiliated with the AWS Student Builder Groups program and connected to AWS Builder Center (community.aws/buildergroups). It is part of a global network of 600+ student-led groups.
  3. 1.3The Group operates as a wing of the DIA Programming Club at Daffodil International Academy and follows the policies of the institution.
  4. 1.4The Group is not an official Amazon Web Services entity. AWS and related marks belong to Amazon.com, Inc. or its affiliates and are used in line with program guidance.

Article 2

Purpose and mission

  1. 2.1Our mission is captured in four words: Learn · Build · Connect · Create Impact.
  2. 2.2

    The Group exists to:

    • Help students learn cloud and AI technologies through hands-on, peer-led activities.
    • Give members practical experience by building and deploying real projects.
    • Connect students with each other, with AWS Builder Center and with the wider global community of builders.
    • Encourage projects that create a positive impact for the school and the community.

Article 3

Membership and eligibility

  1. 3.1Membership is open to currently enrolled students of Daffodil International Academy, regardless of discipline, year or prior experience.
  2. 3.2A student becomes a member by joining the Group on Meetup and/or registering through a channel announced by the committee.
  3. 3.3Faculty and staff may take part as advisors, mentors or guests.
  4. 3.4Members are expected to follow this constitution and the Code of Conduct. Membership may be suspended or ended for serious or repeated breaches, under the process in Article 7.
  5. 3.5Members may leave at any time by leaving the Meetup group or informing the committee.

Article 4

Structure and roles

  1. 4.1

    Advisory

    • Faculty Advisor: a faculty member who guides the Group, supports its activities with the institution and approves major decisions such as amendments and disciplinary outcomes.
    • Convener: a faculty member who helps coordinate the Group with the institution, supports planning and acts as a point of contact for faculty and administration.
  2. 4.2

    Student leadership

    • Leader (Student Builder Group Leader): leads the Group, represents it to AWS Builder Center and the institution, chairs committee meetings and is accountable for the Group's plans and conduct.
  3. 4.3

    Core team

    • Event Management and Logistics: plans events end-to-end, including venue, schedule, logistics and Meetup event pages.
    • Technical, Event Management and Logistics: owns the technical side of sessions (labs, demos, environments, tooling) and supports event delivery.
    • Community and Communications: manages member communication, announcements and relationships with partners and other groups.
    • Social Media Management: runs the Group's social media presence and promotes events.
    • Social Media and Content Management: creates content (posts, recaps, visuals, write-ups) and keeps it consistent with the Group's brand.
  4. 4.4The committee (the Leader and core team, with the Faculty Advisor and Convener) may create, merge or retire roles as the Group grows. Changes are recorded in the meeting minutes.
  5. 4.5One person may hold more than one role if the committee agrees.

Article 5

Activities

  1. 5.1Events are created and managed on the Group's Meetup page. RSVPs, reminders and updates go through Meetup.
  2. 5.2

    Typical activities include:

    • Workshops: guided, hands-on sessions on cloud and AI topics.
    • Builder sessions: time to build and deploy projects together with peer support.
    • Talks, study groups and community meetups.
    • Collaborative projects, challenges and hackathons.
  3. 5.3Members are encouraged to use AWS Builder Center and other official AWS learning resources.
  4. 5.4Activities must follow institution rules and must not commit members to any cost without clear notice.

Article 6

Member benefits

  1. 6.1

    Depending on what is available at the time, members may receive:

    • Access to learning resources and AWS Builder Center.
    • A campus community of peers and mentors.
    • Hands-on events and workshops.
    • Swag, credits or other program benefits when AWS or partners make them available.
  2. 6.2No specific benefit is guaranteed. The committee will share benefits fairly and openly when they become available.

Article 7

Code of conduct

  1. 7.1Everyone in our spaces, online and offline, must be respectful, inclusive and professional.
  2. 7.2

    The following are not tolerated:

    • Harassment, discrimination or intimidation of any kind.
    • Plagiarism or misrepresenting other people's work.
    • Misuse of cloud accounts, credentials or resources, including sharing secrets or running workloads that break provider terms or the law.
    • Behaviour that endangers the safety or well-being of others.
  3. 7.3Concerns can be raised with any committee member, the Faculty Advisor or by email at aws@diapc.dev. Reports are handled confidentially.
  4. 7.4The committee, with the Faculty Advisor, may issue a warning, restrict participation or end membership, after giving the person a chance to respond.

Article 8

Elections and term

  1. 8.1Student committee roles are held for one academic year, unless the committee and Faculty Advisor agree otherwise.
  2. 8.2Before the end of a term, the committee announces open roles and invites applications or nominations from members.
  3. 8.3Selections are made by member vote or by a selection panel that includes the outgoing Leader and the Faculty Advisor. The method is announced in advance.
  4. 8.4The Leader must also meet any requirements set by the AWS Student Builder Groups program.
  5. 8.5If a role falls vacant mid-term, the committee may appoint an interim holder until the next selection.
  6. 8.6Outgoing role holders should hand over accounts, documents and access to their successors.

Article 9

Meetings

  1. 9.1The committee meets regularly, at least once a month during the academic term, in person or online.
  2. 9.2A committee meeting needs a majority of current student committee members to make decisions (quorum).
  3. 9.3Decisions are made by consensus where possible, otherwise by simple majority. The Leader has a casting vote.
  4. 9.4Key decisions and action items are recorded and shared with the committee.
  5. 9.5General member meetings may be called by the committee to share plans and gather feedback.

Article 10

Amendments

  1. 10.1Any member may propose an amendment in writing to the committee.
  2. 10.2Amendments require approval by a two-thirds majority of the committee and the consent of the Faculty Advisor.
  3. 10.3Approved amendments take effect when published on this page, with the date of the change.

Questions or suggestions? Email aws@diapc.dev.