Datarray sprint July 28, 2010
Join us for a datarray sprint on July 28. Several of us will meet at UC Berkeley from 2pm (Pacific Time) until our fingers bleed from typing or until 6 or 7pm, whichever comes first. If you can't be there in person, grab an item from the issue tracker or create your own. I'm told some of us will hang out on IRC #scipy, so we can coordinate there. A datarray is a subclass of a Numpy array that lets you label the axes and label the elements along each axis. Our target is to get this into Numpy. We are currently in the prototype stage, so this is a good time to jump in. code: http://github.com/fperez/datarray issue tracker: http://github.com/fperez/datarray/issues
On Tue, Jul 27, 2010 at 11:13 AM, Keith Goodman <kwgoodman@gmail.com> wrote:
Join us for a datarray sprint on July 28. Several of us will meet at UC Berkeley from 2pm (Pacific Time) until our fingers bleed from typing or until 6 or 7pm, whichever comes first.
If you can't be there in person, grab an item from the issue tracker or create your own. I'm told some of us will hang out on IRC #scipy, so we can coordinate there.
A datarray is a subclass of a Numpy array that lets you label the axes and label the elements along each axis. Our target is to get this into Numpy. We are currently in the prototype stage, so this is a good time to jump in.
code: http://github.com/fperez/datarray issue tracker: http://github.com/fperez/datarray/issues
At the end of the datarray sprint we released datarray 0.0.3: download: http://pypi.python.org/pypi/datarray doc: http://fperez.github.com/datarray-doc We did two things: - Put datarray in standard package form (added setup.py, license, directory structure, etc) - Bug fixes What we did not do: - Communicate well with those we invited to join us through IRC. I apologize. Going forward we would like to: - Move the repo from Fernando's personal github account to a datarray account. But we do not know a way to move a github repo along with all its meta data (fork queue, issue tracker etc). - Merge the work that has already been done by others. Going forward, if pull requests contained a single issue (we did not discuss this, just my guess) it would be easier to merge. Now that we have an issue tracker, opening an issue helps too.
On Thu, Jul 29, 2010 at 1:06 PM, Keith Goodman <kwgoodman@gmail.com> wrote: <snip>
Going forward we would like to:
- Move the repo from Fernando's personal github account to a datarray account. But we do not know a way to move a github repo along with all its meta data (fork queue, issue tracker etc).
Is Fernando's github still the most up to date location for datarray? Skipper
On Mon, Aug 23, 2010 at 2:19 PM, Keith Goodman <kwgoodman@gmail.com> wrote:
On Mon, Aug 23, 2010 at 2:17 PM, Skipper Seabold <jsseabold@gmail.com> wrote:
Is Fernando's github still the most up to date location for datarray?
Yes.
We'd love to move it out of my page to a numpy-owned repo, so once that dust settles I'm more than happy to ask github for a move. It makes no real sense that it's in my github account, as I have no more special rights in there than anyone else (and likely less time available to do real work than others). Since it seems that we're now very close to a real move of numpy to github, we should be good to move this over in a week or two. Regards, f
On 24 August 2010 03:17, Fernando Perez <fperez.net@gmail.com> wrote:
We'd love to move it out of my page to a numpy-owned repo, so once that dust settles I'm more than happy to ask github for a move.
I guess we can just create the new repo ourselves, or does GitHub track some other meta-data that should be moved? Regards Stéfan
2010/8/23 Stéfan van der Walt <stefan@sun.ac.za>:
On 24 August 2010 03:17, Fernando Perez <fperez.net@gmail.com> wrote:
We'd love to move it out of my page to a numpy-owned repo, so once that dust settles I'm more than happy to ask github for a move.
I guess we can just create the new repo ourselves, or does GitHub track some other meta-data that should be moved?
Yes, please do *not* create it. We need to make a manual move request, see for example: http://support.github.com/discussions/organization-issues/123-request-to-mov... This ensures that all metadata moves with the repo (issues, fork queues, etc). Once moved, only I have to re-fork and we're done. People will then need to update their remote urls in their clones (or re-clone if they are lazy) but that's it. Cheers, f
participants (4)
-
Fernando Perez -
Keith Goodman -
Skipper Seabold -
Stéfan van der Walt