[sage-devel] Re: Best way to discuss an open ticket?

2014-08-10 Thread Volker Braun
If you know who wrote the code in question or who maintains it, you can CC 
them on the trac ticket. Other than that, posting to sage-devel is 
perfectly ok if you have questions.



On Sunday, August 10, 2014 9:35:58 PM UTC+1, Paul Graham wrote:
>
> Im not sure if the other developer that has now made a comment on the 
> ticket im using as an example, #16228, did so because i made this post to 
> the mailing list or because they came across it purely through trac 
> somehow. I dont know if thats a coincidence or not, but basically i am just 
> wondering if in this case and future cases, making a mailing list post like 
> "#16228 make tachyon respect standard verbosity settings" is the thing to 
> do? Hopefully that makes sense :)
>
> On Sunday, August 10, 2014 12:45:19 PM UTC-7, Paul Graham wrote:
>>
>> In working on some of the beginner tickets, and for some of them they are 
>> straightforward enough that i can work on them on my own up to changing the 
>> status to needs-review. But for others if im unsure where to start on it, 
>> or cant push my code to trac without input from other developers, what is 
>> the best way to get some feedback on a specific ticket?
>>
>>
>> E.g. #16228, http://trac.sagemath.org/ticket/16228 , im unsure of which 
>> approach to take. I commented on the ticket to see if there is a place on 
>> trac where tickets with new comments are bumped to, and Active Tickets -> 
>> By Time , shows it add the top, but i dont know if this is a common place 
>> to look.
>>
>> I couldnt find much info on the needs_info status, and didnt see too many 
>> examples on the mailing list titled like "#12345 doing x in x", so am 
>> wondering what the usual way to do this is?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: Best way to discuss an open ticket?

2014-08-10 Thread Dima Pasechnik
On 2014-08-10, Paul Graham  wrote:
> --=_Part_2607_1440653767.1407702958902
> Content-Type: text/plain; charset=UTF-8
>
> Im not sure if the other developer that has now made a comment on the 
> ticket im using as an example, #16228, did so because i made this post to 
> the mailing list or because they came across it purely through trac 
> somehow. I dont know if thats a coincidence or not, but basically i am just 
> wondering if in this case and future cases, making a mailing list post like 
> "#16228 make tachyon respect standard verbosity settings" is the thing to 
> do? Hopefully that makes sense :)
Sure, this makes sense.

Yes, I saw your previous post...

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: Best way to discuss an open ticket?

2014-08-10 Thread Paul Graham
Im not sure if the other developer that has now made a comment on the 
ticket im using as an example, #16228, did so because i made this post to 
the mailing list or because they came across it purely through trac 
somehow. I dont know if thats a coincidence or not, but basically i am just 
wondering if in this case and future cases, making a mailing list post like 
"#16228 make tachyon respect standard verbosity settings" is the thing to 
do? Hopefully that makes sense :)

On Sunday, August 10, 2014 12:45:19 PM UTC-7, Paul Graham wrote:
>
> In working on some of the beginner tickets, and for some of them they are 
> straightforward enough that i can work on them on my own up to changing the 
> status to needs-review. But for others if im unsure where to start on it, 
> or cant push my code to trac without input from other developers, what is 
> the best way to get some feedback on a specific ticket?
>
>
> E.g. #16228, http://trac.sagemath.org/ticket/16228 , im unsure of which 
> approach to take. I commented on the ticket to see if there is a place on 
> trac where tickets with new comments are bumped to, and Active Tickets -> 
> By Time , shows it add the top, but i dont know if this is a common place 
> to look.
>
> I couldnt find much info on the needs_info status, and didnt see too many 
> examples on the mailing list titled like "#12345 doing x in x", so am 
> wondering what the usual way to do this is?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.