Here are a few suggestions about features in sasq2.

The current project section isn't very good. We need a new one I think people should be able to register projects, and other people should be able to join the project. People involved in the project should be able to post news and source code. I think it would be best if project files were uploaded to a YPN controlled server (I guess you have at least a few MB left for this on 34sp, right?). I don't think we'll need more than a few MB's for the first projects. Everybody should be able to download the latest source/executables, and sometimes the project admin makes a stable release. I think it would be great with a 'to do' list for every project.

Now something about how to join a project. I don't think it would be a very good idea to let people join, and directly after that post source code. It would be good if you do like in ICQ, you request authorisation from the project administrator(s) to make you able to post sources, news etc.

Like on sourceforge, you should give every project a few KB for a home page, where they could tell the rest a little about the project. You don't need alot of space to do that, I think most pages will take between 10 and 50 KB (no graphics/flash demos allowed ).

This project section should be for large projects (not compared to Linux kernel and such big projects, hehe), with at least 2 more or less active developers. For small code snippets, we don't have to change alot. The code snippet/tutorial sections are OK.

What we need is somewhere to post medium-sized projects, like small games, tools, libraries etc. For those small programs, it would be great if you could get a little more information (platform, language(s) etc.) than the short description when you post it as a code snippet.

If you want to know somebodys programming skills, you have to ask him on IRC or via mail. I suggest we let people fill in some information about their programming skills when they join (old members could edit their profile). You could let people fill in how good they are at some programming languages/operating systems, maybe on a scale 1 - 5.

I suggest we ask about at least the skills in following languages: Assembler, BASIC, C, C++, Delphi, Fortran, Pascal, VB, Java, PHP, HTML, JavaScript, COBOL (hehe).

Maybe it would be interesting to know the age of all members, so you could let people fill in their birth year.

You maybe want to have one tutorial/code snippet section where you can post links to other peoples tutorials.

Also make a good link library, divided in categories, where members can submit good links.

Now I don't have many more ideas =)

I suggest a member rating thing based on how other people rate you, not just the code and tutorials you submit. I also think md5() would be good

Well... First off, the projects:
You don't really give us a unified picture of how you want the projects to be handled. I take it, you want it this way:
All projects have their own space on YPN.
1.Small projects, hosted on 34sp
2.Medium projects, hosted somewhere our's
3.Large projects, hosted on admins' servers/hosts.

Yeah, pretty nice idea.
Authorisation from admins: this might be an option. As you are a very good project leader (good at giving orders ), for me, your words do weight a lot in this q.

I think the programming skills & age stuff might be included too.

About the tutorial links: we do prefer people to post their own tutorials. If you know a very good tutorial, mail the author and ask if he won't post it here. Of course, when it's about people not as young, there might be a section of tutorial links... But as there was going to be a link section anyhow, this might be innecessary .

thanks for the suggestions.

jgrant: yeah, md5() is for sure. The memer rating isn't really, we'll think about that.

Hmm, the Private message thing from this board should be incorporated through the whole site. Where it shows messages you have, that way you would not have to write your own message thing.

The thing is, I don't think we'll need a lot of space for the projects. The biggest projects in the history of YPN (or written by YPN members), are projects like BozOS, Twintops perl game and YPN itself. Those are pretty small (or at least not more than medium size) projects.

So, how much server space do we need for projects of this size (and maybe a bit larger projects)? The sources wouldn't take more than maybe 100kb compressed for a pretty large project. If someone have a lot of binary data (like pictures and sound in a game), that may take some more space.

If someone makes a project, and it's growing so big we can't host it on the 34sp space, we can always register an account on a free web host (we maybe need to find a really good one everybody can use). Everything stored in the 34sp space is just links to the free host.

Thanks for listening to me

Some more suggestions (not about projects):

* Show the last date every member did something (post on the board, submitted, logged in).
* Show the number of members & the latest member on the front page
* Count visitors, and make the statistics public.

I also hope you make a very good link section It could become a great library to search in after a couple of months.

Your current download section isn't very good. Either delete it and let it be replaced by the links section, or improve it (so users can post links to downloads).

Thanks for listening

On suggestions:
1: Yep, sure.
2: I have intended to this already
3: We have a statistics service from 34sp but it does not count unique hits. It'd be a good idea to make the stats public, yeah... We might even do an own, advanced counter (I'm much at it reinventing the wheel nowadays)

About the links section/downloads: I do hope it will be a great, searchable database of programmer resources. I think it will be split into sections as well, one containing downloads.

So we're basicly thinking similar things .

Good I hope this will be finished soon =)

I'd just like to say that I totally agree with all of the ideas robert mentioned in his first post.

jgrant: I'll look over that function too