Time to commit: If you plan on participating and will not need lodging or any significant reimbursements (such as if you live in the Portland area, or are planning on participating remotely), feel free to update the wiki page appropriately. Otherwise, please send me an email with an estimate of your anticipated travel expenses, whether you will need lodging or not, as well as what days you plan on attending, and I will get back to you as soon as I have the chance.
If you are a not a US citizen, I will need to hear from you on or before Friday, February 1st, there are a couple extra hurdles that need to be sorted out for your reimbursement. If you are a US citizen, please get back to me as soon as you are able, it will make all our lives easier in the long run. Original Annoucement: Dates: March 25-29, 2013 Location: Portland State University (Portland, Oregon) Wiki Page: http:// <http://wiki.sagemath.org/sagedaysgit>wiki.sagemath.org<http://wiki.sagemath.org/sagedaysgit> / <http://wiki.sagemath.org/sagedaysgit>sagedaysgit<http://wiki.sagemath.org/sagedaysgit> Objectives: * Prepare the Sage codebase for the new directory layout necessary for a unified repository * Create a set of development tools for interfacing with Trac and Git * Extend the Trac's Git functionality to include the ability to "attach" branches to tickets This is NOT a Sage days to learn about how to develop with Git, hopefully we will have a Sage days focused on that closer to the switch. -- Andrew -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
