Added the scope of the team #39
Conversation
|
I propose that instead of leaving these two items blocked that we create an intermediate task that moves towards fulfilling parts of those two tasks in the form of creating a Solid Community of Practice Group aimed at organizations and individuals using Solid to provide real world solutions. I volunteer to lead the task force and will begin by setting up monthly meetings and creating a github repo and gitter chatroom for shared discussions. I have already convened a meeting similar to what I envision for this group. It is summarized below including the reaction of participants to the idea of an ongoing Community of Practice group : On July 10, 2023, a meeting was held between three groups working on Solid approaches to the exchange of information between governments and their citizens. The Flemish government, under the auspices of the EU, has a project - Digital Flanders - which enables storage, verification, and privacy-protecting access to diplomas and other certifications and plans to extend the use of Solid to the delivery of social benefits. The project has been live since May 2023. The Open Commons initiative in Portland, Oregon is exploring the use of Solid in addressing issues of sustainability, smart cities, and delivery of social services. In conjunction with the U.S. National Institute of Standards and the EU, Open Commons is working to form Open Source Program Offices (OSPO) in a number of U.S. cities joining a global network exploring how data can work in municipal governments. In conjunction with Open Commons, the OpenPDX PASS project is in late stages of development of a Solid platform that supports provision of services to houseless individuals through consolidating their personal documents in Solid Pods and providing mechanisms for social service agencies to access the documents as permitted by and under the control of the individual. The team also has plans to extend the platform to areas such as public transit, disaster preparedness, and professional license management. The three groups explained their projects, remarked on the many similarities, and expressed a desire for further discussion. I agreed to work towards building a space to further these discussions - monthly meetups and a github repo. We all agreed to work to expand the audience to other members of the Solid community of practice - organizations and individuals using Solid to accomplish real world solutions. Participants expressed that they want the discussions to focus on getting things done rather than theoretical implications. Other goals included developing shared solutions (code that works for more than one project); sharing information on increasing adoption of Solid by municipal governments and other agencies. I have proposed elsewhere that this task be carried out as part of the W3C Community Group but I believe that this task should be a Team task regardless of its eventual relationship to the CG so we should get this going as a separate action from any action or lack thereof in regard to the CG. |
|
Phrased similarly to the other tasks : Solid Community of PracticeResponsibilitiesMembers of the Solid Community of Practice team are tasked with promoting networking between organizations and individuals working on Solid solutions to real world problems. The Team should make an effort to ensure that socially beneficial organizations and underrepresented voices are part of the target audience and highlighted in the content. Task Members
|
README.md
Outdated
|
|
||
| ### One-off Tasks | ||
| - [[Blocked] Converting SolidProject.org to RDF](/tasks/solidProjectRdf.md) |
There was a problem hiding this comment.
If we're calling out tasks that are blocked, do we need to clarify what is blocking them?
tasks/codeOfConductEnforcement.md
Outdated
| # Code of Conduct Enforcement | ||
|
|
||
| ## Responsibilities | ||
| Members of the Code of Conduct Enforcement Task are responsible for enforcing the [code of conduct](https://github.com/solid/process/blob/main/code-of-conduct.md) |
There was a problem hiding this comment.
There is the Code of Conduct Committee, which to my understanding is a separate/independent group. It can be still listed here for visibility, but linking to the section in the CoC which describes the CoCC.
Name is a bit confusing to me. It gives me the impression of a group separate from Solid Team being set up, but this is still a goal and task within the Solid Team. Could we simply follow the guidelines Jackson is proposing here and have it be a task force within Solid Team? Such as "Diversity Outreach and (Networking) Events Task" or even "project"? Other than that sounds good to start working towards these goals. If we can unblock some of these items that's great. |
I am not fixated on that particular name. However the name that is confusing to me is "Solid Community Group", since apparently most members of the group do not see growing the Solid Community or providing networking opportunities for community members as within the scope of that group. Currently there are regular meetings of those interested in the specs. I propose regular meetings of the wider community, starting with this Community of Practice Group. If it turns out that the CG is not where the community engagement work I am proposing lands, and we end up having a separate group discussion aimed at implementers, it would make sense to me for the CG to adopt a name like Solid Specifications Community Group or similar making it clear to all that they are not the place for general discussion, community building, networking or anything other than providing feedback and getting clarity on the specifications. |
membership.md
Outdated
| | Ruben Verborgh | [IMEC]([https://www.imec-int.com/en](https://www.imec-int.com/en)) | | | ||
| | Kelly O'Brien | [Inrupt]([https://www.inrupt.com](https://www.inrupt.com/)) | | | ||
| | Alain Bourgeois | N/A | | | ||
| | Sarven Capadisli | | | |
There was a problem hiding this comment.
| | Sarven Capadisli | | | | |
| | Sarven Capadisli | [csarven.ca](https://csarven.ca/) | https://csarven.ca/#i | |
membership.md
Outdated
| @@ -0,0 +1,31 @@ | |||
| # Solid Team Membership | |||
There was a problem hiding this comment.
| # Solid Team Membership | |
| # Solid Team | |
| ## Membership |
File may need to be renamed to team.md or members.md where "membership" is one aspect. Or just distinguish the title / subtitle.
membership.md
Outdated
| @@ -0,0 +1,31 @@ | |||
| # Solid Team Membership | |||
|
|
|||
| To apply to be a Solid Team Member, send an email to [email protected]. Solid Team membership is reviewed and approved by the Solid Director. Solid Team Members may also be expelled by the Solid Director or may resign. | |||
There was a problem hiding this comment.
Where in the minutes does it say to use emails for applications? To foster transparency, applications should be done as PRs instead of emails. Ditto responses to PRs. (We'll need to have a simple template later asking key questions.. why do you want to be a member, how do you want to contribute.. ) If "privacy" is such a concern, the email should go to the Director directly instead of a select few that has access to the general info@.
membership.md
Outdated
|
|
||
| Solid Team members must attend Solid Team meetings on a semi-regular basis. They are also expected to participate in Solid Team activities to some degree. | ||
|
|
||
| ## Current Members |
There was a problem hiding this comment.
- Tag/Re-confirm that the individuals that want to be a member (determine commitment by either in or out.. no half way).
- Membership is missing Dmitri and Barath (unless they've stated otherwise on record).
- Order alphabetically.
- 50% of the current membership is from one organisation. This demands a serious review by the Director in order to ensure diversity (among other things). Setting a maximum percentage (or some other factor) for membership per organisation would be one simple way to approach this. Another would be one vote per organisation, with the exception of independents.
membership.md
Outdated
|
|
||
| ## Current Members | ||
|
|
||
| | Name | Organization | WebId | |
There was a problem hiding this comment.
| | Name | Organization | WebId | | |
| | Name | Organization | WebID | |
membership.md
Outdated
| | Vincent Tunru | | | | ||
| | Michiel de Jong | [Ponder Source]([https://pondersource.com/)) | | | ||
| | Hadrian Zbarcea | [Inrupt]([https://www.inrupt.com](https://www.inrupt.com/)) | | | ||
| | Inrupt Maintenance Team | [Inrupt]([https://www.inrupt.com](https://www.inrupt.com/)) | | |
There was a problem hiding this comment.
Membership should be limited to accountable individuals, so list actual names instead of 'maintenance team' along with contact method. At least one identifiable individual needs to be present as per Responsibilities.
@jeff-zucker, I share the opinion that "Solid Community Group" is a confusing name, but it is the name it is given by the W3C. All W3C community groups are named "XYZ Community Group". Calling it any other name is equally confusing. I also share @VirginiaBalseiro's doubt about why we'd need a separate group with a separate name, if what we're really after is meetings of the whole Solid Project 🤔 I would just propose to call them Solid Project Meetings, organized under the Solid Project by the Solid Team. Granted, this does not resolve all of the confusion, especially for newcomers (I wonder if we ever can). But with good descriptions on the website and certain core READMEs on the repo's, I think most people will do fine. If not, there's absolutely nothing wrong with someone ending up at the wrong meeting, and being guided towards the right one. |
If @VirginiaBalseiro said that, I missed it. Can you point me to where she said that?
I don't know where you get that impression. Please read over my proposals above. They relate to a very specific target audience - implementers who want to network with other implementers to advance their projects. This is not spec writers, or developers, or website creators, or Solid World managers or any of the other groups that make up the Solid Project. |
|
I interpreted her following statement that way:
But I see that I misunderstood your intention (or at least the target audience thereof), so please ignore my proposal then. If indeed it is to be a meeting and/or group specifically for implementers of all kind, you could call them the Solid Implementers Meetings, and possibly follow the suggestion has been raised of establishing a W3C Business Group to further organize things around implementation? I'm just doing suggestions, based on my now hopefully correct understanding of what your purpose was/is. 🙂 |
I agree on unblocking these and creating a sub-team along the lines of other sub-teams proposed. It would be also good to define the means of coordination and communication between this team and broader Solid Team and CG. Don't have a strong opinion on the name but I like @woutermont 's suggestion of "Implementers" group or something along those lines. I also agree that it might be good to explore the idea of forming a Business Group. |
|
I prefer the name "Practitioners" to "Implementers" but will settle for either. My concern is that developers know where to go to get specific kinds of help and that those wanting to join our efforts know where there are others working on similar issues. I see a need for at least three groups aimed at this part of our community. Developer Engagement Task Force
Practitioner Engagement Task Force
W3C Community Group & Working Group
I volunteer to lead the Practitioners group. I envision a monthly video call for the Practitioners with eventual breakout calls for different verticals. I would also work to build a page for the website highlighting projects, a registry of projects, github repos for project demos, inter-project discussions and eventually vertical libraries that support multiple projects. I propose Jon Wilson to lead the Developers Task Force as a home for his onboarding work. Both the developers and practioners groups can benefit from mentoring and hackathons but with different orientations and level of specificity. Hopefully any hackathons organized with Team participation would coordinate with one or both of the developer and practioner task forces. |
I guess you mean you prefer kebab-case to camelCase. I don't find camelCase to be any stranger in itself than the convention of PascalCase for classes and camelCase for properties. Other common alternatives are snake_case and PascalCase. None of these are particularly natural or easy to write or read at all times. It probably does make some sense to pick one, as much as is possible for the permissionlessly extensible Solid "project", or to define roles for each, and to note this/these in all relevant programmer/implementer guides. |
|
@TallTed , I skipped mentioning the context but it was about the filenames / URLs of the tasks in this PR. Vegan kebab-case and snake_case is generally common out there and recommended - easier for humans at the very least to distinguish the terms. FWIW. Pascal/camelCase is generally common for coders. |
tasks/solidCommunityCss.md
Outdated
| # Upgrade SolidCommunity.net to CSS | ||
|
|
||
| ## Responsibilities | ||
| Currently, SolidCommunity.net is running on NSS. In order to depricate NSS, it should be upgraded to CSS. Preferably, this upgrade will have no effecto on the users of SolidCommunity.net outside of the aestetics of the UI. |
There was a problem hiding this comment.
| # Upgrade SolidCommunity.net to CSS | |
| ## Responsibilities | |
| Currently, SolidCommunity.net is running on NSS. In order to depricate NSS, it should be upgraded to CSS. Preferably, this upgrade will have no effecto on the users of SolidCommunity.net outside of the aestetics of the UI. | |
| # Migrate SolidCommunity.net server from NSS to CSS | |
| ## Responsibilities | |
| Currently, [SolidCommunity.net](https://solidcommunity.net/) is running on [NSS](https://github.com/nodeSolidServer/node-solid-server). This work changes the server from NSS to [CSS](https://github.com/CommunitySolidServer/CommunitySolidServer/). Preferably, this change will have no effect on the users of SolidCommunity.net outside of the aesthetics of the UI. Certain components, such as WAC, will be unchanged. |
WAC bit is as stated by @timbl in Solid Team.
There was a problem hiding this comment.
Small tweaks to @csarven's suggestion
| # Upgrade SolidCommunity.net to CSS | |
| ## Responsibilities | |
| Currently, SolidCommunity.net is running on NSS. In order to depricate NSS, it should be upgraded to CSS. Preferably, this upgrade will have no effecto on the users of SolidCommunity.net outside of the aestetics of the UI. | |
| # Migrate SolidCommunity.net server from NSS to CSS | |
| ## Responsibilities | |
| Currently, [SolidCommunity.net](https://solidcommunity.net/) is running on [NSS](https://github.com/nodeSolidServer/node-solid-server). This work changes the server from NSS to [CSS](https://github.com/CommunitySolidServer/CommunitySolidServer/). We intend this change to have no effect on the users of SolidCommunity.net outside of the aesthetics of the UI. Certain components, such as WAC, will be unchanged. |
|
Thanks for mentioning me, @jeff-zucker ! I would love to be a part of this team in any capacity, and if I could help by leading a group for developers, even better, as that's what I hope to focus on (development and onboarding), whether officially or unofficially. Do I need to apply to be a part of the Solid Team? I looked at the Readme on the main page, and followed the "Join the Solid Team" link, but it wasn't clear. Please let me know, thanks! |
The Practitioner Engagement Task Force is an excellent idea. We have a team working on a platform to streamline the delivery of social and municipal services and it would be very valuable to share experiences with other teams working on real-world Solid projects. |
👍 Totally agree @pinfold @jeff-zucker. I think it's actually very necessary (more than an excellent idea) from a community point of view. Growing the community is needed initially for developing the core of the spec. I think we reached a point where the community should be more about adoption. |
|
In the light of #46 I think it's better if we remove the explicit mention of Solid World from the team scope, and instead mention something like "support Solid-branded events like Solid Symposium and others as and when needed" |
|
The members of the Solid Team are in a unique position to know what is going on in Solid - we create and monitor changes to the website and community server; we hear about the work of the CG, COCC, Practitioners, and other key parts of Solid directly; we monitor the forums and chat rooms; we have the participation of @timbl. There is no other group I am aware of that covers such a broad spectrum of the Solidverse or is in a better position to let the world know about Solid. Not that it should ever be the source, but the Team is the broadest source. Wnen Timea was MCing Solid World she always left space for a short "news from the Team" section and I think that should be reinstated. Further, I believe we as a Team have a responsibility to model and promote the principles we believe in - the use of the web for net social benefit and diversity of all kinds. If there is ever going to be a concerted outreach to the global south or to other under-represented populations, where should it come from if not the Solid Team? We need people to write specs and create data models. How can we attract them without outreach? And if that outreach is not based on diversity, how else will anyone in the outside world gain confidence that Solid practices what it preaches? And any such diviersity-based outreach will be weaker if it is not done in coordination with others and is not done by a group of people with a broad knowledge of the Solidverse. For these reasons, I am not in favor of off-loading Solid World or other initiatives. I am in favor of Virginia's proposal to have them carried out by community members under the oversight of the Team. I would hope that some of these initiatives can be supported by companies but with the understanding that the oversight remains with the Team. I would also hope that we can find support from a foundation for a broader outreach and diversity effort. If such funding is obtained it would be even more important to coordinate the outreach and the publicizing so having Team events, publications, and web resources under one roof will be even more important. |
That's why I say, let events be organised by whoever is organising them, if any problem arises around branding or conduct then the team or the CoCC can step in, but otherwise I think we should not stand in the way of anyone and let a thousand flowers bloom. I also think any communication around Solid World or other events can say they are "organised by the community" but they cannot say they are "organised by the Solid team" or "organised by the Solid project". I'm documenting this here because Virginia asked me to. Whenever I say the team has no business "supervising" the Solid World organisers, I get the response "but we have it in our scope". So my solution is: let's remove it from our scope, be done with it, and spend our energy on other things such as https://matrix.to/#/!SWuPNCVLGJhfHYZIxj:gitter.im/$A9EsN5kMVhMsuo5G7RoDYyoruEPZdxCxoUvM3pxRAwY?via=gitter.im&via=matrix.org |
You misunderstand my use of the word oversight, which was perhaps the wrong word. I don't mean it in the sense of supervise but in the sense of coordinate. The Team should support a coordinated effort to broaden the Solid community and that includes things like Solid World. But not in isolation, we should have a showcase like it, and a website, and a newsletter which work in coordination to broaden Solid. Just to give one example of a coordinated outreach. Suppose Women in Solid came to the Team with the idea of a coordinated burst of attention to broadening gender diversity in Solid. We could have forum discussions, newsletter items, and a Solid World made up of developers from the Women in Solid group. That would take coordination.
We have been over this multiple times for the past year and have said repeatedly that no one expects that . What we expect are things like coordination on topics, and a transparent selection process oriented towards the principles of DEI.
What we have expected is that the organizer of Solid World is a member of the Solid Team. It is not a matter of the Team dictating to that organizer, but of the organizer being part of the team with the expectation that the organizer give general reports when appropriate and be open to suggestions and discussion from other team members., No one is interested in micro-managing. If the current organizer of Solid World had participated in this way, even minimally, we would not be having this discussion.
There is nothing about the Team taking responsibility for a single event that in any way prevents or discourages anyone else from blooming. If Inrupt wants to continue with "Inrupt Solid Showcase", they are welcome to, as is anyone else to create any event they want. Why would the fact of the Team having an event prevent anyone else from having an event? |
* Removed "blocked" statuses until we have a definition and explanation for said status * Removed CoC enforcement as task, as this fall under the purview of CoC Committee * Minor fixes, rename files camelcase > kebab case
VirginiaBalseiro
force-pushed
the
scope-of-team
branch
from
8a92927
to
98f5596
Compare
…nd In Person Meetups
I have incorporated this here: 9538bb9 Let me know if that covers it or I should modify anything. |
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
| @@ -2,8 +2,8 @@ | |||
|
|
|||
| ## Responsibilities | |||
|
|
|||
| There are certain tasks that the Solid Team wants to do, but does not have the resources to do it. That's where fundraising is important. Members of the fundraising task are responsible for finding grants/methods to raise funds for the Solid team. | |||
| There are certain tasks that the Solid Team wants to do, but does not have the necessary resources. That's where fundraising is important. Members of the fundraising task force find grants/methods to raise funds for the Solid team. | |||
There was a problem hiding this comment.
| There are certain tasks that the Solid Team wants to do, but does not have the necessary resources. That's where fundraising is important. Members of the fundraising task force find grants/methods to raise funds for the Solid team. | |
| There are certain tasks that the Solid Team wants to do, but does not have the necessary resources. That's where fundraising is important. Members of the fundraising task force find grants and other means by which to raise funds for the Solid team. |
| @@ -2,8 +2,8 @@ | |||
|
|
|||
| ## Responsibilities | |||
|
|
|||
| Members of the Meeting Organization Task are responsible for organizing meetings. This includes sending calendar invites, messages, and emails to update members of reoccurring and special meetings. It also includes ensuring that meeting minutes are recorded in the [meetings folder](/meetings/). | |||
| Members of the Meeting Organization Task Force are responsible for organizing meetings. This includes sending calendar invites, messages, and emails to update members of reoccurring and special meetings. It also includes ensuring that meeting minutes are recorded in the [meetings folder](/meetings/). | |||
There was a problem hiding this comment.
| Members of the Meeting Organization Task Force are responsible for organizing meetings. This includes sending calendar invites, messages, and emails to update members of reoccurring and special meetings. It also includes ensuring that meeting minutes are recorded in the [meetings folder](/meetings/). | |
| Members of the Meeting Organization Task Force organize meetings. This includes sending calendar invites, messages, and emails to update members of reoccurring and special meetings. It also includes ensuring that meeting minutes are recorded in the [meetings folder](/meetings/). |
| Members of the [Practitioners Task Force](https://github.com/solid-contrib/practitioners) engage with individuals and organizations building Solid software for use in the real world. The Practitioners Task Force should provide networking and collaborating opportunities such as regular online meetups and github repos; provide a pathway between working practitioners and other parts of the Solid community such as the W3C Community Group, SolidProject.org, and Solid World; and support efforts to highlight and publicize the work of practitioners. In keeping with the Solid vision, the Practitioners Task Force should pay special attention to socially beneficial initiatives and strive for diversity of participation. The Practitioners lead should keep the Solid Team informed about practitioner activity. | ||
|
|
||
| ## Task Members |
There was a problem hiding this comment.
| Members of the [Practitioners Task Force](https://github.com/solid-contrib/practitioners) engage with individuals and organizations building Solid software for use in the real world. The Practitioners Task Force should provide networking and collaborating opportunities such as regular online meetups and github repos; provide a pathway between working practitioners and other parts of the Solid community such as the W3C Community Group, SolidProject.org, and Solid World; and support efforts to highlight and publicize the work of practitioners. In keeping with the Solid vision, the Practitioners Task Force should pay special attention to socially beneficial initiatives and strive for diversity of participation. The Practitioners lead should keep the Solid Team informed about practitioner activity. | |
| ## Task Members | |
| Members of the [Practitioners Engagement Task Force](https://github.com/solid-contrib/practitioners) engage with individuals and organizations building Solid software for use in the real world. The Practitioners Task Force should provide networking and collaborating opportunities such as regular online meetups and github repos; provide a pathway between working practitioners and other parts of the Solid community such as the W3C Community Group, SolidProject.org, and Solid World; and support efforts to highlight and publicize the work of practitioners. In keeping with the Solid vision, the Practitioners Task Force should pay special attention to socially beneficial initiatives and strive for diversity of participation. The Practitioners lead should keep the Solid Team informed about practitioner activity. | |
| ## Task Force Members |
There was a problem hiding this comment.
Given that this is not currently "Officially" how we work. Let's add this to the agenda for the next Solid Team meeting to discuss with the larger team. It would also be useful to link to a definition for consensus as it means different things to different people.
Made a PR to discuss separately: #49 |
This PR summarizes the findings and perscriptions of an exercise conducted by the Solid Team to solidify the scope of the Solid Team, as represented in these meeting minutes: