Hi,
the deadline is now *soon*.
See bellow some new comments, and some old comments reasserted.
jvoisin wrote (04 Apr 2012 11:14:05 GMT) :
> Please found attached the current version of my proposal to review.
The "preference USB stick" term is not defined, and does not match
what we've been using to describe the Tails persistence storage.
Either use commonly agreed terms, or explain how and why what you mean
is different. Also, you use the "configuration USB stick" wording
somewhere else.
> 5.1 Persistence
I guess you plan to use the persistence feature that will be shipped
in Tails 0.11, but this is left for the reader to guess. I think it
should be made explicit.
> 5.3 Boot process
I think some steps are missing:
* when is the persistent storage passphrase asked to the user?
* when is the persistent storage unlocked, and persistence
feature activated?
(FYI this is done, in Tails 0.11, at tails-greeter time, by
unlocking the LUKS volume and running the live-persist program).
> 5.5 Services
* I think "etherpad" is the name of a specific piece of software, and
not (yet) of a feature. The "collaborative text editing" wording
would look clearer to me, when you're talking of this feature,
implemented by another piece of software
> 5.8 GUI
> * Setup of the persistence USB stick
Tails 0.11 will ship a GUI that already does exactly this part.
> 7. Timeline
> 3nd iteration (sic) - Remote administration
How is the user supposed to authenticate as root to the SSH server?
> 6th iteration Install a gobby service
> This step does not involve any configuration of the service, only
> the setup : no user interactions are involved during this milestone,
> since there is no configuration involved.
Is protecting the Gobby service with a password postponed to step #7?
> 7th iteration Basic configuration management
> The user should be able to edit the configuration of the Gobby
> service during the creation of the Tails server USB stick.
What configuration are you thinking of?
Random comments:
* In Debian, a "package manager" is something like APT. I think you
rather intend to ask package *maintainers* to add debconf options.
* The Wheezy release is *not* planned for June. The freeze is.
* My remarks about sobby vs. infinoted-0.5, were not taken into account
at all, so this part of your text still feels seriously wrong.
See my email sent on Fri, 30 Mar 2012.
* I see no clear explanation of the actual configuration management
problem you're trying to solve. I asked this explanation on Sun, 25
Mar 2012.
* s/debian/Debian/
* s/Ssh/SSH/, again.
* s/packet/package/, again.
* s/will me/will be/
* s/tails/Tails/
* s/starup/startup/
* more generally, a spell check pass would be welcome
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
