Team Membership

 The aim of this document is to outline AsioTec projects development policies and make developers informed of policies, standards and procedures which Team consider to be core values of development system. This document is not intended to be the universal guide to everything - the opportunities open to members are endless, and as a result, it is designed to teach the principles which should make up a good AsioTec Member and software developer.

1. Introduction

 Most of this guide is targeted at developers, but, if you are just interested to see what makes our projects development work, this guide might provide some valuable insights.

 The best way to get noticed, and to possibly join AsioTec Team, is it file intuitive and accurate bug reports, with patches if possible and to help us out with what you think would make projects better for everyone whether by providing patches for new features or solving existing issues.

2. Becoming a Member

a) Introduction

 There are many ways to join AsioTec and there are also various steps that new “recruits” have to go through before they become official members.

b) Helping Out

 Firstly; to be asked to become a developer everyone should either apply to an opening, or just help out whether in the form of user support, filing bug reports or sending patches. We notice frequent contributors making contributions to our projects and we attempt to reward them by giving the chance to join AsioTec. We have many paths, and the Constitutive Members are always looking out not just for developers - documentation writers and infrastructure maintainers are just as important too.

c) Mentoring

 All new members must have a mentor, who is an existing AsioTec member responsible for guiding a new member as well as offering to help him later after the he has passed through the recruitment process. A mentor should assist by helping with any questions recruits might have, as well as outlining responsibilities, especially those in relation to what new member would initially work on. Once a member agrees to mentor a new recruit, the mentor should file a bug and assign it to himself.

NOTE: The Constitutive Members reserve the right to assign a recruit a new mentor if the initial mentor is idle to queries about the new member or if the mentor files the bug but then does not assist through the rest of the process.

d) Waiting

 All new members pass through a waiting period of up to a month, depending on how ready the mentor thinks the member is as well as feedback from any other related staff. In special cases, the waiting period is determined by the Constitutive Members.

 Additionally, new members should be responsive to their mentors and all Constitutive Members having any questions. Any recruits who do not reply promptly will have their “New Member” bug closed, which would only be reopened at the discretion of the Constitutive Members.

e) Jumping the Gap

 After mentor and Constitutive Members deemed recruits work to be of a suitable standard, they will set them up with the services that their require.

 After this time, recruit enters a “probationary period” of 30 days during which mentor is responsible for all actions, providing accountability. Also, Constitutive Members may reject new developers during this time if they feel it is appropriate.

3. What Members Get

a) Introduction

 AsioTec provides members with all the necessary services which they might need for their development efforts. If anything else is required, members should not hesitate to contact the Constitutive Members.

 All recruiters should organize the following services themselves. If they experience any problems, they should contact mentors.

b) Bug Tracker

 AsioTec Members are able to change all aspects of bugs in Bug Tracker. If member have an existing account the email address should be changed to his AsioTec address by any Constitutive Member.

c) VCS

 Not all members receive VCS access. If it is required to do some work, Constitutive Members should be contacted. The needs for this to happen may need to be justified, however.

d) IRC

 When being a member, you will receive an asiotec/* cloak signifying that you are a team member. Everyone who do not get one, should contact Constitutive Members. Please be aware that Freenode cloaks may neither contain underscores (_) nor dots (.) in the last part, so members must either choose an appropriate nickname or a differing cloak.

e) Mail

 All members are provided with a member@asiotec.org mail address for AsioTec use.

f) Forums

Ask one of the Constitutive Members in #asiotec to update your forum status on the, if needed. Forum accounts are not mandatory.

g) Shell Access

 Members currently may get a shell account on BellSrv. This provides some storage, Linux access and also an IRC tunnel for members to use to access FreeNode.

4. Activity Policiec

 We understand that as life changes, so may member's availability. We respectfully request that if member knows he will be unavailable for an extended period of time (vacation, big project at work, family needs, etc) that he notifies the Team.