-
Notifications
You must be signed in to change notification settings - Fork 103
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
Update Events list to preview Solid World #790
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@csarven Would this suffice to at least be able to promote this event for now? Alternatively we could also list Inrupt if you're more comfortable with that @hzbarcea? We can always update it back to Solid Team later if we get consencus on that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, any organiser besides Solid Team will suffice. It should not be changed once that's committed.
AFAICT, the first public announcement about this event predates ( https://matrix.to/#/!ICiXwJRUuUgyPLIEvn:gitter.im/$EO3PUU7C16H3CjOz40QTwbL5vErf6PZv2Vv7Bh1YTNQ ) Hadrian joining the Solid Team ( even as early as https://github.com/solid/team/blob/main/meetings/2023-05-17.md#proposed-solid-worldnewsletter-instructions ), and nothing on record (by the Solid Team) indicating that Hadrian is assigned to organise SW, .. let alone disclose/inform any information about the event to the Solid Team in a meeting or in chat.
On a related note, people that are not even on the Solid Team have knowledge about the SW agenda and its publication ( https://forum.solidproject.org/t/solid-world-june-2023/6604 , https://web.archive.org/web/20230628165958/https://forum.solidproject.org/t/solid-world-june-2023/6604 ).
That said, Solid events happen everywhere with different organisers, and solidproject.org can continue to acknowledge them. So, it is completely okay to acknowledge Hadrian or another entity, if they and the proposer of this PR agrees, as the organiser of this event.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Vinnl thanks for the proposal. I am perfectly fine with that. At this point, it's water under the bridge. The event took place a few hours ago and presenters had a lot of great material. I can see Solid getting more and more ground. And Jackson did a wonderful job. A recording will be available, as always.
I guess we will discuss this more in a different forum. I see an acknowledgement that nothing has changed (and a claim that this is a problem), I saw everybody acting in good faith, for the good of the community, yet an unprecedented action was taken to not publish the existence of the event, denying (to some extent) the solidproject.org's audience the opportunity to participate.
The risk/reward reasoning that went into this rejection eludes me, especially given the fact that steps we taken to address the issues @csarven raised. Oh, well...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain how you've reached that interpretation?
I understood Vincent's response and change suggestion as a good indicator that my review and messages was clear enough about what's intended, but you might have misinterpreted.
Here are some of my messages:
I asked Chat GPT to paraphrase them and it came up with this:
Does that clarify my review and messages?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"There is nothing on record that the Solid Team organised this event". The Solid Team cannot and should not micromanage the details of each Solid World. It delegates that to nearby folks who trusted to do a useful job, and thanked for their time and effort. Solid World can still be said to be held under the auspices of the Solid Team. @csarven You seem to want a world which is painfully bureaucratic.
And with phrases like "deep and long running issues pertaining to open and transparency" you sow distrust and suspicion where it is not helpful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Micromanagement is not intended. As discussed in Solid Team meetings, what's being asked is the minimal transparency. Not every detail needs to be run by the team, just some awareness.