Comments (7)
Ok, fair enough. I've updated the title of the issue and edited the original comment accordingly. Some examples were requested, so I left those in.
I am aware of the interoperability panel and have been following the minutes.
Thank you. I think more accessible communication and interaction about the good work that's happening out in the open could go a long way towards addressing some of the concerns you report. Since you've been following the interoperability activity, I'd welcome any thoughts you have on how we could better communicate what we're up to so people feel more informed or even more inclined to participate.
from process.
Nobody from the forum, afaict, is working on solid-panes. The mashlib has been in a state that has been described as a proof of concept, and clunky.
If so, I'm sure everyone can benefit from your contributions to those projects.
from process.
I fail to see how (your perceived) lack of activity or quality in those projects is process related. I don't know why you can't turn that around into something useful to all. Clearly you deeply care about those repositories/projects as you've brought them up. You can reach out to folks that have worked on them to get you going. Would you like introductions?
from process.
@sideshowtom The scope of the Solid project is to evolve the ecosystem of Solid specifications so that they can be used by anyone freely in the public or private space. We operate under the Solid Process in an open and transparent fashion. Minutes are filed on the community group wiki, or in the github repository for each panel. We cannot speak on behalf of any private company, and consequently it's inappropriate to file issues here targeting any individual organization. If you have a question or issue to raise with a private company, i suggest you take it up with them directly.
Our top focus in the Solid project is to create specifications and standard patterns that can be used by everyone to create software. It's up to the community, which is made up of individuals, academia, and organizations from the public and private sector, to take these specifications and develop on them. We cannot control what any of them do - we can only do our best to improve the specifications so that all of you can do more with them, and support any implementation that aims to codify them as best we can.
Nobody from the forum, afaict, is working on solid-panes. The mashlib has been in a state that has been described as a proof of concept, and clunky.
Any issues or concerns that you have around software like mashlib or solid-panes should be addressed in that specific software repository. We could certainly discuss how the work we're doing on the specifications influences software like mashlib or solid-panes - but your comment seems to be directed more at the user experience of those specific implementations, and so it should be directed to people working in those respective repositories so they can address your concerns properly.
Another similar example is in the area of data interoperability.
Were you aware that there's a data interoperability panel that meets weekly?
If they had more information, especially about what is not getting attention, they would probably be more inclined to pitch in.
If you want more perspective on what we're focusing on in the interoperability panel, you can start by reading the Problems and Goals that are guiding our current work.
All panel sessions are open to anyone that wants to join, and we do our work out in the open. If you'd like a run-through of current interoperability panel work items, join a session and we'll take you through them.
I'm sure there are ways we can improve how we communicate what we're up to across the various panels to keep the community informed. If you have suggestions on how we can do that, we're always happy to listen. In fact, that is the type of feedback we were hoping to elicit in #202.
Circling back to the title of this specific issue, and content in the original post related to a private organization - it really doesn't belong here. I believe your aim is to be constructive, and in that light am respectfully requesting that you update the issue title and contents of the original post to remove any speculation about private companies, and instead refocus it on the issues and concerns that we can and should actually address in this venue. Otherwise this issue isn't constructive as reported.
from process.
Ok, fair enough. I've updated the title of the issue and edited the original comment accordingly. Some examples were requested, so I left those in.
I am aware of the interoperability panel and have been following the minutes.
from process.
I thought I was being constructive, but it turns out I'm just a process problem.
from process.
Now its you that's off topic. It isn't just me that is hanging back, and I think the topic of the issue is one of the reasons. It seems to me that issue can be addressed on its own merits.
from process.
Related Issues (20)
- Create a private Gitter room for Women of Solid HOT 6
- Proposal to establish a Solid Verifiable Credentials Panel HOT 1
- Proposal to re-establish the Solid Notifications Panel HOT 1
- Proposal: ensure the Solid GitHub organization only contains working code and up-to-date documents HOT 4
- heads up
- Include a consequences section in Solid Code of Conduct HOT 2
- Update text or reference to aims of the Solid Gitter channels HOT 3
- Use of @solid npm namespace
- Add activity period to roles HOT 1
- Remove panellists from panel information
- Process for domain renewal HOT 2
- Repo security policies
- Propose W3C Solid Working Group Charter
- Linked Data / Solid Resource Version? HOT 5
- The Future of Creators HOT 7
- Please provide contact information that does not rely on solidcommunity.net being up
- Replace panels with breakout task forces HOT 6
- Update Solid Process parts that are not already in the CG charter
- MIT License and/or W3C CLA and FSA HOT 36
- Describe how CoC committee gets updated HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from process.