Commit 0762469c authored by Nicolas Lenz's avatar Nicolas Lenz
Browse files

Update Readme

parent 382b0ae9
# mask
# Sewing Patterns
Sewing pattern for a face mask.
This is a pattern with instructions for an ergonomic face mask with a protusion for fitting well over the nose even without a clip and another protusion for fitting under the chin as well.
## Getting started
It can be made single- or double-layered. I use double-layer for interior spaces where aerosols can accumulate easier. When walking, cycling, ... outside I use a single-layered mask as aerosols are less of a problem outside and it's easier to breathe. Optionally, you can equip a double-layered mask with a nose clip. I use simple aluminium flat wire (as aluminium doesn't rust), but anything bendable should work.
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
I designed this back when home-made cloth masks were used, which is what got me into sewing.
Already a pro? Just edit this and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
The pattern consinsts of hand-crafted (because I'm weird) SVG vector files. Run `make` to generate printable PDFs. Take care to print using original scale.
## Add your files
- [ ] [Create]( or [upload]( files
- [ ] [Add files using the command line]( or push an existing Git repository with the following command:
## Instructions
cd existing_repo
git remote add origin
git branch -M main
git push -uf origin main
### Materials
## Integrate with your tools
- About 2 × 32 cm × 16 cm of fabric (for a double-layered mask)
- About 50 cm of elastic band
- Sewing thread
- *Optional* About 12 cm of flat wire or something similar
- [ ] [Set up project integrations](
### Instructions
## Collaborate with your team
1. Print out the patterns in original size.
1. Cut out two outer pieces from your fabric.
1. Lay the pieces on top of each other, outside on outside
1. Sew the long curved sides together about 5 mm from the edge, optimally using an overlock stitch to prevent fringing.
1. *(For single-layered masks)* Hem the upper and lower edges by folding about 3 mm of the fabric edge over to the inner side twice and securing that hem using a simple straight stitch.
- [ ] [Invite team members and collaborators](
- [ ] [Create a new merge request](
- [ ] [Automatically close issues from merge requests](
- [ ] [Enable merge request approvals](
- [ ] [Automatically merge when pipeline succeeds](
*(For double-layered masks)*
1. Cut out two inner pieces.
1. Hem the short straight edges.
1. Lay them on top of each other, inside on inside.
1. Sew the long curved sides together.
1. Pin or clip the outside and inside pieces together, outside on outside, nose curve on nose curve.
1. Sew together the upper and lower edges, again optimally using an overlock stitch.
1. Turn inside-out so it is oriented correctly and carefully press.
1. For both short sides: fold in about 3 mm of fabric as hem, then fold about 1,5 cm and sew over the hem. That should leave a tunnel of fabric.
1. Channel elastic band (about 22cm depending on the elasticity and your head size) through the tubes, knot the ends together and push the knots into the tunnel.
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](
- [ ] [Use pull-based deployments for improved Kubernetes management](
- [ ] [Set up protected environments](
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to []( for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment