Lets get the Image gallery started!
 

1) I know that there's another project thread, but it sucks. This is my attempt to get things going, as it seems they're frozen. I don't care if I have to work alone, this project will get done.

The first step in any project is the outline, at least in my opinion. Here is the rough draft of the outline, I want everyone involved to add to it as they see fit, and once the outline is done we will start coding.


Image Gallery (Phlox?)
- Display images using the GD framework
-- brand images with a small transparent logo (prevent theft)
-- allow author comments, viewer comments, ratings
-- option to add borders or other presentational effects

-allow multiple organization schemes
--Top Level -> Category -> images
--TL -> images
--TL -> author -> images

-Display images in a way that allows simple sorting from the main page
-- Sort by author / category / ect (via ajax)

-Permanant links to the images
-User Generated image option

-Create images via ajax and GD.
-- Style text, manipulate images, ect. (rendair?)

-Design accessibly and Search Engine Friendly-ly
--I hate having to say this. Usability is accessibility. Accessibility isn't just for people with disabilities, it's for people generally using the internet. Do we really want to give another company the opportunity to make money by adding a SEO feature to our product? It should come included.

Thats all I can think of. If there aren't any contributions to this thread I will just stop helping. As more comments are made I will attempt to edit this post accordingly. Moderators could help with that though =)


As for the actual project, I want all communication to be done via the forum and pastebin. This way, people can join in whenever they want, and we can keep a running track record of the project.

I would love to hear that a particular idea is extremely dumb. Less unused features means less wasted time.


Needed:
At this point there are a few specialists we need.
-- An Ajax expert
-- A GD pro
-- someone willing to devote mind numbingly long hours to the project
-- Someone who can tell me how to edit files remotely on my Linux box from vi (remote mounting?)

Guidelines
I want this to be a learning experience for everyone. This is a learning community so my only guideline is to comment your code and explain the WHY as well as the HOW. Well commented code does more good than having style guidelines. Naming conventions, on the other hand, can only simplify everything. If someone could write up some good naming conventions that would be great.

As for the Javascript, there should be a poll on either using traditional javascript or jquery/prototype/moo. I would prefer not using prototype, as it is more of a ruby framework, and not moo, because it really isn't as powerful nor elegant as jquery (in my opinion). So it really comes down to Jquery (barely any learning curve) or just plain javascript (no learning curve)

We need to build our project around certain values. PHP is a large language that can create a large variety of programs. From fast and feeble, to slow juggernauts.
I suggest secure and powerful.
This doesn't mean that it can't be fast, or simple. I want it to be as fast as possible and as simple as possible, but I believe a learning project would benefit most from security and power.

Before making a suggestion
View our project in the eyes of someone looking for a gallery. What do you want? What don't you want?

Developer Management
We deserve to just close this site if we split up the developers and the designers. Without a good harmony between the two there will be problems. If you're on Talkphp, you should be able to develop php code. If you're worth your stuff, you should be able to create an interface (not necessarily design.. those are two opposite sides of the brain).

I don't know what to do in this area... I think we should just roll with things and see what comes up.

Another thing then. If you think we should vote of which javascript framework, then we should vote about if we should use a php framework, and which one if yes?

And yes, I think too that we should get this thing started sometime.

I agree with the JS framework, however I don't think this project would benefit that much from a PHP framework.

jQuery is my JS vote.

If you want something to happen, start it without asking. Polling is what has gotten us nowhere to far. If you don't I will. I have about a week of free time, do you want to get this started or shall I? I could get the ball rolling on this now, but I would only be there for a week.

We should use whatever JS frameworks we need, if we need jQuery, good, but if we need moo.fx later on, go for it. No PHP frameworks, lets use our own code.

Agree, are we having SVN? if so where?

Google Code is fine, does that allow public commits? We've already got a project set up there anyway. Personally, I'd prefer to use git but do we need to introduce a learning step for those who don't use git (the same can be said for SVN). In the end, write some code and put it somewhere, we can worry about combining, consolidating, versioning and whatnot later.

Not sure if it does allow public commits, I'll do some research, I know you can checkout publicly.

EDIT: On looking into it, it seems you need be me a member of the project to commit.

I dont mind doing the GD as i seem to use it alot anyway :P

GD is a great way to manipulate images, but why display them though it?

I meant manipulate images with it. Not thinking clearly at the time. This really isn't a pole.

As for the first php file... where do we start?

PM me for FTP details. For now, since I don't want to deal with SVN / CVS or any of that other stuff, the project will be hosted on tphp.eglast.com, and we can develop our own version change system if need be. Right now I want to get this started. You can also PM village idiot for FTP details, since I think he is the most eager to start this.

Just comment your code, and leave a changelog and todo file in there, so people can know what they can do to help and all that other stuff.

I wouldn't advise just using FTP. A VCS would make it a-lot easier.

Anyway We can always import to SVN at a later date.

I don't exactly know what a VCS is, so I doubt most developers would, either. I want this to be as simple as possible. If you want to help me with setting up SVN or this VCS get on MSN right now (aaron@aetherdesigns.com) or PM me an IRC room.

VCS (version control system) i.e. SVN/CVS/GIT etc.

I don't mind sorting one out, but ,most of the free ones out there require people to sign up and permissions given in order to commit files/changes.

I can add people to the google code account if you want?

A good resource for SVN is: http://svnbook.red-bean.com/

Anyway, if you want to start things off with FTP, then go ahead, then I (or someone else) can import the code to the google code SVN repo.

I don't want to work with google on this. That's more than I need to mess with.

I say just use a changelog file and just hope for the best. We don't have 50 developers working on a gigantic project. We have like 5.

Working with SVN is a lot better, easier and quicker in the long run than FTP as it automates a lot of things (like changelogs) amongst other things.

I don't mind writing tutorials (I actually started one but never got chance to add to it.)

Like I said, if you want to make a start with the code using FTP, that's fine, I just think that later on we will need some form of version control.

Ok, Aaron just left me in charge of coding, so lets get started! I will make a new thread shortly with our official standards.