-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add open properties, and make company list a table (fixes #25) #27
Conversation
Thanks for kicking it off! Would you like to keep this PR open to start filling the table? I feel like it's kind of pointless to make the change without adding at least some of the additional information it supports. Also, there are two minor fixes needed: re-add spaces between the icons and the corresponding titles, and remove the parenthesis around the statement links (perhaps the quote marks too, if you think that makes sense). |
Sure. Could you rank the properties so that I may start with the highest priority ones? |
Phew, that's kinda hard :) Perhaps @whit537 will have better insight. From my POV, I'd rank "open product" highest, followed by (in order of implementation ease) open standards, open communication, and open finance. The latter tree are IMO reversed in terms of actual impact for openness, but I list them like that because I see openness as a multi-staged route where each step is harder (i.e. has more cultural resistance) but is supported by the previous ones. Let me know if you agree -- this is just one guy's opinion :) |
I agree with most of your opinion. The open communication and finance are hard to compare IMO, as the operation details can be as sensitive as finance. Maybe I should clarify the meaning of open communication first. As open product in most cases already includes open discussion about development (public bug/issue tracker), I assume open communication is more about the decision making processes about tech/human/finance resources. |
Well, I would define "open product" to mean only open source/open hardware/open specs or equivalent. For open communication, I'd consider an IRC channel, a public issue tracker (even if there's a private one for sensitive issues or something like that), etc., where developers engage with users, as valid for those purposes. E.g. UserVoice portals, or even blogs or twitter accounts can be considered open communication channels if there really is some meaningful (i.e. consequential from the POV of the product) interaction between those employed by the company and their "prosumers". Open decision-making is likely even harder than open finance, since it requires non only transparency, but relinquishing control to some degree. We probably should split that concept from open communication channels, which would make these both concepts better defined and easier to assess. |
Indeed. Even if the decision-making can be just read-only to public, it'll inevitably cause feedback which will be hard to ignore completely. |
Please check again. I filled in open product & finance columns. |
Will review tomorrow. Sorry for the delay :/ |
@nobodxbodon, it looks great! This table approach clearly helps define "open company" in a more concrete way, and make our coverage of those aspects more visible. Regarding your question:
No, it's neither realistic nor the expectation. Quoting the guidelines for inclusion document:
Following from that, by the way, I'm wondering if we should have the "openness" link in a separate column, and leave the first column to have just the name and main URL of each company. What do you think? |
@waldyrious, do we need to merge the "openness" link with current "statement" column then? About the explicit requirement, I wonder how we can track/collect those companies that meet it? Or do we need to rely on those companies to find this project and contribute to it? |
@nobodxbodon I wouldn't say so, because the former is a static page and (to quote the inclusion guidelines) "easily reachable -- either present in the main navigation menu, or otherwise reachable within 1-2 clicks from the home page", while the latter is typically a blog post or at least written more in the style of an opinion piece, retrospective, or somesuch.
Not sure I'm getting what you're asking here -- could you clarify? Assuming the explicit requirement is clearly defined (let me know if it isn't as clear, or visible, as I thought!) as a dedicated page or section about openness accessible from the main page on the company's website, it doesn't sound like something hard to verify. Are you asking how to deal with companies that are committed to openness, but haven't expressed it in this particular way? |
After a second thought, I'm not sure it's necessary to add 'Openness' column. As the "only one explicit requirement" is the page with commitment description, it makes sense that the first column is its link, instead of the company homepage. Besides, if the column is named as 'Openness', it sounds like an overall property, instead of the individual properties like the other columns (open product, open finance, etc). |
That's more compact, sure, but I think it would be nice to have a "company" column with the name and the homepage link, and then the relevant openness properties to the right. Also because the inclusion guidelines are not set in stone, so it isn't a given that the openness page will always be the single required openness property. (In fact, I'd like to hear your thoughts about whether having that one as the single requirement makes sense, or whether we should include something else now that we are defining the remaining properties more explicitly.) |
It seems to me the requirement is mostly subjective at the moment. IMO instead of deciding a standard at this moment, it is more important to cover all the aspects of openness, so that it will be clearer which aspects are distinguishable and essential. The page of describing commitment to openness seems to me proper to be an aspect named "claiming" or "self statement", rather than general term as "openness", which would make it sounds like the criteria to be included in the list. About the issue of how to track/collect the open companies, I meant the scalability and maintainability of this project. Obviously we can't monitor every new company and check if they meet the requirements. Even keeping track of the companies on the list can be quite some workload. So how can we keep the list up-to-date? |
Agreed. What about "openness pledge"?
I'm quite comfortable with the project being a community-curated list, in the sense that the maintainers ought to try to keep it up to date to the best of their knowledge, but aren't expected to actively go out seeking new entries to add (though they can certainly do so if they wish!). It's a model similar to Wikipedia, where people who come across the list and are interested in the topic will likely know of other companies that could be added, so as long as we keep a welcoming and responsive stance towards contributions, it's likely that the project will remain active and as up-to-date as those interested in it want it to. Does that make sense to you? |
Sounds good. I'll add the column and put the company homepage in the first column. Some have the pledge on the homepage so they'll be the same link.
The up-to-dateness would rely on the page visits then. Is this page referenced in other popular pages, like the pages related with open business in Wikipedia? Also, are all the companies notified about their presence in the list? They may be happy to find the other companies with the same values. |
Cool 👍
Kind of. It will depend on the popularity of both the project and of the companies. It's a model similar to Wikipedia's: more popular pages get more visits and therefore more vandalism, but also more eyes ensuring they are correct and up to date. One could say this kind of system balances out naturally: if nobody's bothered about the absence of open company X on the list (or correctness/completeness of its entry), it's likely a sign that the company isn't that impactful, so readers of the list won't be too harmed by its lack of proper coverage.
Not sure; I believe Wikipedia doesn't reference it, but we could probably add the link to the relevant pages, which shouldn't be a problem since there's no commercial interest and the criterion for inclusion are objective and community-determined. Once this PR is merged I'll add the link to the relevant articles.
The original opencompany.org system relied on active participation of the listed companies, but that is potentially cumbersome if some of them don't have eyes/hands available to comply with the pledge requirements (that's what prompted me to start this list -- see opencompany/www.opencompany.org#103 and opencompany/www.opencompany.org#130 for background). So the goal is to be independent of the companies' involvement, but we can certainly reach out to them :) |
Please check the new commit. Would you please open a new issue to keep track of adding the link relevant wiki pages? |
Looks good :) a few observations:
As for your question, I'm a bit confused by what you mean by "link relevant wiki pages". Can you clarify? |
Your three points addressed. PTAL. |
Oh, you meant the wikipedia page! I thought you were referring to this repo's wiki, hence my confusion :) sure, I'll create an issue to track that. |
@nobodxbodon sorry for the delay. I've looked into the latest changes and I believe the table is in a state worth merging. Further improvements can be made later, including filling in more cells. Please confirm if you're ok with me merging this. Furthermore, I will give you access to the repository (let me know if you'd like to join the OpenCompany org as well), so you can make quick fixes without delay. For larger changes, PRs are still preferred. |
Sure please go ahead with merging. Thanks for granting me access. |
I'm not sure what is visible in https://github.com/orgs/opencompany to you -- please take a look and let me know if you have any questions. In any case, org membership is kind of a fluid thing -- it aims to reflect those doing active work in OCI's mission, rather than some sort of sanctioned role. |
I added the properties as discussed in the issue, without any additional links yet.