Thanks for the advice. Trying to make a contribution is why I'm here.
That's why I worry about version control systems. Last time I tried
to contribute to an open source project via a "semi-official
mirror" (this one actually run by a core developer) it did not work
and I ended up having to resubm
On Wed, Apr 21, 2010 at 6:01 AM, Kevin Howerton
wrote:
> Cujo... for starters it's Amon Tobin's first moniker (he remixes jazz
> into some delightful tunes, if you don't know of him I strongly
> recommend you go to your local record store and pick up a copy of
> "Adventures in Foam").
>
> Also, I
On Wed, Apr 21, 2010 at 10:18 AM, SmileyChris wrote:
> ... And it seems like i'm reiterating the discussion about
> http://code.djangoproject.com/wiki/TicketChangeHelp
>
> I'm advocating for the friendly text in the ticket page itself, as I'm
> not sure that was specifically mentioned in the relat
This sounds like a great idea to me.
+1 for me. I've a been a bit reluctant to up my participation for a variety
of reasons, but kind of knowing how best to proceed is one of the large
ones.
Thanks,
Paul
On Tue, Apr 20, 2010 at 10:43 AM, Stephen Crosby wrote:
> What could be very helpful here
... And it seems like i'm reiterating the discussion about
http://code.djangoproject.com/wiki/TicketChangeHelp
I'm advocating for the friendly text in the ticket page itself, as I'm
not sure that was specifically mentioned in the related part of this
thread (but probably implied)
On Apr 21, 10:13
On Wed, Apr 21, 2010 at 10:00 AM, Jacob Kaplan-Moss wrote:
> On Tue, Apr 20, 2010 at 4:49 PM, Robert Coup
> wrote:
>
>> I can write you a trac extension/patch - just didn't want to spend the
>> time on it if nobody was keen. May be as simple as customising the
>> email template, but we don't want
On Apr 21, 9:46 am, Jeremy Dunck wrote:
> [...] Even so, the perception of ignored tickets is part of the
> problem-- whether tickets are actually ignored or not, the perception
> still would discourage contribution.
>
> I'd like to highlight tickets that have sat in each queue for a period
> of
I just built something in a similar vein as this for my team's
internal use. Amusingly, I used Django's inspectdb feature to directly
interface with Redmine's database and provide a separate front-end.
The data feeds into a javascript graphing library.
The ability to visualize languishing issues,
That sounds like a great idea! Even having been at this for a few
months I'd watch it just to see how somebody else handles things.
On Apr 20, 10:55 am, Alex Gaynor wrote:
> On Tue, Apr 20, 2010 at 1:36 PM, Bmheight wrote:
> > +1 to Stephen Crosbys' proposal, although I think this would be a bit
That's awesome. I'll definitely add to that when I have some time
tonight.
On Apr 20, 2:49 pm, Robert Coup
wrote:
> On Wed, Apr 21, 2010 at 9:12 AM, Jacob Kaplan-Moss wrote:
> > I like this a lot. Especially the "your next steps" part - it makes it
> > very obvious what the next thing interested
On Tue, Apr 20, 2010 at 4:49 PM, Robert Coup
wrote:
> Tada... http://code.djangoproject.com/wiki/TicketChangeHelp
>
> Most of it is empty - please help fill it in!
This is an awesome start - thanks! I'll try to help fill stuff in and
edit for tone/style as I can.
> I can write you a trac extensi
Cujo... for starters it's Amon Tobin's first moniker (he remixes jazz
into some delightful tunes, if you don't know of him I strongly
recommend you go to your local record store and pick up a copy of
"Adventures in Foam").
Also, I felt it was somewhat apt due to the rabid nature of the
discussions
On Wed, Apr 21, 2010 at 9:12 AM, Jacob Kaplan-Moss wrote:
> I like this a lot. Especially the "your next steps" part - it makes it
> very obvious what the next thing interested parties should do is.
>
> Could you start a wiki page with this stuff? Until we figure out how
> to get it more visible,
On Mon, Apr 19, 2010 at 9:19 AM, Jacob Kaplan-Moss wrote:
...
> So: here's your chance. You have suggestions about Django's
> development process? Make them. I'm listening.
I have a perception that there are some phases of the ticket lifecycle
where things get stuck -- I think that if you look at
+1
I would also be willing to contribute some time in developing this Wiki
page, editing, etc.
On Tue, 20 Apr 2010, Jacob Kaplan-Moss wrote:
On Tue, Apr 20, 2010 at 3:53 PM, Robert Coup
wrote:
Idea #1:
When a ticket is currently closed Trac sends you an email saying
"status:closed resol
On Tue, Apr 20, 2010 at 3:53 PM, Robert Coup
wrote:
> Idea #1:
> When a ticket is currently closed Trac sends you an email saying
> "status:closed resolution:wontfix" and whatever comment is made by the
> person who closed it.
> How about a plugin for Trac that expands these ... "concise" emails w
On Tue, Apr 20, 2010 at 5:09 PM, Karen Tracey wrote:
> On Tue, Apr 20, 2010 at 5:03 PM, Alex Gaynor wrote:
>>
>> Do you have any idea how that caused the fail, it should be completely
>> innocuous?
>>
>
> I'm guessing it's got something to do with the ... at the beginning of the
> line making it
On Tue, Apr 20, 2010 at 5:03 PM, Alex Gaynor wrote:
>
> Do you have any idea how that caused the fail, it should be completely
> innocuous?
>
>
I'm guessing it's got something to do with the ... at the beginning of the
line making it appear to be a shell continuation line, not ellipsis for
output
On Tue, Apr 20, 2010 at 4:54 PM, Karen Tracey wrote:
> On Tue, Apr 20, 2010 at 3:44 PM, Anssi Kaariainen
> wrote:
>>
>> I am trying to run some doc tests, but can't figure out how.
>> Specifically I would like to run the doc tests in regressiontests/
>> forms/widgets.py.
>>
>> Running "./runtests
Hi all,
On Tue, Apr 20, 2010 at 8:34 AM, Gabriel Hurley wrote:
> When I finally did submit my first patch, I was terrified of getting
> it wrong and having it rejected. I'd seen it happen on other tickets.
>
As a project, I'm sure we don't want any (even potential) contributors to be
terrified.
On Tue, Apr 20, 2010 at 3:44 PM, Anssi Kaariainen wrote:
> I am trying to run some doc tests, but can't figure out how.
> Specifically I would like to run the doc tests in regressiontests/
> forms/widgets.py.
>
> Running "./runtests.py --settings=test_sqlite forms" from the tests
> directory it ru
I am trying to run some doc tests, but can't figure out how.
Specifically I would like to run the doc tests in regressiontests/
forms/widgets.py.
Running "./runtests.py --settings=test_sqlite forms" from the tests
directory it runs the unit tests (changing them results in failures)
but not the doc
Also a +1 from me on the proposal for a tutorial for contributing and
how to get into the process of using Django's trac. I also tried to
get into triaging tickets a few times but I was very unsure in most
cases how to handle the status of the tickets, how to decide what
needs to be done or if this
On Tuesday 20 April 2010 16:43:25 Alex Gaynor wrote:
> In general I don't think that the fields on tickets are nearly as
> liable to being inaccurate as people are making it sound. That
> said marking users who are committers or triagers or what not
> probably wouldn't hurt.
Since our contributi
On Mon, Apr 19, 2010 at 7:52 PM, Russell Keith-Magee
wrote:
> On Tue, Apr 20, 2010 at 5:20 AM, Don Guernsey wrote:
>> How do I sign up to help? Is there an overall schematic for how django
>> works?
>
> There's no official signup process; just dig in and get your hands
> dirty. General guidance o
On Tue, Apr 20, 2010 at 1:36 PM, Bmheight wrote:
> +1 to Stephen Crosbys' proposal, although I think this would be a bit
> difficult to perform as the Framework evolves and the documentation on this
> would be a bit outdated as time goes on (And have to yet again maintain
> another Document to kee
+1 to Stephen Crosbys' proposal, although I think this would be a bit
difficult to perform as the Framework evolves and the documentation on this
would be a bit outdated as time goes on (And have to yet again maintain
another Document to keep up to date).
It it still none the less a good idea in m
What could be very helpful here is some education for would-be Django
developers. The tutorial format has worked so well for educating new Django
users, why not apply it also to Django developers also? After the 1.2
release, why don't we come up with a Django developers tutorial that walks
us throu
On Mon, Apr 19, 2010 at 3:34 PM, Gabriel Hurley wrote:
> When I finally did submit my first patch, I was terrified of getting
> it wrong and having it rejected. I'd seen it happen on other tickets.
> It wasn't until I got *more involved* and started keeping up with the
> trac timeline--watching th
On Tue, Apr 20, 2010 at 11:39 AM, Jacob Kaplan-Moss wrote:
> On Mon, Apr 19, 2010 at 2:32 PM, Giuseppe Ciotta wrote:
>> Having an additional field{s} in the ticket, only accessible to core
>> developers, where they would put the "official" (as in: approved by a
>> core developer) triage status of
On Mon, Apr 19, 2010 at 2:32 PM, Giuseppe Ciotta wrote:
> Having an additional field{s} in the ticket, only accessible to core
> developers, where they would put the "official" (as in: approved by a
> core developer) triage status of the ticket, could improve the
> efficency of the tickets review.
On Mon, Apr 19, 2010 at 8:19 AM, Jacob Kaplan-Moss wrote:
> Hi folks --
>
> I'd like to try to reboot the discussion that's been going on about
> Django's development process.
>
> I'm finding the current thread incredibly demoralizing: there's a
> bunch of frustration being expressed, and I hear t
On Apr 20, 10:38 am, Andrew Badr wrote:
> Umpires? Strike three off a curveball?
+1, though I'd quoted big bang theory, no need for a umpire, bdfl
should be more than enough!
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this
Umpires? Strike three off a curveball?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@goo
34 matches
Mail list logo
