-
Notifications
You must be signed in to change notification settings - Fork 27
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
improve repository structure in openvocab orga #23
Comments
We do intend to create another substream focused on process. If IPO tables
wants to take an active part, that would immediately trigger the substream.
|
@Lars2i what do you think? To my understanding you don't want to get into exchanges and currencies aspect of OVN. But if we isolate process aspect nicely as well as ressources (or assets) for I/0, we would all find nice common ground to work on. |
👍
|
i also recommend we update meta, as it hasn't changed since this org began; i think it could be useful to link the repos together, provide overall context, and be a space for discussions like this. |
@elf-pavlik @ahdinosaur - I'm good with whatever restructuring you all want to do. |
@elf-pavlik from what i understand, sounds good. |
Do you all want to initiate the projects repo, or should I do it? If you do it, please make it so both we (NRP) and IPOTables can comfortably use it. For example, include something like: And if I do it, I'll include something similar that would show the IPOTables view. @Lars2i - got any suggestions? Is some of the language and the diagram from http://ipotables.net/ good for starters? Then we can work out the details in issues. |
@bhaugen please just go ahead and start process repository including in the README whatever you see fitting there. We can all iterate from it using issues and pull request workflow 🎯 @ahdinosaur I don't understand difference between ovn and meta repositories 😕 Can't we just move few bits of information from meta to ovn and then if really needed rename it? |
First draft done: https://github.com/openvocab/process Please improve. |
@elf-pavlik my thinking is that this org is for all vocabs, not only value network vocabs although that's what i'm most interested in. but happy with whatever the group wants to do with this org, i'll follow along. |
from #17 (comment), 👍 to a separate vocab repo for resource, as it seems "assets" from "Open OS" (which i'm now using as my reference Enspiral use case for Holodex) would be resources with relationships but no exchanges or processes. |
i'm thinking this repo should be our "home repo" for this org. to me, this means:
thoughts? |
@ahdinosaur sounds good to me. Except I don't get the last one.... and I noticed that you have a generated context, and then I put out my context attempt in a different place.... sorry! |
@fosterlynn yeah, at the moment i'm thinking we follow @elf-pavlik's lead and put our per-vocab contexts within each vocabulary repo (based on the examples in that repo's markdown), then somehow we build everything all together (which may include using markdown sources in this repo) into the website. this is all open for discussion and/or an experiment to find what works best through trying things out. |
not sure how you did renaming of orgas but now both exist it also got gitter chat room freaked out 😉 |
https://gitter.im/valueflows seems to be a little confused, but also seems to work. I take that back, it was working earlier this morning, but when I reloaded the page, it does not appear to be working... Clicked on the name in the left panel several times, and got back in. Freaked out is an accurate description! |
yeah, that was me renaming and then creating |
I sorta waiting to see if @elf-pavlik and @fosterlynn can get to the valueflows chat room. If not, https://gitter.im/gitterHQ/gitter seems to be a pretty good place to ask for help. |
I can't get in, I get to a page for valueflows, but nothing is there, can provide details if it will help. |
https://gitter.im/valueflows seems to work again, thanks to an intervention by @mydigitalself of gitter. |
https://github.com/openvocab
The text was updated successfully, but these errors were encountered: