Mark,

I have access to 64bit Mac and 32bit Linux development machines.  Which 
platforms do you still need .a's compiled on?  Let me know and I will be happy 
to build them and send them to you.

Thanks,

Matt

On Sep 12, 2013, at 8:15 AM, Matthew Taylor <[email protected]> wrote:

> If you cannot make progress on a task without someone else's help, it
> would be blocked. Only disown the ticket if you don't plan on working
> on it anymore. If you are willing to let it go to someone else, just
> mention that in a comment, and you might even mail the list (like you
> just did :) ) and let people know it's available and you are blocked.
> Then anyone can just come and reassign it to themselves.
> 
> Don't be afraid to mail the list if you need help with anything, or
> you want to discuss a ticket. If it becomes a distraction from the
> other more theoretical conversations on the ML, we could potentially
> create a "nupic-dev" mailing list that only includes messages about
> active code development.
> ---------
> Matt Taylor
> OS Community Flag-Bearer
> Numenta
> 
> 
> On Thu, Sep 12, 2013 at 2:46 AM, Marek Otahal <[email protected]> wrote:
>> Matt,
>> I closed PR#228 per this discussion, NPC-256 tracks that instead. Now I
>> wonder what should I set progress to? It's almost finished, hence "in
>> progress", but requiring sb else to intervene (do a compilation in this
>> case) - so "blocked"? and should I disown, so that other ppl know sb
>> can/need to take it up?
>> 
>> 
>> On Wed, Sep 11, 2013 at 10:46 PM, Matthew Taylor <[email protected]> wrote:
>>> 
>>> Guys,
>>> 
>>> A certain amount of direct communication always needs to occur between
>>> developers to avoid nasty merges. The SCM system's merging tools can only do
>>> so much for us. One way to mitigate this situation is to create tickets in
>>> our issue tracking system before you start any significant work. If everyone
>>> is doing this, there would be a central location to find out who is working
>>> on what issues.
>>> 
>>> I would encourage everyone wanting to work on NuPIC to create tickets to
>>> describe any work you're planning on doing. Feel free to write a note to the
>>> ML as well, especially if you think it's something that others might be
>>> working on.
>>> 
>>> If you are working on a ticket, mark it to "In Progress" and add it to the
>>> current sprint.
>>> 
>>> For example, David, you are working on NPC-300. If you go to our agile
>>> board[1], you can move this ticket from "To Do" into the "In Progress"
>>> column of the page simply by dragging it over.
>>> 
>>> ---------
>>> Matt Taylor
>>> OS Community Flag-Bearer
>>> Numenta
>> 
>> 
>> 
>> --
>> Marek Otahal :o)
>> 
>> _______________________________________________
>> nupic mailing list
>> [email protected]
>> http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
>> 
> 
> _______________________________________________
> nupic mailing list
> [email protected]
> http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org


_______________________________________________
nupic mailing list
[email protected]
http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org

Reply via email to