Project

General

Profile

Feature #15864

Make onboarding of new developers easier

Added by u about 1 year ago. Updated 6 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
08/30/2018
Due date:
% Done:

0%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:
Starter:
Affected tool:

Description

We need to define how to do that first. Initial ideas coming from the experience of onboarding new FT members in 2018:

  • improve doc for new code contributors
  • ISO build troubleshooting doc: issue → solution/workaround
  • clarify expectations e.g. build an ISO to test your proposed changes

Team: foundations team; assist: ignifugo


Related issues

Related to Tails - Bug #14516: Lower technical requirements for new contributors Confirmed 08/30/2017
Related to Tails - Feature #7036: Move custom software to main git repo In Progress
Related to Tails - Feature #15342: Add option to our build system for caching the wiki In Progress 02/22/2018
Related to Tails - Feature #8477: config/chroot_local-hooks/10-tbb: please retry a failed download Confirmed 12/23/2014
Related to Tails - Bug #16639: Output of the ISO/IMG build is confusing Confirmed
Related to Tails - Bug #16355: Test suite: please detect and warn about “Known issues”… In Progress 01/14/2019
Related to Tails - Bug #16617: Document "options kvm_intel nested=1" Resolved

Associated revisions

Revision 02c43ba4 (diff)
Added by intrigeri 6 months ago

Allow submitting code for review without waiting for Jenkins to run the entire test suite.

Let's explicitly allow submitting a branch immediately after running the
relevant test suite scenarios locally. This should make it possible for
a developer to start working on a ticket and submit the resulting branch for QA
in one single work session: while the branch builds on Jenkins, one can run the
relevant test suite scenarios locally. I hope this can lower the amount of WIP
developers carry and the number of context switches they have to do
(refs: #15864).

Worst case, we'll notice any test suite regression after the merge;
we can then revert the merge and nicely ask the branch submitter
to fix the regression before we merge it again.

History

#1 Updated by intrigeri about 1 year ago

  • Related to Bug #14516: Lower technical requirements for new contributors added

#2 Updated by intrigeri about 1 year ago

  • Subject changed from FT: Make onboarding of new developers easier to Make onboarding of new developers easier
  • Description updated (diff)
  • Assignee deleted (intrigeri)

#3 Updated by intrigeri 6 months ago

  • Related to Feature #7036: Move custom software to main git repo added

#4 Updated by intrigeri 6 months ago

  • Related to Feature #15342: Add option to our build system for caching the wiki added

#5 Updated by intrigeri 6 months ago

  • Related to Feature #8477: config/chroot_local-hooks/10-tbb: please retry a failed download added

#6 Updated by intrigeri 6 months ago

  • Related to Bug #16639: Output of the ISO/IMG build is confusing added

#7 Updated by intrigeri 6 months ago

  • Status changed from Confirmed to In Progress

#8 Updated by intrigeri about 2 months ago

  • Related to Bug #16355: Test suite: please detect and warn about “Known issues”… added

#9 Updated by intrigeri about 1 month ago

  • Related to Bug #16617: Document "options kvm_intel nested=1" added

Also available in: Atom PDF