Hi, sajolida: > NB: I'm putting Cody in copy again.
(So I'll do the same and will ignore the "Please answer to tails-project only" part of your initial email.) > intrigeri: >> sajolida: >>> We brainstormed on this with Cody today and came up with a plan to >>> improve things. >> >> I like your plan. I'll comment inline below. > Thanks for the feedback, I'm glad you like it :) >>> Move "Report an error" as a option to contact us >> >> I don't understand this sentence. > Right now we have three purple headings: > 1. Report an error 2. Request a feature > 3. Get in touch with us > Our proposal is to advertise "Report an error" as a way of contacting us > (by email)... Thanks, now I get it. Clarified on the blueprint. >>> Inline issues from latest release >> >> We did try to inline inc/stable_*_release_notes at some point but then >> we had to revert it due to ikiwiki bugs (#9564, #6907). I suspect that >> this part of your plan would reintroduce exactly the same kind of bugs >> e.g. on /news. IMO it's not merely an implementation detail, but >> rather a matter of taking into account the limitations of our tools >> while designing. > We could also copy the content instead of using inlines: > - I could prepare the replacement of the old list in the branch where I > write the release notes. We have a good process for that so it's not > going to be forgotten. > - We could have a comment in the release notes template to remind us to > update the copy whenever we update this section after the release, > which happens quite often. > It would be a bit more painful for translators, but less painful than > having broken inlines. Worse case, the copies are a bit out of sync > during a release cycle. If we detect that it will be easy to sync the > copies. OK. That's probably the best we can do for now. Cheers, -- intrigeri _______________________________________________ Tails-project mailing list Tails-project@boum.org https://mailman.boum.org/listinfo/tails-project
