-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: emphasize tentative nature of meetings #102
Conversation
If this panel also concludes that it will have no more meetings until the decision of the special topic meeting of 2023-10-10, it might be better to use a text similar to solid/data-interoperability-panel@fa0b1b1. |
The tentative has been only this summer. Until that, we met every Thursday for 3 years. What we need to do is revise/renew the panel charter once eveyone is back. |
@CxRes, I had come to believe that this panel would follow the direction of the CG towards a structure based on two central meetings, possibly complemented with breakout task forces. Not sure why or where I got that impression; possibly because @csarven seemed to be in favor of it, and he is chair/editor of this panel/spec. In any case, do you feel there will be meetings between now and 2023-10-10? If not, I would still merge this PR to shed clarity until then. |
This is why I had been so insistent on dealing with the Solid process in entirety rather than just the charter. But there were other compulsions, as I know now. The reorganization imho is not official until someone pens it down (though I share your impression too). I would continue to presume that we will stick with the current schedule once this self-imposed hiatus is over. If there is a change to the text here, I would rather say we are on a summer/fall hiatus than say tentative slot (which does not accurately reflect history and current process, we are not even discussing tentative slots for this panel)! I would request you to hold on till we get a clear picture from @csarven and @elf-pavlik as to their availability and/or some instruction to re-organize from the CG! |
I don't see what this has to do with the charter. Whether we did this before, during, or after the chartering, fact remains that people are confused, and so it is important to shed some clarity.
Which whill (hopefully) happen on October 10th.
When would that be?
Fine for me. I worded it as 'tentative' because that is how this panel has been meeting these summer months: on and off, mostly by ad-hoc conversation on Matrix. But if you want to reword it, please do a suggestion to the PR.
The instructions for reorganization are pretty clear: a special topic meeting has been planned on 2023-10-10 to deal with that. As to this specific PR: this is more urgent, to address the confusion multiple people have brought to the attention. Note that it is just my suggestion to describe the factual status of this panel's meetings, not to change it. |
I am confused too! :)
It depends on Sarven and Pavlik's plans and energy (and really I want to hear from them in their capacity as co-authors). I am happy with a meeting next week even (TPAC this week). Once they chime in, I am ok with text change to "on hiatus"! And if others are interested in having a meeting and brought this up to you (or have specific concerns), please share it, we can plan something in the interim! |
I think we can bring up solid/process#324 next Wednesday and probe other participants' preferences. In the second week of October we also should already know if WG was approved, please remember that the intention is for the WG to pick up the notifications work as well. |
Background: solid/specification#458 (comment) -- so it was intended to transition from panels to task forces. I suggest convening in solid/specification (so that we can slowly phase out solid/notifications-panel) for notifications discussions and panning adhoc meetings on work items. Major discussions should happen in special topic meetings. Major decisions can be in CG weekly. |
Action following multiple cases of uncertainty (cf. matrix)