Open jaxoncreed opened 1 year ago
The Solid Team will potentially be taking on projects that might require compensation. Having funds available will help Solid team members complete their jobs.
A high potential funding source is NL-Net (https://nlnet.nl/). They have funded many Solid projects in the past and the kinds of projects the Solid Team would pursue are in line with their goal to "contribute to an open information society."
Open Action Items:
The Solid team has administrative access to the following systems:
It is the task of a Solid administrator to maintain these services. Currently, the core maintainer is Solid Team member, David Bowen.
Open Action Items:
SolidCommunity.net offers a free service to let users try out Solid. Currently, it is maintained by Solid Team member, Alain Bourgeois.
Open Action Items:
Full explanation here:https://github.com/solid/solidproject.org/discussions/783
To summarize, SolidProject.org currently uses Jekyl and Github. We want to create an RDF-based site so that we're dogfooding our own technology. Perhaps the best change would be creating one, RDF-based source of truth for information like Solid Team members, and apps listed on the apps page. We would also want to establish a technical process for people to propose new information to pages and for the Solid team to review it.
Jeff has created a demo here: https://jeff-zucker.solidcommunity.net/sp4/
Note: this change would not affect the hosting of the Solid Specification on github, unless spec members wanted it to.
Open Action Items:
The this week in Solid newsletter keeps the community informed about what's happening in Solid. Currently, the newsletter is sent by Solid Team member, Kelly O'Brien.
Open Action Items:
Solid World keeps people informed about Solid through a monthly webinar. Currently, Solid World is lead by Solid Team member, Kelly O'Brien.
Open Action Items:
The Solid Team could take a more active role in setting up meetups or helping people on the ground set up meetups. It could provide educational resources and promotional support.
Open Action Items:
SolidCommunity.net currently runs on NSS and upgrading it to CSS would bring it in line with modern standards. However, because of differences in the way authentication data is stored, work must be done to either transform the data, or build an integration for CSS to understand the old authentication data.
Open Action Items:
The necomer experience for Solid is not where we want to be. We could create detailed, easy to follow documentation in the vein of w3 schools.
Open Action Items:
Encourage diversity and inclusion by pairing with projects that are providing social benefit and which include marginalized people in key roles. Provide the projects with networking and mentoring assistance. Provide paid internships for marginalized people to participate in these projects and or in core projects which directly benefit the Solid community. Create hackathons that work on these projects. Create ongoing online meetings and symposia to network socially relevant projects using Solid.
This proposal could benefit from funds for internships, methoring, holding/promoting hackathons/meetings/symposia, hiring of professional experts in diversity to advise us on reaching out to specific communities.
Have the content creators take a pass on cleaning up the content of SolidProject.org. We've been kicking this can down the road for a while now and it might be valuable to have a number of the creators take a spike and propose high level changes for the group to vote and agree on and then just make the changes. We've been in analysis paralysis here for too long.
Ensure that solidproject.org is hosted from a Solid server. Evergreen issue: https://github.com/solid/solidproject.org/issues/248 . Why? Because!
We should be running our main web site on solid. We can coordinate with the solid project pod..
Social media accounts provided by third-party services, e.g., Twitter (or other status updates), Vimeo.
There is a problem with the way this has been phrased.
There is a confusion between scope as" jurisdiction" and scope as things the team will spend their own effort on directly. The team has a high level to ensure the wellbeing and functioning of the whole movement. So the "jurisdiction" in a sense is very wide indeed. The set of things it may have to worry about is anything solid. But almost everything has to be delegated. So things like Solid World, meetups, hackathons should happen and should be in the cause of the project, and the team should keep an eye on them but the team can't be expected to micromanage the program of each event.
We can use Solid Org thsolidproject.solidcommunity.net also as a Project which does as much of its work as possible actually in Solid. (including this poll for example)
There’s been a lot of discussion around what the scope and responsibilities of the Solid Team are. In the meeting on April 19th, members of the Solid team will meet to decide what the scope is.
The point of this exercise is to define what is in the jurisdiction of the Solid team. Based on this we can begin efforts to find resources for and complete the items we determine are in our jurisdiction.
To prepare for the meeting, we can use this thread to propose potential areas of responsibility for the team, as well as other ideas.
I’ll list some I’ve heard below, and I'll include actions that the Solid team currently does as well as actions that we might do. Feel free to add comments of your own. If there is a specific proposal you want to put forward mark it with a “Proposal:” header.