@hpy I added a page titled “projects” under the about section on openhardware.science which redirects to https://gosh-community.gitlab.io/gosh-okh-search/ for now - if a sub-domain is created I am happy to put that link there instead. (there’s also a page for communities such as reGOSH and AfricaOSH as well if anyone wants to check that out too )
Happy to hear feedback from others on adding it to the website!
Ah, cheers @blaise and sorry I missed your question before @Juliencolomb. These are not actually explicitely “GOSH” projects. Technically they are just science related hardware I filtered out of the main list manually. My post title here was a bit misleading. I believe, in practice, all but one of them are from GOSH community members though.
As we build out the list, and automate the manual process of filtering (and yes, add tags for browsing!) we may see more projects from people who don’t even know what GOSH is. It’s also worth making that clear on the page itself: that this is a list of open science hardware projects from around the web.
EDIT: Though it might actually make more sense to go the other way: for GOSH community to add their projects to this list and feed that up to the main site.
Since there is no formal “membership” of GOSH (beyond the director and officer roles, if those are the right words) and anyone can join this forum, I think it’s totally OK to be a bit loose with who’s project gets added as long as there is consent from the creators (and adding a OKH manifest to their project indicates consent).
That is they way I had been thinking about it when writing about it for “v2” of this project:
I think it would make sense to contact https://en.oho.wiki/wiki/Home: you do not have to reinvent the wheel and they are already crawling the net for manifest files (I think). @rmies can tell more about this.
For GOSH relation, at first glance, it seems to me we would need authors to indicate it, at best somewhere in the manifest (not sure where it could go, though).
In theory, we could then take oho data and filter it by that “GOSH project” tag and show them on the website.
I have been touching base with OHO/LOSH people through the IOP alliance meetings and others. I am taking a bit of a different approach with OKH search, specifically, as the plan stands, we are not going to use a crawler. Instead we will to build this federation of communities (as illustrated above). These communities can self-curate and get a page listing their projects (like this GOSH page).
That does make sense, but I do I think it makes more sense to go the other way: to present GOSH projects on this page and let OHO crawl it if they want to.
Hi Kaspar,
sorry for the naive question, but populating the OKH search directory/list will automatically populate the GOSH one? or are these two separate things that need to be entered manually twice?
Yesss I’m familiar with it, and it is great! Thanks
On where to add stuff
Oh ok. I think there is a general need for an active projects directory. We have considered adding projects to the OHO “wiki” (mentioned above), or to the WikiData list (on which @jarancio has worked, if I understood correctly).
There are a few recruitable GOSHers who might be willing to work on adding [their] projects, with a small chance of forming a working group around all this.
On how to add stuff
I understand that the current way to contribute is to (1) make a YAML file, (2) put it up somewhere, (3) make a PR to add it to the JSON file at the repo.
I could have done it for my project by now, but I never seem to find the time to go through those steps. Perhaps it is true for others.
Is there a more straightforward way to add projects? I imagine that even a forms could work.
Sligthly off-topic: is there an open-know-who?
There was also a clear interest in having a GOSH people directory.
This sounds very similar to what the OHM folks have (i.e. the “experts” directory @jarancio?).
To sum up, I’m looking for a happy way to help move this initiative forward. Thanks a lot
No, not yet. That’s still the way to do it currently. You can now add the file itself to the local-manifests folder on Gitlab and it should get added. There is also this form that generates a manifest.
Oh, and it’s worth mentioning that if you’d like to continue to use OKH for your effort @naikymen then you can also ask questions or make suggestions on the IOP Alliance forum here: