organization
organization copied to clipboard
opensourcedesign
Merge "organization" related repos into this one
Since I am probably the one most responsible for creating so many repos, I admit I was a lil bit repo-happy in previous times... thus, there is a bit of confusion, so it's time to start condensing and pruning things. Similar to the goals of using submodules to make this easier to contribute and participate!
I originally envisioned using this repo organization as a place for operational related things pertaining to "running the organization / community" which is Open Source Design at a meta level, yet things which did not pertain to the website, or content related things (jobs, talks, fonts, etc...).
The three low hanging fruit repos I would like to merge into this repo are:
- [x] Merge funding repo
- [ ] Port over content in funding Issues
- [ ] Merge resources repo
- [ ] Port over content in resources Issues
- [x] Merge Design-Brief repo
It may also make sense to merge events into here, but seeing as those are specific content items, might be best to leave that separate.
Once a few people chime in and feel OK with this decision, I will proceed in the coming days.
I was poking around for an issue mover - what do you think of this: https://github.com/google/github-issue-mover?
Or would you rather just create some articles if they're more "conversation" and link to those?
what do you think of this: https://github.com/google/github-issue-mover?
Interesting. That looks promising.
Or would you rather just create some articles if they're more "conversation" and link to those?
Maybe a mixture of moving some, but also distilling the knowledge down? I feel there are lots of good links and perspectives in those existing threads- but not lot of action based on said links.
My initial goal with the "funding" repo was to create a structure/pipeline for transparency collaborating to raise funds and grow OSD. However, an emergent benefit should be, nice documentation to help projects looking for funding and such to find said information...
My initial goal with the "funding" repo was to create a structure/pipeline for transparency collaborating to raise funds and grow OSD. However, an emergent benefit should be, nice documentation to help projects looking for funding and such to find said information...
I think that this type of content should actually go there. Having different repos for different areas is legitimate; it allows us to filter issues much better than using labels or string tags in the titles does. I think what needs to be clearer isn't the repo structure (which is what you're trying to do by merging them here), but the collaboration pipeline. Have a note in the README asking people to open issues for what they want to discuss.
Only one remark about the resources repo: It was the first repository and holds a bit of history for the organization, so I’m not sure if we should entirely remove it. :) Maybe port it to a branch.
In any case I think the resources repo should be half merged with the website (the actual list of resources) and only the other half into the organization, like the people part for example. :)
