29th August 2019
Hello and welcome to another edition of This Month in Solid!
Solid is a set of open specifications, built on existing open standards, that describes how to build applications in such a way that users can conveniently switch between data storage providers and application providers and take the data generated along.
This is a monthly summary of Solid progress.
Want something mentioned? Contact the Solid Manager at info@solidproject.org. This Month in Solid is openly developed on GitHub. If you find any errors in this month’s issue please submit a pull request.
Weekly Solid Call
Every Thursday there is an hour long public call where newcomers can introduce themselves, anyone can ask general questions about Solid, and we recap the weeks works on Solid.
You can read the minutes of this weeks call here.
Next weeks call will be on the 5th September at 1000 CEST on this line. You can find the agenda here where you can also add items by joining the W3C Solid Community Group or send an email to info@solidproject.org.
Press
Talks & Articles
Have you seen any articles or talks about Solid this week? If you’ve seen any talks, articles, or written blog posts about Solid please do send them over for next week. This week there were no talks or articles on Solid.
Upcoming Events
Solid Events are run by members of the Solid community like you. If you are interested in organising a Solid Event you may be interested in reading the tips for a organising successful Solid events here.
Date | Event | Organiser |
---|---|---|
10-10-2019 | Solid Amsterdam | Jeroen van Beele |
Solid Implementation
If you have any new apps, Pods, or identity providers or there are updates to existing Solid implementations make sure to add them to the list so they get included in next weeks edition. This week there are no new Pods and apps or updates to existing Pods and apps.
Solid Development
The Solid standard is currently referred to as the specification.
All work on Solid Development is carried out on the Solid GitHub account. Here is an overview of the the repositories on the Solid GitHub.
Solid Development Process
You can read about how development of the Solid specification works which is led by the editors.
This week there have been some process proposals that have been reviewed and accepted:
- Add editor assignments, permission scheme, and substantive changes
- include reference to links
- Update code-of-conduct.md
Conversations about these proposals happened on these issues which have now been closed:
- Current editor PRs do not provide sufficient details for an informed decision
- Style document with headings
- Definition of substantive changes in the editorial process might cause trouble
Conversation about process changes with activity this week:
Solid Development Roles
Editors
Editors are responsible for reviewing proposals to the Solid specification.
Anyone can apply to be an editor by submitting a pull request.
This week some new editors got appointed:
There are some open editor applications from:
Panellists
Solid Panels are groups of individuals focused on a specific problem or domain relevant to Solid, with an aim to propose changes to the Solid Specification, Solid Roadmap, and/or Supporting Documentation. Anyone may join a panel or suggest a new panel by submitting a pull request.
This week the Notification Panel was started and the Humans and Machines Panel was closed.
Sarven joined the App Authorisation Panel.
The Entry Document Panel switched the communication channel to issues on the specification repository.
Solid Proposal Development
Here is an overview of active panel conversations to work on generating proposals this week.
Proposals for Editorial Review
Anyone can draft a proposal and submit it for editorial review.
Below are a list of proposals that are ready for editorial review. If you are part of a panel and want to add a proposal for editorial review submit a pull request to add them to the list below.
Item | Proposal | Panel |
---|---|---|
Solid Specification | none | not applicable |
Solid Roadmap | none | not applicable |
Supporting Documentation | none | not applicable |
Editorial Revision
Proposals to Solid undergo editorial review by the editors.
This week the following proposals were reviewed.
Proposal | Associated Panel | Editorial Assignment | Substantive Change (yes/no) | Vote of Assigned Editors |
---|---|---|---|---|
Write CORS section | Specification Entry Document Panel | ————- | ————- | ————- |
Add HTTP section | Specification Entry Document Panel | ————- | ————- | ————- |
Updates on Solid Projects
Solid projects are activities happening on the Solid GitHub other than panels. Below are the links to where there were active conversations on each of the projects.
Node Solid Server Project
This week there was activity in the following channels:
- Server home page should link to pod when user is logged in
- PR # 1282 with minimized rewrite on resource-mapper.js
- Fix false response despite accept headers for containers
- :ant: Reuse ldp
- reduced solid server/api/microservice
- GET on ANY container with an index.html returns HTML, not Turtle
- Resource-mapper now considers content type when inserting index.html
- fix issues #1120 #1256 from NSS5.1.6 resource-mapper
Data Browser Project
This week there was activity in the following channels:
- Documentation
- Make the new module system in rdflib work
- Release mashlib as version 1.0.0
- Look at ContactPicker API for integration with Solid Contacts
- clean up forms-intro.html
- Allow either default or non-default export in pane API
- Cannot Add Address, Email or Phone to Profile
- Add Friends on Profile not working
- Publish to npm on every push
- Do Not Show “Log in” or “Sign Up for Solid” buttons when logged in and visiting another Pod
- Add form field for ORDERED list of things
- Remove/obsolete the part/sequence way of making forms
- Add enum choice field
- Writing away
import $rdf
to prepare for next version of rdflib - error on editing file.acl with solid-sharing pane
- Mashlib should work as a general purpose library
- Make mashlib work as a library again
- Generate GH-pages HTML files again (alternative approach)
- Data browser web app has vanished
- Generate GH-pages HTML files again
- Current mashlib.js and .css breaks the app
- The warning about using
require('mashlib')
should only be given if it is used - Reintroduce basicPreferences
- Add developer and power user mode
- A basic preferences global Pane that allows the user to indicate whether they’re a Power User and/or a Developer
- Transition to non-default export for rdflib v1
- Allow loading .ttl files
- 409 Error when attempting to edit Profile Highlight Color
- Restore undefined newThing
- Cannot Add Address, Email or Phone to Profile
- Move TrustedApplications to the basicPreferences Pane
- Move trustedApplications into basicPreferences
- Extract TTL for basicPreferences into own files
- Add link to delete user profile from basicPreferences
- Add account deletion link(s) to preferences
- Adjusting for changes in global dashboard in solid-panes
- Release solid-ui as version 1.0.0
- Movement path for user menu is unforgiving and sometimes behind other elements
- Move the content of the subheader into a footer
- Being able to delete existing pictures from “Edit your profile”
- Consolidate main.css and tabbedtab.css into one file: mash.css
- Should not list available panes within a global dashboard pane
- Profile picture looks weird in user menu
- Add “View your profile” in the user menu
- Forms UI should remove user input UI when resource not editable
- Only show panes based on the type of user
- Can create a folder at /(root) level but not edit the related .acl
- Allow for creation of ACL resources on folders directly under root
- Separating dashboard and outline
- 409 Error when attempting to edit Profile Highlight Color
- Prevent users from deleting their root ACLs
- Stop specific sharing pane on /(root) deletes .acl
- Adjusting for changes in global dashboard in solid-panes
- Tweaks to get the tests for tabs.js working
- Don’t store a field’s default value in the store
- Some default styles are missing from mash.css
- Filter panes based on user roles
- Adding audience
- Adding audience to panes and filtering based on that and user roles
- Adds feature to add cancelButton to end of tabs
- Added methods to filter panes based on user roles (Developer/PowerUser)
- The rounded corners on the tabs.js tabs are rather wide
- Separating dashboard and outline
Until next week!