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
2018-12-04 20:09:22 ~japaric I think the chapter covers more than what was planned in #9
17
+
2018-12-04 20:09:37 ~japaric so let's close #9
18
+
2018-12-04 20:09:43 @jamesmunns :+1:
19
+
2018-12-04 20:09:46 @korken89 sgtm
20
+
2018-12-04 20:10:23 ~japaric 5 - debugonomicon; any updates there?
21
+
2018-12-04 20:10:52 Hamilton2 May I jump in and ask japaric a couple of unrelated question to the meeting? :)
22
+
2018-12-04 20:11:11 @therealprof japaric: Not really IIRC.
23
+
2018-12-04 20:11:28 ~japaric Hamilton2: could you wait until the meeting is over?
24
+
2018-12-04 20:11:32 Hamilton2 ok :D
25
+
2018-12-04 20:11:46 @korken89 Nothing new sadly, I have had little time since last meeting to work on it
26
+
2018-12-04 20:12:16 @korken89 There are a lot of open issues if someone wants to take a stab as well, all help is welcome :)
27
+
2018-12-04 20:12:44 @therealprof Yeah, got plenty of ideas but had little time. Going to brighten up, though,
28
+
2018-12-04 20:13:05 ~japaric korken89: perhaps the debugonomicon should be mentioned in the next newsletter
29
+
2018-12-04 20:13:28 @korken89 This would be awesome, to help bring awareness and hopefully some extra contributions!
30
+
2018-12-04 20:13:46 ~japaric +1
31
+
2018-12-04 20:14:04 ~japaric korken89: there should be an issue for the next newsletter in the blog repo; you can comment over there
32
+
2018-12-04 20:14:19 @korken89 +1, will put a comment there!
33
+
2018-12-04 20:14:38 ~japaric moving on, issue 6 is the showcase site
34
+
2018-12-04 20:15:01 @therealprof \o/
35
+
2018-12-04 20:15:07 ~japaric as mentioned last week a mockup was posted to https://github.com/rust-embedded/showcase/issues/2
36
+
2018-12-04 20:15:39 @therealprof Looks fantastic.
37
+
2018-12-04 20:15:42 ~japaric there has mostly been positive feedback so I'm going to go ahead and set up CI to build the site
38
+
2018-12-04 20:16:33 @korken89 Yeah, looks really good
39
+
2018-12-04 20:17:01 ~japaric if someone wants to give me a hand with #3 (submission template) or #4 (grading rubric) that'd be awesome
40
+
2018-12-04 20:18:12 ~japaric I think that's it for the leftover edition issues
41
+
2018-12-04 20:18:42 ~japaric Rust 1.31 / 2018 edition should be out in 2 days
42
+
2018-12-04 20:18:58 ~japaric we should update some of the book to recommend stable instead of beta by then
43
+
2018-12-04 20:19:06 @korken89 \o/
44
+
2018-12-04 20:19:07 * thejpster will be happy to not have start each workshop explaining how to `rustup install beta`
45
+
2018-12-04 20:19:16 ~japaric :-)
46
+
2018-12-04 20:19:48 ~japaric next issue is about the embedded webpage
47
+
2018-12-04 20:20:00 ~japaric the new rust-lang.org was launched a few days ago: http://beta.rust-lang.org/what/embedded
48
+
2018-12-04 20:20:02 @thejpster I think we have some `extern crate` stanzas which aren't necessary. Or at least I wasn't sure they were neccessary, or that we did a good job of explaining why they were necessary. I'll follow up in the issue.
2018-12-04 20:20:54 ~japaric thejpster: let's discuss that in the issue tracker (panic_handler crates are necessary; cortex-m-rt sometimes may be necessary)
52
+
2018-12-04 20:21:22 ~japaric the embedded webpage is at http://beta.rust-lang.org/what/embedded
53
+
2018-12-04 20:21:34 ~japaric we have the option of adding some code snippets to the page
54
+
2018-12-04 20:21:51 ~japaric the CLI webpage has some code in it http://beta.rust-lang.org/what/cli
55
+
2018-12-04 20:21:59 @korken89 The only thing I don't like is that the "Learn more" buttons do not align xD
56
+
2018-12-04 20:22:36 ~japaric if you have suggestions about what snippets we should add, if any, please comment in https://github.com/rust-embedded/wg/issues/259
57
+
2018-12-04 20:22:48 @jamesmunns korken89: theres an issue open for that already :)
58
+
2018-12-04 20:22:58 @jamesmunns I did ask for it, but it was lower prio than content
59
+
2018-12-04 20:23:03 @korken89 Awesome :D
60
+
2018-12-04 20:23:07 @jamesmunns And I don't know how CSS works.
61
+
2018-12-04 20:23:14 @jamesmunns :)
62
+
2018-12-04 20:23:51 @ithinuel ((hello))
63
+
2018-12-04 20:24:08 ~japaric ithinuel: hello
64
+
2018-12-04 20:24:40 ~japaric re the snippets issue we should make a decision in like one or two weeks
65
+
2018-12-04 20:24:58 ~japaric we can add the snippets before the year ends
66
+
2018-12-04 20:26:03 ~japaric last item on the agenda: svd2rust
67
+
2018-12-04 20:26:10 ~japaric there are a few things blocked on it
68
+
2018-12-04 20:26:18 ~japaric on a new release of it**
69
+
2018-12-04 20:26:36 @therealprof Yeah. And CI is wonky again…
70
+
2018-12-04 20:26:40 ~japaric jamesmunns: was there something you wanted to land before the release?
71
+
2018-12-04 20:26:59 ~japaric we were going to postpone the Cargo features
72
+
2018-12-04 20:27:05 @jamesmunns japaric: I think the last decision was to "push" the cargo features
73
+
2018-12-04 20:27:26 ~japaric therealprof: is it? got a link to failed build?
74
+
2018-12-04 20:27:36 @jamesmunns Yeah, I could strip out the other changes: making all targets generate code in the same way (some currently write to file, some write to stdout), and maybe the Cargo.toml generation
75
+
2018-12-04 20:27:39 * therealprof is looking
76
+
2018-12-04 20:27:46 @jamesmunns But I don't know if anyone wants that by itself.
77
+
2018-12-04 20:27:56 @jamesmunns Let me know if you do, though.
78
+
2018-12-04 20:28:32 ~japaric jamesmunns: it would be nice to make the code generation uniform
79
+
2018-12-04 20:28:41 ~japaric do you have time to make a PR for that?
80
+
2018-12-04 20:28:56 ~japaric otherwise I can a PR from #254, I think
81
+
2018-12-04 20:29:03 @jamesmunns I can do that this week, yeah. Maybe tonight or tomorrow
2018-12-04 20:30:16 ~japaric I have some local breaking changes for the msp430 codegen part of svd2rust that are required to make msp430-rt closer to cortex-m-rt v0.6.x
87
+
2018-12-04 20:30:47 ~japaric if we don't want to block the v0.14.0 release on that we could disable the msp430 target for the v0.14.0 release
88
+
2018-12-04 20:31:08 ~japaric and then enable it again with the required msp430-rt changes
89
+
2018-12-04 20:31:21 ~japaric otherwise those changes would need to wait for v0.15.0
90
+
2018-12-04 20:31:40 ~japaric thoughts?
91
+
2018-12-04 20:32:30 ~japaric I can't land the msp430 stuff right now because it needs to be tested and I don't have a msp430 micro :-)
92
+
2018-12-04 20:33:07 @therealprof I'd prefer if we could unblock cortex-m-rt for now.
93
+
2018-12-04 20:33:55 ~japaric oh yeah, definitively; I think we should release v0.14.0 asap
94
+
2018-12-04 20:34:28 ~japaric the question is if we do what we proposed above for the msp430 or postpone the msp430-rt for v0.15.0
95
+
2018-12-04 20:35:01 @therealprof +1 for the latter
96
+
2018-12-04 20:35:44 ~japaric ok, I'll check with cr1901; if we don't get an answer in time we postpone the msp430-rt for v0.15.0
97
+
2018-12-04 20:36:18 ~japaric that covers all the items in the agenda
98
+
2018-12-04 20:36:32 ~japaric anyone would like to discuss anything in particular?
99
+
2018-12-04 20:37:17 Lumpio- Anything anything?
100
+
2018-12-04 20:37:30 @jamesmunns Compiler fences are maddening.
101
+
2018-12-04 20:37:34 @korken89 I have one thing, is anyone planning to go to embo++?
102
+
2018-12-04 20:37:39 @jamesmunns (or, trying to understand them)
103
+
2018-12-04 20:37:51 @korken89 I talked to the organizers, they are looking for Rust talks in embedded
104
+
2018-12-04 20:37:55 Lumpio- stm32f103xx-hal (or at least some HAL) needs to be on crates.io!
105
+
2018-12-04 20:37:57 ~japaric Lumpio-: anything that would benefit from being discussed during a meeting :-)
106
+
2018-12-04 20:38:11 hannobraun korken89: Me an Matthias Endler are planning to submit a proposal for a workshop.
107
+
2018-12-04 20:38:42 hannobraun I opened a GitHub issue a while back (I think you've seen it), but haven't heard about anything else.
108
+
2018-12-04 20:38:47 @thejpster korken89, I'm general unhappy about conferences that can't cover costs. It does limit speakers to those who are relatively well-off.
109
+
2018-12-04 20:38:52 @jamesmunns If anyone has feelings about when OxidizeConf should/shouldn't be, and aren't able to pre-purchase a ticket, feel free to DM/email me
110
+
2018-12-04 20:39:11 @jamesmunns (we also will be covering speaker costs)
111
+
2018-12-04 20:39:24 @thejpster jamesmunns, my boss wanted me to ping him a link to your conference. I think they're interested in supporting it.
112
+
2018-12-04 20:39:26 @korken89 hannobraun: Perfect, I talked to the organizer and there should be no problems
113
+
2018-12-04 20:39:27 Jacob_____ I wouldnt hold up svd2rust at all but Id like to see library/programmatic usage merged https://github.com/rust-embedded/svd2rust/pull/214
114
+
2018-12-04 20:39:38 @korken89 thejpster: The ticket to the conference is covered
115
+
2018-12-04 20:39:46 @korken89 However, not sure about the rest
116
+
2018-12-04 20:40:15 @korken89 jamesmunns: That's really good
117
+
2018-12-04 20:40:16 @jamesmunns I would love to see you all there, at least for the Impl days, even if you have no interest in Talks/Workshops :)
118
+
2018-12-04 20:40:22 ~japaric Jacob_____: I'll review your PR later today
119
+
2018-12-04 20:40:41 @jamesmunns thejpster: I'll send you a PM, but oxidize@ferrous-systems.com is the best place to reach out for sponsorship info
120
+
2018-12-04 20:41:18 Jacob_____ @japaric I closed mine and Im aligned with tones111 older pr now. Though hes not exporting the build.rs which is something I can separately pr or whatever
121
+
2018-12-04 20:41:31 hannobraun jamesmunns: I'll be there if at all possible. Don't have anything non-optional in my calendar in April and May so far.
122
+
2018-12-04 20:41:45 Jacob_____ I think this is covered in the conversation there just wanted to point out I am still interested in it
123
+
2018-12-04 20:42:01 @korken89 jamesmunns: As long as it does not collide with embo++ I will most likely join :)
124
+
2018-12-04 20:42:07 @jamesmunns Jacob_____: I'll take a look at your PR too, and see if I can mesh my changes with what you have proposed
125
+
2018-12-04 20:42:09 @therealprof My calendar is already filling up for next year. If I can fit it in I'll be there.
126
+
2018-12-04 20:42:30 @therealprof Requires a date(ish) though…
127
+
2018-12-04 20:42:31 @jamesmunns Looks like embo++ is in March, so definitely shouldn't be a problem
128
+
2018-12-04 20:43:03 @jamesmunns Yup, still a WIP. hoping to have something concrete by end of year, hopefully before the 24th
129
+
2018-12-04 20:43:12 @korken89 \o/
130
+
2018-12-04 20:43:34 hannobraun korken: Just do what I did and block out all of April and May in your calendar ;)
131
+
2018-12-04 20:43:46 hannobraun korken89, I mean
132
+
2018-12-04 20:44:08 @korken89 :D
133
+
2018-12-04 20:44:21 @korken89 I need to start saving money for all the travels ^^
134
+
2018-12-04 20:45:34 * therealprof buys some time
135
+
2018-12-04 20:47:09 ~japaric I'm sensing some radio silence so I think we can finish this meeting early today
136
+
2018-12-04 20:47:30 @therealprof Do we have a plan for svd2rust?
137
+
2018-12-04 20:47:53 @therealprof Anything we need to do when 2018 edition lands?
138
+
2018-12-04 20:48:03 @thejpster Party like it's ... 2018?
139
+
2018-12-04 20:48:20 ~japaric therealprof: we can ship svd2rust after jamesmunns lands the PR cleaning up the file generation
140
+
2018-12-04 20:48:30 @thejpster Off topic - who wants to see Monotron do a directory listing from an SD card?
141
+
2018-12-04 20:48:42 @jamesmunns thejpster: I do, I do!
142
+
2018-12-04 20:48:43 ~japaric therealprof: you can open some champagne when the 2018 edition is out ;-)
143
+
2018-12-04 20:48:50 @therealprof thejpster: Bring it on. :-D
2018-12-04 20:49:16 @jamesmunns oh, if resource team people are here, please check the github team chat
146
+
2018-12-04 20:49:41 @therealprof japaric: Champagne is checked but I meant do we need to immediately follow with some updates to website, org site, books, twitter?
2018-12-04 20:50:15 @jamesmunns I am behind on newsletters, but let me know if anyone wants tweets
149
+
2018-12-04 20:50:32 @jamesmunns Or, let me know if you want access to the twitter account (must be a resources team member)
150
+
2018-12-04 20:50:51 @therealprof No time to learn how twitter works…
151
+
2018-12-04 20:50:54 @therealprof :-D
152
+
2018-12-04 20:51:41 hannobraun therealprof: Like most social media, it works best if you don't have an account and think very little about it.
153
+
2018-12-04 20:52:04 @therealprof hannobraun: That I can do. :-D
154
+
2018-12-04 20:52:16 ~japaric therealprof: we can tweet the docs site when the edition is out and the embedded web page when the new r-l.o site is launched
155
+
2018-12-04 20:52:22 hannobraun therealprof: Always happy to help :)
156
+
2018-12-04 20:52:51 @korken89 Is there an open issue for the next newsletter? I can't seem to find it
2018-12-04 20:53:13 @therealprof japaric: The last few svd2rust PRs and updated didn't seem to get picked up by CI.
159
+
2018-12-04 20:53:18 @jamesmunns but uh... yeah, I'm a bit late.
160
+
2018-12-04 20:53:44 @korken89 jamesmunns: Thanks!
161
+
2018-12-04 20:55:49 ~japaric therealprof: also there will be a blog post about the 2018 edition on the Rust blog featuring the domain WGs, which I forgot to mention last week since I wasn't here ;-)
162
+
2018-12-04 20:56:27 @jamesmunns japaric: oh, did we need to approve anything about that? They pinged us to review the copy, but I don't think I ever responded
163
+
2018-12-04 20:56:36 ~japaric jamesmunns and I provided the content
164
+
2018-12-04 20:56:44 ~japaric jamesmunns: I reviewed the text
165
+
2018-12-04 20:56:54 @jamesmunns :+1: tyvm
166
+
2018-12-04 20:57:37 @therealprof Nice.
167
+
2018-12-04 20:59:36 ~japaric that's it for this meeting; thanks everyone for attending; have a great week and see you next Tuesday!
0 commit comments