The Community 6 * ten thousands problem:
How do we keep track of
10,000 user-developers, artists, 3D scanner hobbyists, museum curators, architectural historians, engineering students, etc.
Note: these numbers are approximate, but will guide our thinking on this problem until we have a solution. I think there may be 10,000 ways. And only a few good ones. And probably, 200-400 years, minimum.
We don't want to spend 10,000 hours figuring this out, so it would be best to enlist some experts. We also don't want to keep parts on 10,000 damn websites. 2-3 websites is better than 10,000 websites, and 1 website twice or thrice as good, because it means 10,000 less outgoing links to mirrored content to check.
Yes. 200-400+ years for things like scans of sculpture from the 1600s.
10,000 user-developers, minimum.
At least a few dozen languages.
Definitely 1000 gears, etc.
Certainly a few dozen repstraps.
Hopefully a few dozen RepRaps.
Only one Policy that we generally try to follow, and the responsible site administrators definitely follow, and that needs editing before we show it to the EFF and Archive.org for review, let alone a museum curator or paper library archivist!
This is utterly impossible!
No it's not. We can do it with clever scripting, lots of server space, and an "agile" website written with good software architecture and social networking principals in mind.
We might be able to do it all with a mediawiki. Maybe.
Are you crazy?
Nope. We're patient. And unstoppable. Not that we don't mind volunteer help from software architects, library archivists, and users who want to upload to RepRap.org. In fact, we are actively soliciting volunteer help from software architects, library archivists, and users uploads. --Sebastien Bailard 02:58, 24 January 2010 (UTC) (firstname.lastname@example.org)
Many reasons. And hey, wikipedia is a good helpful resource for people, and RepRap machines are about making fun stuff and useful stuff for people, so the RepRap.org should be a good, maximally helpful resource for people scanning with RepRaps, printing with RepRaps and building RepRaps. Aka RepRap user-developers.
Does this matter? I only came here to make a RepRap, I don't care about that stuff
No worries! Our primary job is the RepRap documentation, but many of us work on how to document things to make with RepRaps. And why are you reading this? This is a library issue.
We are still defining the problem. "Projects, Parts, Arts, and Docs" is pithy, but I don't know what it means.
This is an information science problem, and a social networking problem.