[arch-dev-public] Junior Devs
Hi guys, This was brought up a few times, so I'd like some clarification. What restrictions (apart from the possibility of getting the boot, and no read-access to arch-dev) do we put on Junior devs? It used to be that they could not push packages, but that is no longer a technical limitation. Should we still enforce it? Is there a restriction with respect to [core]? My preference would be to not have any limitation, but that they should be instructed to bring things up on ML / IRC when doing stuff for the first time to avoid problems. Cheers, Tom
Am 03.06.2013 16:37, schrieb Tom Gundersen:
Hi guys,
This was brought up a few times, so I'd like some clarification.
What restrictions (apart from the possibility of getting the boot, and no read-access to arch-dev) do we put on Junior devs? It used to be that they could not push packages, but that is no longer a technical limitation. Should we still enforce it? Is there a restriction with respect to [core]?
On the new server, repo access and ftp access are using the same group. There is no special group for [core] access either.
On Mon, Jun 3, 2013 at 4:48 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Am 03.06.2013 16:37, schrieb Tom Gundersen:
Hi guys,
This was brought up a few times, so I'd like some clarification.
What restrictions (apart from the possibility of getting the boot, and no read-access to arch-dev) do we put on Junior devs? It used to be that they could not push packages, but that is no longer a technical limitation. Should we still enforce it? Is there a restriction with respect to [core]?
On the new server, repo access and ftp access are using the same group. There is no special group for [core] access either.
Makes it simple then. So the only question remains, do we want to tell people "don't do that", or not? -t
On Mon, Jun 03, 2013 at 04:37:44PM +0200, Tom Gundersen wrote:
Hi guys,
This was brought up a few times, so I'd like some clarification.
What restrictions (apart from the possibility of getting the boot, and no read-access to arch-dev) do we put on Junior devs? It used to be that they could not push packages, but that is no longer a technical limitation. Should we still enforce it? Is there a restriction with respect to [core]?
Junior devs do not have access to arch-dev, and they cannot write to [core]. However, I think these same limitations apply to new devs as well (at least, they applied to me and others).
My preference would be to not have any limitation, but that they should be instructed to bring things up on ML / IRC when doing stuff for the first time to avoid problems.
Some random thoughts: The only real difference that I can see between a full fledged dev and a junior is the presence of a mentor. This is probably something we should provide for all new devs, junior or not -- likely the same person who proposed their recruitment, similar to how TUs operate. Of course, I suspect that most people we "hire" wouldn't need such a mentor -- they're all smart ponies who probably just need a nudge in the right direction learning to grapple with the mess that is our SVN/repo setup. I tend to think I'm in support of getting rid of the "junior dev" title, but I do think that we should retain some sort of small grace period for all new devs. d
On 06/03/2013 05:37 PM, Tom Gundersen wrote:
Hi guys,
This was brought up a few times, so I'd like some clarification.
What restrictions (apart from the possibility of getting the boot, and no read-access to arch-dev) do we put on Junior devs? It used to be that they could not push packages, but that is no longer a technical limitation. Should we still enforce it? Is there a restriction with respect to [core]?
My preference would be to not have any limitation, but that they should be instructed to bring things up on ML / IRC when doing stuff for the first time to avoid problems.
Cheers,
Tom
Junior dev was used only when we have invited users straight from the community when we needed help in some areas back in the days and they didn't had any idea what's going on. Is not the case when TUs are brought in our dev team. -- Ionuț
On 3 June 2013 23:23, Ionut Biru <ibiru@archlinux.org> wrote:
On 06/03/2013 05:37 PM, Tom Gundersen wrote:
Hi guys,
This was brought up a few times, so I'd like some clarification.
What restrictions (apart from the possibility of getting the boot, and no read-access to arch-dev) do we put on Junior devs? It used to be that they could not push packages, but that is no longer a technical limitation. Should we still enforce it? Is there a restriction with respect to [core]?
My preference would be to not have any limitation, but that they should be instructed to bring things up on ML / IRC when doing stuff for the first time to avoid problems.
Cheers,
Tom
Junior dev was used only when we have invited users straight from the community when we needed help in some areas back in the days and they didn't had any idea what's going on.
Is not the case when TUs are brought in our dev team.
-- Ionuț
Yeah, precisely that. At least, TUs are expected to know our packaging infrastructure and practices well enough to not need mentoring, so IMO there really is little reason for a juniour title in these cases unless we specifically want to be sure of their competence. And, we don't get access to things unnecessarily; if you don't package for core there is no need for access there. -- GPG/PGP ID: C0711BF1
On 4 June 2013 02:48, Rashif Ray Rahman <schiv@archlinux.org> wrote:
And, we don't get access to things unnecessarily; if you don't package for core there is no need for access there.
I'm told this is no longer the case, so all is well -- folks will have the power to bring down core as well :) -- GPG/PGP ID: C0711BF1
participants (5)
-
Dave Reisner
-
Ionut Biru
-
Rashif Ray Rahman
-
Thomas Bächler
-
Tom Gundersen