1 |
Hi Gentoo Science Team, |
2 |
|
3 |
I'm interested in joining the Science Team as a developer. For a |
4 |
detailed description of my previous experience with ebuilds and Gentoo I |
5 |
refer to the emails I forwarded below (the short summary is that I |
6 |
maintain spyder (The Scientific PYthon Development EnviRonment) and some |
7 |
dependencies in ::gentoo, and that I'm a Trusted Contributor to the GURU |
8 |
project.). I'll also add some more information on what I do |
9 |
scientifically in this email. |
10 |
After just over 5 years of studying Physics, I'm at the verge of |
11 |
completing my Masters in Physics of Molecules and Materials. The past |
12 |
year I've been busy with an internship at the High Field Magnet |
13 |
Laboratory (Nijmegen, The Netherlands), where I've been working on |
14 |
creating a setup for Oscillating Cantilever Magnetometry, with varying |
15 |
levels of success (the pandemic didn't make things easier). I submitted |
16 |
my Thesis this week, and am currently awaiting a review and a result. |
17 |
After which I'm hoping to start a PhD (if the pandemic allows that). |
18 |
|
19 |
I would love to hear if anyone has the time for mentoring me. As I also |
20 |
said in the emails I forwarded below, I have already taken a look at the |
21 |
quizzes linked on the Gentoo website and I feel like I can answer a lot |
22 |
of the questions in there (not all of them though, so I do still need to |
23 |
study a bit). |
24 |
|
25 |
Best regards, |
26 |
Andrew |
27 |
|
28 |
|
29 |
-------- Forwarded Message -------- |
30 |
Subject: Interested in becoming a Gentoo developer |
31 |
Date: Sat, 15 Aug 2020 16:36:58 +0200 |
32 |
From: Andrew Ammerlaan <andrewammerlaan@××××××.net> |
33 |
To: recruiters@g.o |
34 |
CC: Joonas Niilola <juippis@g.o>, Michał Górny |
35 |
<mgorny@g.o>, heroxbd@g.o, sping@g.o |
36 |
|
37 |
|
38 |
Hi recruiters@g.o, |
39 |
|
40 |
|
41 |
I started contributing to ::gentoo in Novemeber/December of last year |
42 |
via the proxy-maint project. My first project was getting spyder-4 in |
43 |
the tree. Spyder is the Scientific PYthon Development EnviRonment, and I |
44 |
use it a lot for data analysis and such (I study Physics), at the time |
45 |
the spyder ebuild was outdated and contained a couple of bugs that had |
46 |
been open for quite some time, eventually I decided that I would just |
47 |
fix it myself. This was a *massive* Pull Request |
48 |
(https://github.com/gentoo/gentoo/pull/13988 I had to split it up a |
49 |
bit), and @juippis, @hartwork and @heroxbd helped me a lot with it. Back |
50 |
then I didn't really know what I was doing, but I found that everyone |
51 |
was really helpful in giving feedback on my work and linking me the |
52 |
relevant documentation and tutorials. I learned a lot from the |
53 |
experience, and I still proxy-maintain dev-python/spyder and some of its |
54 |
dependencies such as dev-python/python-language-server. |
55 |
|
56 |
In January I joined the ::guru project |
57 |
(https://wiki.gentoo.org/wiki/Project:GURU) as a Contributor |
58 |
(https://bugs.gentoo.org/706002). I had some new package ebuilds that I |
59 |
wanted to share, but I didn't want to add to the already huge amount of |
60 |
PRs that get assigned to the proxy-maint team. I found that GURU was the |
61 |
perfect place for these new ebuilds. My second project consisted of |
62 |
writing ebuilds for Vidify and deps (https://vidify.org/ |
63 |
https://github.com/vidify/vidify). Vidify is an awesome tool that |
64 |
automagically fetches the music video from YouTube that corresponds to |
65 |
whatever music you're listening to at the moment on any client (e.g. |
66 |
spotify web, or media-sound/spotify via dbus). Here and there I helped |
67 |
the developer of Vidify with some bugs I found, and I translated his |
68 |
website to my native language (Dutch). In ::guru, I still maintain |
69 |
media-video/vidify and dependencies such as dev-python/tekore, |
70 |
net-misc/lyricwikia, dev-python/httpx, dev-python/uvicorn, |
71 |
dev-python/python-vlc, dev-python/python-mpv and dev-python/pydbus. |
72 |
|
73 |
Because I noticed that contributions to GURU's dev branch were not being |
74 |
merged to the master branch, I requested to become a Trusted Contributor |
75 |
to ::guru in early-March (https://bugs.gentoo.org/711868). My request |
76 |
was granted, and from that moment on I've been reviewing commits from |
77 |
other Contributors to GURU's dev branch a couple of times each week, and |
78 |
providing feedback where necessary, before merging them to the master |
79 |
branch. Among others, I also added ebuilds for media-tv/droidcam, |
80 |
games-action/multimc and games-action/minecraft-launcher to ::guru. |
81 |
|
82 |
Nearing the end of March, I discussed with @mgorny and @juippis the idea |
83 |
of mentioning the GURU project in Pull Requests to ::gentoo that only |
84 |
add 'new packages'. My hope was that this would reduce somewhat the huge |
85 |
amount of PRs assigned to the proxy-maint project, and at the same time |
86 |
increase the amount of contributions to, and popularity of, the GURU |
87 |
project. Initially, I did this manually by leaving comments on the 'new |
88 |
package' Pull Requests, but together with @mgorny we automated this: |
89 |
https://github.com/mgorny/assign-pull-requests/commit/f2115b4f253d55a1fd63dbe77165aec5174069e9 |
90 |
. This has resulted in a steady stream of new Contributors to ::guru. |
91 |
|
92 |
In April, @juippis opened a discussion on adding some common guidelines |
93 |
for the GURU project (https://github.com/gentoo/guru/issues/5). After |
94 |
discussing some basic rules and regulations with the community of |
95 |
Contributors, I wrote a draft README.md for the ::guru repository, which |
96 |
I committed to the repository early in May, and can be viewed on the |
97 |
::guru GitHub mirror: https://github.com/gentoo/guru . |
98 |
|
99 |
This week I finished the first draft version of my thesis, and therefore |
100 |
I now have a lot of extra time on my hands. I would like to spend this |
101 |
extra time learning even more about ebuilds/portage/Gentoo, and |
102 |
hopefully become a Gentoo developer at some point. I read the 'Becoming |
103 |
a Developer' section on the Gentoo website, and took a quick look at the |
104 |
quiz linked there, and I feel like I could answer a lot of the questions |
105 |
in there. Though there are also some that I do not know how to answer, |
106 |
and therefore still require more studying and reading on my part. |
107 |
|
108 |
I read that I have to find a mentor, and I was hoping either @juippis, |
109 |
@mgorny, @heroxbd or @hartwork (who I have CC'ed) would have the time to |
110 |
do that. |
111 |
|
112 |
Best Regards, |
113 |
Andrew |
114 |
|
115 |
P.S. Sorry for the really long email, I felt like I needed to describe |
116 |
my past involvement in the Gentoo community, but the length of the email |
117 |
might have gotten a bit out of hand. |
118 |
|
119 |
-------- Forwarded Message -------- |
120 |
Subject: Re: Interested in becoming a Gentoo developer |
121 |
Date: Tue, 18 Aug 2020 12:37:29 +0200 |
122 |
From: Andrew Ammerlaan <andrewammerlaan@××××××.net> |
123 |
To: Benda Xu <heroxbd@g.o>, Joonas Niilola <juippis@g.o> |
124 |
CC: recruiters@g.o, Michał Górny <mgorny@g.o>, |
125 |
sping@g.o |
126 |
|
127 |
|
128 |
Hi all, |
129 |
|
130 |
Thank you for your replies and kind words :) |
131 |
|
132 |
On 18/08/2020 01:09, Benda Xu wrote: |
133 |
> Hi Joonas, |
134 |
> |
135 |
> Thanks for informing us. |
136 |
> |
137 |
> Joonas Niilola <juippis@g.o> writes: |
138 |
> |
139 |
>> To all other CCd members: Andrew is definitely an upcoming candidate for |
140 |
>> becoming an official developer. I acknowledge the work he's done for |
141 |
>> Guru and Proxy-maint projects so far, and can vouch for him. He's also |
142 |
>> been polite in his interactions with us, and everyone he's been guiding |
143 |
>> so far. |
144 |
>> |
145 |
>> To Andrew: Sorry I'm currently not in a position to mentor. It's good to |
146 |
>> see you peeked at the quiz. If you can comfortably answer the questions |
147 |
>> without having to search too much to tackle them, that's a good sign. |
148 |
>> I'd personally still like you to get more experience first. |
149 |
>> |
150 |
>> Note: I'm not a recruiter so everything below this line is just my view |
151 |
>> on things, they can either be regarded or disregarded, but should |
152 |
>> possibly give you some tips how to continue. I just wanted to reply in |
153 |
>> case no one else has yet: |
154 |
>> |
155 |
>> So far your activity consists of basic package maintenance in ::gentoo |
156 |
>> and managing Guru overlay. You have 120 commits in 8 months to ::gentoo, |
157 |
>> and you had a short period where you were reviewing Github pull requests |
158 |
>> for ::gentoo repo. You've kept Guru clean and merged other user commits |
159 |
>> to master branch. |
160 |
>> |
161 |
>> I'd suggest you to try help projects that are close to packages you use |
162 |
>> / are interested in. Looking at your previous contributions, I'd say |
163 |
>> python and science projects would be closest. Something a bit more |
164 |
>> technical than version bumps through proxy-maint. Not saying you should |
165 |
>> attempt to fix any/every bug in bugzilla, but check what packages you |
166 |
>> use, which projects maintain them and if there is a call for aid from |
167 |
>> them. That'd make you more visible for others, too. It's always better |
168 |
>> to focus on packages you use, because you see the outcome and have |
169 |
>> experience of them. |
170 |
> Cool. The science project welcomes Andrew to join. We have worked with |
171 |
> Andrew since at least the beginning of this year. His contributions |
172 |
> were of high quality. |
173 |
|
174 |
It would be awesome to join the science project. Scientific/python |
175 |
packages are indeed the packages I am most involved with. |
176 |
I'm currently working on another major version bump of spyder-5.0, which |
177 |
introduces some new dependencies, and hopefully python3.8 compatibility |
178 |
(it's another huge PR I'm afraid). |
179 |
|
180 |
>> I know you had that eclass you wanted to push and we'd need to finish |
181 |
>> checking it... I'm not 100 % convinced about it yet. But let's finish |
182 |
>> it. Just keep doing what you do and be yourself, you'll get there! |
183 |
I indeed still have an open PR for a version bump of mkdocs and adding |
184 |
the docs.eclass. The PR might have gotten slightly out of date in the |
185 |
meantime, but I'll update it to the latest version once I get a green |
186 |
light on the eclass. |
187 |
|
188 |
As far as the eclass itself is concerned, it has been in ::guru for some |
189 |
time and it has been doing what it should be doing, though it might |
190 |
indeed need some more work as it probably is not perfect yet. It would |
191 |
be awesome if I could get some feedback on it. I already sent it to the |
192 |
mailing list once, but I suppose I could send it a second time. |
193 |
|
194 |
Best regards, |
195 |
Andrew |
196 |
|
197 |
-------- Forwarded Message -------- |
198 |
Subject: Re: Interested in becoming a Gentoo developer |
199 |
Date: Tue, 18 Aug 2020 08:19:45 +0200 |
200 |
From: Michał Górny <mgorny@g.o> |
201 |
Organisation: Gentoo |
202 |
To: Andrew Ammerlaan <andrewammerlaan@××××××.net>, recruiters@g.o |
203 |
CC: Joonas Niilola <juippis@g.o>, heroxbd@g.o, |
204 |
sping@g.o |
205 |
|
206 |
|
207 |
Hi, |
208 |
|
209 |
On Sat, 2020-08-15 at 16:36 +0200, Andrew Ammerlaan wrote: |
210 |
> [...] |
211 |
> |
212 |
> I read that I have to find a mentor, and I was hoping either @juippis, |
213 |
> @mgorny, @heroxbd or @hartwork (who I have CC'ed) would have the time |
214 |
> to do that. |
215 |
> |
216 |
|
217 |
I can vouch for Andrew as well. He's going to be a great new member |
218 |
in our community. |
219 |
|
220 |
However, with my current workload I can't really mentor you full-term. |
221 |
Nevertheleess, if you need some extra help, please don't hesitate |
222 |
to ping me. |
223 |
|
224 |
-- |
225 |
Best regards, |
226 |
Michał Górny |