This kind of should be in the brainstorming section, but it's more related to development, AND since Noccy will probably never give me a solid spec, I decided to post here.
If you don't know what Commons is, go read my post from last year explaining it. This spec will obviously be language agnostic, so try not to suggest funky names that won't really fit. Here's what we came up with so far.
Obviously the spec is far from finished. And notice the naming conventions, try to keep it short, succinct, devoid of multiple words or dashes or weird names, and try not to suggest toplevel modules. Toplevel modules should be categories, like "net", "io", "os", "fs", etc. The idea is to supplement the stdlib of various languages.
Read the comments on that page and see if you can come up with some ideas. It would be greatly appreciated. As much as I'd like to just go ahead and port all my code from miniature to what we have so far in terms of a spec, I really want to wait until it's at least 80% complete and covers most of what we'll need in Bongos - i.e., "net" and "os"-related.
Now the first incarnation of Commons will be implemented in Python, so for those of you who are Pythonistas, try not to deviate too much from standard library naming, organization, etc. (and for those curious, yes, some libraries can be proxies to stdlib libraries, f.ex, commons.re, commons.os.path, and so on)
I couldn't do this myself, since I suck at organization. Look no further than my room. kthx
this time imma stand up and shout
imma do things my way, its my way, my way or the highway