Project

General

Profile

Feature #8578

Point friendly academic people to research projects that would help Tails

Added by intrigeri over 4 years ago. Updated 3 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
01/07/2015
Due date:
% Done:

10%

Feature Branch:
Type of work:
Communicate
Starter:
Affected tool:

Description

Some nice people working in academia say they can find students who could work on Tails-related things, either as short internships, or as full-blown research projects. We should identify what kind of projects this could be and tell them.


Related issues

Related to Tails - Feature #11898: Have a readable blueprint about randomness in Tails Resolved 11/04/2016

History

#2 Updated by BitingBird over 4 years ago

Should we create a page in contribute about that?

#3 Updated by intrigeri over 4 years ago

Should we create a page in contribute about that?

Yes, I expect that in the end the result of the work this ticket is about will land there.

#4 Updated by intrigeri about 4 years ago

  • Assignee deleted (intrigeri)

#5 Updated by sycamoreone over 3 years ago

#6 Updated by sycamoreone over 3 years ago

  • Blueprint set to https://tails.boum.org/blueprint/Tails_research/

#7 Updated by Dr_Whax over 3 years ago

  • Assignee set to Dr_Whax
  • % Done changed from 0 to 10

I have written up a page and listed various blueprints of research problems that might be of interest in helping us achieve a better Tails. I'll have some back and forth with various people before we announce it officially to the world.

#8 Updated by u over 3 years ago

Eventually consider linking to our New contributor section.

#9 Updated by intrigeri over 3 years ago

  • Status changed from Confirmed to In Progress

Dr_Whax wrote:

I'll have some back and forth with various people before we announce it officially to the world.

How is it going?

#10 Updated by intrigeri over 3 years ago

I wonder if linking to https://research.torproject.org/ would be useful.

#11 Updated by Dr_Whax over 3 years ago

I've added the piece about research on tor to the blueprint. I'll ask symacoreone to give feedback. I'll reply back within 2 weeks.

#12 Updated by Dr_Whax over 3 years ago

  • Assignee changed from Dr_Whax to intrigeri
  • QA Check set to Ready for QA

#13 Updated by intrigeri over 3 years ago

  • Assignee changed from intrigeri to Dr_Whax
  • QA Check changed from Ready for QA to Info Needed

Is there a branch somewhere, that I am supposed to review?

#14 Updated by sycamoreone over 3 years ago

  • Assignee changed from Dr_Whax to intrigeri

AFAIK there is just the blueprint and no branch yet. Should we create a branch before this is "Ready for QA"?

#15 Updated by intrigeri over 3 years ago

AFAIK there is just the blueprint and no branch yet.

Thanks!

Should we create a branch before this is "Ready for QA"?

Not necessarily. For sure, it would help me evaluate the current state of things if I had a clearer idea of what's the plan to integrate this material into our website, but I'm fine with looking at the blueprint and we can iterate from that :)

#16 Updated by intrigeri over 3 years ago

  • Assignee changed from intrigeri to Dr_Whax
  • QA Check deleted (Info Needed)

Great, all this looks mostly good. I wonder if we should perhaps define more precisely the suggested research problems we need help with: just pointing to e.g. https://tails.boum.org/blueprint/randomness_seeding/ might be a bit rough. OTOH, while sometimes it's good to zoom in on a more specific problem to save researchers time, sometimes we would welcome a shiny new solution to the general problem at hand. So perhaps we should keep the links to the blueprints (as a way to introduce the general problem) and, on each of those blueprints, add a "Potential research projects" section that lists more specific problems that we would be glad to see researched? I'm not too sure.

#17 Updated by Dr_Whax over 3 years ago

  • Assignee changed from Dr_Whax to intrigeri

intrigeri wrote:

Great, all this looks mostly good. I wonder if we should perhaps define more precisely the suggested research problems we need help with: just pointing to e.g. https://tails.boum.org/blueprint/randomness_seeding/ might be a bit rough. OTOH, while sometimes it's good to zoom in on a more specific problem to save researchers time, sometimes we would welcome a shiny new solution to the general problem at hand. So perhaps we should keep the links to the blueprints (as a way to introduce the general problem) and, on each of those blueprints, add a "Potential research projects" section that lists more specific problems that we would be glad to see researched? I'm not too sure.

OK, I see, that's a valid point. I'm OK with linking to the blueprints, e.g, randomness_seeding if we would be a bit more verbose on the blueprint and have a short summary of the general problem like you say and add a "potential research projects" section that lists more specific problems.

I think adding a general section makes sense. I have added the following under the research ideas section:

If you have an idea yourself and would like to propose it, please write to us through the tails-dev mailinglist.

What do you think?

#18 Updated by intrigeri about 3 years ago

  • Assignee changed from intrigeri to Dr_Whax

OK, I see, that's a valid point. I'm OK with linking to the blueprints, e.g, randomness_seeding if we would be a bit more verbose on the blueprint and have a short summary of the general problem like you say and add a "potential research projects" section that lists more specific problems.

Please go ahead then :)

I think adding a general section makes sense. I have added the following under the research ideas section:
If you have an idea yourself and would like to propose it, please write to us through the tails-dev mailinglist.
What do you think?

Good.

#19 Updated by u about 1 year ago

  • Related to Feature #11898: Have a readable blueprint about randomness in Tails added

#20 Updated by u about 1 year ago

We should probably update the blueprint just a little bit and then send it to the relevant people? There's not much left to do!

Drwhax: will you take care of this or do you want to unassign yourself?

#21 Updated by Dr_Whax 12 months ago

@u hey, I updated it slightly, if you have any tips on what to remove or add, do let me know and i'll fix it.

#22 Updated by Dr_Whax 12 months ago

  • Assignee changed from Dr_Whax to u
  • QA Check set to Info Needed

#23 Updated by u 12 months ago

  • Assignee changed from u to segfault

Hi @segfault. We've been briefly talking about this, what do you think about this blueprint? Is this sufficient? If not, don't hestitate to add some things.

@muri: thoughts?

#24 Updated by u 12 months ago

Also: should we link this blueprint from somewhere under contribute?

#25 Updated by geb 12 months ago

u wrote:

Also: should we link this blueprint from somewhere under contribute?

+1. Good idea !

u wrote:

We should probably update the blueprint just a little bit and then send it to the relevant people? There's not much left to do!

I can send it to a few friends working in research to have their opinion before publishing it and sharing it more broadly.

But meanwhile, a few suggests :
  • Add a (direct) link to the design spec
  • Add a nice paragraph explaining why people could be interested to do research on Tails: usage, userbase, open design spec, "state of art" tool, and maybe also
  • Try to list nice publications that are using Tails for research purpose.

While none of those suggestions should be blocking, I beleive they could be valuable to add (especially the specs & publication list, which I beleive would be the first thing researchers may look for), through they could be added latter.

If you agree on those suggests and are fine to not wait for publishing, I commit to do it. Please assign it to me once the rest is done.

#26 Updated by u 12 months ago

Hi geb! thanks for your insight. As this is a blueprint you can already edit it yourself (top right corner, mouse over the wrench then click "edit") and this is most welcome :)

#27 Updated by u 12 months ago

  • Assignee changed from segfault to geb

Reassigning to geb so he can work on it.. we are not in a hurry, this blueprint is really old :)

#28 Updated by intrigeri 3 months ago

  • QA Check deleted (Info Needed)

Also available in: Atom PDF