|
1 | | -<!-- |
2 | | - <<< Author notes: Header of the course >>> |
3 | | - Include a 1280×640 image, course title in sentence case, and a concise description in emphasis. |
4 | | - In your repository settings: enable template repository, add your 1280×640 social image, auto delete head branches. |
5 | | - Add your open source license, GitHub uses Creative Commons Attribution 4.0 International. |
6 | | ---> |
| 1 | +# Michał Trojaczek |
7 | 2 |
|
8 | | -# Launchpad: Profile README |
| 3 | +**Analiza techniczna, fonoskopia, inżynieria dowodów cyfrowych, procedura karna. |
| 4 | +Łączę prawo, technologię i dokumentację techniczną w jedną całość.** |
9 | 5 |
|
10 | | -_Say hello to your community._ |
11 | | - |
12 | | - |
13 | | -<!-- |
14 | | - <<< Author notes: Start of the course >>> |
15 | | - Include start button, a note about Actions minutes, |
16 | | - and tell the learner why they should take the course. |
17 | | - Each step should be wrapped in <details>/<summary>, with an `id` set. |
18 | | - The start <details> should have `open` as well. |
19 | | - Do not use quotes on the <details> tag attributes. |
20 | | ---> |
21 | | - |
22 | | -<details id=0 open> |
23 | | -<summary><h2>Welcome</h2></summary> |
24 | | - |
25 | | -Say ‘Hello world’ with a profile README that lets you introduce yourself to the GitHub community. You decide what information to include in your profile README, so you have full control over how you present yourself on GitHub. This experience walks you through a quick tutorial to create your profile README. |
26 | | -- **Who is this for**: New developers, new GitHub users, and students. |
27 | | -- **What you'll learn**: How to create a public repository for use as a profile README. |
28 | | -- **What you'll build**: We'll make a profile README file. |
29 | | -- **Prerequisites**: None. This course is a great introduction for your first day on GitHub. |
30 | | -- **How long**: This launchpad takes about 20 mins to complete. |
31 | | - |
32 | | -**About your profile README** |
33 | | - |
34 | | -You can share information about yourself with the community on GitHub.com by creating a profile README. GitHub shows your profile README at the top of your profile page. Here are some examples of information that visitors may find interesting, fun, or useful in your profile README. |
35 | | -- An "About me" section that describes your work and interests |
36 | | -- Contributions you're proud of, and context about those contributions |
37 | | -- Guidance for getting help in communities where you're involved |
38 | | - |
39 | | -Here’s an example of a Campus Expert profile README |
40 | | -<img width="1367" alt="Screen Shot 2023-03-13 at 2 55 41 PM" src="https://user-images.githubusercontent.com/107881423/224805660-26f7272f-6df1-42c0-b4c4-f3b2d790dd65.png"> |
41 | | - |
42 | | - |
43 | | - |
44 | | - |
45 | | - |
46 | | - |
47 | | -## Start Here |
48 | | - |
49 | | -1. **What is a profile README?**: A _[profile README](https://docs.github.com/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme)_ is essentially an "About me" section on your GitHub profile where you can share information about yourself with the community on GitHub.com. GitHub shows your profile README at the top of your profile page. For more information, see "[Managing your profile README](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme)". |
50 | | - |
51 | | -2. **What is a repository?**: A _[repository](https://docs.github.com/get-started/quickstart/github-glossary#repository)_ is a project containing files and folders. A repository tracks versions of files and folders. For more information, see "[About repositories](https://docs.github.com/en/repositories/creating-and-managing-repositories/about-repositories)" from GitHub Docs. |
52 | | -<br>:tv: [Video: Exploring a repository](https://www.youtube.com/watch?v=R8OAwrcMlRw) |
53 | | -3. **Course tips:** |
54 | | -GitHub will display your profile README on your profile page if all of the following are true: |
55 | | - - You've created a repository with a name that matches your GitHub username. |
56 | | - - The repository is public. |
57 | | - - The repository contains a file named README.md in its root. |
58 | | - - The README.md file contains any content. |
59 | | - |
60 | | - |
61 | | -</details> |
62 | | - |
63 | | -<!-- |
64 | | - <<< Author notes: Step 1 >>> |
65 | | - Choose 3-5 steps for your course. |
66 | | - The first step is always the hardest, so pick something easy! |
67 | | - Link to docs.github.com for further explanations. |
68 | | - Encourage users to open new tabs for steps! |
69 | | ---> |
70 | | - |
71 | | -<details id=1> |
72 | | -<summary><h2>Adding a profile README</h2></summary> |
73 | | - |
74 | | -1. Open an additional tab in GitHub and follow the instructions below. |
75 | | - |
76 | | -2. In the upper-right corner of any page, click the ‘+’ and use the drop-down menu, and select New repository. |
77 | | -<img width="265" alt="Screen Shot 2023-03-13 at 3 27 56 PM" src="https://user-images.githubusercontent.com/107881423/224812150-895e1373-03c1-4208-83be-6f671eb41496.png"> |
78 | | - |
79 | | -3. Under "Repository name", type a repository name that matches your GitHub username. For example, if your username is "octocat", the repository name must be "octocat". |
80 | | -<img width="662" alt="Screen Shot 2023-03-13 at 3 28 06 PM" src="https://user-images.githubusercontent.com/107881423/224812371-3870872e-df11-4da8-8bbe-9d9ae3d57c3f.png"> |
81 | | - |
82 | | -4. Optionally, add a description of your repository. For example, "My personal repository." |
83 | | -<img width="643" alt="Screen Shot 2023-03-13 at 3 28 13 PM" src="https://user-images.githubusercontent.com/107881423/224812472-7c8da3b3-48fd-4d46-8ac6-dcadcef09d67.png"> |
| 6 | +--- |
84 | 7 |
|
85 | | -5. Select Public. |
86 | | -<img width="651" alt="Screen Shot 2023-03-13 at 3 28 20 PM" src="https://user-images.githubusercontent.com/107881423/224812820-b40fd7a7-6802-4777-bf43-08c4b306efa9.png"> |
| 8 | +## O mnie |
87 | 9 |
|
88 | | -6. Select Initialize this repository with a README. |
89 | | -<img width="642" alt="Screen Shot 2023-03-13 at 3 28 28 PM" src="https://user-images.githubusercontent.com/107881423/224812890-790983ba-53d5-4eab-ba99-c46fb980b714.png"> |
| 10 | +Pracuję na styku prawa karnego procesowego, akustyki sądowej, analizy danych oraz techniki budowlanej. |
| 11 | +Buduję narzędzia i dokumentację, które mają jedną cechę wspólną: muszą być **rzetelne**, odtwarzalne i odporne na fantazję instytucjonalną. |
90 | 12 |
|
91 | | -7. Click Create repository. |
92 | | -<img width="646" alt="Screen Shot 2023-03-13 at 3 28 34 PM" src="https://user-images.githubusercontent.com/107881423/224813018-b15edbee-2765-414a-a14c-eacb2a85d7b7.png"> |
| 13 | +Moje repozytoria to zapis pracy nad: |
93 | 14 |
|
94 | | -8. Above the right sidebar, click Edit README. |
95 | | -<img width="646" alt="Screen Shot 2023-03-13 at 3 28 41 PM" src="https://user-images.githubusercontent.com/107881423/224813085-b9f3df65-65dd-4d20-9298-1231f5b07e3b.png"> |
| 15 | +- cyfrową mapą dowodową w sprawach karnych, |
| 16 | +- automatyzacją analizy nagrań (Whisper, diarization, fonoskopia), |
| 17 | +- rekonstrukcją i oceną procesową (protokoły, e-protokoły, łańcuch dowodowy), |
| 18 | +- technicznym audytem instalacji CWU/CO budynku Joliot-Curie 19A, |
| 19 | +- narzędziami do precyzyjnego dokumentowania przestrzeni (fotogrametria, termowizja, pomiary 3D). |
96 | 20 |
|
97 | | -9. The generated README file is pre-populated with a template to give you some inspiration for your profile README. |
98 | | -<img width="659" alt="Screen Shot 2023-03-13 at 3 28 49 PM" src="https://user-images.githubusercontent.com/107881423/224813159-539f5b7d-ce1b-448e-bf92-f0c6d40f710f.png"> |
| 21 | +Nie zajmuję się „ładnymi slajdami”. Interesuje mnie to, co jest prawdziwe, spójne i nadaje się do przedstawienia przed sądem lub w raporcie technicznym. |
99 | 22 |
|
100 | | -To add a photo, simply drag the file from your computer into the text edit box and it will be uploaded in that section. For a summary of all the available emojis and their codes, see "Emoji cheat sheet." |
| 23 | +--- |
101 | 24 |
|
102 | | -10. When you've made your customizations and want to save your work, select Commit Changes. |
103 | | -<img width="353" alt="Screen Shot 2023-03-13 at 3 38 58 PM" src="https://user-images.githubusercontent.com/107881423/224814477-ccef9444-5e98-4aac-8f78-8960b678abf5.png"> |
| 25 | +## Specjalizacje |
104 | 26 |
|
| 27 | +### Postępowanie karne |
| 28 | +- analiza uchybień proceduralnych (art. 147–155, 313–314, 399 §1, 404 §2 k.p.k.), |
| 29 | +- dowody cyfrowe, integralność treści, rekonstrukcja przebiegu czynności, |
| 30 | +- porównanie protokołów z nagraniami i wykrywanie rozbieżności, |
| 31 | +- pisma procesowe (wnioski dowodowe, zażalenia, sprostowania protokołów). |
105 | 32 |
|
106 | | -_You did it! :tada:_ |
| 33 | +### Fonoskopia i analiza audio |
| 34 | +- diarizacja wielomówcowa (pyannote), |
| 35 | +- transkrypcja (Whisper / OpenAI), |
| 36 | +- analiza przerw, energii, formantów i anomalii nagrań, |
| 37 | +- badania autentyczności nagrań (artefakty, clipping, synchroniczność odgłosów). |
107 | 38 |
|
| 39 | +### Inżynieria danych i narzędzia techniczne |
| 40 | +- Python (audio processing, automatyzacja, raportowanie), |
| 41 | +- ffmpeg, sox, kalibracja i archiwizacja nagrań, |
| 42 | +- GitHub jako repo dowodowe: struktury akt, wersjonowanie skanów, metadane, |
| 43 | +- zaawansowane środowisko faktyczno-dowodowe. |
108 | 44 |
|
| 45 | +### Audyty techniczne i dokumentacyjne |
| 46 | +- pełna inwentaryzacja instalacji CO/CWU (Leica DISTO X6, FLIR C5, Samsung S24 Ultra), |
| 47 | +- fotogrametria, laserowe wyznaczanie osi (Bosch GLL 3-80 C), |
| 48 | +- raporty energetyczne i eksploatacyjne, |
| 49 | +- dokumentacja PDF z pełną obsługą polskich znaków i poprawnym layoutem. |
109 | 50 |
|
| 51 | +--- |
110 | 52 |
|
111 | | -<!-- |
112 | | - <<< Author notes: Finish >>> |
113 | | - Review what we learned, ask for feedback, provide next steps. |
114 | | ---> |
| 53 | +## Obecne projekty |
115 | 54 |
|
116 | | -<details id=X> |
117 | | -<summary><h2>Finish</h2></summary> |
| 55 | +### **IIK_70_24 – Digital Evidence Repository** |
| 56 | +Repozytorium obejmujące: |
| 57 | +- mapę dowodów, |
| 58 | +- nagrania M4A/OGA/WAV + diarization, |
| 59 | +- skany akt (k. 1–150+), |
| 60 | +- narzędzia do analizy integralności dowodów, |
| 61 | +- wnioski procesowe i rekonstrukcje czynności. |
118 | 62 |
|
119 | | -_Congratulations, you've completed this launchpad and joined the world of developers!_ |
| 63 | +### **Fonoskopia – narzędzia** |
| 64 | +- pipeline diarization + transkrypcja + analiza sygnału, |
| 65 | +- badanie ciągłości nagrań i artefaktów procesowych, |
| 66 | +- skrypty do segmentacji zgodnej z przebiegiem rozprawy. |
120 | 67 |
|
121 | | -<img src=https://octodex.github.com/images/collabocats.jpg alt=celebrate width=300 align=right> |
| 68 | +### **Joliot-Curie 19A – audyt instalacji CO/CWU** |
| 69 | +- dokumentacja techniczna, |
| 70 | +- analiza strat ciepła i błędów wykonawczych, |
| 71 | +- raporty PDF/XLSX z automatyczną segmentacją tabel. |
122 | 72 |
|
| 73 | +--- |
123 | 74 |
|
124 | | -### What's next? |
| 75 | +## Z czego korzystam |
125 | 76 |
|
| 77 | +**Hardware** |
| 78 | +- Dell Precision 7550 (CUDA), |
| 79 | +- Samsung Galaxy S24 Ultra (fotogrametria, nagrania), |
| 80 | +- Leica DISTO X6, FLIR C5, Bosch GLL 3-80 C, |
| 81 | +- HP Color LaserJet Pro M252dw. |
126 | 82 |
|
127 | | -Check out these resources to learn more or get involved: |
128 | | -- Check out the [Student Developer Pack](https://education.github.com/pack) for more resources and exclusive partner offers. |
129 | | -- Explore more Experiences to help you make the most of your GitHub account. |
130 | | -- [Read the GitHub Getting Started docs](https://docs.github.com/en/get-started). |
| 83 | +**Software** |
| 84 | +- Python 3.13, ffmpeg, Whisper, pyannote, JetBrains, GitHub Copilot, |
| 85 | +- Audacity / Adobe Audition (analiza sygnału), |
| 86 | +- Git LFS do archiwizacji dowodów. |
131 | 87 |
|
| 88 | +--- |
132 | 89 |
|
133 | | -</details> |
| 90 | +## Kontakt |
134 | 91 |
|
135 | | -<!-- |
136 | | - <<< Author notes: Footer >>> |
137 | | - Add a link to get support, GitHub status page, code of conduct, license link. |
138 | | ---> |
| 92 | +**E-mail:** michal@trojaczek.com |
| 93 | +**GitHub:** github.com/michaltrojaczek |
| 94 | +(Repozytoria prywatne udostępniam na życzenie w ramach współpracy projektowej.) |
139 | 95 |
|
140 | 96 | --- |
141 | 97 |
|
142 | | -Get help: [Post in our discussion board](https://github.com/skills/.github/discussions) • [Review the GitHub status page](https://www.githubstatus.com/) |
| 98 | +## Motto robocze |
| 99 | + |
| 100 | +„Wszystko jest proste, dopóki nie trzeba tego udowodnić przed sądem.” |
143 | 101 |
|
144 | | -© 2023 GitHub • [Code of Conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) • [CC-BY-4.0 License](https://creativecommons.org/licenses/by/4.0/legalcode) |
0 commit comments