On 09/01/16 13:08, Hugo Osvaldo Barrera wrote:
Not an actual django developer (I'm a user lurking here really), but I'd
still like to chime in:
Doesn't make your input any less valid... in fact, perhaps makes it more
valuable :)
* Jira is too complex. Devs may end up understanding it,
On Wednesday, January 6, 2016 at 10:09:08 AM UTC-3, Victor Sosa wrote:
>
> HI,
>
> I felt like lost using trac; it is kind of messy. I just don't feel
> comfortable
> with it.
> I see so many open source project using Jira that is just natural. Search
> is easy, categorize is easy, look
No problem. Don't forget the documentation too. That was called out in the
original license. For instance, I'd put it right on the README.md on the
correct project(s) on GitHub under the license section.
OTOH, I'm now interested in checking it out, so thanks.
On Fri, Jan 8, 2016 at 3:42 AM,
Hi Joe
On Fri, Jan 8, 2016 at 7:16 AM, Joe Tennies wrote:
> I'm not a lawyer, but I care about licensing.
>
> The MIT License would allow you to relicense it, but you must keep the
> original copyrights in tact. (From license: Redistribution and use in
> source and binary
I'm not a lawyer, but I care about licensing.
The MIT License would allow you to relicense it, but you must keep the
original copyrights in tact. (From license: Redistribution and use in
source and binary forms, *with or without modification*, are permitted...)
It does have a list of "buts" too.
Hi Andrey,
On 01/07/2016 04:23 PM, Andrey Antukh wrote:
> On Fri, Jan 8, 2016 at 12:42 AM, Florian Apolloner
> The DRFv2 (as DRFv3) as far as I know is licensed using MIT permissive
> license that does not impide take the source and re-license it under
> other license.
>
> taiga.io
HI Florian
On Fri, Jan 8, 2016 at 12:42 AM, Florian Apolloner
wrote:
> Hi Yamila,
>
> On Thursday, January 7, 2016 at 2:22:21 PM UTC+1, Yamila Moreno wrote:
>>
>> I just wanted to let you know that me or anyone in our team would be glad
>> to answer any question about the
Weighing in on Jira specifically - I’ve had to use it on a number of
projects, and I’ve never had a good experience with it. That might be
because the Jira instances were badly configured - bit if that’s the case,
it suggests to me that there’s a deeper problem with Jira being too complex
for it’s
I used Jira at my previous company. It is a great tool, but it is
_extremely_ heavyweight. Unless you need to high level of customisation of
workflows and integrations it can provide, and have someone intimately
familiar with it and/or have the nearly-full-time job of learning and
fiddling
Hi Yamila,
On Thursday, January 7, 2016 at 2:22:21 PM UTC+1, Yamila Moreno wrote:
>
> I just wanted to let you know that me or anyone in our team would be glad
> to answer any question about the product, saas or installation, migrating
> issues or anything related. No strings attached, of
Hi,
> Are you already familiar with Trac and the way we use it?
>
I'm familiar with trac (we were using it some year ago), and I'm a bit
familiar with django workflow because I attended a couple of sprints.
Anyway, I'm not an expert in trac.
>
> Key things are:
>
> * integration with
On Thu, Jan 7, 2016, Yamila Moreno wrote:
>I'm Yamila, part of Taiga Team and Kaleidos (the company that develops
>Taiga.io). We're very happy to be as a "completely hypothetical" candidate
>for a new bugtracker. Taiga (a Django and open source project) being used
>by
Hi there,
I'm Yamila, part of Taiga Team and Kaleidos (the company that develops
Taiga.io). We're very happy to be as a "completely hypothetical" candidate
for a new bugtracker. Taiga (a Django and open source project) being used
by django-dev would be huge :)
I just wanted to let you know
To search Trac, use "site:code.djangoproject.com your query" in a Google
search box. Works great in my experience.
On Wednesday, January 6, 2016 at 6:42:44 PM UTC-5, Josh Smeaton wrote:
>
> FWIW I actually like Jira (much more than Trac) and find it a lot easier
> to use. I think the trick is
FWIW I actually like Jira (much more than Trac) and find it a lot easier to
use. I think the trick is configuring very basic workflows so users don't
have to fight through transitions. Open, Closed, Assigned/In Progress and
transitions to and from each state would get us really close to the
Looks like it is a NO to the proposition.
Daniele
I like what I saw in taiga, that's a way better bug tracking UI; you can
check here:
https://tree.taiga.io/project/taiga/issues?page=1
On Wednesday, January 6, 2016 at 12:18:13 PM UTC-4, Daniele Procida wrote:
>
> On Wed, Jan 6, 2016, Daniele
On Wed, Jan 6, 2016, Daniele Procida wrote:
>By all means it's useful to get votes on something like this, even
>before we consider those questions, because if enough people want
>something it's always possible - but be aware that simply getting lots
>of votes for it would only
For whatever it's worth, our company switched from Pivotal Tracker to JIRA
because we added a QA team and they wanted all this flexibility in devising
bug ticket "workflows." All it did from my perspective is add 47 layers of
complexity on top of a massively confusing UI and insists on NOT
>
> FWIW Jira seems to be an exception among bug trackers: some people really
> love it, others really hate it. It depends on who set it up and maintained
> it in the company where they used it.
>
> Since we don’t have a resident Jira expert, we run the risk that most of
> the Django community
FWIW Jira seems to be an exception among bug trackers: some people really love
it, others really hate it. It depends on who set it up and maintained it in the
company where they used it.
Since we don’t have a resident Jira expert, we run the risk that most of the
Django community will fall
Agreed with the above for the same reasons.
On Wed, Jan 6, 2016 at 9:17 AM, Shai Berger wrote:
> What Marc and James said, and in particular what Daniele said : I get to
> use Jira on a daily basis and find it cumbersome and confusing.
>
> Shai see
>
>
> On 6 בינואר 2016
What Marc and James said, and in particular what Daniele said : I get to use
Jira on a daily basis and find it cumbersome and confusing.
Shai see
On 6 בינואר 2016 15:43:02 GMT+02:00, Marc Tamlyn wrote:
>Yeah, this is a non-starter for me. All bug trackers are bad, we
Ditto.
On Wednesday, January 6, 2016 at 2:43:44 PM UTC+1, Marc Tamlyn wrote:
>
> Yeah, this is a non-starter for me. All bug trackers are bad, we should
> stick with the bad one we are used to.
>
> Marc
>
> On 6 January 2016 at 13:26, Victor Sosa
> wrote:
>
>> To answer
Yeah, this is a non-starter for me. All bug trackers are bad, we should
stick with the bad one we are used to.
Marc
On 6 January 2016 at 13:26, Victor Sosa wrote:
> To answer you question:
> There is a plug-in to migrate all the data to Jira and similar to
> integrate
To answer you question:
There is a plug-in to migrate all the data to Jira and similar to integrate
with any it with any in you infrastructure. (I just don't know it all you
infrastructure)
https://confluence.atlassian.com/jira/importing-data-from-trac-238617182.html
On Wednesday, January 6,
I'd be against such a change. I've used a lot of bug trackers, and the only
thing I've learned is there is no good one; replacing one with another just
swaps one set of annoying limitations/frustrations for another. And since
there's a lot of inertia in whatever's currently being used, and it
On Wed, Jan 6, 2016, Victor Sosa wrote:
>I felt like lost using trac; it is kind of messy. I just don't feel
>comfortable
>with it.
>I see so many open source project using Jira that is just natural. Search
>is easy, categorize is easy, look through the all issues and
HI,
I felt like lost using trac; it is kind of messy. I just don't feel comfortable
with it.
I see so many open source project using Jira that is just natural. Search
is easy, categorize is easy, look through the all issues and task is quick.
I would like to propose a vote on Jira as the
28 matches
Mail list logo