On Sun, Jan 20, 2008 at 10:13:44PM +0100, Georg Brandl wrote:
Since this bug day was a relative success, I suggest to introduce a
more-or-less regular schedule.
Feb 23 would make a nice second bug day in 2008, wouldn't it?
That works for me. I've updated the wiki page to give Feb. 23 as the
Excellent ! When will be the next one ? :-)
On Jan 20, 2008 2:14 AM, A.M. Kuchling [EMAIL PROTECTED] wrote:
Today's bug day was a great success. Experienced people like Georg,
Facundo, and Gregory P. Smith participated, and we also had people who
submitted their first patches, some of which
Quentin Gallet-Gilles wrote:
Excellent ! When will be the next one ? :-)
Everyday can be a bug day. :)
Nobody is going to stop you from squalling through the bug tracker.
Christian
___
Python-Dev mailing list
Python-Dev@python.org
Malte Helmert wrote:
One question there: Will the easy keyword in roundup be maintained
further, i.e. will new easy bugs be marked in the future? That would be
very useful for neophyte contributors.
Yes, we will keep marking easy bugs with the easy keyword.
Christian
A.M. Kuchling schrieb:
Today's bug day was a great success. Experienced people like Georg,
Facundo, and Gregory P. Smith participated, and we also had people who
submitted their first patches, some of which got applied today, too.
Hopefully we'll see those people again.
As of this
A.M. Kuchling schrieb:
Today's bug day was a great success. Experienced people like Georg,
Facundo, and Gregory P. Smith participated, and we also had people who
submitted their first patches, some of which got applied today, too.
Hopefully we'll see those people again.
As of this
On Sun, Jan 20, 2008 at 11:23:38AM +0100, Quentin Gallet-Gilles wrote:
Excellent ! When will be the next one ? :-)
We could certainly try to hold one in February. Maybe on the 16th?
For March the best date is probably the Monday of the sprints at
PyCon, because there will be a Python core
Today's bug day was a great success. Experienced people like Georg,
Facundo, and Gregory P. Smith participated, and we also had people who
submitted their first patches, some of which got applied today, too.
Hopefully we'll see those people again.
As of this writing, 37 issues were closed
On Jan 19, 2008 5:14 PM, A.M. Kuchling [EMAIL PROTECTED] wrote:
Today's bug day was a great success. Experienced people like Georg,
Facundo, and Gregory P. Smith participated, and we also had people who
submitted their first patches, some of which got applied today, too.
Hopefully we'll see
On Jan 11, 2008 12:13 PM, A.M. Kuchling [EMAIL PROTECTED] wrote:
No one pushed back on the 19th as a bug day, so I'm going to go ahead
and send out announcements this evening.
We should mark issues in the tracker that are good candidates for new
developers. How do we want to do this? We
On Fri, Jan 11, 2008 at 09:45:14PM +0100, Christian Heimes wrote:
Please add two keywords, one for bug day and one for easy tasks. May
beginner task, easy or novice level makes a good keyword.
I think marking easy tasks is all we need. That would certainly be
useful during ongoing non-bugday
No one pushed back on the 19th as a bug day, so I'm going to go ahead
and send out announcements this evening.
We should mark issues in the tracker that are good candidates for new
developers. How do we want to do this? We could add a new keyword
('beginner', 'bugday', ???) or add a prefix to
Guido van Rossum wrote:
Yes, it does. Unfortunately, I've been using bug day in some
comments and that doesn't seem to work well in the search.
I think a keyword is easier, I can add it if you want me to.
Please add two keywords, one for bug day and one for easy tasks. May
beginner task,
Guido van Rossum wrote:
(I have no idea if anyone can add keywords or if I have magical
powers. On the left side bar there's a section Administration which
contains a link Edit Keywords.)
I'm unable to add new keywords although I've the developer role. I guess
one needs to be a coordinator to
I've added an easy keyword, with description This is an easy task
(e.g. suitable for GHOP or bug day beginners).
Let me know if more is needed, Andrew.
(I have no idea if anyone can add keywords or if I have magical
powers. On the left side bar there's a section Administration which
contains a
On Fri, Jan 11, 2008 at 03:58:35PM -0800, Guido van Rossum wrote:
Let me know if more is needed, Andrew.
Thanks!
I've run searches for a few different components and marked a few bugs
with the 'easy' keyword; I see that Tiran is doing this, too.
(I have no idea if anyone can add keywords or
A while ago Georg suggested holding a bug day some time soon. I
suggest Saturday January 19th. It's a weekend day; it gives us two
weeks to prepare by drawing up bug lists; there's a PyPy sprint
January 12-19 (http://codespeak.net/pypy/dist/pypy/doc/news.html), so
it may be helpful to have the
I've updated the bug day pages in the wiki:
http://wiki.python.org/moin/PythonBugDay
http://wiki.python.org/moin/PythonBugDayStatus
How do we want to flag good candidate bugs? Should we add a keyword
to Roundup, or just list them on the PythonBugDayStatus wiki page?
Another
2008/1/4, A.M. Kuchling [EMAIL PROTECTED]:
I've updated the bug day pages in the wiki:
This one should be also updated:
http://wiki.python.org/moin/MissingFromDocumentation
All the issues pointed by it are already closed (or don't exist (!)).
A.M. Kuchling wrote:
Another task is to get logging set up for the #python-dev IRC channel.
Searching didn't find any existing archive; we could run it on
python.org somewhere, but does anyone here already run an IRC logging
bot? Maybe someone could just add #python-dev to their existing
On Fri, 04 Jan 2008 16:53:46 +0100, Christian Heimes [EMAIL PROTECTED] wrote:
A.M. Kuchling wrote:
Another task is to get logging set up for the #python-dev IRC channel.
Searching didn't find any existing archive; we could run it on
python.org somewhere, but does anyone here already run an IRC
On Fri, Jan 04, 2008 at 04:53:46PM +0100, Christian Heimes wrote:
It'd be nice if we can also get a bot into #python-dev to broadcast svn
commits and bug tracker changes. The Twisted guys have good bot with
decent msg coloring but IIRC it's tight into TRAC. For svn we could
probably use CIA
Christian Heimes wrote:
It'd be nice if we can also get a bot into #python-dev to broadcast svn
commits and bug tracker changes. The Twisted guys have good bot with
decent msg coloring but IIRC it's tight into TRAC. For svn we could
probably use CIA bot and tie it into a svn post commit hook.
A.M. Kuchling schrieb:
On Fri, Dec 07, 2007 at 10:04:38PM +0100, Georg Brandl wrote:
there wasn't much response to the bug day proposal, but I still think it's
a good idea. I'd propose a date in January, when Christmas etc. is over.
It would also be nice if someone did the organizing who
On Fri, Dec 07, 2007 at 10:04:38PM +0100, Georg Brandl wrote:
there wasn't much response to the bug day proposal, but I still think it's
a good idea. I'd propose a date in January, when Christmas etc. is over.
It would also be nice if someone did the organizing who hasn't got a
daily batch of
Giampaolo Rodola' schrieb:
O.T. - I noticed that the PEP-3 still refers to the old sourceforge
bug tracker. Shouldn't it be rewritten?
Yes, thanks! I did a minimal change, but still someone could elaborate
it, describing current practices.
Georg
--
Thus spake the Lord: Thou shalt indent with
Hi,
there wasn't much response to the bug day proposal, but I still think it's
a good idea. I'd propose a date in January, when Christmas etc. is over.
It would also be nice if someone did the organizing who hasn't got a
daily batch of GHOP tasks to review and commit :)
Georg
--
Thus spake the
O.T. - I noticed that the PEP-3 still refers to the old sourceforge
bug tracker. Shouldn't it be rewritten?
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
Is another bug day planned in the next week or two?
John
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Georg Brandl wrote:
it's time for the 7th Python Bug Day. The aim of the bug day is to close
as many bugs, patches and feature requests as possible, this time with a
special focus on new features that can still go into the upcoming 2.5 alpha
release.
so, how did it go? a status report /
[/F]
so, how did it go? a status report / summary would be nice, I think ?
http://wiki.python.org/moin/PythonBugDayStatus
has been kept up to date. Note that, e.g., there are still open items
in the Bugs/patches to assess for commit section, if you want to do
more than just read.
Tim Peters wrote:
[/F]
so, how did it go? a status report / summary would be nice, I think ?
19 bugs, 9 patches (which were mostly created to fix one of the bugs).
Not much, but better than nothing and there has been quite a participation
from newbies.
Georg Brandl wrote:
Tim Peters wrote:
[/F]
so, how did it go? a status report / summary would be nice, I
think ?
19 bugs, 9 patches (which were mostly created to fix one of the bugs).
Not much, but better than nothing and there has been quite a
participation
from newbies.
I've just
Hello,
it's time for the 7th Python Bug Day. The aim of the bug day is to close
as many bugs, patches and feature requests as possible, this time with a
special focus on new features that can still go into the upcoming 2.5 alpha
release.
When?
^
The bug day will take place on Friday, March
On 3/15/06, Georg Brandl [EMAIL PROTECTED] wrote:
Neil Schemenauer wrote:
I think it would be a good idea to follow the Plone project and try
to encourage new developers by offering assistance to get them up
and running. AFAIK, we've done that for the other bug days but it
might help to
Neil Schemenauer wrote:
I think it would be a good idea to follow the Plone project and try
to encourage new developers by offering assistance to get them up
and running. AFAIK, we've done that for the other bug days but it
might help to publish the fact that no prior Python development
Hi,
I know, PyCon's just been, but not many bugs were closed and
there really ought to be some issues resolved before 2.4.3 happens.
The number of open bugs is again crawling to 900.
I myself are looking at many bugs and patches over time, but with
most of them I can't decide alone what to do.
On 3/8/06, Georg Brandl [EMAIL PROTECTED] wrote:
Hi,
I know, PyCon's just been, but not many bugs were closed and
there really ought to be some issues resolved before 2.4.3 happens.
The number of open bugs is again crawling to 900.
I myself are looking at many bugs and patches over time,
On 3/8/06, Georg Brandl [EMAIL PROTECTED] wrote:
I know, PyCon's just been, but not many bugs were closed and
there really ought to be some issues resolved before 2.4.3 happens.
The number of open bugs is again crawling to 900.
I myself are looking at many bugs and patches over time, but with
On 3/8/06, Jeremy Hylton [EMAIL PROTECTED] wrote:
On 3/8/06, Georg Brandl [EMAIL PROTECTED] wrote:
I know, PyCon's just been, but not many bugs were closed and
there really ought to be some issues resolved before 2.4.3 happens.
The number of open bugs is again crawling to 900.
I myself
[Georg Brandl]
I know, PyCon's just been, but not many bugs were closed
Ya, it was very much a development sprint this year -- new features.
and there really ought to be some issues resolved before 2.4.3 happens.
The number of open bugs is again crawling to 900.
I myself are looking at many
I think it would be a good idea to follow the Plone project and try
to encourage new developers by offering assistance to get them up
and running. AFAIK, we've done that for the other bug days but it
might help to publish the fact that no prior Python development
experience is necessary.
Neil
Is anyone interested in joining a Python bug day this Sunday?
A useful task might be to prepare for the python-core sprint at PyCon
by going through the bug and patch managers, and listing bugs/patches
that would be good candidates for working on at PyCon.
We'd meet in the usual location:
Greetings,
It seems like a good idea to have another Python bug day. Saturday
June 25th seems the most practical date (this coming weekend is too
soon, and the weekend after is a minor holiday -- Father's Day).
We'd convene in the usual place: the #pydotorg IRC channel, on
On Fri, Jun 10, 2005 at 11:35:47AM -0300, Gustavo Niemeyer wrote:
Not sure if that's a reason to prevent the event, since
fixing bugs is a good thing no matter when, but that's two
days before EuroPython, and many people might be moving to
the conference at that time.
Thanks for pointing that
It seems like a good idea to have another Python bug day. Saturday
June 25th seems the most practical date (this coming weekend is too
soon, and the weekend after is a minor holiday -- Father's Day).
We'd convene in the usual place: the #pydotorg IRC channel, on
irc.freenode.net.
Assuming no
46 matches
Mail list logo
