Page History

...

Title	<title of your proposal here>
Description	<description text here>
Proposer	<your name here>
Resource requirements	<money? effort? coordination? unicorns?>
+1's	<for others to voice their support - add your name here>

Ideas

Title
Description	Business continuity challenge from FedCM Input/Requirements The hackathon experience Participation from critical software stacks Participants to attend W3C to advocate for resolving any issues raised by R&E stacks Output: A cadence of communication EduGain slack updates and updates to InCommon CACTI Recommendations for how software developers /software stacks and federation operators respond to Fed CM – Leif J Common communication language for larger scale motivation of resources - Chris P This new approach that browsers are proposing appears to have significant impact to R&E federation access practices. If you have software, have your developers reviewed https://fedidcg.github.io/FedCM/ ? Are they aware of a hackathon planned in Feb to test R&E tools and provide the W3C with feedback? Have you considered business continuity effects for your systems, especially if you suppliers do not address the new browser controls? A REFEDS working group is proposed. Resources participation in W3C working group (slack channel in W3C for this community group) to support actual resolution committing technical issues
Proposer	Zacharias Törnblom (SUNET), Judith Bush
Resource requirements	Need technical experience as well as CSuite outreach
+1's	Chris Phillips Leif Johansson Leif Johansson Nicole Roy

...