Hi Becka, On Thu, Mar 3, 2016 at 8:55 AM, Becka <[email protected]> wrote:
> Hi, > > I've been spending some time looking over the docs, and I'm really > interested in making them more approachable to relative n00bs like myself, > particularly when it comes to contributing to Django and the docs. > Fantastic! This sort of contribution is most appreciated! Thanks for offering to help out. > It seems like there's some conflicting information around where to look > for issues. > > * There's one address <https://code.djangoproject.com/newticket> where > you need to log in, but I can't see where to sign up > > * There's another url > <https://code.djangoproject.com/query?status=!closed&easy=1>where there > are some "easy pickings" tickets > > Where can tickets be filed? Where should someone starting out look for > tickets, and can they (we) open issues? I'd like to clarify what the docs > ssay about this point. > We’re using a system called Trac as an issue tracker; when you hit code.djangoproject.com, that’s our Trac instance. Trac has a number of features, including an issue tracker, a wiki, and a few other bits and bobs. The homepage of the Trac instance is a wiki page that tells you where to go next (or, at least, tries to!) The first two links under “getting started” on that page are links into the ticket tracker; If you’re looking for somewhere to make your first contribution “easy pickings” is a list of tickets that has been pre-filtered to only contain issues that might be easy for a newcomer to tackle. Easy pickings is a good place to start if you want to make your first contribution. The other link (“tickets”) is a link to a wiki page that contains a couple of other pre-canned queries that can be helpful. All of those pre-canned queries will ultimately end up at https://code.djangoproject.com/query, which is the searchable index of all tickets. From there, you can add and remove filters to find the exact ticket you want. If you want to report a new issue, the first link you provide (/newticket) is where you should go (unless it’s a security issue, in which case a whole other procedure is required). The login is required as a spam measure - if you don’t lock down Trac, random bots drop by and open tickets for !!Fr33 STUFF!!. I hope that helps - if there’s anything else we can do to explain the process we have, let us know! Yours Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq848NRqQO6WpqOX4ZAs%2Bm%2B_JZqRievPq8Cmiw82UdaF28jA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
