[sage-devel] Re: Jobs involving SageMath

2015-06-06 Thread Samuel Lelievre
2015-06-06 21:50:52 UTC+2, Samuel Lelievre: http://wiki.sagemath.org/jobs Discussion moved to sage-marketing https://groups.google.com/d/topic/sage-marketing/iEVH8PfRCNE/discussion -- You received this message because you are subscribed to the Google Groups sage-devel group. To

[sage-devel] Re: need help posting to trac

2015-06-06 Thread Dima Pasechnik
first of all, in your trac account you need the public key of your ssh key-pair (If I lose you here, please shout!) login to trac in the browser, go to Preferences, and select the SSH Keys tab; paste there your id_rsa.pub from ~/.ssh/ on your local machine, and click Save... below the pasting

[sage-devel] Re: Full-time developer position in Bordeaux for Fall 2015

2015-06-06 Thread Dima Pasechnik
On Thursday, 4 June 2015 11:18:56 UTC+1, vdelecroix wrote: Dear all, In the context of the OpenDreamKit project, a position is opened for a full-time developer for 1 to 4 years at the University of Bordeaux starting in Fall 2015 it's not quite clear what do you mean by 1 to 4 years.

[sage-devel] Re: need help posting to trac

2015-06-06 Thread Dima Pasechnik
subject ought to be ...help for pushing changes to the trac's git server (in the era of hg it would be ... help for uploading mercurial patches to trac) On Friday, 5 June 2015 19:07:12 UTC+1, David Perkinson wrote: I have just made a *lot* of revisions to the files in the sage/sandpiles/

[sage-devel] FYI: `gap_packages` optional doctests don't pass, so the package was moved to experimental.

2015-06-06 Thread Dima Pasechnik
WTF? Can you at least give a notice to fix the doctests?! #17390: GAP 4.7.7 -+- Reporter: slelievre |Owner: Type: enhancement| Status: closed

[sage-devel] Re: FYI: `gap_packages` optional doctests don't pass, so the package was moved to experimental.

2015-06-06 Thread Volker Braun
If you can fix the doctests then just switch it back to optional, its not a big deal. Really only the content of build/pkgs/gap_packages/type changed. On Saturday, June 6, 2015 at 11:38:24 AM UTC+2, Dima Pasechnik wrote: WTF? Can you at least give a notice to fix the doctests?! #17390: GAP

[sage-devel] Re: FYI: `gap_packages` optional doctests don't pass, so the package was moved to experimental.

2015-06-06 Thread Dima Pasechnik
On Saturday, 6 June 2015 16:18:26 UTC+1, Volker Braun wrote: Jeroen made those comments, for the record. Does Jeroen now have an authority to decide which package does not deserve to be called 'optional'? just wondering... On Saturday, June 6, 2015 at 4:47:30 PM UTC+2, Dima Pasechnik

Re: [sage-devel] Re: FYI: `gap_packages` optional doctests don't pass, so the package was moved to experimental.

2015-06-06 Thread Jeroen Demeyer
On 2015-06-06 16:47, Dima Pasechnik wrote: all of them looked as it sent by a bot I get mistaken for a bot, how sad is that... -- 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

[sage-devel] Re: FYI: `gap_packages` optional doctests don't pass, so the package was moved to experimental.

2015-06-06 Thread Dima Pasechnik
On Saturday, 6 June 2015 10:47:09 UTC+1, Volker Braun wrote: If you can fix the doctests then just switch it back to optional, its not a big deal. Really only the content of build/pkgs/gap_packages/type changed. sure, but I got 4 messages about different optional packages, all of them

[sage-devel] Re: FYI: `gap_packages` optional doctests don't pass, so the package was moved to experimental.

2015-06-06 Thread Volker Braun
Jeroen made those comments, for the record. On Saturday, June 6, 2015 at 4:47:30 PM UTC+2, Dima Pasechnik wrote: On Saturday, 6 June 2015 10:47:09 UTC+1, Volker Braun wrote: If you can fix the doctests then just switch it back to optional, its not a big deal. Really only the content of

[sage-devel] Re: FYI: `gap_packages` optional doctests don't pass, so the package was moved to experimental.

2015-06-06 Thread Dima Pasechnik
by the way: $ git blame build/pkgs/gap_packages/type ef11087e (Jeroen Demeyer 2015-06-01 10:12:49 +0200 1) experimental So that did happen few days ago already... On Saturday, 6 June 2015 16:35:55 UTC+1, Dima Pasechnik wrote: On Saturday, 6 June 2015 16:18:26 UTC+1, Volker Braun wrote:

[sage-devel] Re: Jobs involving SageMath

2015-06-06 Thread Dima Pasechnik
On Saturday, 6 June 2015 21:46:20 UTC+1, Samuel Lelievre wrote: 2015-06-06 21:50:52 UTC+2, Samuel Lelievre: http://wiki.sagemath.org/jobs Discussion moved to sage-marketing https://groups.google.com/d/topic/sage-marketing/iEVH8PfRCNE/discussion marketing? I don't think

Re: [sage-devel] Jobs involving SageMath

2015-06-06 Thread Justin C. Walker
On Jun 6, 2015, at 14:05, Dima Pasechnik dimp...@gmail.com wrote: On Saturday, 6 June 2015 21:46:20 UTC+1, Samuel Lelievre wrote: 2015-06-06 21:50:52 UTC+2, Samuel Lelievre: http://wiki.sagemath.org/jobs Discussion moved to sage-marketing

Re: [sage-devel] Re: FYI: `gap_packages` optional doctests don't pass, so the package was moved to experimental.

2015-06-06 Thread Dima Pasechnik
On Saturday, 6 June 2015 17:44:52 UTC+1, Jeroen Demeyer wrote: On 2015-06-06 16:47, Dima Pasechnik wrote: all of them looked as it sent by a bot I get mistaken for a bot, how sad is that... well, sorry. But the four messages looked identical; I thought we have a new reincarnation of

[sage-devel] Jobs involving SageMath

2015-06-06 Thread Samuel Lelievre
Hi all, I created a jobs page on the SageMath wiki: http://wiki.sagemath.org/jobs I think it adding a link to that page on the sagemath.org homepage would make sense, what do you think? I also noticed that SageMath has a LinkedIn profile https://www.linkedin.com/grp/home?gid=2010654

[sage-devel] Re: need help posting to trac

2015-06-06 Thread kcrisman
Yes. The most important git command is git status and tells you where you currently are. The preferred (=less confusing) workflow is to first create a branch and then start editing. There are various ways to later fix it, though. For example git checkout -b my_branch would work in your