[Ludovic Hirlimann]

For all of those who think that Camino is not being developed anymore, may I suggest to read this post by one of the main developers of Camino.

[Jim Paradise]

If I had *any* developing skills (beyond Hypercard! ) I would gladly help. Camino remains my default browser and I cannot see that changing. There's been great work done over the past year (except changing the Sidebar!) and I really hope that Camino continues and succeeds.

[Ludovic Hirlimann]

Originally posted by Jim Paradise:
If I had *any* developing skills (beyond Hypercard! ) I would gladly help. Camino remains my default browser and I cannot see that changing. There's been great work done over the past year (except changing the Sidebar!) and I really hope that Camino continues and succeeds.

You can simply help by triagging bugs. trust me this is time consuming. Let me give you a simple little example : Reading all open bugs concerning camino that where /are assigned to bryner@netscape.com took me more than 8 hours for approximatly 90 bugs. Most of these bugs where pre 0.7 and needed to be checked against nightly build, to let know the developers is the bug was still there or had diseapeared with the move to the trunk. Do do this kind of work, which is greatly appreciated by the developers (because He can spend some time using his coding skills to fixe the bugs), you need time and net access.
Many bugs are too simply described, this pages renders badly, and an URL is given - this does not help developers. But if you take the time to look at the page's source and modify it until it shrink to less then 10 lines with the problem being reproduced then you are helping the developer find a solution to the bug faster. Please read this document http://www.mozilla.org/quality/.

[smeger]

I've been toying with the idea of contributing code to Camino for a long time. Basically what's been stopping me (aside from never having enough time in the day) is the enormity of the whole thing - it doesn't seem like the sort of project one could just casually jump into, and I've never been willing to spend a week familiarizing myself with the entire codebase.

Something that would help me a lot would be a regularly updated to-do list of programming tasks that need to be done. Ideally, each list entry would contain a textual (or image) description of what should be achieved, and a hint of which files or directories would need to be edited to achieve this.

For example:

Task:Make the url textfield autocomplete text like Safari.
Detail:When typing an address into Safari's URL bar, if the beginning of the typed adddress has been typed before or is present in the bookmarks, the closest match will appear to the right of the insertion point and will be hightlighted. Pressing "return" will select this URL. Additional typing will overwrite it.
Files Affected:CMURLBar.m, CMFelcher.m, CMSmegma.m

If there were something like this available, I'd be much more likely to casually jump in and lend a hand periodically instead of just checking Bonzai to see what's up and never doing anything.

[Ludovic Hirlimann]

Originally posted by smeger:
I've been toying with the idea of contributing code to Camino for a long time. Basically what's been stopping me (aside from never having enough time in the day) is the enormity of the whole thing - it doesn't seem like the sort of project one could just casually jump into, and I've never been willing to spend a week familiarizing myself with the entire codebase.

Something that would help me a lot would be a regularly updated to-do list of programming tasks that need to be done. Ideally, each list entry would contain a textual (or image) description of what should be achieved, and a hint of which files or directories would need to be edited to achieve this.

For example:


If there were something like this available, I'd be much more likely to casually jump in and lend a hand periodically instead of just checking Bonzai to see what's up and never doing anything.

Good idea, something like doxygen ?
or like Abisource Project of the week ?

/me thinks you should post this and other ideas on the Camino mailing list, which you can browse archive, and subscribe here

[Wevah]

smeger says what I was thinking...

[Ludovic Hirlimann]

Originally posted by Wevah:
smeger says what I was thinking...

Please come and join the mailing-list.

[Wevah]

Done. I don't know how active I'll be at the moment, though.

[mrmister]

That was a great post from Pinkerton, and I am going to try and triage some bugs this upcoming weekend.

[Ludovic Hirlimann]

Originally posted by mrmister:
That was a great post from Pinkerton, and I am going to try and triage some bugs this upcoming weekend.

Bigest list is simon Fraser's - but some people are working on it. Look into the archive to see which bug list still needs to be triagge or ask Pink on IRC. Some work on some unconfirmed bugs is needed too, like making testcase etc ....

[smeger]

Originally posted by Ludovic Hirlimann:
Bigest list is simon Fraser's - but some people are working on it. Look into the archive to see which bug list still needs to be triagge or ask Pink on IRC. Some work on some unconfirmed bugs is needed too, like making testcase etc ....

Links & chatroom name?

[Ludovic Hirlimann]

Originally posted by smeger:
Links & chatroom name?

irc://irc.mozilla.org channel is of course #mozilla ....

[Japser]

Originally posted by smeger:
I've been toying with the idea of contributing code to Camino for a long time. Basically what's been stopping me (aside from never having enough time in the day) is the enormity of the whole thing - it doesn't seem like the sort of project one could just casually jump into, and I've never been willing to spend a week familiarizing myself with the entire codebase.

Something that would help me a lot would be a regularly updated to-do list of programming tasks that need to be done. Ideally, each list entry would contain a textual (or image) description of what should be achieved, and a hint of which files or directories would need to be edited to achieve this.

For example:


If there were something like this available, I'd be much more likely to casually jump in and lend a hand periodically instead of just checking Bonzai to see what's up and never doing anything.

For this purpose the mozilla project has bugzilla which keeps track of bugs and enhancement request. Each big bug gets a target for wich milestone the bug should be fixed. So if you do a search on a specific milestone for Camino you get a list of bugs that the developers want fixed before a certain milestone. This way they have a to do list

On my personal Camino Graphics Project page I have a special Project links section that contains most used and handy links to get familiar with Bugzilla (which is a bit of a maze when you start using it) and other things you need to know. If you have any question about using it you can always aks me . Any help with the project is always appreciated.

[Japser]

The Camino 0.8 to do list:

http://bugzilla.mozilla.org/buglist....mp;value0-0-0=