Re: [Tails-dev] Windows 10 theme for Tails/Jessie

[Christian Medel]

Hi,

I have a question for you. Will you be strictly using GNOME-SHELL or 
will the next TAILS include the Cinnamon panel? If that's the case, that 
could fix the GNOME-Panel extension and bring the DE look even more than 
Windows 10.


Ex. http://gnome-look.org/CONTENT/content-pre2/171327-2.png

Cheers,


Le 2015-10-21 10:10, anonym a écrit :

Christian Medel:

Hi,

Hi!

I've added another project member to Cc, since he's the one that (at
least previously) was responsible for this feature. Alan, feel free to
remove yourself if you are not interested any more!

Also, Christian, would you mind us continuing this email exchange on our
public mailing list, tails-dev@boum.org [1]? If so, feel free to respond
to this email to that address instead. If so, please don't trim any of
the content, so the context is kept intact.

[1] You can register here: https://mailman.boum.org/listinfo/tails-dev/
but you can also send emails there without registering -- we'll just
have to remember to keep you Cc:ed. :)


Thanks for your interest in the theme.
I'm very interested in the TAILS project, and upgrading to GNOME 3.14
wouldn't be too hard.

I am very glad to hear this, thanks a lot!

Note though, that there still is no collective decision on that your
theme is the way to go (only my opinion so far). However, I see little
reason for that when the alternative seems to be no Windows theme in
Tails at all, as it stands now. Also, note that we had decided on a
"Windows 8" theme, but honestly, why not 10?


Right now, I'm downloading Jesse to have a place where to test.

Great! As long as you stay stricly using packages from Debian Jessie, it
should fit us perfectly. Let us know of any packages dependencies for
your theme (e.g. I know it needs gtk2-engines-murrine but perhaps there
are more?)


So, yes, I'll be porting this theme to GNOME 3.14. I hope to finish it in
two or three days.

That's fast. :)


I'll probably just lack the GNOME extension from what I read here :
https://tails.boum.org/blueprint/update_camouflage_for_jessie/

Sorry, which "GNOME extension" are you referring to? GNOME Classic? If
so, note that there's no problem if your theme remains a GNOME Shell theme.

Actually, in our blueprint you only need to follow the "Goals and
non-Goals" section, and the "Requirements" section, but replace "Windows
8" with "Windows 10" (and you can ignore the point about Tails Greeter
-- if you make a normal GNOME theme, that will fit that need perfectly).

Next, would you also be interested in (potentially) further refining
your theme? I haven't really had the time to try your theme, and TBH my
only experience with Windows 10 is from screenshots, so I do not know
how closely they match. As you've seen among our goals, we want them to
match quite well, so if there are e.g. some Tails applications (in the
sys tray or task bar) whose icons look very out of place in Windows, the
icon theme may need to "borrow" more icons from Microsoft. :)

BTW, we track this issue as:

 https://labs.riseup.net/code/issues/8064

But there's not much going on there since we've been stuck on the "ask
for help" stage for >half a year. You may want to register an account
there and at least announce your interest in helping us out.

Thanks for your interest!

Cheers!



___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Windows 10 theme for Tails/Jessie

[anonym]

Christian Medel:
> Hi,
> 
> I have a question for you. Will you be strictly using GNOME-SHELL or
> will the next TAILS include the Cinnamon panel? If that's the case, that
> could fix the GNOME-Panel extension and bring the DE look even more than
> Windows 10.

If it is packaged in Debian and can be mixed into GNOME Shell, why not?
So is it? Will it pull in *all* of Cinnamon?

> Ex. http://gnome-look.org/CONTENT/content-pre2/171327-2.png

Is this with or without the Cinnamon panel? It would be helpful to have
screenshots to compare with. Like I've said, I'm not really familiar
with Windows 10's exact look.

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Windows 10 theme for Tails/Jessie

[Christian Medel]

I guess I just booted in a normal Cinnamon session altogether.
The bad thing with SHELL is that it doesn't look at all like windows. 
Even with window list and bottom panels activated, there's no way to get 
a decent taskbar or hide the top bar. No system tray either.


I successfully have tested Windows 10 v0.6.7 in SHELL. It looks just 
like on 3.18, since the theme was originally built for Linux Mint 17.1. 
To answer a previous question, if corrections are needed I will gladly 
do my best to correct them.


This is how Debian looked while in a GNOME 3.14 session :

http://i.imgur.com/wPq01XH.png

some bugs :
- terminal background color & text color
- metacity only for GTK 2.0 apps
- all things said in 2nd paragraph
Le 2015-10-21 11:59, anonym a écrit :

Christian Medel:

Hi,

I have a question for you. Will you be strictly using GNOME-SHELL or
will the next TAILS include the Cinnamon panel? If that's the case, that
could fix the GNOME-Panel extension and bring the DE look even more than
Windows 10.

If it is packaged in Debian and can be mixed into GNOME Shell, why not?
So is it? Will it pull in *all* of Cinnamon?


Ex. http://gnome-look.org/CONTENT/content-pre2/171327-2.png

Is this with or without the Cinnamon panel? It would be helpful to have
screenshots to compare with. Like I've said, I'm not really familiar
with Windows 10's exact look.

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Help needed with screenshots of Mac boot menu with Tails

[Spencer]

Hi,



sajolida:
I want something like this but wonder what the label is with Tails:

http://cdn.osxdaily.com/wp-content/uploads/2014/10/boot-from-os-x-yosemite-installer.jpg



Using a library computer I can see that the label is 'Windows', and 
unlike Kali and the likes, there is no extra EFI volume :)




That's for the instructions on the website.

Bonus point if you manage to send a direct PNG screenshot and not a
photo of the screen but I'm not sure that's possible.



Find those hard drive volume icons and make one yourself (I will if you 
provide some sizing info).  There are two volumes; one labeled 
'Macintosh HD' (if not customized), and one labeled 'Windows'.


Wordlife,
Spencer

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Redmine maintainence Oct. 28, 9:30am EST - Oct. 30

[micah]

Hello!

Over here at riseup we have been sad about the state of redmine, partly
because we know that you fine tails people are also sad about some bugs
in the current implementation. We have been trying to keep with the
Debian provided package of redmine for ease of maintenance, but the
current package doesn't solve the parenting problems that you are having
(among other problems), there isn't an easy way to bring the fixes in
From upstream, and there doesn't look like there will be a new version
in debian any time soon (even if we helped with that process).

So, with heavy hearts, we have decided to migrate from the debian
packaged redmine to the upstream release... and to do that, we need to
schedule some downtime.

We came up with Oct. 28th (wednesday) at 9:30am eastern US time for
starting the upgrade process. This was the best time for us to come
together and work on this. We are expecting the work to not last very
long, but with redmine we have found it best to expect the unexpected,
so we want to schedule the outage for two days, through the 30th, to get
everything worked out before we are done.

 micah


signature.asc
Description: PGP signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Help needed with screenshots of Mac boot menu with Tails

[Spencer]

Hi,



Spencer:
[Something close to correct]



Actually, here[0] is the DVD startup screen, and here[1] is the USB 
Stick startup screen.


These are a hybrid of Yosemite, El Capitan, and whatever came on the 
2009 macs in this library (depreciated startup disk and USB icons appear 
at boot).


Let me know if you would like these adjusted in any way.

Wordlife,
Spencer

[0]: macbootDVD.png
[1]: macbootUSB.png
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Redmine maintainence Oct. 28, 9:30am EST - Oct. 30

[BitingBird]

micah:
> 
> Hello!
> [...]
> We came up with Oct. 28th (wednesday) at 9:30am eastern US time for
> starting the upgrade process. This was the best time for us to come
> together and work on this. We are expecting the work to not last very
> long, but with redmine we have found it best to expect the unexpected,
> so we want to schedule the outage for two days, through the 30th, to get
> everything worked out before we are done.
> 
>  micah
> 
Noted... and thanks very, very much to you and all the others riseup
birds for your amazing work!

Cheers,

 BitingBird (yeah, me too)
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Help needed with screenshots of Mac boot menu with Tails

[sajolida]

Hi,

Could someone with a Mac and a typical OS X install, take a screenshot
of what the boot menu looks like with a Tails USB stick plugged in?
Either installed using `dd`, either installed using Tails Installer
(please specify which one and if that makes a difference).

I want something like this but wonder what the label is with Tails:

http://cdn.osxdaily.com/wp-content/uploads/2014/10/boot-from-os-x-yosemite-installer.jpg

That's for the instructions on the website.

Bonus point if you manage to send a direct PNG screenshot and not a
photo of the screen but I'm not sure that's possible.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Computer Help

[mrcosmic13]

I was wondering is a ThinkPad T410 was usable with Tails? It is listed as a 
computer that will not work but I read that other computers on that list DID 
work. 

Thanks
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Desktop Camouflage

[Spencer]

Hi,

Copying dev since they care.

I am checking in on the status of the camouflage feature for Jessie; is 
anybody porting it?  Last thing I heard was intrigeri about a month ago 
after a dev list reminder.


If not, I can update the relevant Greeter work.  Let me know.

Wordlife,
Spencer

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] More Native English doc fixes

[sajolida]

Jesse W:
> I've gone through the changes to the docs since 1.6 (using this modified
> version of sajolida's suggested git diff command):
> 
> git diff 1.6.. -- wiki/src/\[\^b]\*.{mdwn,html}
> 
> and here's a branch with my fixes: 
> https://gitlab.com/JesseW/tails/commits/doc_fixes3

Merged as well, thanks!

> I'm still waiting on my other doc fix branch to go in, also:
> 
> https://gitlab.com/JesseW/tails/commits/add_doc_contrib_info

Full disclosure: I'm not always as fast as on the first review :)
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] PATCH: Small improvements to contribute/how/documentation.mdwn

[sajolida]

Jesse W:
> As promised in my last email, two small improvements to
> contribute/how/documentation.mdwn 
> 
> https://gitlab.com/JesseW/tails/commits/add_doc_contrib_info

Merged, thanks!

I added two nitpicking on top of you work with:

  - 3235f56 Don't use serial comma in series of two
  - 965ff16 Avoid abbreviations
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Releasing automated tests

[anonym]

[Moving discussion to tails-dev@]

Given the trimming that has happened, some context may have been lost.
The discussion is about that we now, in our Jenkins setup, automatically
test images built from doc/ and web/ branches, which wastes a lot of
time on our isotesters.

> From: intrigeri 
> Date: Tue, 20 Oct 2015 13:08:31 +0200
> 
>> From: bertagaz 
>> Date: Mon, 19 Oct 2015 12:29:26 +0200
> 
>>> From: anonym 
>> 
>>> Still, once we release 1.7, then all doc/ and web/ branches will become
>>> tested. I suspect we will need a permanent fix for only building (not
>>> testing) these branches -- it's useless to test them 99.9% of the time,
>>> and they will block (for ~5 hours) test runs from relevant branches that
>>> got something pushed to them right after them.
> 
>> That's something we didn't decide when during the design round. Sounds
>> doable, but I wonder if there are still some valid points to still test
>> that branches.

True, but there's an overwhelming amount of them, and their
modifications are limited to something that is completely isolated from
most of Tails, the OS, meaning that a huge part of each test run on them
is just a (possibly out-dated) re-run of master/devel/stable depending
on which branch it was based on. That is unlike feature/, bugfix/ and
test/ branches, that need a full run in general. Perhaps you can see
where I'm going:

As an optimization, we could introduce @web and @doc tags, and run the
test suite with `--tag @web` or `--tag @doc` for doc/ and web/ branches,
respectively. Then we could even have automated tests of @web changes
before deploying them by browsing the local wiki in Tails. :)

Note that I may not have the correct understanding of the doc/ vs web/
distinction, so I'd like a clarification just in case so we don't design
something stupid. I suspect that since we don't have any automated tests
for the *website* (as opposed to the docs) we only care about doc/ and
only need to test web/ if we want to start testing the website.

> FTR I dislike the idea of blacklisting such branches based on their
> name. I'm not going to debate it here [...]

Please do it here, then! :) I guess it's related to that you want at
least doc/ branches to be tested, since our automated test suite
actually depend on the documentation (see two quotes below for more on
this).

I wonder if we could have a configuration filem like
config/jenkins_testing, which has settings controlling how the automated
test suite is invoked on Jenkins. I imagine something like this:

ENABLE = {true,false}

Whether to run the test suite at all. Hence, when merging another base
branch into master as part of the release process, we just make sure to
set this to `false` and we're done. When merging master into a base
branch, it must be set to `true`. So it's similar to config/base_branch,
except that it includes master as a special case. Is this problematic?
Won't merge conflicts save us?


If we prefer it, we could implement my tagging idea with this:

CUCUMBER_ARGUMENTS = 

This makes Jenkins invoke run_test_suite with extra CUCUMBER_ARGUMENTS.
And it could be used for the @web/@doc idea above if we have it set to
`--tag @doc` or whatever in master. We could even test master then, in
the same way. We just have to update the release process in the same way
as for the ENABLE setting, but for CUCUMBER_ARGUMENTS.

Since this affects how Jenkins will invoke a script, there's a security
concern vs the shell that has to be considered. Also arbitrary paths can
be given. Hence we probably may want to have this option *instead*:

RUN_WITH_TAGS = 

So if it's set to ["tag1", "~tag2,tag3"] it would be translated to these
distinct arguments:

['--tag', 'tag1', '--tag', '~tag2,tag3']

in the usual safe (i.e. shell-free) list syntax used for exec in many
programming languages (python, ruby, perl...). This would also improve
the situation for @fragile, and also be subject to the same release
process update as ENABLE above.



Note that ENABLE gives an alternative implementation for the problem
that #10389 wants to solve, i.e. "don't run tests for WIP branches". I
think I prefer this approach, so we avoid excessive branch re-naming.

Also note that with the flexibility from
CUCUMBER_ARGUMENTS/CUCUMBER_TAGS we can remove `--tag ~@fragile` from
the Jenkins wrapper script (#10288) by setting it in the config instead.

Using CUCUMBER_ARGUMENTS/CUCUMBER_TAGS the true power users could even
do "focus" testing of specific features/scenarios via a temporary tag
and then making Jenkins only test that tag -- now the test suite will
not waste time on other scenarios. FWIW. I don't think this will play
nicely with our future ideas about Jenkins updating tickets in Redmine
given the test results. That could be fixed if we added another option:

JENKINS_REVIEW = {true,false}

It would be true by default (I guess), and would then enable Jenkins

Re: [Tails-dev] Desktop Camouflage

[sajolida]

Spencer:
> Copying dev since they care.
> 
> I am checking in on the status of the camouflage feature for Jessie; is
> anybody porting it?  Last thing I heard was intrigeri about a month ago
> after a dev list reminder.
> 
> If not, I can update the relevant Greeter work.  Let me know.

Oops, already answered on tails-ux without putting tails-dev in copy:

https://mailman.boum.org/pipermail/tails-ux/2015-October/000695.html
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Desktop Camouflage

[intrigeri]

Spencer wrote (21 Oct 2015 07:21:26 GMT) :
> I am checking in on the status of the camouflage feature for Jessie; is 
> anybody
> porting it?

No, nobody has started any porting work.

Cheers,
-- 
intrigeri
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Desktop Camouflage

[anonym]

intrigeri:
> Spencer wrote (21 Oct 2015 07:21:26 GMT) :
>> I am checking in on the status of the camouflage feature for Jessie; is 
>> anybody
>> porting it?
> 
> No, nobody has started any porting work.

Maybe we are in luck that Windows 10 was released so recently? Generally
such releases seems to motivate themers to make emulation themes, and lo
and behold:

http://gnome-look.org/content/show.php/Windows+10+Theme?content=171327

It is updated very frequently, and the theme seems to match the
screenshots I've seen of Windows 10 quite nicely (better than our
current Windows 8 theme vs the actual thing, imho). This is pretty
promising. I've updated #8064, asking alan for his opinion.

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.