👍

👍

👍

👍

👍

The examples given are definitely challenging to consider.

I would be in favor of documenting some “simpler” interesting and desirable examples in spec itself with sample browser renderings.

For example an inline flow element that is wrapped across multiple lines, both where the boxes are disjoint, and where the boxes are touching, or perhaps wrapped across 3+ lines, to illustrate an “outline that encloses all the element’s boxes” as a more ideal rendering than say separate boxes for each piece.

Perhaps related, the spec mentions non-rectangular (effectively) three times in the outline section, “Outlines may be non-rectangular” (twice) and “The parts of the outline are not required to be rectangular”. While clarifying/documenting some preferred outline renderings, perhaps we can simplify the definition and remove the apparent duplicate descriptions.

👍

@csageland sorry to miss you!
Best #IndieWebSummit yet!
Wide variety of sessions, hacks, demos. Check out session notes & videos: https://indieweb.org/2018/Schedule#Tuesday
And join us in chat! https://indieweb.org/discuss

A few from #Portland this week:
1 #IndieWebSummit group photo, 📷 @aaronpk’s camera on timer
2 #IndieWeb Leaders Summit the day before @MozPDX, 6 in room + 6 remote
3 Bowl of the gods #acaibowl with peanut butter on top at Kure that morning
4 Chipotle chili bowl with quinoa at Prasad the night before that
5 Berlin IWS Remote Viewing hosted @EmbassyNetwork by 📷 @anikasai
6 Participant proposed & led @IndieWebSummit sessions
7 Running @Nov_ProjectPDX with @DesignNatalie (not pictured)
8 Fresh #NP_PDX tag thanks to co-leaders Lara & Shelby
9 Black Currant Cider limited-edition #donut @BlueStarDonuts

#2018_176 #2018_177 #2018_178

More photos soon. Got photos from @IndieWebSummit to share?
Add them to https://indieweb.org/2018#Photos

Finished my @IndieWebSummit coding project!

Completed plain text readable reply-contexts¹ (instead of just URLs) for all responses; in particular got these working:
* in-stream² for new GitHub issues
* on permalinks for all replies & reacji³
 
Sometimes it’s the small details.

¹:https://indieweb.org/reply-context#Minimal_text_reply_contexts
² https://indieweb.org/reply-context#Why_in-stream
³ https://indieweb.org/reacji

Grateful for the 10th (likely final?) @OSBridge.

@OSBridge culture & values continue to be an inspiration that can benefit every tech/OSS conference (including those I help with).

If you have been to @OSBridge, pass on what you have learned*

*http://www.yodaquotes.net/always-pass-on-what-you-have-learned/

This is your last @xoxo reminder!

~25min to do #xoxofest registration survey!

https://my.xoxofest.com/attend

You can do it in <10 min!

1 line answers to (abbr’d)

What do you do?
What are you working on?
What’ve you made that you’re proud of?

Sharing brief @IndieWebSummit notes as they come to mind.

This was the first year people pre-wrote proposals before the #BarCamp organizing session. As facilitator I decided to have people who never proposed before go first.
 
Coincidentally, @Christi3k just announced the same thing @OSBridge unconference organizing session.

This may be worth codifing as a normal practice. Let first-timers propose sessions first before anyone who has done this before, especially at an @IndieWebCamp before.

The other thing I did was, after the the first-timers finished explaining and scheduling their BarCamp session proposals, I had people *other than* the remaining session proposers choose from the remaining session proposals posted on the side of the grid, and advocate for them. I think that worked quite well for selecting for the sessions that were more compelling for more people. #2018_177

The 8th annual @IndieWebSummit wrapped up yesterday and simply put, I was blown away by the sessions everyone organized and especially by the incredible things everyone made & demonstrated.

Notes & videos: https://indieweb.org/2018/Schedule#Tuesday

Photos coming #indieweb #openweb

https://github.com/kartikprabhu Looks like you can also use the Clipboard API (https://caniuse.com/clipboard) to write directly to the clipboard (using navigator.clipboard.writeText) in response to e.g. a click on a link (or button), see and try the code in Example 10 here:

https://w3c.github.io/clipboard-apis/#clipboard-writetext-data

https://github.com/kartikprabhu according to the linked examples on:

https://indieweb.org/citation#append_to_text_selection_copy

It looks like you can intercept document.oncopy and change the selection (using selection.selectAllChildren) to then cause the copy command itself to copy whatever text you want, rather than having to use execCommand("copy").

Finished #RodeoValley 30k in 05:10:17 yesterday! 📷 @kellyfuson #2018_174
My first 30k and the hardest #race I’ve run. First 2 hours felt great, powered up the Miwok ridge, then the heat slowed everything down to a struggle. Race write-up continues after photo summaries:
2 🌄 Marin Headlands sunrise
3 Dressed to race!
4 Ready 30k 50k start
5 SCA photo stop
6 Hill 88 view to Rodeo Beach
7 Race temperature over time

#run #trailrun #trailrace #insidetrail #latergram #nofilter

Always better participating in a race with friends. Kelly and I carpooled, and picked up our Inside Trail race bibs (different races), got ready, and had someone take our photo with Rodeo Beach in the background (photo 3).

The air was cool at the 30k & 50k start (photo 4), and the crowd started at a nice easy pace (in contrast to everyone bursting out of the gate at Double Dipsea).

The 30k course started with a gradual uphill. Everyone pacing themselves provided a good sense of momentum, enough to run up the first set of hills, all the way up to the SCA trail where I saw a few taking photos so I did too (photo 5).

Smooth run up and down SCA and Alta trails to Marincello, took off downhill without missing a beat, and somehow passed a lot of people who had passed me on the uphills.

Made it down to the Tennessee Valley parking lot in (personal) record time. Refilled my water bottle at the aid station and headed up Miwok, where the temperature got noticeably warmer the higher I went. It was a tough slog by myself. When another runner passed me who was also struggling, I found the energy to barely keep up, several paces behind.

We reached the turn onto Coyote Ridge and it had definitely heated up.

Weather forecasts had predicted mid 70s in Mill Valley, and 80 at Rodeo Valley. Clear, not a cloud in the sky.

I didn’t realize until after I synced the temperature data from my watch (photo 7) that since that 2 hour mark, temperatures on the course went from 80 up to 95°F (except for a brief drop to 75°F after hour 4 in Tennessee Valley).

When I felt the heat hiking up Coyote Ridge, I figured it was the predicted mid 70s, accentuated by the direct sunglight. With a full water bottle I pressed on, hitting the halfway mark at about 2h15m in, with over 2200' (much more than half) of vertical climb completed. I had started feeling the effects of the heat, my stomach would no longer accept any food, and I had to slowly sip from my bottle up the hill.

Ran most of the way downhill to Coastal, it was hot enough to slow down and walk a few times. Made my way down to Pirates Cove, without much difficulty. Then the real challenge started.

The climb up out of Pirates Cove was brutal and long. It was feeling hotter still, and I figured it had crept up to ~80°F (when it was actually closer to 95). I knew I had enough water to make it back to the aid station. I focused on my breathing, and watched my heartrate, pushing uphill only hard enough to keep it between 140-150bpm.

The hill seemed to go on forever. I kept pushing until a couple of times I literally had to stop, take a few deep breaths, and then keep pressing on. By the time I got to the top, I was exhausted, too tired go downhill as fast I normally would. It was still a morale boost to see the valley below. I knew I could make it back to the Tennessee Valley parking lot aid station.

Taking it slow back to the aid station, I was able to snack when I got there. Refilled my water bottle, and took off back down Tennessee Valley trail for the remaining 4 miles.

The final steep Coastal Trail south ascent was brutal. Just kept pushing uphill like I did out of Pirates Cove, hands on my knees when necessary. Every so often the plants alongside the trail were tall enough to cast a shadow, and I paused to restabilize my legs, focus on breathing regularly. Again it felt like 80 degrees when it was more like 95.

For over a year now I’ve been doing warm Vinyasa yoga (90-95 degrees) about twice a week. As I practiced more I was better able to reach a conscious flow, better able to think clearly despite the 95 degree temperatures. Only after my run (and seeing the temperature chart) did it click — all that warm Vinyasa had trained me to push sustainably even in that much heat, and still focus & think with a strong enough will to keep going.

Reached the Hill 88 crest (photo 6) where I could see Rodeo Beach (the finish) in the distance! As I started an easy run down the hill, I heard someone call out my name. I was so focused on finishing that I didn’t recognize his voice or face until he was much closer. Clayton and Kissie were running up the hill on their on Saturday trail run! They wished me luck and I kept trudging down the hill.

Eventually I picked up speed and passed one person who had passed me on the Coastal uphill. Knowing I’d finish in minutes, I focused on a swift but steady pace, on sure footing more than speed.

Finished (photo 1), saw Kelly cheering me in (she’d finished her half marathon about two hours before).

30k (18.6mi) done! (my Suunto watch only recorded 29.97km, clearly I should have ran it out another 30 meters after crossing the finish 😂) The farthest I have ever ran on trails.

3,780 feet elevation gain (secondmost during a run, only to Double Dipsea last Saturday) according to my Suunto watch / Strava.

And a 1 mile PR of 7:20, during my sprint down Marincello, finally beating my nearly three year old timed track mile PR of 7:23 (tantek.com/2015/188/t1) under totally different conditions (downhill vs flat, trail vs track, after ~7mi vs 1mi warm-up).

Thirsty & hungry, I refilled my water bottle, drank deeply, ate snacks, and picked up my finisher’s medal and t-shirt. We retrieved our bags from bag-check and headed to the beach.

Stripped down to my running shorts, walked into the surf, and dove in, fully submerged.

Best ice bath ever.

1. #fbf to #TrackTuesday 3d ago DD recovery/taper for Rodeo 30k: 5x400 + 90-120s stretching between. #2018_170
2-4. 10d ago at #Kezar #track before/during sunrise, taper for Double Dipsea: 800 1200 1600 400 race pace & stretch breaks. #2018_163
5. 17d ago late solo 4x400+stretches. #2018_156
6. 2018-05-08: stadium stairs, 3x400+stretches, abs. #2018_128
7. 2018-04-24: 400 200 400 400 200 400 #2018_114

Previously: http://tantek.com/2018/108/t3/yasso-fast-track-tuesday

#run #runner #runners #latergram #nofilter

In @microformats.org year 14, we welcome new admins @aaronpk @gRegorLove @martijnvdven @HeNeArXn! http://microformats.org/wiki/admins
All have been active for years, helping welcome new members and doing essential wiki gardening & #microformats2 parser updates!

It was the longest day of the year, yet among the darkest days for the U.S.
2300+ children still forcibly separated from their parents, “spread across states”:
https://www.cnn.com/2018/06/21/politics/migrant-family-separation-what-next/index.html “by thousands of miles and a bureaucratic maze”: https://www.nytimes.com/2018/06/21/us/immigrant-children-separating-families.html

All due to unacceptable inhumane directives from POTUS and the bible-distorting AG. Backing down to detaining whole families is still just cover for racist internment.

More families being detained. More facilities being constructed. Because of an imagined (immigrant) threat.

The parallels to WWII Japanese internment are blatant, yet here we are.

It’s long past time to have the difficult conversations with friends and family that may have voted for POTUS, and the GOP that’s sacrificed all principles to support him. Keep the pressure up and see it through to making a difference in November.

Previously: http://tantek.com/2016/314/t1/doublestandard-wtf

Mozilla has been participating in the design and development discussions of Houdini at the CSS Working Group since the beginning and continues to do so.

For Houdini as a whole ("CSS Houdini family features" that have published drafts per this issue), I think the most accurate current summary position is "worth prototyping".

As individual Houdini specifications technically mature (with web developer feedback & iteration) and assuming we see broader use-cases across the web, we can consider stating upgraded positions for each individual specification as appropriate, taking into account the importance of other web platform features.

If anyone has concerns about particular Houdini drafts that should block an explicit "worth prototyping" position, please speak up and we can use "under consideration" while we file issues on those drafts and iterate accordingly.

In addition, since https://github.com/surma ’s tracker was mentioned, this overall Houdini position should not be taken to apply to anything that is not yet at least a published working draft.

If an explicit position is desired for proposals in https://ishoudinireadyyet.com without a working draft, please file separate issues for those.

CSS Basic User Interface Module Level 3 (#CSS3UI) is now a @W3C Recommendation!
Congrats fellow co-editor @frivoal and thanks to the @CSSWG for all the hard work (and patience) for so many years. #openweb @CSS3UI
https://www.w3.org/TR/2018/REC-css-ui-3-20180621/

Previously: https://twitter.com/css3ui/status/941695566194597889
and http://tantek.com/2015/189/b1/css-basic-user-interface-level-3

Happy 13th to @microformats.org!
With more use of #microformats2¹, especially among the growing #indieweb² network of websites, we’ve iterated key³ specs⁴ for real-world needs and are seeing more active community members. More updates & posts coming up!

¹ http://microformats.org/wiki/microformats2
² https://indieweb.org/
³ http://microformats.org/wiki/microformats2-parsing
⁴ http://microformats.org/wiki/h-entry

6 days til the 8th @IndieWebSummit gathers innovators, artists, designers, and journalists to share, make, and grow the independent web, publishing & interacting with each other using their personal websites instead of social media silos.

Join us: https://2018.indieweb.org/

Yesterday: finished my first #DoubleDipsea #race in 3:59:26! 📷 IG jasonthepatsfan
Felt strong, especially on the downhill finish. When I saw the guy in front slow down with maybe 20 yards to go, I sprinted extra hard to beat him by mere feet: 620th of 691 finishers.

#dserunners #optoutside #getoutside #raceeverything #run #runners #trailrun #trails #Dipsea #Stinsonbeach #Marin #yestergram #latergram #nofilter #2018_167

Previously: http://tantek.com/2017/167/t2/went-double-dipsea-cheer-ran

@lightcoin thanks for the post and photo!

Would have loved to show more of @schnarfed’s great work on indiemap.org; definitely click through and try playing with the interactive network graph. Great visualization and data!

@csageland thank you and looking forward to meeting you @IndieWebSummit!
Got ideas for what you want to brainstorm and make?
Join us in chat.indieweb.org (or via Freenode IRC, Slack, or Matrix indieweb.org/discuss#Join_Discussions)

going to Decentralized Web Meetup @InternetArchive tonight, looking forward to talking & sharing about #longevity #selfdogfooding #indieweb principles, demonstrating examples using my website, and inviting everyone to @IndieWebSummit!

Links and thoughts for discussion:
* Longevity https://twitter.com/internetarchive/status/741832908323708929
* Use what you make https://indieweb.org/
* Principles https://indieweb.org/principles supporting a plurality of projects
* Owning my data, federating to participate: tantek.com
* 2010+ every tweet, 2015+ photos & videos, 2017+ events
* 2018-02+ GitHub issues, comments, reactions
* indiemap.org
* https://2018.indieweb.org/ - inviting everyone here to IndieWeb Summit in two weeks
 - back to selfdogfooding, it’s an indie event that accepts federated RSVPs, and also accepts sign-ups via webform.

Have been watching this thread, and want to also encourage vocabulary re-use wherever possible, as it greatly helps sharing content and bridging across various heterogenous systems.

https://github.com/kevinmarks mentioned h-entry already, which builds on all the experience and expertise from RSS and Atom.

Similarly, consider https://microformats.org/wiki/h-card (based on the IETF vCard standard, and adapted for the web and JSON-friendly) for references and descriptions of people.

Most recently I saw the calendar-app event example in a previous comment, which could re-use https://microformats.org/wiki/h-event as well (similarly based on the IETF iCalendar standard). Happy to present an example using LZ syntax etc with h-calendar vocabulary if that would be helpful.

All of these vocabularies have been both implemented and successfully interoperably deployed peer-to-peer across numerous websites, publishing and parsing / consuming. (stats and examples available at indiemap.org)

Happy to help answer any questions about how these vocabularies are developed and how they’re community maintained, either here or chat.indieweb.org.

Remembering last Friday, running #hillsforbreakfast with #NPSF around a #waterfall on an #island in the middle of a lake in #GoldenGatePark, snapping wildlife, at sunrise. #takemeback #StrawberryHill #optoutside #getoutside #wakeupthesun #fromwhereirun #latergram #nofilter #2018_159

#XOXOFest, self-described “experimental festival celebrating independently produced art and technology”, opens for this year’s registration next week!

http://blog.xoxofest.com/post/174829185270/registration-for-xoxo-2018

Having been to @XOXO several times I highly recommend it to #independent #creatives of all backgrounds, even knowing the more people apply for it, the less chance I personaly have to go again (see blog post for details).

Will miss you @Dries! Can you perhaps participate in the summit remotely? https://indieweb.org/2018#Remote_Participation
Add yourself (no RSVP needed) https://indieweb.org/2018/Guest_Book#Remote_Participants
And join the chat whenever you can and say hi! https://indieweb.org/discuss

The 8th annual @IndieWebSummit is in 2 weeks!

Want to
* Own your identity on the web
* Reply to #Mastodon toots with your own website
* Grow the practical user-centric #decentralizedweb #dweb
* Build with @W3C + #IndieWeb standards & experts

RSVP: https://2018.indieweb.org/

Learn, get inspired, brainstorm, design, create, make, and help grow the present & future of the independent #openweb!

ICYMI: Yesterday #netneutrality protections expired. Via @ACLU (I‘m a member)
https://www.aclu.org/blog/free-speech/internet-speech/how-net-neutrality-will-end

This is a looming problem for everyone on the #internet, except maybe large telecomms shareholders.

#openinternet #openweb #indieweb #sfallhands

#SFAllHands: @TheWebbyAwards lifetime achievement winner @MitchellBaker starts @Mozilla plenary with a reminder of the recent Manifesto addendum for a better open #internet. #openweb
Previously: http://tantek.com/2018/133/t1/mozilla-manifesto-addendum

my #SFAllHands ⚡️intro
* 8 yrs #openweb #standards @Mozilla[1]
* may know me from: #CSS[2] #microformats[3] #indieweb[4]
* recently: Standards Outreach w @david_bryant
* editing: CSS2.2, CSS scrollbars
* interesting: Vouch[5]
* controversial opinion: technical contributors @Mozilla should be actively using their own website, even if just one blog post a year

[1] https://wiki.mozilla.org/Standards
[2] https://wiki.mozilla.org/CSS
[3] microformats.org
[4] https://indieweb.org/
[5] https://indieweb.org/Vouch - vouching as a practical decentralized solution to commenting, with some trust without requiring a hard-identity, designed to reduce abuse etc. as we have seen in centralized social media, but distributed across the web peer-to-peer

Awesome #dweb/#openweb meetups & #IndieWeb Summit coming up!
June
13th: #DecentralizedWeb Meetup @InternetArchive
18th: Re-Decentralising The Web, London @WebStandards
26-27 @IndieWebSummit, Portland OR
29th: @OSBridge, Portland OR

Links & tickets: https://indieweb.org/Events#Upcoming

👍

I should have been more clear, it would be great if the Confluence Metrics graphs UI itself linked to the definition so it was more easily discoverable.

I.e. by putting a span with an ID on the definition of "Grace Period" in the README, and then linking to that fragment from the web UI, by hyperlinking the first instances of "Grace Period" (with quotes) appearing in the div class="text-content" elements in https://github.com/GoogleChromeLabs/confluence/blob/301782981ff6eeee30f4d272dcce6635ed09c943/static/view/confluence.html

I started a pull request at https://github.com/GoogleChromeLabs/confluence/pull/303 but figured you may have a more preferred method / markup for this.

Thanks for your consideration!

I think IndieAuth makes a lot of sense as the way to implement a federated login protocol to provide a "simpler UX for OAuth2" login for Gitea as this issue is named.

It would also be possible to provide support for the "with GitHub" portion (as originally noted in the issue) without having to ask / wait for GitHub to implement IndieAuth, by adding https://indieweb.org/RelMeAuth support.

https://indielogin.com/ is an example of an open source service that supports both of those, IndieAuth as github.com/aaronpk suggested and RelMeAuth, and is in daily use by folks signing-into the IndieWeb.org site.

went to Larkspur Community Run with Equator Coffees & Salomon @EquatorCoffees. Thanks @Amy_Leedham for the heads-up and Esther @SalomonSports for the Sense Ride shoe trial + Q&A! Despite many delays, made it, shoes were great, got a pair @SFRunCo!

Reminder @W3C Advisory Committee members:

TODAY 23:59 EDT is the deadline to vote in the current @W3CAB election!

Please take a few minutes to vote:
https://www.w3.org/2002/09/wbs/101147/ab20180502/

I and six others are running:
https://www.w3.org/2018/05/02-ab-nominations

Thanks for voting!

#NPSF Double PR Wednesday done!
35:20 #earlygang ~5:30, no music
34:40 #normalgang ~6:30, with music (19s slower than March)

5hrs+ sleep. Some coffee. Again tough two sessions.

Previously:
2018-04: DNF. 1 lap, bathroom break, 2 more laps.
2018-03: http://tantek.com/2018/087/t1/back-to-double-pr-wednesday

Grateful for so much this morning. Waking up with sunny skies, @Nov_Project_SF at Aquatic Park, sunbeams beaming and sparkling water.

#NPSF #NovemberProject #SF #AquaticPark #beach #cove #sun #sunbeams #sparkling #water #nofilter

I would disagree with applying this only to explicit u-photo, I think that would result in a surprise to web authors. The simpler model is to handle "alt" for u-photo regardless of whether it is implicit or explicit.

In addition, why shouldn’t it apply to any use of u-* with an img?

E.g. "u-featured" on an img should also pick up any alt attribute.

In short, I’d rather NOT go through multiple proposal/consensus/prototype/changes to get "alt" to work properly. I’d rather we figure out how "alt" should work and change the parsing spec once to handle it.

Note the issue name "image alt text is lost during parsing" is not specific to u-photo. Let’s fix this for any use of any image (img) tags in the parsing spec.

Overcast at #SFRC. Shorter run today (~11.1miles), still 2100+' of climbing.

The cool weather was perfect for running, and the cloud cover provided nice diffuse lighting for the trail flowers. Made it to Muir Beach and touched the Pacific. Slowly getting faster at hills. Less than six months to ECSCA 50k.

Previously: a few times in May (to be latergrammed) and tantek.com/2018/097/t1/last-saturday-sfrc-longest-trail-run

#fromwhereirun #run #trail #trails #trailrun #optoutside #getoutside #Marin #Miwok #overcast #clouds #nofilter

going to IndieWeb Summit 2018! June 26-27th at the Elliot Center in Portland, Oregon!
This will be the #indieweb #openweb #dweb event of the year. RSVPs limited to 100 total, sign-up before tickets sell-out: https://2018.indieweb.org/

Registration (on the microformats wiki) works fine. I just tried it and created a new account. If you are having trouble understanding the microformats wiki, whether with registration or anything, please state the problem as a question and check the FAQ accordingly: http://microformats.org/wiki/faq

Recommend closure of issue #3704, works for me, no changes to HTML Standard needed.

https://github.com/upsuper your suggested text makes sense to me, and I have also added an explicit note so implementers hopefully don’t accidentally propagate body to viewport.

Please take a look at the prose after the property value table at https://drafts.csswg.org/css-scrollbars-1/#scrollbar-color-properties and if the updates are sufficient to resolve this issue, go ahead and close.

Thanks https://github.com/upsuper, this suggestion makes sense per your reasoning. I have updated the spec accordingly. Please take a look https://drafts.csswg.org/css-scrollbars-1/#scrollbar-color-properties and if the updates are sufficient to resolve this issue, go ahead and close.

🎉

Thanks https://github.com/upsuper and good call. Do you have any preferred wording for this, or shall I clone language from https://drafts.csswg.org/css-overflow/#overflow-propagation ?

👍

Ran #BayToBreakers 2018 Bonus 15k in 1:46:11! Slower pace than last year, but longer distance.

~3.5 min slower than the Hot Chocolate 15k: http://tantek.com/2018/007/t2/finished-hot-chocolate-15k

Last year: http://tantek.com/2017/142/t1/beautiful-day-people-baytobreakers

The @W3CAB is now actively tracking @W3C Process issues in public @GitHub https://github.com/w3c/w3process/issues e.g. we recorded a consensus today: https://github.com/w3c/w3process/issues/190#issuecomment-389439047
This is a new level of #OpenAB transparency, working in the open in real time (when we can)

👍

👍

👍

👍

👍

👍

👍

👍

👍

👍

👍

👍

👍

👍

#W3CAC and one more overview:
@tidoust on @W3C Strategy https://www.w3.org/2018/Talks/ac-slides/intro/strategy-2018.pdf

#W3CAC two more great overviews:
@koalie on @W3C Marketing & Communications https://www.w3.org/2018/Talks/cm-ac2018-marcomm/
@torgo on @W3C Technical Architecture Group (TAG) @W3CTAG  http://slides.com/torgo/tag-update-acberlin-05-2018

In #Berlin 🇩🇪 @W3C Advisory Committee meeting (#W3CAC) as a member of @W3CAB, sitting next to @torgo, listening to @jeff_jaffe’s intro, and @plhw3org’s projects update: https://www.w3.org/2018/Talks/ac-slides/project-intro/ (more links inside)

ICYMI: @Mozilla Manifesto addendum on inclusivity, civil discourse, dignity, individual expression, critical thinking, reasoned argument, shared knowledge, verifiable facts, diverse communities, common good:
https://blog.mozilla.org/blog/2018/03/29/mozilla-marks-20th-anniversary-commitment-better-human-experiences-online/ by @MitchellBaker

I should have said prioritized for rather than tailored to.

I agree with your stated goal and scope of "make the process doc easier to understand for all W3C stakeholders". The current content certainly helps with that goal, and I am hoping that re-ordering the content as I am suggesting would help even more.

I stand by the title suggestion: W3C Process Document for Busy People should start with how to make specs

I believe this will serve all W3C stakeholders as you described, and here is why (additional thinking compared to initial issue description).

(I wrote a version of this shortly after this morning’s meeting in IRC, and will repeat here to help move this forward.)

The very name of "Process Doc for Busy People" implies that *time* (or lack of it - being busy) is the prime priority (saving time in particular) and design center of the document.

Thus beyond *who* it is for, if we recognize that some things in the process happen far more often (and thus require referring to the process more frequently) than others, we can take that prime priority of saving time, and implement it by ordering process section by frequency of use, thus saving more people more time more often, since they will take less time to find their more frequent uses.

E.g. iterating on specs happens more often than AC votes on transitioning specs happens more often than AC votes on WG (re)charters happens more often than votes on TAG/AB elections, happens more often than host agreement(s) being iterated, happens more often than change of Director. (illustrative, not exhaustive list)

This is roughly similar to (though not the same as) the order I initially listed, yet this updated thinking is based on more objective criteria.

Thank you for the invitation to raise a PR.

If this line of thinking (ordering sections by frequency of use, most to least) sounds appealing, I can work on a new explicit section list order accordingly, and presuming that has consensus, can work on a pull request for it, all while maintaining the narrative style so the whole document still flows well.

👍