Tails

#1 Updated by intrigeri 2015-09-14 14:58:32

• Status changed from New to Confirmed
• Type of work changed from Discuss to Contributors documentation

> At first sight we could add this to the" talk to us" section on https://tails.boum.org/contribute/how/code/#index6h1

Note that this section comes from the contribute/talk inline, which is used on quite a few contribute/how/* pages. Is the proposal to add the full mentorship thingie documentation there (and on most of contribute/how/*)? Or to add a link to a dedicated page?

#4 Updated by Anonymous 2015-11-26 02:55:52

• Assignee set to sajolida
• QA Check set to Ready for QA
• Feature Branch set to 451f:tails/doc/10179-mentors

Hi sajolida,

would you be able to review my doc please?

Thanks.

#5 Updated by geb 2016-01-03 22:27:20

• Assignee changed from sajolida to emmapeel

Hi,

Great job u :-)

Some short notes:
1) Maybe the list can be completed, even if guess that it will never cover all cases. For myself i was surprised to see no mention on “debian related work”.
2) Even if it is on the same page, i think that some text and a link to https://tails.boum.org/contribute/#talk can worth it.
i) Saying that people are free to come if they want to discuss.
ii) especialy for all subjects that don’t have a specific mentor. That would also the problem 1).
3) Is there anybody in charge of welcoming people, finding a mentor if no one is explicitely listed and redirecting the person to her/him ? Frontdesk ? If there is, it may worth a mention.

[Assigning the bug to emmapeel as request by u for another rewiew]

#6 Updated by emmapeel 2016-01-04 20:21:41

• Assignee changed from emmapeel to sajolida

I would add a note about mentors hanging out on xmpp.

Also add electrum to anonym’s list maybe?

#7 Updated by Anonymous 2016-01-06 11:23:09

• Status changed from Confirmed to In Progress
• % Done changed from 0 to 20

Thanks for the input, i’ve updated the page in [doc/10179-mentors 8c6f89b].

Now ready for review by sajolida.

#8 Updated by sajolida 2016-01-15 19:30:20

• related to Bug #7047: Further simplify the links on the Contribute session added

#9 Updated by sajolida 2016-01-15 19:30:40

• related to Bug #10708: Have a mapping between parts of Tails and their programming languages added

#10 Updated by sajolida 2016-01-15 19:31:00

• Assignee deleted (sajolida)
• QA Check changed from Ready for QA to Info Needed

* Your “list of things” duplicates much of “Reference documents” and
“Tools for contributors”. I think that such pointers should be
formatted in a way that’s useful for everybody (newcomers and
less-newcomers) as the line between the two don’t really exist
so I propose we merge both lists. See also Bug #7047.

* I was wondering which items should figure in such a list of
mentors. For example, “Documentation”, “Debian”, and “Sysadmin”
already have dedicated pages. So it sounds weird to put the
contact person outside of these pages. But then I also understand
the idea of having all the contact information in the same
place… Another possibility would be to make sure we have contact
information on each of /contribute/how/ and find some formatting
to make it look the same across different sections. Or duplicate
it both in the dedicated page and on single list.

* The rest of your list is about specific tools and this relates to

Bug #10708: before knowing that she will work on Tails Upgrade, a
newcomers needs to know in which programming language it is
written. So I’d like to make sure that your list can be later on
expanded to fix Bug #10708. Maybe we should have a page or a table
listing our different subprojects, their programming languages,
main developers, Redmine view, Git repository, etc. This could
maybe replace part of /contribute/git.

• We spell “Tails Installer”, “Tails Upgrader”, “Tails Greeter”.
• You initially considered creating a separate page but apparently
  changed your mind and decided to put it in /contribute
  directly. What made you change your mind? I’m not against putting
  it in /contribute so I’d like to be convinced :)
• I wonder whether putting nicknames of people will be enough for
  newcomers to know how to contact them. Maybe we should put email
  addresses as well?

#14 Updated by Anonymous 2016-01-27 19:09:50

• Assignee set to sajolida

sajolida wrote:
> * Your “list of things” duplicates much of “Reference documents” and
> “Tools for contributors”. I think that such pointers should be
> formatted in a way that’s useful for everybody (newcomers and
> less-newcomers) as the line between the two don’t really exist
> so I propose we merge both lists. See also Bug #7047.

I’ve merged my list of things with the Tools for contributors.
The thing is, that when I started contributing i wanted some place easy to find all i need. But i’m fine doing this like this.

> * I was wondering which items should figure in such a list of
> mentors. For example, “Documentation”, “Debian”, and “Sysadmin”
> already have dedicated pages. So it sounds weird to put the
> contact person outside of these pages. But then I also understand
> the idea of having all the contact information in the same
> place… Another possibility would be to make sure we have contact
> information on each of /contribute/how/ and find some formatting
> to make it look the same across different sections. Or duplicate
> it both in the dedicated page and on single list.

A lot of contribution areas do not have a dedicated page i believe. And as said, my idea was to make things easier for new contributors, not add more complexity.

> * The rest of your list is about specific tools and this relates to
> Bug #10708: before knowing that she will work on Tails Upgrade, a
> newcomers needs to know in which programming language it is
> written. So I’d like to make sure that your list can be later on
> expanded to fix Bug #10708. Maybe we should have a page or a table
> listing our different subprojects, their programming languages,
> main developers, Redmine view, Git repository, etc. This could
> maybe replace part of /contribute/git.

Sure. As said by intrigeri, this should be done in Bug #10708 then.

> * We spell “Tails Installer”, “Tails Upgrader”, “Tails Greeter”.

Corrected.

> * You initially considered creating a separate page but apparently
> changed your mind and decided to put it in /contribute
> directly. What made you change your mind? I’m not against putting
> it in /contribute so I’d like to be convinced :)

Actually, we decided this during a contributor meeting.

> * I wonder whether putting nicknames of people will be enough for
> newcomers to know how to contact them. Maybe we should put email
> addresses as well?

If we can prevent spamming, I’m fine with putting my address but i think we should then ask all people listed there.

I let you continue on this ticket then?

#15 Updated by Anonymous 2016-01-27 19:11:00

• QA Check deleted (Info Needed)

#16 Updated by sajolida 2016-03-14 18:50:52

• Assignee changed from sajolida to emmapeel

> I’ve merged my list of things with the Tools for contributors.

Thanks!

I pushed some more commits in the main repo to add more sections and
mentors and clean up a bit the list.

> A lot of contribution areas do not have a dedicated page i believe. And as said, my idea was to make things easier for new contributors, not add more complexity.

Sure, the list includes:

• Types of work which have dedicated pages (eg “Documentation”)
• Specific tools that could be covered by Bug #10708, but we’re not there yet.
• Core features (eg “MAC spoofing” or “AppArmor”)

Still I’m not really happy to see that the mentors for Debian related
work are not mentioned on contribute/how/debian.

But I have no good proposal that would work for these three types of
“area of expertise” (“type of work”, “tools”, and “core feature”).

> Sure. As said by intrigeri, this should be done in Bug #10708 then.

Yeap. Hopefully Emma will work on this.

>> * You initially considered creating a separate page but apparently
>> changed your mind and decided to put it in /contribute
>> directly. What made you change your mind? I’m not against putting
>> it in /contribute so I’d like to be convinced :)
>
> Because I thought that it’s not enough info for a dedicated page. But it can become one, in Bug #10708 i guess :)

Understood.

>> * I wonder whether putting nicknames of people will be enough for
>> newcomers to know how to contact them. Maybe we should put email
>> addresses as well?
>
> If we can prevent spamming, I’m fine with putting my address but i think we should then ask all people listed there.

Understood and I’m convinced now.

> I let you continue on this ticket then?

I want more opinions to know if we should merge this as it is now or
solve my concern about not having mentors mentioned on the type of work
pages first.

#17 Updated by emmapeel 2016-08-26 03:26:20

• Assignee deleted (emmapeel)
• Feature Branch changed from 451f:tails/doc/10179-mentors to emmapeel:doc/10179-mentors

Sorry for delay, added some changes, please review

#18 Updated by intrigeri 2016-08-26 04:14:38

• QA Check set to Ready for QA

#19 Updated by Anonymous 2016-09-03 08:59:22

• % Done changed from 20 to 30
• QA Check changed from Ready for QA to Pass
• Feature Branch changed from emmapeel:doc/10179-mentors to 451f:doc/10179-mentors

Ok, reviewed. I’m fine with this right now. Follow-up work should be done on the other ticket. I merged this into my branch and updated it from master. I’ll try to merge this into the main repo myself soonish.

#21 Updated by intrigeri 2016-09-10 05:29:22

• blocks Feature #11772: Frontdesk: Document who to assign tickets to internally added

#22 Updated by elouann 2016-09-12 13:02:39

• blocked by deleted (Feature #11772: Frontdesk: Document who to assign tickets to internally)

#23 Updated by elouann 2016-09-12 13:02:51

• has duplicate Feature #11772: Frontdesk: Document who to assign tickets to internally added

#24 Updated by Anonymous 2016-11-19 11:21:10

• Feature Branch changed from 451f:doc/10179-mentors to doc/10179-mentors

#25 Updated by Anonymous 2016-11-23 22:01:56

• Status changed from In Progress to Resolved
• % Done changed from 30 to 100
• QA Check deleted (Pass)