You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
210: add logs and minutes for the last meeting r=therealprof a=japaric
r? @rust-embedded/all (anyone)
Co-authored-by: Jorge Aparicio <jorge@japaric.io>
2018-09-11 20:07:48 @adamgreig (it's rustc and fixed in upcoming nightly)
6
+
2018-09-11 20:08:08 ~japaric first thing is to remind you that there are two open RFCs waiting for review
7
+
2018-09-11 20:08:13 ~japaric they are linked in the paper
8
+
2018-09-11 20:08:23 ~japaric the voting majority one and the Cortex-A team one
9
+
2018-09-11 20:08:32 * japaric hasn't had a chance at look at either
10
+
2018-09-11 20:08:58 ~japaric next we move onto the milestone issues that we didn't cover last week
11
+
2018-09-11 20:09:02 hannobraun Cortex-A isn't awaiting review, if I understand correctly. It's more like a draft.
12
+
2018-09-11 20:09:07 ~japaric jamesmunns: around?
13
+
2018-09-11 20:09:27 hannobraun Well, not awaiting approval, I mean
14
+
2018-09-11 20:10:08 ~japaric hannobraun: ack
15
+
2018-09-11 20:10:26 ~japaric let's skip issue 1 since jamesmunns is not around
16
+
2018-09-11 20:10:38 ~japaric issue 2 I'll tackle this week
17
+
2018-09-11 20:11:09 ~japaric issue 3 and 4 shouldn't be too much work if anyone wants to fix the reported issues
18
+
2018-09-11 20:11:26 ~japaric otherwise I'll try to get to them this week
19
+
2018-09-11 20:12:10 ~japaric for issue 5 we have a PR that turns cortex-m-quickstart into a cargo-generate template
20
+
2018-09-11 20:12:20 @therealprof (y)
21
+
2018-09-11 20:12:27 ~japaric I'm not sure what's the status for the other arches
22
+
2018-09-11 20:12:36 ~japaric I'll ping the other teams on the issue
23
+
2018-09-11 20:13:14 ~japaric issues 6 and 7 are about updating the DNS
24
+
2018-09-11 20:13:16 awygle i feel confident we don't have any for msp430 at the moment
25
+
2018-09-11 20:13:34 ~japaric which should hopefully be fixed this week
26
+
2018-09-11 20:14:03 ~japaric the DNS upgrade should happen this week and we'll probably open a formal PR to create an ops team
27
+
2018-09-11 20:14:17 ~japaric more details in https://github.com/rust-embedded/wg/issues/156
28
+
2018-09-11 20:14:46 ~japaric the last item in the backlog is "communicating absences"
29
+
2018-09-11 20:14:58 ~japaric this is an idea I got from andre-ritcher
30
+
2018-09-11 20:15:16 ~japaric the proposal is to share information about the absences of team members in e.g. a private google calendar
31
+
2018-09-11 20:15:48 ~japaric this information could be used to reduce the voting majority threshold since not all members are around
32
+
2018-09-11 20:16:21 @adamgreig hmm
33
+
2018-09-11 20:16:24 ~japaric and in general it's good to enough if people are not going to be around for extended periods of time, I guess
34
+
2018-09-11 20:16:39 @adamgreig i was imagining the voting majority threshold being to adapt to not all members wanting to vote on an issue rather than not being present to do so
35
+
2018-09-11 20:16:40 ~japaric thoughts on having something of this sort?
36
+
2018-09-11 20:16:45 awygle i see this as interesting but not enormously useful
37
+
2018-09-11 20:16:54 @adamgreig if anything i'd want to postpone major votes if someone's been away a bunch and hasn't had time to look at something
38
+
2018-09-11 20:17:05 awygle probably most useful for japaric and other "core team" members (idk if we have a formal notion of that or not)
39
+
2018-09-11 20:17:11 hannobraun adamgreig: +1
40
+
2018-09-11 20:17:43 @therealprof Not a big fan of a private absence calendar.
41
+
2018-09-11 20:18:09 @korken89 I get a feeling that this can easily be forgotten
42
+
2018-09-11 20:18:41 @adamgreig depending on how we feel about information being semi-public we could just have apologies in issue threads for upcoming meetings
43
+
2018-09-11 20:18:54 @adamgreig but that's both public and still of somewhat questionably utility
44
+
2018-09-11 20:20:38 ~japaric ok, it seems that the idea doesn't have much approval. We can revisit it later, perhaps when andre-richter is around
2018-09-11 20:21:49 ~japaric let's start with issue 9
48
+
2018-09-11 20:22:00 ~japaric there was some progress last week: https://github.com/rust-embedded/book/pull/20
49
+
2018-09-11 20:22:52 ~japaric I have written content for this section that covers writing an embedded program that runs on QEMU; it then covers how to run the program on hardware
50
+
2018-09-11 20:23:04 @theJPster sorry I'm late. Got in late, parcels to collect, dinner to cook...
51
+
2018-09-11 20:23:37 * japaric waves theJPster
52
+
2018-09-11 20:23:42 * theJPster can't find the etherpad
2018-09-11 20:24:32 ~japaric theJPster: currently discussing issue 9
57
+
2018-09-11 20:25:05 ~japaric I hope that land that PR this week after the beta comes out
58
+
2018-09-11 20:25:30 ~japaric oh, and I forgot to mention but panic_handler will be available in the beta that comes out this week
59
+
2018-09-11 20:25:45 ~japaric so you should be able to follow the book using 1.30-beta
60
+
2018-09-11 20:26:10 @theJPster yay
61
+
2018-09-11 20:26:30 ~japaric I'll also be updating discovery and the embedonomicon this week to work with 1.30-beta
62
+
2018-09-11 20:26:51 @korken89 Awesome!
63
+
2018-09-11 20:26:56 @adamgreig +1, yay beta
64
+
2018-09-11 20:28:04 @adamgreig as i mentioned last meeting i expect to have some time this week to have a crack at (some of) concurrency/tips for C/integration with C chapters, though as before if anyone is keen or interested please shout out and take them
65
+
2018-09-11 20:28:05 @therealprof I absolutely love the new #[entry] and #[exception] macros.
66
+
2018-09-11 20:28:41 @adamgreig especially shout if you're interested in doing concurrency as it's probably my least comfortable of the topics
67
+
2018-09-11 20:28:42 ~japaric re issue 9 / section 2. If you have more suggestions about what else to cover leave comments in https://github.com/rust-embedded/book/issues/4
68
+
2018-09-11 20:29:36 ~japaric I think that's it for issue 9
69
+
2018-09-11 20:29:38 @therealprof I've converted both my stm32f042 and nrf51 series of crates to use the latest cortex-m-rt stuff. I'm hoping we can land the #[interrupt] macro as well so we have a complete and ergonomic story.
70
+
2018-09-11 20:30:05 ~japaric picking back up issue 8, which I skipped
71
+
2018-09-11 20:30:18 ~japaric the setup instructions need to be updated
72
+
2018-09-11 20:30:33 ~japaric because of the new PR (#20)
73
+
2018-09-11 20:30:47 ~japaric they have to cover installing cargo-genarate, using the beta, remove gcc, etc.
74
+
2018-09-11 20:31:12 @theJPster :)
75
+
2018-09-11 20:31:35 @theJPster can we get cargo-generate pre-packaged in some way? cargo-foo things are a bit of an ass to build
76
+
2018-09-11 20:31:41 ~japaric I guess I can do that since the requisites are in my head
77
+
2018-09-11 20:31:55 @adamgreig it's sort of a shame cargo-generate requires openssl/cmake be installed i guess
78
+
2018-09-11 20:32:01 ~japaric theJPster: last time I head, the plan was to ship cargo-generate as a built-in Cargo command
79
+
2018-09-11 20:32:15 @adamgreig that'd be nice
80
+
2018-09-11 20:32:29 ~japaric I have also requested to have cargo-add shipped as a built-in Cargo command
81
+
2018-09-11 20:33:08 ~japaric cargo-add issue: https://github.com/rust-lang/cargo/issues/5586 if you want make noise
82
+
2018-09-11 20:33:43 ~japaric I'll check with the cargo team to see if built-in cargo-generate is going to happen
83
+
2018-09-11 20:34:53 ~japaric other than that, issue 8 also has an open PR. I think there's still other stuff to cover in it
84
+
2018-09-11 20:35:36 ~japaric I think that's all for issue 8
85
+
2018-09-11 20:36:23 ~japaric issue 10, we have to decide what else to cover
86
+
2018-09-11 20:36:49 ~japaric I asked on the thread if it would make sense to cover &'static mut T, which is the no-allocator version of Box<T>
87
+
2018-09-11 20:37:09 ~japaric no answer yet, so I'll check back later
88
+
2018-09-11 20:37:16 @therealprof Re: cargo add-ins. cargo-bloat was recently broken for embedded by a cargo dependency update. Swift reaction of the developer after the report fixed the problem by removing the cargo dependency and another update also made it work for embedded again.
89
+
2018-09-11 20:38:46 ~japaric ok, moving on. section 11 saw no progress last week
90
+
2018-09-11 20:39:10 ~japaric I won't have time to work on that this week
91
+
2018-09-11 20:39:30 ~japaric but adamgreig might be able to do some work this week
92
+
2018-09-11 20:39:51 @therealprof It's been hard to keep up with you last week. ;)
93
+
2018-09-11 20:40:42 ~japaric therealprof: I'm busy this week so you'll have an easier time
94
+
2018-09-11 20:41:22 ~japaric ok, next: issues 12 and 13 are waiting for a PR to be reviewed.
95
+
2018-09-11 20:41:35 ~japaric sadly, haven't had a chance to look at it
96
+
2018-09-11 20:42:08 @korken89 Same here, I will start helping a lot more actively after the upcoming Monday (heavy deadlines right now)
97
+
2018-09-11 20:42:19 ~japaric probably won't have time this week either since I'm prioritizing writing / updating books
98
+
2018-09-11 20:42:33 ~japaric so it'd be nice if someone else could take a look
99
+
2018-09-11 20:43:08 @therealprof Where's the PR for 12 and 13?
2018-09-11 20:44:04 @therealprof I'll review it later today.
103
+
2018-09-11 20:44:20 ~japaric therealprof: +1
104
+
2018-09-11 20:44:22 @korken89 Thanks!
105
+
2018-09-11 20:44:37 @therealprof Watched that talk from jamesmunns the other day. That was really a good one.
106
+
2018-09-11 20:45:25 ~japaric next: issues 14 and 15 saw no progress last week
107
+
2018-09-11 20:45:51 ~japaric adamgreig and somewhere else volunteered to write stuff in the coming weeks, iirc
108
+
2018-09-11 20:46:09 @korken89 I was one of the ones volunteering
109
+
2018-09-11 20:46:26 ~japaric korken89: for both?
110
+
2018-09-11 20:46:35 @adamgreig yep, I should have some time this week to have a go, was going to be looking at the two c sections first and potentially then concurrency but if aynone else wants to do any then please do
111
+
2018-09-11 20:46:35 * japaric looks at last week minutes
112
+
2018-09-11 20:46:38 @korken89 14
113
+
2018-09-11 20:46:45 @korken89 (After Monday :) )
114
+
2018-09-11 20:46:53 @adamgreig korken89: i'll start with 15 if you wanna take 14 then :P
115
+
2018-09-11 20:47:11 @korken89 adamgreig: Sure!
116
+
2018-09-11 20:47:17 @adamgreig though 'tips' is probably quite amenable to a bunch of people contributing
117
+
2018-09-11 20:47:45 @korken89 s/Tips/Guidelines
118
+
2018-09-11 20:47:53 @korken89 ?
119
+
2018-09-11 20:48:02 @adamgreig I guess it will be a mix of both
0 commit comments