It seems we have a new Pharo GH organization every day! There is for example (pharo-project, pharo-vcs, pharo-rdbms...). The problem is that each of these creates another entry point that must be known to users, and therefore another list for us to manually maintain, and we know the struggle of keeping docs in sync quite well. My question is: why can't we consolidate into a few general buckets (like one for official and one for community) and manage the categorization with GH topics (a.k.a. tags) and teams? Here's a discussion of this idea: https://github.community/t5/How-to-use-Git-and-GitHub/Structuring-repositori... IIUC you can use teams to scope the access for each repo. With topics/tags, someone could just go to the one organization and search for vcs or rdbms to see a list of just those repos. Here's an example of a saved search like that: https://github.com/atom/?utf8=â&q=topic%3Apackage&type=&language= ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html