Mon, 2016-01-18 06:07:04 -0800 (PST), kcrisman:
See last year's Sage GSOC wiki page
>>
>> http://wiki.sagemath.org/GSoC/2016
>>
>>
> For the record (especially newbies), that's
> http://wiki.sagemath.org/GSoC/2015
>
>
>> for inspiration and formatting (copy-paste and adapt from there).
>
> See last year's Sage GSOC wiki page
>
> http://wiki.sagemath.org/GSoC/2016
>
>
For the record (especially newbies), that's
http://wiki.sagemath.org/GSoC/2015
> for inspiration and formatting (copy-paste and adapt from there).
>
>
But not *too* much copy-paste ;-)
--
You received
For GSoC, we should really insist that the coders try to get their code
on trac from the start. In particular, they should follow the "one
ticket, one issue" rule and not just dump everything on one ticket.
I have seen some GSoC projects where one person codes for the summer,
puts the code on
Mentors should also consider subscribing to sage-gsoc
https://groups.google.com/forum/#!forum/sage-gsoc
where applicants will introduce themselves.
2016-01-18 12:21 GMT+00:00 Samuel Lelièvre :
> Hi all,
>
> Sage will be applying to Google Summer of Code (GSOC) again this year.
>
> Informatio
Le lundi 18 janvier 2016 10:18:54 UTC, Harald Schilly a écrit :
>
> the hosting is on github, and if a subdirectory matches a project,
> it's a "sub-page"
>
> So, the second link is pointing here:
> https://github.com/sagemath/git-developer-guide
>
> I don't know anything about this repositor
On Jan 17, 2016, at 1:12 AM, Volker Braun wrote:
>
> IMHO the app should just start and manage its own jupyter server; Launch it
> on startup and shut it down when the app is closed. The notebook server
> doesn't fork into the background so its trivial to just keep a single
> process, no need
Hi all,
Sage will be applying to Google Summer of Code (GSOC) again this year.
Information for applicants is on this wiki page.
http://wiki.sagemath.org/GSoC/2016
Anyone with ideas for projects, please add them there.
See last year's Sage GSOC wiki page
http://wiki.sagemath.org/GSoC/2
the hosting is on github, and if a subdirectory matches a project,
it's a "sub-page"
So, the second link is pointing here:
https://github.com/sagemath/git-developer-guide
I don't know anything about this repository.
> Harald, I actually don't know where doc.sagemath is coming from, can you
> ha
> Harald, I actually don't know where doc.sagemath is coming
> from
It is our "new doc index" since the last hosting changes. What used to
be the index is not used anymore as far as I know.
http://doc.sagemath.org/html/en/website/
Nathann
--
You received this message because you are subscr
I vaguely remember copying it there during the git transition for testing,
please remove. Harald, I actually don't know where doc.sagemath is coming
from, can you handle it?
On Monday, January 18, 2016 at 8:47:05 AM UTC, Jeroen Demeyer wrote:
>
> On 2016-01-18 09:19, Samuel Lelièvre wrote:
> >
On 2016-01-18 09:19, Samuel Lelièvre wrote:
http://www.sagemath.org/git-developer-guide/trac.html
This looks like an oudated version of the real developer guide. Not sure
what it's doing there.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" grou
Hi all,
anyone know why these two documents are online:
http://doc.sagemath.org/html/en/developer/trac.html
http://www.sagemath.org/git-developer-guide/trac.html
and whether one is an old version of the other?
Best, Samuel
--
You received this message because you are subscribed to the
12 matches
Mail list logo
