# Collaborating with Bespokify

At Bespokify, we employ tools and processes that allow us to efficiently manage projects and client requests. In order to make collaboration as smooth as possible, we ask that everyone involved in these projects adhere to these guidelines.

# Introduction to GitLab

Bespokify uses GitLab (a code-management web application located at git.bspkfy.com) as an internal and external collaboration and project management tool. All work that Bespokify undertakes passes through GitLab.

Each Client is granted access to a space in GitLab to post requests for pattern or application development, post bugs or other issues that require fixing, or otherwise formally communicate with the Bespokify team. Each Client lets the Bespokify team know which individuals should be granted access to GitLab in order to act on their behalf. This is done by sending an email to contact@bespokify.com with the individual's name, and email address. A Bespokify team member will then send an automated invitation to the nominated authorised representatives. All login credentials will be sent via email.

# Using Issues

Clients are assigned to a Plan project within GitLab. Communications between both parties takes place here through the use of issues.

An issue refers to any task that requires handling. These may refer to the development of specific modules, bugs that have been identified, or any topic that needs to be brought to the attention of project leaders. it is within these issues that communication takes place. We prefer all correspondence to occur here as it centralises the conversation for a specific issue in a single location, and allows additional team members to easily track its history.

While it is necessary to log in to GitLab to post new issues, Clients may add comments to these issues by simply replying to the email notifications they receive. These replies will be logged under the corresponding issue in GitLab so our staff can follow up on them.

# Initiating new projects

A Client can request Bespokify to develop a custom pattern or application by posting an issue. The Client should include all reference materials and specifications in the issue's description so the Bespokify team can fully understand the scope and expectations for the job.

Bespokify will take the time to review each new request and ask the client clarification questions to establish the full scope of work. When this scope has been confirmed, Bespokify will reply with a quote and time estimate for the work.

The Client may approve the estimate in the GitLab issue, and by doing so authorise Bespokify to execute the work as per the determined scope and charge the client the amount agreed upon.

If the client declines to proceed, or does not give written approval for the job estimate within 30 days, the job will be closed and no further action will be taken.

# Approving patterns

To evaluate the quality of patterns the Client will nominate up to 10 measurement profiles for fit testing that will be included in the project scope.

A pattern project will be considered delivered successfully when the pattern meets the agreed scope outlined in the GitLab issue, and one of the following conditions are met:

1. The client produces test patterns for the nominated measurement profiles and the alterations are consistently within a ±1cm tolerance;
2. The client generates a pattern for any profile other than a nominated measurement profile. This indicates the pattern is suitable for commercial use; or
3. A 30-day period has elapsed since the last test pattern was generated and/or feedback was entered into the GitLab issue.

# Reporting pattern bugs

Bugs or issues identified with patterns must follow this procedure in sequential order:

1. The client must first rule out sewing errors by taking measurements off the final sewn garment and comparing them against the Garment Measurement values displayed in the Tech Pack.
2. The client must secondly rule out input measurement error by investigating the source of the measurements and checking there were no errors or omissions in the measurement profile used to create the order.
3. If the first two steps are correct then the client should post an issue in GitLab. The title of the issue should refer to the product and describe the problem in plain language, and the description should include any supporting evidence (such as screenshots, step-by-step guides, or action points) to assist Bespokify in investigating the issue.
4. Bespokify will review and respond to each issue as soon as possible, and will ask the client any clarification questions in the GitLab issue. Once the problem has been properly identified by Bespokify, the following action will be taken:
   1. If the problem is determined to be Bespokify's fault, a solution will be deployed as soon as possible. Once the solution has been deployed to the production server, the issue will be closed and the client will be notified by an automated GitLab email notification.
   2. If the problem is determined to be the client's or another party's fault, Bespokify will post an explanation in the GitLab issue and then close the issue. No further action will be taken.
5. The client will test any solutions by generating new patterns and samples. If the problem persists, the client should repeat this procedure until the bug is fully resolved.

# Tips and etiquette

1. You can notify individuals when writing a post by using @ preceding their username (e.g. @lucy). Avoid referencing multiple people at a time unless your post explicitly requires their response or contribution.
2. Include images and other attachments in your posts to aid communication. You may drag and drop images directly into the message for easier uploading.
3. Format your posts using Markdown script. Here's a great cheat sheet to get you started.