On Friday 30 April 2010 19:22:33 Idan Gazit wrote:
> FWIW, I spoke with Alex the other week about turning piano-man into
> a more finished product.
>
> So long as core guarantees that they'll at least take a look at
> whatever is made, I'm +1 on rolling our own, and am willing to
> champion this p
On Fri, Apr 30, 2010 at 3:57 PM, Gabriel Hurley wrote:
> I'd also be interested in working on this, as long as I'm not alone on
> it. Have you and/or Alex set up any kind of mailing list for it? Do
> you plan to use git's issue tracker or something else? What's the
> process plan for getting devel
I'd also be interested in working on this, as long as I'm not alone on
it. Have you and/or Alex set up any kind of mailing list for it? Do
you plan to use git's issue tracker or something else? What's the
process plan for getting development kick-started on it?
- Gabriel
On Apr 30, 11:22 am,
On Apr 30, 8:02 am, Jeremy Dunck wrote:
> I haven't heard one proposed. I'll take a look at RedMine and/or
> steal ideas from launchpad -- but writing a new tracker isn't the
> problem I'm trying to solve.
FWIW, I currently use (and administer) Redmine for my company. I'd say
it's only a margi
FWIW, I spoke with Alex the other week about turning piano-man into a
more finished product.
So long as core guarantees that they'll at least take a look at
whatever is made, I'm +1 on rolling our own, and am willing to
champion this project.
I think having something we can easily shape to meet o
On Fri, Apr 23, 2010 at 10:26 PM, Russell Keith-Magee
wrote:
...
>>> I'm not a huge fan of Trac - it's
>>> got lots of quirks and bugs that annoy the bejezus out of me,
>> ...
>> Perhaps upgrading would get us some distance?
>
> Possibly. Was that you volunteering to become our Trac jockey? :-)
>
On Fri, Apr 30, 2010 at 10:56 AM, Jeremy Dunck wrote:
> On Sun, Apr 25, 2010 at 1:27 AM, Stephen Wolff
> wrote:
>>> I recognize running tests w/ regressions pass would be useful, but
>>> it's getting into CI-land -- once we have some CI infrastructure in
>>> place, I'd be happy to use that.
>>>
On Sun, Apr 25, 2010 at 5:37 PM, yml wrote:
...
> While spending some more time looking at launchpad.net I stumbled upon
> another very neat feature you can also sort the bug by heat [1].
Thanks for this -- I'll be reading it shortly.
--
You received this message because you are subscribed to t
On Sun, Apr 25, 2010 at 1:27 AM, Stephen Wolff wrote:
>> I recognize running tests w/ regressions pass would be useful, but
>> it's getting into CI-land -- once we have some CI infrastructure in
>> place, I'd be happy to use that.
>>
>>
>
> In case you missed it, there already is some CI infrastru
The timing of this discussion is interesting, because I came to a
similar conclusion last week and decided to start writing a drop-in
replacement for Trac based on Django. Part of my desire was based on
the fact that Trac has such poor support for other VCS and such spotty
support for other databa
Just to make it clear I am not saying that Launchpad is "The Solution"
to all the problems. I have decided to dig in its documentation and
post the feature that I found interesting and I discover that
launchpad has grown a some very useful features with regards to the
issues we were discussing.
On
On 04/25/2010 05:15 PM, Russell Keith-Magee wrote:
However, the *huge* impediment that you have avoided mentioning is
that moving to Launchpad would require moving Django to using Bazaar
for version control. Moving to a DVCS has been proposed many times in
the past, and rejected. The reasons for
On Mon, Apr 26, 2010 at 4:48 AM, Gabriel Hurley wrote:
> I've been dancing around this idea for a while. I know it's not a new
> thought, and Alex Gaynor and Justin Lilly even started work on "piano
> man" [1]... I'd be curious to know what the state of that project is
> and if a few more devs wor
On Mon, Apr 26, 2010 at 2:34 AM, yml wrote:
> As you have noted I have avoided to the DVCS matter because I knew it
> is a slippery slope and because it don't really matter. Launchpad
> allows you to import branch from many of the popular VCS [1] cvs, svn,
> git, hg. The documentation mention tha
On Apr 25, 5:21 pm, Gabriel Hurley wrote:
> I'm in a similar boat to Russell... LaunchPad's UI always seemed like
> a complete disaster to me...
>
> However, in reading through LaunchPad's FAQ to give it a fair chance,
> I saw a couple of other features that Trac doesn't have to add to the
> lis
I'm in a similar boat to Russell... LaunchPad's UI always seemed like
a complete disaster to me...
However, in reading through LaunchPad's FAQ to give it a fair chance,
I saw a couple of other features that Trac doesn't have to add to the
list:
* Out-of-the-box OpenID support
* "Bug Expiry" to
On Sun, Apr 25, 2010 at 4:48 PM, Gabriel Hurley wrote:
> I've been dancing around this idea for a while. I know it's not a new
> thought, and Alex Gaynor and Justin Lilly even started work on "piano
> man" [1]... I'd be curious to know what the state of that project is
> and if a few more devs wor
I've been dancing around this idea for a while. I know it's not a new
thought, and Alex Gaynor and Justin Lilly even started work on "piano
man" [1]... I'd be curious to know what the state of that project is
and if a few more devs working on it might be able to bring it to a
place where it'd be re
As you have noted I have avoided to the DVCS matter because I knew it
is a slippery slope and because it don't really matter. Launchpad
allows you to import branch from many of the popular VCS [1] cvs, svn,
git, hg. The documentation mention that drupal is using this feature
to import on a regular
Hi Russell, Jacob,
What do you think, is it good idea to write django-based bug tracker
as a trac replacement?
As we all know, Django would be a perfect fit for such project!
Current Trac templates & layouts can be used for prototyping the project.
On Sun, Apr 25, 2010 at 6:15 PM, Russell Keith-
On zo, 2010-04-25 at 23:15 +0800, Russell Keith-Magee wrote:
> However, the *huge* impediment that you have avoided mentioning is
> that moving to Launchpad would require moving Django to using Bazaar
> for version control.
You don't *have* to use the bzr/code bits of launchpad to use the
bugtra
On Sun, Apr 25, 2010 at 10:54 PM, yml wrote:
> Hello,
>
> On Apr 23, 12:32 pm, Russell Keith-Magee
> wrote:
>> On Fri, Apr 23, 2010 at 3:04 PM, Jeremy Dunck wrote:
>> > Commiters and triagers,
>> > I've gone through the contributing doc and tried to identify places
>> > that tickets might get s
Hello,
On Apr 23, 12:32 pm, Russell Keith-Magee
wrote:
> On Fri, Apr 23, 2010 at 3:04 PM, Jeremy Dunck wrote:
> > Commiters and triagers,
> > I've gone through the contributing doc and tried to identify places
> > that tickets might get stuck (or other places that automation might
> > smooth th
5-10: The most useful of the lot for me personally. An automated
process that applies patches and runs tests would be nice; if it can
autocheck the appropriate flags ("patch needs improvement", "needs
tests" etc) that would be even better.
I recognize running tests w/ regressions pass wou
On Sat, Apr 24, 2010 at 2:34 AM, Jeremy Dunck wrote:
> On Fri, Apr 23, 2010 at 11:32 AM, Russell Keith-Magee
> wrote:
> Frequent contributors are not the only audience for this tool -- I'm
> trying to help answer the question -- where is help most needed right
> now?
>
> With that perspective, d
On Fri, Apr 23, 2010 at 11:32 AM, Russell Keith-Magee
wrote:
>> Can a DB dump be shared?
>
> I don't have any problem sharing the raw ticket data. However, I'm not
> sure if there's anything else in the database (like emails and
> passwords/hashes) that we would want to strip out before sharing.
>
On Fri, Apr 23, 2010 at 11:32 AM, Russell Keith-Magee
wrote:
...
> 2: Would be useful as a work list for people looking for. It would
> also be useful if tickets could be auto-disowned; i.e., if there's no
> activity from the owner after a month, post a comment asking for a
> status update; if no
On Fri, Apr 23, 2010 at 3:04 PM, Jeremy Dunck wrote:
> Commiters and triagers,
> I've gone through the contributing doc and tried to identify places
> that tickets might get stuck (or other places that automation might
> smooth the process).
> If you could take a few minutes to give feedback on
Hi Jeremy,
And what about information on the page if the patch commits cleanly,
and if all tests pass after applying patch?
Not just sending email to the patch author, but making it visible to everyone.
On Fri, Apr 23, 2010 at 10:04 AM, Jeremy Dunck wrote:
> Commiters and triagers,
> I've gone
Commiters and triagers,
I've gone through the contributing doc and tried to identify places
that tickets might get stuck (or other places that automation might
smooth the process).
If you could take a few minutes to give feedback on the list,
hopefully prioritizing in your named column with +/-
30 matches
Mail list logo
