Hi All,
Just a quick note to say that PHP was accepted as an organisation for
GSoC 2009. We have until the 23rd of March to try and liaise with any
potential students we have available and work on our ideas list that we
might suggest.
Our ideas list at http://wiki.php.net/gsoc/2009 has a few
See: http://cvs.php.net/viewvc.cgi/pear/Bugtracker/
That's the pear bug tracker modified for all pear/pecl/php bugs I worked
on about 1.5years ago. :) It has that roadmap thing..
--Jani
Ilia Alshanetsky wrote:
Sean,
You make some very good points and I'll be the first to agree there is
Jani Taskinen wrote:
See: http://cvs.php.net/viewvc.cgi/pear/Bugtracker/
That's the pear bug tracker modified for all pear/pecl/php bugs I worked
on about 1.5years ago. :) It has that roadmap thing..
The one Barry worked on for GSoC 2008 is at
http://cvs.php.net/viewvc.cgi/bugtracker
I've
Decided to start from scratch
Even tho I didnt finish it, the code I wrote has built into something
bigger which is also open source
I just didnt have time to come back to work on the bug tracker during Uni,
has and still is very busy
On Mon, 26 Jan 2009 10:52:22 +, Scott MacVicar
On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most importantly
makes it easy to report and update bugs which is conducive to more
issues being reported. Often extra features of bug trackers make
them overly complex to use and people
hi everyone,
On Sat, Jan 24, 2009 at 11:40:08AM -0500, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most importantly
makes it easy to report and update bugs which is conducive to more
issues being reported. Often extra features of bug trackers make them
In that case why wasn't this pointed out last year, and I could of done
something more useful with my GSoC time last year..
On Sun, 25 Jan 2009 15:05:37 +0100, sean finney sean...@debian.org wrote:
hi everyone,
On Sat, Jan 24, 2009 at 11:40:08AM -0500, Ilia Alshanetsky wrote:
I think our
Stop top-posting.
On Sun, Jan 25, 2009 at 15:17, ba...@barrycarlyon.co.uk wrote:
In that case why wasn't this pointed out last year, and I could of done
something more useful with my GSoC time last year..
I did:
Hi,
I think that there needs to be more feedback from the community on how
projects are going and the way they should go. This might help to curb some
of the problems being discussed where there was a gap between the project
and what the community wants. Feedback would also help the student know
On 25.01.2009, at 16:17, Graham Kelly wrote:
Lastly, I really think all the PHP GSoC projects should be hosted in
PHP's
CVS under a central location (maybe something like
/repository/gsoc/2009/projectname/). It was very hard at times to
find the
work done for other projects.
Actually
On Sun, Jan 25, 2009 at 02:17:31PM +, ba...@barrycarlyon.co.uk wrote:
In that case why wasn't this pointed out last year, and I could of done
something more useful with my GSoC time last year..
http://markmail.org/message/daf4zi5dfktv7jjt
sean
signature.asc
Description:
Am 25.01.2009 um 14:29 schrieb Lukas Kahwe Smith:
On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most importantly
makes it easy to report and update bugs which is conducive to more
issues being reported. Often extra features of bug
On 25 Jan 2009, at 16:12, David Zülke wrote:
Am 25.01.2009 um 14:29 schrieb Lukas Kahwe Smith:
On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most
importantly makes it easy to report and update bugs which is
conducive to more issues
On 25 Jan 2009, at 15:22, Lukas Kahwe Smith wrote:
On 25.01.2009, at 16:17, Graham Kelly wrote:
Lastly, I really think all the PHP GSoC projects should be hosted
in PHP's
CVS under a central location (maybe something like
/repository/gsoc/2009/projectname/). It was very hard at times to
On Sun, Jan 25, 2009 at 5:22 PM, Scott MacVicar sc...@macvicar.net wrote:
On 25 Jan 2009, at 15:22, Lukas Kahwe Smith wrote:
On 25.01.2009, at 16:17, Graham Kelly wrote:
Lastly, I really think all the PHP GSoC projects should be hosted in
PHP's
CVS under a central location (maybe something
Sean,
You make some very good points and I'll be the first to agree there is
definitely a room to improve the existing bug-tracker, in particular
its integration with the repository commits, but I do not think it
needs a fundamental rewrite. From what I can see most (I think its
all, but
Of course being mentor for the past 2 years I want to be a mentor
again this year. But there are a few things we need to fix. I sent an
email to the other mentors about 3 months ago about things that went
not-so-well last year.
Here are a few things that were suggested and came out of this
Scott MacVicar wrote:
Hi Everybody,
It's almost that time again where we rush at the last minute to organise
something for the Google Summer of Code, so in the interest of being
prepared I'm thinking it's time to start collecting ideas for potential
students. I've updated a few of the Wiki
Add the bugtracker, and I can get round to finishing, unis been far too
busy this year so far :-(
On Fri, 23 Jan 2009 13:37:18 -0800, Andrei Zmievski and...@gravitonic.com
wrote:
Scott MacVicar wrote:
Hi Everybody,
It's almost that time again where we rush at the last minute to organise
On Fri, Jan 23, 2009 at 23:09, ba...@barrycarlyon.co.uk wrote:
Add the bugtracker, and I can get round to finishing, unis been far too
busy this year so far :-(
Finishing what exactly?
I'd like to add the bugtracker idea again.. but the last year
bugtracker gsoc turned into something
Hannes Magnusson schrieb:
I'd like to add the bugtracker idea again.. but the last year
bugtracker gsoc turned into something completely different and not at
all usable for php.net.
What is bugging me is the question whether we really need our own
bugtracker software.
--
Sebastian Bergmann
Hi Everybody,
It's almost that time again where we rush at the last minute to
organise something for the Google Summer of Code, so in the interest
of being prepared I'm thinking it's time to start collecting ideas for
potential students. I've updated a few of the Wiki pages with some
22 matches
Mail list logo
