Closed lauradereynal closed 8 years ago
Target is May 8th for first version of the report. Adding @sabrinang in the issue to follow.
needs design resource for week of May 4
@cassiemc will review
Hey @LauraReynal @thisandagain – Earlier this week I thought @sabrinang might have time to help but she is on PTO 4/5 days next week. So please lean on me to help with this, especially after Monday (busy day onboarding Jordan and our new contractor). When do you think the content for this will be ready to go?
Hey @cassiemc thanks for the message. I am unsure when the content will be ready for a design review, but it will be probably not be before the end of this heartbeat May8th. Will let you know a couple days in advance when ready for design.
However, there is a bunch of design help needed on some graphics. They would need to happen before the report itself in order to incorporate them. What do you think ? tracking here the design tasks have Sabrina's handle https://github.com/MozillaFoundation/research/issues/47
hey @LauraReynal, @thisandagain filled me in on what needed to be done last week and I think this is a good first task for Jordan. Not sure his Github nick yet but @thisandagain is working with him 1:1 in Portland.
Great. Thanks @cassiemc
I added @lovegushwa as the assignee for the design tickets that were assigned to Sabrina. @LauraReynal perhaps you and @lovegushwa could connect tomorrow morning to talk through the illustrations and diagrams? It would also be nice to have him join us for the draft walkthrough on Thursday.
@LauraReynal status? [flagged!]
Work in progress, moving to next heartbeat.
This will be tackled after Bangladesh and Whistler.
@LauraReynal: status? I'm going to move this to July 17 -- correct if that's wrong. [flagged!]
@LauraReynal is on PTO this week and next so let's bump to the following heartbeat.
Update: This took a backseat to the Gates Foundation proposal. Picking up in the next heartbeat.
Update: made good progress on copy - still needs some work.
For next heartbeat, could we get help from:
Thoughts ?
I can definitely do copy review/writing.
@LauraReynal I want to help with design / fixing up the template a bit more as well.
WFM if @lovegushwa can balance this with the Fundraising work. There is a fundraising workweek this week so his involvement will be minimum at this point. Have updated the RACI above.
Update :
Next week: There will be a lot to do and the week will be dedicated to editing frameworks, layout and copy revisions. I'll be working with Jordan but I already started.
We should be good to publish on Wednesday 19th or Thrusday 20th.
cc/ @davidascher
FYI, design work is tracked here https://github.com/MozillaFoundation/Design/issues/71
:mag: @adamlofting Do you think you would have time to convert the spreadsheet into a couple of pie charts ? Or should I do it manually as for the previous reports? Let me know, im happy to remove you from this bug if you have no time.
@KevZawacki the document is ready for your copy review from page 1 to 48 now if you would like to start. I can ping you later when the rest of the copy is finished. Let me know if this is okay for you :santa: :-)
Update for the universe:
Left to do:
Update: The document has been fully reviewed by Andrew, it's good to go. We've made some good design work with Jordan. I'm meeting with Adam monday. I still have a bunch to do, but I think we can reach our deadline of Wednesday or thrusday the latest. I have started to work on the inDesign document. :racehorse:
@KevZawacki I saw you made some copy edits. Thank you very much. Is the rest of the document good to go, or is there a page I should stop at, when I migrate to inDesign?
Hey @LauraReynal, I'm copyediting pages 20 and onward right now. Will be done before 5 p.m. ET!
We have made some cool progress with @adamlofting today. Check out some graphs below :-) the rest will be in the report.
Update: I have started to work on the layout in inDesign, but the document needs a full copy review before possible to finish. @KevZawacki has been pulled out because of emergencies with Webmaker Launch so this project is likely to be delayed.
Will update regularly on the progress. Thanks !
cc/ @secretrobotron here is the ticket to update if you have time to help on copy edits
@LauraReynal I could do some proofreading this afternoon if you can link me to the latest doc? Realize I might've missed my window with you today!
Update:
Next Step:
@KevZawacki would you mind proof reading / editing this blog post for publishing the report please? https://etherpad.mozilla.org/blogpostchicago
@davidascher @cassiemc @lovegushwa The final document is here, in PDF. https://drive.google.com/open?id=0B0X05aIHuAbec1htMHplMHpuYk0
I am ready to publish as soon as I have your GO, if you'd like to check it out before we send.
@LauraReynal No problem -- just proofed. Good to go!
Thanks @KevZawacki
Here is the latest link for the report https://drive.google.com/open?id=0B0X05aIHuAbeR0RZTUx0cERWVGs
@cassiemc here is the latest link https://drive.google.com/open?id=0B0X05aIHuAbeRlpCM0ZoejVXN0k
Great, I'm reviewing now.
I'm reading it too. First question I have is whether we really want to call it Chicago Report. I understand why we've been using that moniker internally, but I don't think it's a useful title to someone with no context.
I'll come up with some more specific feedback shortly.
Do we have any institutional audiences or partners who expect this in a particular time frame?
I had the same thought about the title @davidascher. Also, I think we should deliver digital pdfs as page-by-page rather than as spreads, but realize that might mean rejigging some of the design.
I agree with the title. It does not make much sense. Let me know if you have many ideas. We don't have any institutional partner waiting on this.
@cassiemc it has been designed with the idea that it would be read with spreads. For example, full page pictures and quotes are facing relevant text etc. Maybe we can switch to single pages for the next one? Or is it really a blocker for this one? Let me know.
If your spreads in InDesign are one wide page, it will likely be a huge pain to reformat everything. I don't think it's worth it.
If your spreads in InDesign are two pages, you can export it as single pages and then configure the PDF to display spreads by default. Users can override it to view single pages, which can make reading easier, particularly on mobile. (True for Adobe and some mobile readers. Not sure about in-Browser PDFs)
I assumed they were 2 pages and could be exported as single but that would take some effort yet to split the designs properly (I could help). If other reports were spreads I'd say don't worry about it and we can fix it next time.
They are 2 pages and they are separable, but as you point out it would be a lot of work. Let's think about it for the next ones if okay with you ?
@cassiemc Feel free to use the inDesign file directly, if you want to try stuff or make direct changes https://drive.google.com/open?id=0B0X05aIHuAbeRlpCM0ZoejVXN0k
ok thanks @LauraReynal !
Overall, lots of great stuff in here!
Biggest critique I have is that needs a thorough copyediting pass by a native english speaker, paying careful attention to gallicisms. Things like the use of "evolve" and "mitigate" which are used differently in French and English.
It's also quite long, although we can probably just deal with that in a separate, summary document.
I have some typographic nits, but the biggest one is that the light typeface is basically unreadable when printed on a home or low-end office printer.
Some of the quotes are amazing and powerful. I'd like to see them displayed on the Mozilla office screens.
Some random notes:
p. 6 - curly quotes instead of straight quotes p. 6 - remove leading space before "Our approach" p. 10 change "evolve" in second paragraph -- I believe that's a gallicism. Same comment about page 25, 50. p. 13 I don't understand the "flavors of blur" heading. p. 14 titling font seems off-template p. 14 "different between users in emerging/mobile-first markets and developed markets" p. 18 "We then combined the resulting list with our data" -- what data? p. 18 whether skills "operate as bridges" feels like a claim that is worth unpacking somehow. p. 22 remove "In Chicago" in second paragraph. p. 22 -- the typeface in the small subtitles in the pull quotes print too lightly on my fairly high end printer. We should make sure the report is printable by normal printers. p. 34 chicago should be Capitalized p. 40 -- Don't think "mitigated" is the right word. That paragraph is a bit hard to understand. p. 40 -- Not Kick, Kik. p. 40 -- first paragraph in second column is repetitive with second para in first column p. 41 first line needs a rewrite
[david's getting bored with keeping detailed notes at this point]
On Thu, Aug 27, 2015 at 1:39 PM, Laura de Reynal notifications@github.com wrote:
They are 2 pages and they are separable, but as you point out it would be a lot of work. Let's think about it for the next ones if okay with you.
— Reply to this email directly or view it on GitHub https://github.com/MozillaFoundation/plan/issues/372#issuecomment-135549502 .
By the way -- once we've done the style copyedit, I'm going to make it mandatory reading for my entire team and recommended reading for all of MoFo. There's a large number of lessons worth reading, digesting and discussing.
On Thu, Aug 27, 2015 at 4:13 PM David Ascher da@mozillafoundation.org wrote:
Overall, lots of great stuff in here!
Biggest critique I have is that needs a thorough copyediting pass by a native english speaker, paying careful attention to gallicisms. Things like the use of "evolve" and "mitigate" which are used differently in French and English.
It's also quite long, although we can probably just deal with that in a separate, summary document.
I have some typographic nits, but the biggest one is that the light typeface is basically unreadable when printed on a home or low-end office printer.
Some of the quotes are amazing and powerful. I'd like to see them displayed on the Mozilla office screens.
Some random notes:
p. 6 - curly quotes instead of straight quotes p. 6 - remove leading space before "Our approach" p. 10 change "evolve" in second paragraph -- I believe that's a gallicism. Same comment about page 25, 50. p. 13 I don't understand the "flavors of blur" heading. p. 14 titling font seems off-template p. 14 "different between users in emerging/mobile-first markets and developed markets" p. 18 "We then combined the resulting list with our data" -- what data? p. 18 whether skills "operate as bridges" feels like a claim that is worth unpacking somehow. p. 22 remove "In Chicago" in second paragraph. p. 22 -- the typeface in the small subtitles in the pull quotes print too lightly on my fairly high end printer. We should make sure the report is printable by normal printers. p. 34 chicago should be Capitalized p. 40 -- Don't think "mitigated" is the right word. That paragraph is a bit hard to understand. p. 40 -- Not Kick, Kik. p. 40 -- first paragraph in second column is repetitive with second para in first column p. 41 first line needs a rewrite
[david's getting bored with keeping detailed notes at this point]
On Thu, Aug 27, 2015 at 1:39 PM, Laura de Reynal <notifications@github.com
wrote:
They are 2 pages and they are separable, but as you point out it would be a lot of work. Let's think about it for the next ones if okay with you.
— Reply to this email directly or view it on GitHub https://github.com/MozillaFoundation/plan/issues/372#issuecomment-135549502 .
@davidascher I will do same with my team, maybe unpack it in a Socratic vidyo seminar? Itching to read myself but waiting on final copy.
Yes finding a way to get people engaged in the inquiry would be great.
On Thu, Aug 27, 2015, 4:40 PM Chris notifications@github.com wrote:
@davidascher https://github.com/davidascher I will do same with my team, maybe unpack it in a Socratic vidyo seminar? Itching to read myself but waiting on final copy.
— Reply to this email directly or view it on GitHub https://github.com/MozillaFoundation/plan/issues/372#issuecomment-135584986 .
Release field report from Chicago research trip. :earth_americas: :
RACI
Phase: Research / Build / Ship Owner: @LauraReynal Decision: @davidascher Lead design:@cassiemc Lead dev: n/a