sources.json
12,603 bytes
| 1 | { |
|---|---|
| 2 | "S1": { |
| 3 | "text": "It should be some kind of a GitHub clone, but it's a shareable with a link or some way that we can basically share our private GitHub repos, I mean, all of the profile and the chosen repositories with a link, with a time period as well, so I wouldn't have to put some people who want to see my work as a collaborator, and therefore I can just easily share the link where you can see basically my work that I have been doing.", |
| 4 | "ts": "2026-07-23T10:45:55.211Z" |
| 5 | }, |
| 6 | "S2": { |
| 7 | "text": "What's the main thing you want people to be able to do when they open one of your shared links — just look at your code and profile, or something more?", |
| 8 | "ts": "2026-07-23T10:46:00.641Z" |
| 9 | }, |
| 10 | "S3": { |
| 11 | "text": "Yeah, basically, like in GitHub, but it would also be nice to see the activity of your profile and so on.", |
| 12 | "ts": "2026-07-23T10:46:31.238Z" |
| 13 | }, |
| 14 | "S4": { |
| 15 | "text": "Who do you picture actually opening these links — for example, people hiring you, teammates, friends — and do they need a GitHub account of their own to view your work?", |
| 16 | "ts": "2026-07-23T10:46:36.511Z" |
| 17 | }, |
| 18 | "S5": { |
| 19 | "text": "Mainly people who are willing to hire me, and they don't have to have a good top account.", |
| 20 | "ts": "2026-07-23T10:47:03.043Z" |
| 21 | }, |
| 22 | "S6": { |
| 23 | "text": "Got it — the viewers are mostly people who might hire you. Now, who will be creating and sharing these links? Is it just you for your own work, or do you imagine lots of different people signing up to share their own profiles too?", |
| 24 | "ts": "2026-07-23T10:47:10.726Z" |
| 25 | }, |
| 26 | "S7": { |
| 27 | "text": "I'm not really sure about what's the better solution here. Firstly, I would like to, of course, do it for me, myself, but maybe it's useful for other people as well, then therefore we can just make it the other way.", |
| 28 | "ts": "2026-07-23T10:47:57.732Z" |
| 29 | }, |
| 30 | "S8": { |
| 31 | "text": "Walk me through it step by step from your side: once you're ready to share, what would you do to pick which repositories and profile info go into a link, and then how would you hand that link to someone?", |
| 32 | "ts": "2026-07-23T10:48:03.596Z" |
| 33 | }, |
| 34 | "S9": { |
| 35 | "text": "This should be all of the repos that I have and I can just click on the ones I want to basically share on my account or under my account. And therefore, I can just, it generates some kind of a profile and a simple URL which I can just share and send it to other people. And also, I think it should have some kind of a time period that people cannot see it indefinitely. So yeah, for example, like seven days or something like that. And that's also just customizable for people themselves.", |
| 36 | "ts": "2026-07-23T10:49:26.671Z" |
| 37 | }, |
| 38 | "S10": { |
| 39 | "text": "Now picture the person you sent the link to opening it. Walk me through what they see first and what they can click on or move through from there.", |
| 40 | "ts": "2026-07-23T10:49:33.186Z" |
| 41 | }, |
| 42 | "S11": { |
| 43 | "text": "You do ChatGPT like a GitHub, similar to it. And you can see all of the projects, the code, also the commit history, and so on.", |
| 44 | "ts": "2026-07-23T10:50:07.781Z" |
| 45 | }, |
| 46 | "S12": { |
| 47 | "text": "When someone opens your shared link, what exact pieces of information should show up on that page — for example your name, a photo, a short bio, the list of projects, the code inside them, dates of when you worked on things, or anything else?", |
| 48 | "ts": "2026-07-23T10:50:13.840Z" |
| 49 | }, |
| 50 | "S13": { |
| 51 | "text": "Yes, basically all of the GitHub or GitLab things that are basic. Just my main goal is to not make my GitHub projects fully public to the whole world, and I just want to share this one of my profile publicly to a fixed amount of people that I have shared the link to.", |
| 52 | "ts": "2026-07-23T10:50:59.809Z" |
| 53 | }, |
| 54 | "S14": { |
| 55 | "text": "When you pick your projects to share, should the shared page always show the very latest version of your work as it changes, or should it freeze a snapshot of how things looked the moment you made the link?", |
| 56 | "ts": "2026-07-23T10:51:07.570Z" |
| 57 | }, |
| 58 | "S15": { |
| 59 | "text": "I think it's erased to just from the snapshot, because if it changes all the time, then therefore we would just need a lot more complicated code, and I don't think that's necessary. With a snapshot, we just can take the moment's code and that's it.", |
| 60 | "ts": "2026-07-23T10:52:13.693Z" |
| 61 | }, |
| 62 | "S16": { |
| 63 | "text": "Where would this tool actually get your projects and code from? For example, would it connect directly to your existing GitHub or GitLab account to pull everything in, or would you upload your files some other way?", |
| 64 | "ts": "2026-07-23T10:52:19.100Z" |
| 65 | }, |
| 66 | "S17": { |
| 67 | "text": "That's something for you to think about, but mainly, yeah, from my GitHub. I have all of my projects in GitHub.", |
| 68 | "ts": "2026-07-23T10:52:44.551Z" |
| 69 | }, |
| 70 | "S18": { |
| 71 | "text": "When you first set this up to pull from your GitHub, how would you expect to give it permission to see your private projects — for example logging in with your GitHub account and approving access, and would you be okay with it having access to all your repositories or only the ones you point it to?", |
| 72 | "ts": "2026-07-23T10:52:50.627Z" |
| 73 | }, |
| 74 | "S19": { |
| 75 | "text": "I'm not really sure, but why should I give access to all of the repositories when I just think the ones that I want to make public just have access to them.", |
| 76 | "ts": "2026-07-23T10:53:44.894Z" |
| 77 | }, |
| 78 | "S20": { |
| 79 | "text": "Let's think about when that sharing time runs out. Say you set a link to work for seven days and someone tries to open it on day eight — what should they see or be told at that point?", |
| 80 | "ts": "2026-07-23T10:53:52.543Z" |
| 81 | }, |
| 82 | "S21": { |
| 83 | "text": "Just a simple that the URL that you have opened is expired.", |
| 84 | "ts": "2026-07-23T10:54:12.884Z" |
| 85 | }, |
| 86 | "S22": { |
| 87 | "text": "Imagine you send the link to one person, but they forward it to someone else you didn't mean to share it with. Should anyone who has the link be able to open it, or do you want some way to make sure only the people you intended can get in?", |
| 88 | "ts": "2026-07-23T10:54:18.681Z" |
| 89 | }, |
| 90 | "S23": { |
| 91 | "text": "I don't think we need to go that complicated, just if the send it or forward it to someone else, then that's it. Because the code is still not filled with some secrets, but just I don't want to make all of the GitHub repositories public to the whole world. If just a couple of people see it, it's okay.", |
| 92 | "ts": "2026-07-23T10:55:08.560Z" |
| 93 | }, |
| 94 | "S24": { |
| 95 | "text": "Are there any limits this tool needs to respect — for example, how big your projects can be, how many links you can have going at once, or how fast the page should load when someone opens it?", |
| 96 | "ts": "2026-07-23T10:55:15.757Z" |
| 97 | }, |
| 98 | "S25": { |
| 99 | "text": "I'm not really sure, but it should just work normally and same normal, and main thing is to just have the right features that it shows all of the commits and all of the details that are needed.", |
| 100 | "ts": "2026-07-23T10:55:54.492Z" |
| 101 | }, |
| 102 | "S26": { |
| 103 | "text": "Since the page shows a frozen copy of your work, that copy has to be stored somewhere until the link runs out. Once a link expires, do you want that stored copy of your code and profile to be deleted right away, or is it fine for it to sit around somewhere afterward?", |
| 104 | "ts": "2026-07-23T10:56:04.613Z" |
| 105 | }, |
| 106 | "S27": { |
| 107 | "text": "I'm not sure about this, I just picked the most best solution.", |
| 108 | "ts": "2026-07-23T10:56:46.277Z" |
| 109 | }, |
| 110 | "S28": { |
| 111 | "text": "When someone opens your shared link, do they need it to look good and work on a phone screen too, or is it fine if it's really only meant to be viewed on a computer?", |
| 112 | "ts": "2026-07-23T10:56:55.060Z" |
| 113 | }, |
| 114 | "S29": { |
| 115 | "text": "Menim komputerim.", |
| 116 | "ts": "2026-07-23T10:57:09.000Z" |
| 117 | }, |
| 118 | "S30": { |
| 119 | "text": "When someone opens your link, do you want them to only look at your work, or should they also be able to do things like leave comments, download your code, or send you a message — and are there any of those things you'd rather they definitely can't do?", |
| 120 | "ts": "2026-07-23T10:57:16.826Z" |
| 121 | }, |
| 122 | "S31": { |
| 123 | "text": "No comments and I don't think downloading code is necessary for it. Just the main objective is to just them having an overview of my work that I have done and the code not being openly public to the world.", |
| 124 | "ts": "2026-07-23T10:58:23.953Z" |
| 125 | }, |
| 126 | "S32": { |
| 127 | "text": "You've said no comments and no downloading. Are there other things you want to make sure this tool does NOT try to do — for example letting the viewer edit anything, being a full copy of everything GitHub does, or working for teams instead of just one person — things you'd rather leave out to keep it simple?", |
| 128 | "ts": "2026-07-23T10:58:41.168Z" |
| 129 | }, |
| 130 | "S33": { |
| 131 | "text": "It's basically a overview of my code. That's it. Simple. Just an overview of my code.", |
| 132 | "ts": "2026-07-23T10:59:10.328Z" |
| 133 | }, |
| 134 | "S34": { |
| 135 | "text": "Imagine you've just made your first link and sent it to someone. How would you check for yourself that it's working the way you want — what would you look at or try before you felt confident sharing it with a real hiring person?", |
| 136 | "ts": "2026-07-23T10:59:19.328Z" |
| 137 | }, |
| 138 | "S35": { |
| 139 | "text": "just looking at it openly link myself", |
| 140 | "ts": "2026-07-23T10:59:44.926Z" |
| 141 | }, |
| 142 | "S36": { |
| 143 | "text": "When you open that link yourself to check it, what would make you say 'yes, this is right' versus 'something's wrong here'? For example, would you be checking that the correct projects show up, that the code and commit dates look right, or something else?", |
| 144 | "ts": "2026-07-23T10:59:50.508Z" |
| 145 | }, |
| 146 | "S37": { |
| 147 | "text": "has all the projects that i selected and all the commits and ues", |
| 148 | "ts": "2026-07-23T11:00:27.742Z" |
| 149 | }, |
| 150 | "S38": { |
| 151 | "text": "When the hiring person is looking at your page and you've shared, say, three projects, how would they move from one project to another — is there a main list they start on and click into each one, and can they then dig into the files and commit history inside a project and come back out?", |
| 152 | "ts": "2026-07-23T11:00:35.122Z" |
| 153 | }, |
| 154 | "S39": { |
| 155 | "text": "Yes, basically that's it. Just the main page is my profile and there you can just click on the repositories.", |
| 156 | "ts": "2026-07-23T11:01:01.808Z" |
| 157 | }, |
| 158 | "S40": { |
| 159 | "text": "Once the hiring person clicks into one of your projects, what would they see inside it — for example the list of files that they can open to read the code, and a separate list of your past commits — and how would they get back to your main profile page when they're done looking?", |
| 160 | "ts": "2026-07-23T11:01:08.327Z" |
| 161 | }, |
| 162 | "S41": { |
| 163 | "text": "thats your job", |
| 164 | "ts": "2026-07-23T11:01:27.027Z" |
| 165 | }, |
| 166 | "S42": { |
| 167 | "text": "When the hiring person looks at your past commits inside a project, do you just want them to see a simple list of what you changed and when, or should they be able to click a commit and actually see which lines of code changed in that update?", |
| 168 | "ts": "2026-07-23T11:01:39.917Z" |
| 169 | }, |
| 170 | "S43": { |
| 171 | "text": "if doable then just clickable also", |
| 172 | "ts": "2026-07-23T11:02:16.848Z" |
| 173 | }, |
| 174 | "S44": { |
| 175 | "text": "Inside one of your projects, when the hiring person wants to actually read your code, how do you picture them getting to it — do they click on a file name from a list and the code opens up to read on screen, and if your project has folders inside folders, should they be able to open those folders to find files too?", |
| 176 | "ts": "2026-07-23T11:02:26.830Z" |
| 177 | }, |
| 178 | "S45": { |
| 179 | "text": "yes", |
| 180 | "ts": "2026-07-23T11:02:53.057Z" |
| 181 | }, |
| 182 | "S46": { |
| 183 | "text": "When the hiring person has opened one of your files and finished reading the code, how would they get back — do they step back to the list of files in that project first, and then have a clear way back to your main profile page to pick a different project?", |
| 184 | "ts": "2026-07-23T11:03:09.282Z" |
| 185 | }, |
| 186 | "S47": { |
| 187 | "text": "just at the top some button to profile", |
| 188 | "ts": "2026-07-23T11:03:51.522Z" |
| 189 | }, |
| 190 | "S48": { |
| 191 | "text": "You mentioned a button at the top to get back to your profile. When the hiring person has clicked down through several folders inside a project — say a folder inside a folder inside a folder — how would they step back up one level at a time, or jump straight back to the top of that project, without losing their place?", |
| 192 | "ts": "2026-07-23T11:04:02.130Z" |
| 193 | }, |
| 194 | "S49": { |
| 195 | "text": "done", |
| 196 | "ts": "2026-07-23T11:04:13.798Z" |
| 197 | }, |
| 198 | "S50": { |
| 199 | "text": "Interview complete.", |
| 200 | "ts": "2026-07-23T11:04:13.800Z" |
| 201 | } |
| 202 | } |