- From: Juan Caballero <virtualofficehours@gmail.com>
- Date: Sun, 8 Oct 2023 13:49:21 +0200
- To: Evan Prodromou <evan@prodromou.name>, public-swicg@w3.org
- Message-ID: <240f1176-8ff3-37ad-9602-887a09a7afb1@gmail.com>
I am +0.5 on all these ideas, with the caveat that it's a lot of work for chairs to implement them all. GitHub allows issues and PRs to be transferred around and auto-directs from old URLs, so I assume it's fine to work in the current home while these other issues get worked out? I wouldn't want the chairs to feel like this pile of administrative work and decision-making is blocking participation :D On 10/7/2023 8:43 PM, Evan Prodromou wrote: > > -0 > > I think using GitHub for dealing with documents and processes of this > group is a nice idea, but I have some minor quibbles. (There’s always > something, I know!) > > * I don’t like “SWICG”, since the name we currently use is > “SocialCG”, which is objectively 1000% cooler. > * Is it possible to have a repo in the ‘w3c' organizational > namespace? And still give SocialCG people the chance to manage > docs in the repo? w3c/socialcg is free, but I don't know how we > get it. Maybe ask staff? > > I can live with the existing repo, but I'd really like w3c/socialcg as > a homebase for the cg. Also, w3c.github.io/socialcg/ makes a nice home > page URL, if we use GitHub Pages. > > It would be nice to move the draft reports from the AS2 and AP repos > (extensions, data portability) to the socialcg repo. > > We have some long-standing repos in another GitHub organization, > w3c-social <https://github.com/w3c-social>. It would be interesting to > consider shifting those around, either as subdirs of the CG repo, > or... something else. > > Finally, after bengo's proposal and discussion yesterday, I did some > poking around in our old minutes. There are a lot of resolutions > there. It would be nice to have them in one document for reference, > with the text and a link to the minutes where they were resolved. I > think a socialcg repo would be a good place for that document! > > Evan > > On 2023-10-07 2:00 p.m., Dmitri Zagidulin wrote: >> +1 from me, I think Github is a great venue for this discussion. >> >> On Sat, Oct 7, 2023 at 8:04 AM James <jamesg@jamesg.blog> wrote: >> >> Juan, I sincerely appreciate your creating a few issues on GitHub >> and asking this question! I would love to hear from the community >> on using Github to make progress on operating agreements, a CG >> charter, task forces, use cases, and all decision-based business >> by the group. >> >> James >> >> ------- Original Message ------- >> On Saturday, October 7th, 2023 at 12:03, Juan Caballero >> <virtualofficehours@gmail.com> wrote: >> >>> Great meeting yesterday, I think we made a lot of progress on >>> some wicked problems and are talking past each other a little >>> less now. >>> >>> One idea that came up again and again yesterday is that email >>> lists aren't the best way of collaborating on documents, and >>> synchronous meetings aren't particularly high-volume or >>> high-output either. Perhaps we have refined the problem to a >>> single question: >>> >>> > How can consensus be reached on the *scope and goals *of each >>> document that a subgroup works on for a while, before bringing >>> back to the broader group to review and approve? >>> >>> Would the CG issue tracker ( >>> https://github.com/swicg/general/issues/ ) be a good place to >>> make progress on the operating agreements, task forces, >>> use-cases, etc? >>> >>> Thanks, >>> __juan >>> >>> P.S. For the sickos who haven't had their fill of >>> meta-discussions yet, here's a funny issue about other issue >>> trackers: >>> https://github.com/swicg/general/issues/29#issuecomment-1751680966 >>> >>> On 9/29/2023 8:35 PM, W3C Community Development Team wrote: >>>> Hello everyone, >>>> >>>> >>>> >>>> Thank you to everyone who participated in the discussions pertaining to a prospective Working Group (WG). We have two announcements: >>>> >>>> >>>> >>>> >>>> Our next community meeting, and; >>>> >>>> >>>> >>>> An invitation to collaborate on scope for a prospective WG on the W3C wiki. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> October 6th Meeting >>>> >>>> >>>> >>>> We are scheduling a Community Group meeting for Friday, October 6th. >>>> >>>> >>>> >>>> The meeting will be at 11am ET / 4pm UK / 8am PT, and hosted athttps://meet.jit.si/social-web-cg. >>>> >>>> >>>> >>>> The rough agenda for the meeting is as follows: >>>> >>>> >>>> >>>> >>>> Introductions (optional) and community announcements. >>>> >>>> >>>> >>>> IP Protection Note Reminder: (a) Anyone can participate in these calls. However, all substantive contributors to any CG Work Items must be members of the CG with full IPR agreements signed, and (b); To contribute to Work Items: ensure you have a W3 account, and sign the W3C Community Contributor License Agreement (CLA). >>>> >>>> >>>> >>>> A discussion on scope for a prospective WG, following on from our previous CG meeting, discussions on the mailing list, and contributions to the wiki (see below for more information). >>>> >>>> >>>> >>>> Discussion to start a data portability task force that would focus on social web data portability (particularly with regard to ActivityPub), and the scope thereof. >>>> >>>> >>>> >>>> Discussion on a formal decision making process for the group, following on from community discussion. >>>> >>>> >>>> >>>> Any other business. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Call to Contribute to Prospective WG Scope >>>> >>>> >>>> >>>> The Chairs have created a new page on the W3C wiki to discuss the scope of a prospective WG:https://www.w3.org/wiki/SocialCG/WG_Charter_Discussion. >>>> >>>> >>>> >>>> The wiki page is open to all CG members. You can log in with the same username and password you use for your W3C account. Please let the Chairs know via a private email if login doesn't work so we can assist you directly. >>>> >>>> >>>> >>>> WGs have the ability to create technical documents for consideration on the W3C Standards Track and to amend existing W3C Recommendations. The Chairs have created a "Deliverables" section in which we invite you to list any deliverables that you think are appropriate to include in a WG. >>>> >>>> >>>> >>>> If you have further notes or comments about the WG Charter discussion, please leave them on the page so that we can aggregate as much information as possible in one place. >>>> >>>> >>>> >>>> Thanks, >>>> >>>> >>>> >>>> The Chairs >>>> >>>> >>>> >>>> ---------- >>>> >>>> This post sent on Social Web Incubator Community Group >>>> >>>> >>>> >>>> 'October 6th Meeting and Calls for WG Scope Contributions' >>>> >>>> https://www.w3.org/community/socialcg/2023/09/29/october-6th-meeting-and-calls-for-wg-scope-contributions/ >>>> >>>> >>>> >>>> Learn more about the Social Web Incubator Community Group: >>>> >>>> https://www.w3.org/community/socialcg >>>> >>>> >>
Received on Sunday, 8 October 2023 11:49:29 UTC