We areĪlready expecting to add the following to SVG:Īs such, I think many of the timesheet use cases could already be You may be interested to know that weĭiscussed some of the timesheet-like use cases today with Silvia. I think it would be easy enough to make it compatible with the existing work you've done. > Meanwhile, I've set aside some time the week of Feb 17 for a my colleagues and I to write up a proposal of what I was suggesting. We would be particularly interested to hear from other members of theĬSS WG and SVG WG on their thoughts on this matter. In the specification or having separate chapters in separate files but In summary, if feels like they should beĬurrently we are considering other options such as putting the API later In particular, adding new features would often requireĮditing both specifications which could become even more complicatedĭown the recommendation track. However, a number of us are concerned about the specifications growing Also, it wouldĪllow the model specification to progress more quickly without being On the positive side splitting the specification would provide a clearīoundary for user agents that do not support scripting. That was my recollection too, but before committing to any particularĬourse we revisited this issue today and recognised a number of > - Continue work on the JS API alongside the "compatibility" specs. > - Split the model description into its own document for now. > My recollection of what we vaguely decided on Thursday was: I'll send out the minutes of what weĭiscussed yesterday in a moment so you can have an idea of what's on the I *might* be available at some times by phone, but I can't be sure. Thanks to everyone who made #rust and #rust-beginners on Mozilla IRC a great place to hang out! We are sad to see it go.> Sorry for the exceptionally late notice, but I cannot attend on Monday. There are still a couple months before shuts down - we’ll work at making this transition as smooth as possible in this time. ![]() You’re also free to create new channels on freenode in accordance with the freenode rules. For people who wish to continue using IRC, there is an unofficial freenode channel which you can hang out in, though we’d like to emphasize that this is not associated with the Rust teams and is not moderated by our Moderation team. ![]() We understand that not everyone wishes to switch to Discord for many reasons. Rust’s official Discord server does have the #users, #help, and #beginners channels that fill in this purpose, and we recommend people start using those. This leaves the #rust and #rust-beginners channels on Mozilla’s IRC network, which are still quite active, that will need a new home when Mozilla’s network shuts down. The few teams that do use IRC are working with us to find a new home, likely a channel on Discord or Zulip. Almost all the Rust teams no longer use IRC as their official discussion platform, instead using Discord or Zulip (as well as a variety of video chat tools for synchronous meetings). Last year a lot of the teams started exploring new communication platforms. They are looking into new options for the Mozilla community, but this does leave the question open as to what the Rust project will do. Mozilla recently announced that it would be shutting down its IRC network, citing a growing maintenance and moderation burden. Over time, the single channel grew into a set of pretty active channels where folks would come to ask Rust questions, coordinate work on Rust itself, and just in general chat about Rust. ![]() ![]() The Rust community has had a presence on Mozilla’s IRC network almost since Rust’s inception.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |