Feature #15886

Create a "Jobs" page on our website

Added by sajolida 2018-08-31 11:35:32 . Updated 2019-09-27 22:33:18 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_4.0
Start date:
2018-08-31
Due date:
% Done:

100%

Feature Branch:
web/15886-jobs-page
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

We will create a page on our website staying that we are looking for
more contractors to work with us.

When assigning work internally, we would still give priority to people
who are part of the smaller community (tails-summit@) but we’re still
lacking some skills or availability to do more.

These are the profiles that we thought off so far:

  • Front-end web development
  • Visual design, illustrator
  • Accounting
  • DevOps / CI
  • Help desk
  • Technical writer

We would:

  • Continuously collect CVs through that page.
  • Answer kindly to everybody who contacts us (with a template email).
  • Look in that pool when needed.
  • Start working with contractors with a 4 hours project so we see how
    collaborating works while still giving out an interesting piece of
    work.

Subtasks

Related issues

Blocks Tails - Feature #16538: Have illustrations to support our explanation of Tails Resolved 2019-03-06

History

#1 Updated by sajolida 2019-07-29 17:27:54

  • Tracker changed from Bug to Feature
  • Target version changed from 2019 to Tails_3.16

#2 Updated by sajolida 2019-08-22 09:22:06

- Contact: tails-accounting@boum.org.

- Create subpages for open positions.
- Mention briefly other profiles that we might be interested in.

#3 Updated by sajolida 2019-08-31 15:25:28

  • Status changed from Confirmed to Needs Validation
  • Assignee changed from sajolida to intrigeri

Here is a draft.

We could already have 3 consultancy job offers:

  • Technical writer
  • Illustrator
  • Accountant

I propose to start with these and see how it goes.

3 other profiles were also mentioned:

- Front-end web development

- DevOps / CI
- Help desk

I have the feeling that, for these to be useful, we would have to detail a bit more then qualifications that we expect from them. For example, help desk could mean anything and a front-end web development with no experience with static-site generators wouldn’t be really helpful.

I propose to not include them for now, see how it goes with the 3 open job offers, and adjust later.

I didn’t work on the look of the page at all. It’s only meant to be a draft of the structure, ikiwiki tricks, and language. For example, I want to make the section “About Tails” more compact to take less space on all the pages.

I want to link the page from the sidebar. I didn’t do it yet because it forces a full rebuild of the website every time I switch branches in my local build :)

I took inspiration from similar pages from other projects:

#4 Updated by intrigeri 2019-08-31 17:26:41

  • Target version changed from Tails_3.16 to Tails_3.17
  • Feature Branch set to web/15886-jobs-page

Thanks! I probably won’t have time to look into this in the 3.16 cycle though.

#5 Updated by intrigeri 2019-08-31 17:28:19

  • related to #16963 added

#8 Updated by intrigeri 2019-09-04 10:53:15

  • Status changed from Needs Validation to In Progress
  • Assignee changed from intrigeri to sajolida

Great job!

> I propose to not include them for now, see how it goes with the 3 open job offers, and adjust later.

Fine by me.

> I didn’t work on the look of the page at all. It’s only meant to be a draft of the structure, ikiwiki tricks, and language.

So I’ve only reviewed the structure, ikiwiki tricks, and language.

What about adding and tagged(job/open) to the !inline directives?
This would give us an easy way to toggle the visible/hidden status of a given position, yielding nicer Git history than git rm + git revert.

I’m not a big fan of the “Sorry but we don’t have” phrasing. I prefer Signal’s “Sorry, we” and Tor’s “At the moment, we don’t have”. If you feel strongly about it I can live with the current version though.

Should we have an introduction sentence to the “Consultancy jobs” section, before starting the list? (I seem to remember reading something about this sort of things in a style guide.)

s/free software/Free Software/ like in our Social Contract: the capitalized version suggests it’s a well-defined concept, that one should look up if they’re not familiar with it; while the non-capitalized version can easily be (mis)understood as “free as in free beer”. Alternatively, “Free and Open Source Software (FOSS)”, but we don’t use this terminology anywhere else.

I’m not 100% sure about the grammar of “We are a small team that value”; I thought “team” was singular → “values”. Ignore me if you already checked and “value” is correct.

About “mostly in Europe but not only”: I’m not sure it adds much value and I suspect some of us will have bad feelings about it, for privacy reasons (even if this can be deducted from other, publicly available information). So I would be in favor of dropping this.

In “than you day job”: s/you/your/ (← typical example where GitLab/GitHub inline review strive compared to what I’m doing here ;)

IIRC we need sort="age" everywhere to avoid breaking build reproducibility.

What’s the expected benefit of having the !inline directive in wiki/src/tags/job/consultancy.mdwn, as opposed to a link pointing to the relevant page, that’s cheaper to compute?

#9 Updated by intrigeri 2019-09-12 14:25:20

  • Target version changed from Tails_3.17 to Tails_4.0

#10 Updated by sajolida 2019-09-17 00:02:08

> What about adding and tagged(job/open) to the !inline directives?
> This would give us an easy way to toggle the visible/hidden status of a given position, yielding nicer Git history than git rm + git revert.

Done in 1e8c51e38c.

> I’m not a big fan of the “Sorry but we don’t have” phrasing. I prefer Signal’s “Sorry, we” and Tor’s “At the moment, we don’t have”. If you feel strongly about it I can live with the current version though.

Fixed in 193b53ea94.

> Should we have an introduction sentence to the “Consultancy jobs” section, before starting the list?

Nah! It’s good to introduce lists when they are part of a text but here
it’s more of a display mechanism. We have plenty of other lists without
an introduction sentence on the website.

> s/free software/Free Software/ like in our Social Contract

Done in 90a5c8d58d.

> I’m not 100% sure about the grammar of “We are a small team that value”; I thought “team” was singular → “values”. Ignore me if you already checked and “value” is correct.

Indeed! I tend to forget the ‘s’. Fixed in 36d6f8a822.

> About “mostly in Europe but not only”: I’m not sure it adds much value and I suspect some of us will have bad feelings about it, for privacy reasons (even if this can be deducted from other, publicly available information). So I would be in favor of dropping this.

Dropped in 08e9e01753.

> In “than you day job”: s/you/your/

Fixed in 19f5f5185c.

> IIRC we need sort="age" everywhere to avoid breaking build reproducibility.

Fixed in 3b32d5a715.

> What’s the expected benefit of having the !inline directive in wiki/src/tags/job/consultancy.mdwn, as opposed to a link pointing to the relevant page, that’s cheaper to compute?

It’s what ikiwiki generated automatically. Fixed in eb9c3cda75.

I added a bunch of small commits on top and I think that the page is
ready to be published now.

#11 Updated by sajolida 2019-09-17 00:08:41

  • Status changed from In Progress to Needs Validation
  • Assignee deleted (sajolida)

intrigeri, u: You could both do the final validation. There are bits of CSS in there but it’s pretty simple.

Once we’re done with the page itself, we should wait until we have at least 1 redacted job offer to publish it. It’ll be Feature #16538.

#12 Updated by sajolida 2019-09-18 02:02:54

  • blocks Feature #16538: Have illustrations to support our explanation of Tails added

#13 Updated by sajolida 2019-09-18 17:37:34

I’m moving here the comments from Feature #16538#note-7 that relate to the reusable bits of the jobs page.

I’ll process them altogether with the rest of the review for this ticket.

  • “If you want to do other things in life than your day job, Tails is a place for you.” → I would like to rephrase this a bit, something like “If you like flexibility, Tails is a place for you.”
  • “where everybody enjoys comparable salaries and benefits.” → I think we should be careful of not talking about salaries, but instead of “financial compensation”, or “pay”.
  • In How to Apply: “Links to other contributions to free software, GitHub, or GitLab accounts” → add “if applicable” [not to put pressure on people who are merely illustrators].
  • a last missing thing would be to write something along the lines of “We cannot reply to every application. If selected, you’ll hear back from us within a period of 8 weeks.” Feel free to improve!

#14 Updated by Anonymous 2019-09-18 19:15:37

  • Assignee deleted (None)

#15 Updated by sajolida 2019-09-24 20:33:29

> * “If you want to do other things in life than your day job, Tails is a place for you.” → I would like to rephrase this a bit, something like “If you like flexibility, Tails is a place for you.”

Done in 9eb5179d10.

> * “where everybody enjoys comparable salaries and benefits.” → I think we should be careful of not talking about salaries, but instead of “financial compensation”, or “pay”.

Done in 9eb5179d10.

> * In How to Apply: “Links to other contributions to free software, GitHub, or GitLab accounts” → add “if applicable” [not to put pressure on people who are merely illustrators].

This section is meant to be reusable so we don’t have to write it again
each time. Simply Secure had a similar concern that I think is solved in
efcc2c4616 where I’m merging both lines.

> * a last missing thing would be to write something along the lines of “We cannot reply to every application. If selected, you’ll hear back from us within a period of 8 weeks.” Feel free to improve!

I’ll reply to every application. It’s super painful when we don’t hear
back from fundraising applications and I think that sending a template
email to all applicants won’t take much time in comparison with reading
and analyzing all of them, which is something we’ll have to do anyway.

I’ll advertise the design brief and thus the jobs page on Friday. I
think it’s fine if you finish your review after the first publication of
the page.

#16 Updated by Anonymous 2019-09-26 13:20:06

  • Status changed from Needs Validation to In Progress
  • Assignee set to sajolida

All perfect!

#17 Updated by sajolida 2019-09-27 21:14:49

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|24da71889d4283dfc727d40c26f60843bdc9bb64.

#18 Updated by sajolida 2019-09-27 22:33:18

  • Assignee deleted (sajolida)

Thanks!

It’s aliiiiiive now :)