Two ideas:
How about the simplest solution like, just make an open repository for people to post what they like. There can be rules like:
o revise the first post for any revisions to the program, concept, etc.
o intact (fully working) programs shall be only attachments, inline code shall be reserved for conversations.
o program archived shall contain, source code, pseudo code, documentation, revision log, licence, etc.
...
but this will allow everyone to post no matter what they think their level is or even if most may not find it profound.
OR
What about just removing the need for two threads (one here and one in the archive section). The archives can still be locked down and only mod's can post. What im thinking is simple; i imagine that a few people are timid about having their code posted along with a critique thread where the general public can ask questions or pick it apart. This way if a user has a question about an archive app the user is forced to create a thread like
sub: (archive: bob's lisp) formula validation
topic: bob where did you get that formula? Ive always used...
Now the second method will result in more (duplicate) threads in the discussion area but that is where vBulletin's similar threads feature can come into play. Well you get my point I think.
***
I am only thinking back to when i was excited to post my newest creation. My first `look at this code' was pitiful (well maybe not my first, prolly my last *lol*) but I also wasn't afraid to post it amongst people like Kenny Ramage, Dave Stein, R. Robert Bell, etc. because of this simple fact.
Bookmarks