segfault wrote (18 May 2016 13:24:34 GMT) : > sajolida: >> segfault:
>>>> Also, just out of curiosity, when are you planning to work on "Design an >>>> extensible and robust format describing the services and how they >>>> integrate into Tails"? >>> >>> I think this discussion has already started with anonym's mail [1]. I >>> discussed this further with him in XMPP because I had a different design >>> in mind but I think his is better, so I didn't write a mail about this >>> after the chat. I already started implementing and extending the design >>> (I think most shortcomings only become obvious during implementation). >>> Maybe I should send another mail about this. >>> >>> [1] https://mailman.boum.org/pipermail/tails-dev/2016-March/010506.html >> >> You're right and I actually didn't read this thread very carefully >> myself because it was going out of my department. I was thinking that >> for example it would be good to have a blueprint that specifies how to >> describe a new service (the options specific to this service, what needs >> to be made persistent, how to start and stop it, etc.). And anonym's >> email looks like a good start indeed. >> >> This will be useful during the design phase to allow people other than >> anonym and George to review it. For example, I really want intrigeri to >> review your specification because his vision is usually nicely >> complementary to anonym's but I don't expect him to follow our threads. > Ack. Indeed, I'd like to have a look, but I won't follow the entire discussion, so an explicitly RFC will be useful :) > I'm convinced and will start working on a blueprint for the TailsService > and TailsServiceOption designs. :) Yeah :) Cheers, -- intrigeri _______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
