If you believe in Zenphoto and know what it could be capable of, and you want to help make it the greatest photo gallery software available on the [i]entire internet[/i]; if you knew how to program before you learned how to write PHP; if you know at least three languages other than PHP; if you think int carry = x > 9 is elegant; if you enjoy making beautiful user interfaces as much as making beautiful code underneath them; if you believe in simplicity and conciseness; if you know you're an organized, friendly, top-notch software engineer, then [i][b]we want YOU to help develop Zenphoto.[/b][/i]
This is a call for a single developer to add to the current team of.. er... me. I want this project to grow and thrive, but it can't do that with just me doing everything, so I need code help from someone who's motivated to make Zenphoto be a better gallery--the best gallery on the web. I need a creative, thinking, breathing [i]human[/i] programmer, but be warned, if you're going to so much as [i]touch[/i] the zenphoto code, you have to prove yourself. [i]Learn PHP in 24 Hours[/i] will not suffice. Send me an e-mail at trisweb at this domain if you think you're up to the task.
I'll be waiting.
(Okay, now to lighten up a bit, I seriously am looking for a software master to help out, but please email me even if you're not up to that level. If you think you help with future zenphoto development... and learn the way of the zenphoto... then I could use your help.)
(But also seriously, I'm looking for one great developer. If you're it, this is a great opportunity to contribute to what could be the best open source gallery around. Don't pass it up.)
Sorry, one of my tutoring students was working on a C digit-adder, and had this statement:
`
int carry;
if (x > 9) {
carry = 1;
} else {
carry = 0;
}`
And it struck me that the same thing could be reduced to int carry = x > 9, and that's elegant coding to me: reducing 5 lines to 1 that makes perfect sense.
I'm interested in submitting some patches for Zenphoto, because I like the software.
However, maybe it is an idea to create a developers mailinglist (or is it already there?). Mailinglists are easier to follow discussions than forums, because on forums you'll easily miss topics (in my experience).
Also, it may be an idea to mention the location of the svn on the website. I found it using Google and that's not the most userfriendly way (and is a barrier for getting people start hacking on Zenphoto).
The location of the SVN is posted on the sticky here on the forum
http://www.zenphoto.org/support/topic.php?id=1180
If you did actually look at the Wiki, perhaps you'd have realized that there is in fact a "Browse Source" at the top that is a full-featured SVN browser [Edit: I just realized there's no link to the actual SVN up there-- adding now to the DeveloperReference and FAQ]
Still, you [definitely] have a point-- it should be more accessible. I'll put a link to the developer wiki page on the front page.
Quote:If you did actually look at the Wiki, perhaps you'd have realized that there is in fact a "Browse Source" at the top that is a full-featured SVN browser
I did look at it, and noticed that is is possible to browse the source. However, it is a little difficult to create svn patches using that feature :-).
But I noticed that you've added the location of the SVN in several pages on the wiki! Keep up the good work.
I'll try to implement the admin interface for the options and will submit a patch in trac (on bug #10) soon.
@Msturm, thanks! That would be great. Please try to make it as generic as possible, perhaps implementing the get/set methods in the Gallery class...
@keyoshix - You're welcome to help all you want! The best way to start is to submit patches to bugs or enhancements in the bugtracker. For translation, I wouldn't be accepting any specific languages-- what I really need is a general translation framework that can be used for any language.
"if you think int carry = x > 9 is elegant;"
Elegant, yes. Clear enough to be mainted by more than one programmer over the long term, probably not... It's only worth the programmer's brain power if it's called in every pass through a major loop. Remember - first just make it work at all. Optimizing comes later. :-)
My wife adds: "The chances of it rapidly and efficiently doing the wrong operation are way too high."
As for audience participation, more modular code would help with scaling up to multiple programmers. Less likely to have check-in and patching issues with version control that way.
Nods. I have been humbled.
I know I have much to learn still, especially in the area of working with a team of programmers.
I do recognize that that bit of code is illegible, even if it is "cool" that it's a single line. :-) Like I said, I was just with a tutoring student right before I wrote that and it was stuck in my head as "novel."
Zenphoto, on the other hand, I do try my best to make elegant in a different manner -- easy-to-read well-commented code with good modularity, as you have hinted. Each part is divided into a class with a defined purpose and interface. It works quite well from my perspective, and should make sense to others as well, I hope. I'm trying not to do it in the usual PHP idiom...
So, I'm learning. shrug.
My experience so far is that, from a developer view, the code is great -- well organised, nicely commented, highly readable. The code itself has been well thought-out so that there is lots of reuse. Don't change what you are doing