Re: [sage-devel] Re: LazyPowerSeriesRing Replacement

[Kwankyu Lee]

On Tuesday, August 16, 2022 at 9:04:00 AM UTC+9 Travis Scrimshaw wrote:

>  the power series "is" a function (well, formally), we just usually think 
> of it as being equal to an "easier" function.
>

No. You know that a power series is an expression. It has variables, but 
not domain and codomain. 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e6a42805-c1cd-47ca-8215-e09a175efe17n%40googlegroups.com.

[sage-devel] Useful methods for graphics objects

[Kwankyu Lee]

Hi,

I wish  that this would work:

sage: l = line3d([(1,2,3),(2,2,3)])
sage: l.length()
1

Is there already a handy way to get the same result in Sage?

You can image other useful methods attached to a graphics object.



-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8a1d49d3-c045-48c5-a67a-eddb82ee19c9n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Kwankyu Lee]

On Monday, August 22, 2022 at 12:04:57 PM UTC+9 Travis Scrimshaw wrote:

> I am not sure how much I support that because there is no metric. 
>

It is of course euclidean, as you say
 

> you can do
>
> sage: l = line3d([(1,2,3), (4,5,6)])
> sage: V = RR^3
> sage: (V(l.points[1]) - V(l.points[0])).norm()
> 5.19615242270663
>

My point is to attach methods to graphics objects for handy computation. I 
am not sure if this is technically doable. 
 

> There could also be other natural interpretations of length here, such as 
> the number of (non-colinear) segments.
>

(1) .length() could be an alias of .line3d_euclidean_length() as this is 
most useful. 

(2) .line3d_combinatorial_length(): I doubt if this is useful for drawing.

Is this more pedagogical or are you using 3d line segments in some 
> meaningful way?
>

Pedagogical and meaningful :) I thought of this idea while drawing graphics 
to prepare lecture notes for a class next semester. 
If graphics objects get more powered, then drawing (2d or 3d) mathematical 
pictures, which is always difficult, would get less difficult. 

For another example,  we may implement a method to compute the intersection 
point given two line segments (as tikz can do in latex)

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/27ce1283-6d5d-4921-894c-d1043d299b5cn%40googlegroups.com.

Re: [sage-devel] Re: Trac #34152 needs you (to vote)!

[Kwankyu Lee]

hybrid

Hearty thanks for setting up the vote.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8f405fcb-3af7-4947-8395-fcc98d943e01n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Kwankyu Lee]

On Wednesday, August 24, 2022 at 9:18:06 AM UTC+9 Travis Scrimshaw wrote:

> Éric, what do you think about adding such things to SageManifolds? Could 
> this be feasible?
>

It is embarrassing that  an idea of attaching ".length()" method to a line 
segment graphics object leads to SageManifolds. We don't need vectors and 
inner products to compute the length of a line segment.

If we ever implement the idea, then it should be done with basic python 
only for "separations-of-concerns" and for modularization of sage.

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d4fba764-208f-49b9-8f78-5c9be4ec2ac8n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Kwankyu Lee]

On Thursday, August 25, 2022 at 4:06:14 AM UTC+9 Sébastien Labbé wrote:

> Is there already a handy way to get the same result in Sage? 
>>
>
>> You can image other useful methods attached to a graphics object.
>>
>
> For 2d lines, it returns a Graphics object which has a length.
>

Right. That every graphics object (line, circle, etc) is wrapped in 
Graphics object seems to make the implementation not straightforward...
 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c5575504-6ca4-4330-a712-6efc6bd5b916n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Kwankyu Lee]

>
> I have no idea what your argument is for the second part. Separations of 
> concerns means ...
>

I didn't use the phrase in its precise meaning (so I quoted it) 

I meant that you can write pythagorean formula, which is just what you need 
to compute the length of a line segment object,  without using Sage vectors 
and norms heavy machinery. For drawing, you only need simple maths. 
Moreover "Python only" seems necessary because of sage modularization 
effort.  

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3ce6f4dd-2e39-4e5e-8185-67b417a0c386n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Kwankyu Lee]

Let me expand the example a bit.

We are given two points. We draw a line segment connecting the two points. 
Then we want to draw a circle with a diameter the line segment.

Certainly we need to compute the center and the radius of the circle. The 
standard way to do this with Sage is, as Travis described, to do some 
vector calculus.

But an intuitive way (or an object-oriented way ?) is to get the necessary 
information from the line segment. Thus if L is the line segment, I do p = 
L.mid_point(); r = L.length() / 2. Then circle(p, r) will do the work.

On Thursday, August 25, 2022 at 5:55:21 PM UTC+9 Eric Gourgoulhon wrote:

> sage: E = EuclideanSpace(3)
> sage: L = E.line([(1,2,3),(2,2,3)])  # not implemented yet
> sage: L.length()
>

For the above example,  we create the line L and the circle C in 
EuclideanSpace(2). Then we do L.draw() + C.draw(). This is an interesting 
idea. But this would make graphics module a dependency of Euclidean space 
module.

By the way, the purpose of my original post is to ask whether providing the 
facility for the intuitive way of drawing (algorithmic drawing or 
object-oriented drawing, to invent a fancy term) is worth while or just 
waste of energy...

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/528b98a0-c39b-4638-ac31-a044476d3db1n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Kwankyu Lee]

On Friday, August 26, 2022 at 2:57:15 AM UTC+9 Nils Bruin wrote:

> On Thursday, 25 August 2022 at 07:23:41 UTC-7 Kwankyu Lee wrote:
>
>> But an intuitive way (or an object-oriented way ?) is to get the 
>> necessary information from the line segment. Thus if L is the line segment, 
>> I do p = L.mid_point(); r = L.length() / 2. Then circle(p, r) will do the 
>> work.
>>
>
> That sounds like the model that geogebra uses.
>

Yes. It would be a programming interface of the model.

I do think that having a graphical interface such as geogebra has is really 
> a plus for these applications, though, 
>

No intention to compete with geogebra with a graphical interface. 

Rather it would be a competition as like latex vs word. Really tikz does 
that in the latex world. But sage could have some functionality of tikz, 
working directly with sage graphics objects.
 

> In my experience, the tweaking of graphics for publication is what takes 
> by far the most time, so the more interface for that the better. 
>

Yes. We can view it as a way to tweak the graphics objects to get the 
matplotlib object we want. For example, we can easily draw a pentagon in 
sage, but tweaking the pentagon using the edges and vertices of the 
pentagon seems difficult. 

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/937e039c-cbd5-4430-86a2-fc5ea754b6d8n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Kwankyu Lee]

On Friday, August 26, 2022 at 8:04:02 AM UTC+9 Kwankyu Lee wrote:

> On Friday, August 26, 2022 at 2:57:15 AM UTC+9 Nils Bruin wrote:
>
>> On Thursday, 25 August 2022 at 07:23:41 UTC-7 Kwankyu Lee wrote:
>>
>>> But an intuitive way (or an object-oriented way ?) is to get the 
>>> necessary information from the line segment. Thus if L is the line segment, 
>>> I do p = L.mid_point(); r = L.length() / 2. Then circle(p, r) will do the 
>>> work.
>>>
>>
>> That sounds like the model that geogebra uses.
>>
>
> Yes. It would be a programming interface of the model.
>

Now I have this idea. (Sorry for the vague original post.) We add new class 
"GeometricFigure2d" and "GeometricFigure3d". Line segments, circle, etc 
would be subclasses. So we can do

l = figures.Line((1,2,3), (2,4,6))
p = l.mid_point()
r = l.length()
c = figures.Circle(p, r)
c.render(color="green")  # to get the rendered graphics object

We may say that the classes "GeometricFigure2(3)d"  implements descriptive 
geometry but with coordinates, for drawing purpose but not geometry.



 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8de0d74d-63fe-491a-b7ac-e651702e8cd6n%40googlegroups.com.

[sage-devel] Re: Useful methods for graphics objects

[Kwankyu Lee]

On Saturday, August 27, 2022 at 2:57:49 PM UTC+9 Nils Bruin wrote:

> Do keep in mind that there is a basic command-driven interface behind 
> Geogebra as well. 
>

Yes. Thank you.
 

> which does not fully determine a circle in 3-space
>

I was careless. I should have listed two coordinates for 2d line.
 

> It may still be that there's a market for this in sagemath/python; or it 
> may be an enjoyable recreational project to work on. But before you set off 
> on it, it's probably good to know what prior art is available, and it looks 
> like at least the start of what you'd be doing is reimplementing a lot of 
> the things geogebra already has.
>

If there's no market of sage users, then there is no reason to start. If 
there is, we can do the work bit by bit.
 

> On the python front, it looks like Sympy (which we already include) may 
> have a start for you: https://docs.sympy.org/latest/modules/geometry/
>

Thank you very much for helpful comments and info!
 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4e5ac74f-d502-4e3e-80e7-4ee4c57f356an%40googlegroups.com.

Re: [sage-devel] trac.sagemath.org unreachable

[Kwankyu Lee]

This seems a different problem. The website is not accessible.

On Wednesday, August 31, 2022 at 3:48:19 PM UTC+9 dim...@gmail.com wrote:

> new ssh keys on the server, don't know how to tell this to "git trac"
>
> On Wed, 31 Aug 2022, 07:45 Emmanuel Charpentier,  
> wrote:
>
>> This morning (Aug 31, 2022, 8:43), any attempt to reach `
>> trac.sagemath.org` ends up displayong a Python trace :
>>
>> ```
>> Traceback (most recent call last): File 
>> "/usr/local/lib/python2.7/dist-packages/trac/web/api.py", line 602, in 
>> send_error data, 'text/html') File 
>> "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 1104, in 
>> render_template template = self.load_template(filename, method=method) File 
>> "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 1053, in 
>> load_template self.get_all_templates_dirs(), auto_reload=self.auto_reload, 
>> File "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 758, 
>> in get_all_templates_dirs for provider in self.template_providers: File 
>> "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 82, in 
>> extensions components = [component.compmgr[cls] for cls in classes] File 
>> "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 208, in 
>> __getitem__ component = cls(self) File 
>> "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 144, in 
>> __call__ self.__init__() File 
>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 195, in 
>> __init__ self._init_gitolite_admin() File 
>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 66, in 
>> wrapper ret = inner_wrapper(self, *args, **kwargs) File 
>> "/usr/local/lib/python2.7/dist-packages/fasteners/lock.py", line 302, in 
>> wrapper return f(self, *args, **kwargs) File 
>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 52, in 
>> inner_method return method(self, *args, **kwargs) File 
>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 226, in 
>> _init_gitolite_admin self._update_gitolite_admin() File 
>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 287, in 
>> _update_gitolite_admin 'repository'.format(out)) TracError: Error updating 
>> the gitolite-admin repository: Host key verification failed. fatal: Could 
>> not read from remote repository. Please make sure you have the correct 
>> access rights and the repository exists. ; you may have to manually clean 
>> up or re-clone the repository
>> ```
>>
>> Any idea ?
>>
>> -- 
>> 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 an 
>> email to sage-devel+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/0c956548-4fa6-4970-8662-84de5b6975f0n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4a798658-f64e-4931-859d-570459789fc7n%40googlegroups.com.

[sage-devel] Re: trac.sagemath.org unreachable

[Kwankyu Lee]

Perhaps need to update trac server ssh keys stored in github?

On Wednesday, August 31, 2022 at 4:10:34 PM UTC+9 emanuel.c...@gmail.com 
wrote:

> And an attempt to fetch a ticket also failed for related reasons :
>
> charpent@zen-book-flip:/usr/local/sage-9$ git trac checkout 34457
> Loading ticket #34457...
>
> Traceback (most recent call last):
>   File "/home/charpent/Dev/git-trac-command/git_trac/digest_transport.py", 
> line 106, in single_request
> return self.parse_response(response)
>   File "/usr/lib/python3.10/xmlrpc/client.py", line 1354, in parse_response
> return u.close()
>   File "/usr/lib/python3.10/xmlrpc/client.py", line 668, in close
> raise Fault(**self._stack[0])
> xmlrpc.client.Fault:  repository: Host key verification failed.\nfatal: Could not read from 
> remote repository.\n\nPlease make sure you have the correct access 
> rights\nand the repository exists.\n; you may have to manually clean up or 
> re-clone the repository' while executing 'ticket.changeLog()'">
>
> During handling of the above exception, another exception occurred:
>
>
> Traceback (most recent call last):
>   File "/usr/local/bin/git-trac", line 17, in 
> cmdline.launch()
>   File "/home/charpent/Dev/git-trac-command/git_trac/cmdline.py", line 
> 239, in launch
> app.checkout(args.ticket_or_branch, args.branch_name)
>   File "/home/charpent/Dev/git-trac-command/git_trac/app.py", line 118, in 
> checkout
> self._checkout_ticket(int(ticket_or_branch), branch_name)
>   File "/home/charpent/Dev/git-trac-command/git_trac/app.py", line 125, in 
> _checkout_ticket
> ticket = self.trac.load(ticket_number)
>   File "/home/charpent/Dev/git-trac-command/git_trac/trac_server.py", line 
> 133, in load
> ticket = TracTicket(ticket_number, self.anonymous_proxy)
>   File "/home/charpent/Dev/git-trac-command/git_trac/trac_ticket.py", line 
> 155, in TracTicket
> change_log = server_proxy.ticket.changeLog(ticket_number)
>   File "/usr/lib/python3.10/xmlrpc/client.py", line 1122, in __call__
> return self.__send(self.__name, args)
>   File "/usr/lib/python3.10/xmlrpc/client.py", line 1464, in __request
> response = self.__transport.request(
>   File "/usr/lib/python3.10/xmlrpc/client.py", line 1166, in request
> return self.single_request(host, handler, request_body, verbose)
>   File "/home/charpent/Dev/git-trac-command/git_trac/digest_transport.py", 
> line 108, in single_request
> raise TracInternalError(e)
> git_trac.trac_error.TracInternalError:  gitolite-admin repository: Host key verification failed.\nfatal: Could not 
> read from remote repository.\n\nPlease make sure you have the correct 
> access rights\nand the repository exists.\n; you may have to manually clean 
> up or re-clone the repository' while executing 'ticket.changeLog()'">
>
> Of note : I could create a new ticket (the one I was trying to fetch) 
> yesterday afternoon. This might be a problem distinct from the one due to 
> the key change (this week-end, IIUIC).
> Le mercredi 31 août 2022 à 09:04:43 UTC+2, Emmanuel Charpentier a écrit :
>
>> The Web site is still unreachable.
>>
>> Le mercredi 31 août 2022 à 09:02:53 UTC+2, Emmanuel Charpentier a écrit :
>>
>>> Ditto from Git via SSH :
>>>
>>> ```charpent@zen-book-flip:/usr/local/sage-9$ git fetch
>>> @@@
>>> @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
>>> @@@
>>> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
>>> Someone could be eavesdropping on you right now (man-in-the-middle 
>>> attack)!
>>> It is also possible that a host key has just been changed.
>>> The fingerprint for the ECDSA key sent by the remote host is
>>> SHA256:29lzUeszegCYCnVMOJ+Ts/IlCwojLuf03NnVoLlONEs.
>>> Please contact your system administrator.
>>> Add correct host key in /home/charpent/.ssh/known_hosts to get rid of 
>>> this message.
>>> Offending ECDSA key in /home/charpent/.ssh/known_hosts:14
>>>   remove with:
>>>   ssh-keygen -f "/home/charpent/.ssh/known_hosts" -R "trac.sagemath.org"
>>> Host key for trac.sagemath.org has changed and you have requested 
>>> strict checking.
>>> Host key verification failed.
>>> fatal: Impossible de lire le dépôt distant.
>>>
>>> Veuillez vérifier que vous avez les droits d'accès
>>> et que le dépôt existe.
>>> ```
>>>
>>> Removing the old SSH key cleared git access.
>>>
>>>
>>> Le mercredi 31 août 2022 à 08:45:29 UTC+2, Emmanuel Charpentier a écrit :
>>>
 This morning (Aug 31, 2022, 8:43), any attempt to reach `
 trac.sagemath.org` ends up displayong a Python trace :

 ```
 Traceback (most recent call last): File 
 "/usr/local/lib/python2.7/dist-packages/trac/web/api.py", line 602, in 
 send_error data, 'text/html') File 
 "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 1104, in 
 render_template template = self.load_template(filename, method=method) 
 F

Re: [sage-devel] trac.sagemath.org unreachable

[Kwankyu Lee]

On Wednesday, August 31, 2022 at 6:41:19 PM UTC+9 Frédéric Chapoton wrote:

> just be patient and spend your day doing something else, please


It is a day to think about how precious our trac is. Just be careful when 
you touch its soft database.  

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cba0380e-c379-4b96-adce-43ea88754dccn%40googlegroups.com.

Re: [sage-devel] trac.sagemath.org unreachable

[Kwankyu Lee]

Trac is back. 

Anything lost?

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/966c2ada-da30-4ef9-84f6-64b9e47f6285n%40googlegroups.com.

Re: [sage-devel] trac.sagemath.org unreachable

[Kwankyu Lee]

On Wednesday, August 31, 2022 at 10:56:56 PM UTC+9 dim...@gmail.com wrote

> Trac is a timesink. 
> Time spent on looking for fixes for it is time lost, that's for sure.


The trac project seems not well maintained, according to its website. 

We may need to plan migration while trac is still breathing...

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e135af15-faf7-4df4-9883-b6784734207bn%40googlegroups.com.

Re: [sage-devel] trac.sagemath.org unreachable

[Kwankyu Lee]

On Wednesday, August 31, 2022 at 11:14:34 PM UTC+9 Kwankyu Lee wrote:

>
> We may need to plan migration while trac is still breathing...
>

https://www.redmine.org/

seems a successor of trac. 

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/735c0e6e-a8ff-43b3-91b1-0e4320fb639en%40googlegroups.com.

Re: [sage-devel] trac.sagemath.org unreachable

[Kwankyu Lee]

On Thursday, September 1, 2022 at 1:00:23 AM UTC+9 j...@aims.ac.za wrote:

> Or into gitlab, which we can host ourselves,
>
>  https://github.com/tracboat/tracboat
>
> (I have no experience with tracboat)
>

Whether we upgrade trac or migrate to other platform, the process should be 
gradual so  that we run an experimental new server along with the present 
trac server, sharing the (copied) database, for some (or long) time.

If we upgrade trac, the process could be 1.1 -> 1.2 -> 1.3 -> 1.4.
 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8b749ece-9163-47c3-ace4-c9cac58e91dfn%40googlegroups.com.

[sage-devel] Re: Trac no longer seems to push to sagetrac-mirror

[Kwankyu Lee]

>
> Trac is currently running in *survival mode*. 


Is the database safe? Was it backed up? Or can it be cloned to other 
machine? 



 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/23bf54af-6ada-46b9-b057-ba66dbf14a50n%40googlegroups.com.

[sage-devel] Re: BROADCAST MESSAGE

[Kwankyu Lee]

Trac is now in version 1.2. Thanks!

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5c4a24a1-1e40-4ab4-af6f-237c1a2893a2n%40googlegroups.com.

Re: [sagemath-admins] Fwd: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Kwankyu Lee]

> the futre of the trac software itself.
>

According to their developer mailing list

https://groups.google.com/g/trac-dev

the future of trac seems not so ominous to me.

Perhaps publishing our fork of trac with customized plugins (?) to sagemath 
github repo may help increase  the bus factor about our own trac

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c5050c0a-3bcb-4f01-af40-ff3e7a8cb393n%40googlegroups.com.

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Kwankyu Lee]

On Saturday, September 10, 2022 at 6:26:29 PM UTC+9 dim...@gmail.com wrote:
> Moving away from trac is basically a necessity now, as our devops are 
breaking down for some time, and it only gets worse.

I wish that our trac survives the present crisis so that some people can 
have enough time to plan an organized move to github. After that, we may 
make an informed decision.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/362c9bcc-3a47-455e-adaa-a3002d2c36c7n%40googlegroups.com.

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Kwankyu Lee]

According to 

https://trac.sagemath.org/ticket/30406#comment:15

trac continues to be running after migration to keep links to trac alive.

Then do we really need to migrate (copy) tickets to github once and for 
all? I guess that the migrated tickets would be full of broken links 
internal or external. No?

Instead of having broken copies, why don't we keep the old tickets in trac, 
and start only new tickets fresh in github. The release manager would just 
declare to accept only PRs from github and reject branches of tickets from 
trac. Then people would just start to make new tickets in github mirroring 
tickets in trac. Gradually  github will replace trac in all development 
activities, without broken links. No? 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e3c966c0-c65a-4b91-8133-a5e66340a26bn%40googlegroups.com.

Re: [sage-devel] Re: On changing Bernoulli(1) to +½

[Kwankyu Lee]

On Friday, September 16, 2022 at 10:46:09 AM UTC+9 wst...@gmail.com wrote:

> I just happened to stumble again on the original scrap of paper just 
> now where I made up the name 
> Sage back in 2004. 
>
 
A good photo of it deserves to be permanently placed in the history section 
of the sagemath website.  But I could not find the history section.

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/155dc41c-6d30-4792-923f-2ff85d831de7n%40googlegroups.com.

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Kwankyu Lee]

On Friday, September 16, 2022 at 6:30:05 PM UTC+9 dim...@gmail.com wrote:

I'd rather focus the vote primarily on the move away from trac, ...


What would the move mean precisely? As there are two things to be done

(1) The release manager declares to merge tickets only from Github, not 
from Trac.
(2) Trac goes to read-only mode. 

the move can mean

(a) First (1) and then after some time (2) 

or 

(b) (1) and (2) at the same time.

I think it should be (a) as we want to clean up trac (and final good-bye).





-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0bc0cdc4-c6c8-4e10-bd50-a9bde519c36en%40googlegroups.com.

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Kwankyu Lee]

On Sunday, September 18, 2022 at 9:55:10 AM UTC+9 Matthias Koeppe wrote:

> The conversion of the Trac tickets to GitHub Issues/PRs only works in one 
> shot. Incrementally syncing updates from Trac to existing issues is not 
> possible.
> This means that we cannot continue to operate Trac after the switch.
>

That means (1) and (2) at the same time.

I understand that the conversion is one shot process. But that does not 
technically force trac to be read-only. I suspect that there may be still 
some occasions to leave comments or something on trac after the migration. 
Perhaps just my imaginary concern...

Okay. Thanks. 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3580f98e-b869-49cd-a03a-5131cc786a70n%40googlegroups.com.

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Kwankyu Lee]

On Tuesday, September 20, 2022 at 8:09:33 PM UTC+9 dim...@gmail.com wrote:

>
> (by the way, by looking at this list I found that johanrosenkilde 
> works for GitHub now :-))


Surprise! Johan did much work in coding theory in academy and in sage.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5b2fd2c6-1717-4a16-90b0-81ff651db68fn%40googlegroups.com.

Re: [sage-devel] VOTE: move Sage development to Github

[Kwankyu Lee]

+1 for Github

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8c436b61-f132-431d-8f8a-1c1ef2895585n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

[Kwankyu Lee]

> personally I still prefer Trac, but the bus factor argument and 
recruitment of new contributors are more important

+1

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/05430cfc-e2df-4112-bf24-f7910ec00c8en%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

[Kwankyu Lee]

On Monday, September 26, 2022 at 12:21:41 PM UTC+9 John H Palmieri wrote:

> Is there a vision for what Sage 10.0 means?


Sage X :) 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/aa5f330a-60cd-4657-92af-0ee438fc98e9n%40googlegroups.com.

Re: [sage-devel] DISCUSS: move Sage development to Github

[Kwankyu Lee]

On Monday, September 26, 2022 at 3:17:03 PM UTC+9 Kwankyu Lee wrote:

> On Monday, September 26, 2022 at 12:21:41 PM UTC+9 John H Palmieri wrote:
>
>> Is there a vision for what Sage 10.0 means?
>
>
 Yes. See the headline of 

https://trac.sagemath.org/ticket/29705

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/241796ef-94a6-4bdd-b4a7-500460e9496dn%40googlegroups.com.

Re: [sage-devel] Re: Democratic issue: rushing decisions

[Kwankyu Lee]

A suggestion for votes for sage development process:

1.  Anyone can call for a vote for a relevant issue for sage development.
2.  A vote must be preceded by a discussion on the issue on sage-devel, 
where the date and the duration of the vote is determined. A vote lasts at 
least a week. 
3.  If a dispute about the date or the duration of the vote arises, we have 
another vote for the date or the duration among the suggested candidates. 
This vote for vote is called for only once, immediately, and lasts for a 
week.

An exemplary format of a vote is 
https://groups.google.com/g/sage-devel/c/7h5JoRgHpxY

Will we have a vote for this? :) Other suggestion? 


  

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/08d11497-7595-4f11-be10-41640781abfan%40googlegroups.com.

Re: [sage-devel] Re: Democratic issue: rushing decisions

[Kwankyu Lee]

On Friday, October 7, 2022 at 7:05:38 AM UTC+9 John H Palmieri wrote:

> Dima, presumably you're not talking about me, although I proposed that "we 
> start a vote around October 1".
>
 
I guess he means: https://trac.sagemath.org/ticket/33725#comment:26

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/be5e2daa-6e2d-4437-bc3a-a8bf38f5a5c6n%40googlegroups.com.

[sage-devel] Please change https://doc.sagemath.org/index.html

[Kwankyu Lee]

to $SAGE_ROOT/local/share/doc/sage/index.html

which looks tidy. Harald?

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9d190303-71b9-4a9c-ae89-e132c466826dn%40googlegroups.com.

[sage-devel] Re: Help wanted: Merge all contributor information into contributors.xml

[Kwankyu Lee]

On Tuesday, October 11, 2022 at 2:57:52 AM UTC+9 Matthias Koeppe wrote:

> 3. Merge info from 
> ​https://trac.sagemath.org/#AccountNamesMappedtoRealNames 
>  into 
> ​https://github.com/sagemath/website/blob/master/conf/contributors.xml 
> ; 
> note that Trac 1.2 displays real names anyway (for users with legacy 
> accounts, not "gh-" accounts). 
> This is partially scriptable. Note that this list contains at least some 
> accounts of users who have not interacted on any tickets; those should 
> probably not be added to the contributors list.
>

I may do this work (if no one has not volunteered yet).

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/66298d15-a301-4134-854c-9308a3c16094n%40googlegroups.com.

[sage-devel] Re: Help wanted: Merge all contributor information into contributors.xml

[Kwankyu Lee]

I made PR

https://github.com/sagemath/website/pull/311

On Tuesday, October 11, 2022 at 8:42:07 AM UTC+9 Kwankyu Lee wrote:

> On Tuesday, October 11, 2022 at 2:57:52 AM UTC+9 Matthias Koeppe wrote:
>
>> 3. Merge info from 
>> ​https://trac.sagemath.org/#AccountNamesMappedtoRealNames 
>> <https://trac.sagemath.org/#AccountNamesMappedtoRealNames> into 
>> ​https://github.com/sagemath/website/blob/master/conf/contributors.xml 
>> <https://github.com/sagemath/website/blob/master/conf/contributors.xml>; 
>> note that Trac 1.2 displays real names anyway (for users with legacy 
>> accounts, not "gh-" accounts). 
>> This is partially scriptable. Note that this list contains at least some 
>> accounts of users who have not interacted on any tickets; those should 
>> probably not be added to the contributors list.
>>
>
> I may do this work (if no one has not volunteered yet).
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/509c853b-adda-4366-b4a7-5055a2fc96c4n%40googlegroups.com.

[sage-devel] The documentation built for #34730 needs your attention for checking

[Kwankyu Lee]

Hi,

Trac #34730 rebases sage_autodoc onto the upgraded Sphinx 5.3.0. It is 
responsible for formatting Sage objects (functions, classes, etc.) to build 
documentation.

Please check your favorite sections in our documentation 

https://aa74d4badcbe6841833ff983ad5f756c5ac78752--sagemath-tobias.netlify.app/

for any regression due to #34730. 

Thank you in advance.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2b1f2d75-5711-49f0-a414-3e8d12c4265en%40googlegroups.com.

[sage-devel] Re: The documentation built for #34730 needs your attention for checking

[Kwankyu Lee]

By the way, please also review

https://trac.sagemath.org/ticket/34710

 to fix the cluttered TOCs.

On Wednesday, November 9, 2022 at 2:22:43 PM UTC+9 Kwankyu Lee wrote:

> Hi,
>
> Trac #34730 rebases sage_autodoc onto the upgraded Sphinx 5.3.0. It is 
> responsible for formatting Sage objects (functions, classes, etc.) to build 
> documentation.
>
> Please check your favorite sections in our documentation 
>
>
> https://aa74d4badcbe6841833ff983ad5f756c5ac78752--sagemath-tobias.netlify.app/
>
> for any regression due to #34730. 
>
> Thank you in advance.
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d70a4323-844e-4039-b089-db24f088341en%40googlegroups.com.

[sage-devel] Re: The documentation built for #34730 needs your attention for checking

[Kwankyu Lee]

Here is the link to the ticket #34730

https://trac.sagemath.org/ticket/34730

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b3d06326-d02d-45e7-9dad-490d135690d0n%40googlegroups.com.

[sage-devel] Re: The documentation built for #34730 needs your attention for checking

[Kwankyu Lee]

On Thursday, November 10, 2022 at 12:27:55 PM UTC+9 John H Palmieri wrote:

> I think the use of Tachyon instead of Jmol must be particular to that 
> setup. When I build the docs with #34730, it looks the same as in the 
> develop branch, same as on sagemath.org.


Right. It's the same here

https://f38dc83cf09c8c1a4e784b97233f1d1a9d635fb0--sagemath-tobias.netlify.app/reference/plot3d/sage/plot/plot3d/shapes2.html#sage.plot.plot3d.shapes2.text3d
 

for a ticket not related with #34730.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/efdedd80-7d05-4ec6-aea5-bef9ddf71399n%40googlegroups.com.

[sage-devel] Re: Method 'latex.mathjax_avoid_list()' missing in the official docker image

[Kwankyu Lee]

On Tuesday, November 15, 2022 at 8:28:38 PM UTC+9 lucca@gmail.com wrote:

> When using the official docker image, from within a Notebook the
> methods 
>
>- `latex.add_to_mathjax_avoid_list()` 
>- `latex.mathjax_avoid_list`
>
> are missing on the `latex` object.
>

These commands are for old sage notebook interface. They were removed.
 

> These should exist, according to the docs: 
> https://doc.sagemath.org/html/en/tutorial/latex.html#customizing-latex-processing
>
> This prevents using renderers other than MathJax to render more 
> complicated LaTeX output, such ones that involve TikZ pictures.
>
> If the method was changed or support for custom latex processing was 
> removed, I'd urge to update the docs. There is no mention of additional 
> package imports or configuration being needed to use these methods.
>

https://trac.sagemath.org/ticket/34751 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4112bcf0-a255-4ac1-939c-58d844f67ed2n%40googlegroups.com.

[sage-devel] Re: Status of the GitHub migration

[Kwankyu Lee]

>
> The migration script accesses the Trac server via XMLRPC and does not need 
> privileged access. The first conversion of our 35000 tickets takes about 8 
> hours. The migration script keeps a disk cache for the Trac data, so later 
> conversions are fast, enabling quick iterations when fine-tuning the 
> conversion script.
>

Hence all developers are recommended to try to run the conversion script 
for their favorite (open and closed) tickets, and check if the conversion 
is done correctly. If you spot a conversion error, please report it to 

https://github.com/sagemath/trac-to-github/issues/18 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bacc61fe-f02e-4e65-85b3-2fbbfeb4ee5dn%40googlegroups.com.

[sage-devel] Attention wanted: GitHub migration

[Kwankyu Lee]

Happy new year! 

February this year, our migration ship to GitHub will skyrocket!

There are lots of issues to discuss about github migration: 
https://github.com/sagemath/trac-to-github/issues

Please come and share your thoughts!

Thank you for attention.


-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c89d8f17-6f26-4b1b-867f-bf62fe5a126cn%40googlegroups.com.

[sage-devel] Attention wanted: component labels for issues in GitHub

[Kwankyu Lee]

Dear Sage developers,

One of the first things we do when we create a new ticket is to choose the 
"Component" for which the ticket is. After we move to GitHub, we instead 
would choose a label of the form "component: ...". Like in Trac, the kind 
of labels will rarely change and you will be forced to choose one of them.  
Hence it is crucial that we have a good set of labels from the start.  More 
so because, unfortunately, we should limit the number of labels as they 
should be listed in a dropdown list along with other labels. 

We are in the process of determining the labels and mapping trac components 
to github labels at

https://github.com/sagemath/trac-to-github/issues/99

Please come and check. Any comments to improve the set of github labels and 
the mapping are welcome.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4ff80c88-a3ad-43ea-aa00-b3ddde8f91ffn%40googlegroups.com.

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

[Kwankyu Lee]

On Wednesday, January 18, 2023 at 4:08:15 AM UTC+9 Matthias Koeppe wrote:
Tobias' initial proposal was to use the single letter "c: " as the prefix 
for components. I thought it would be too cryptic, so I went with the whole 
word "component: ". But I'd be happy to change it if "c: " (or some other 
idea) seems preferable to others.

That was me, perhaps. Now I advocate for no prefix at all. It seems a 
futile attempt to sort labels in the list. It's better to make the labels 
(and their colors) look good and read well.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c96045d9-1f87-4eba-94db-749743dcebb2n%40googlegroups.com.

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

[Kwankyu Lee]

In the issue description, I see "*Issue created by migration 
from https://trac.sagemath.org/ticket/ 
...". * Would we remove this before 
migration? Perhaps we should because the link will be defunct eventually.




-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9b560c7a-3f2f-4447-b2f5-ff580bb8ff09n%40googlegroups.com.

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

[Kwankyu Lee]

On Thursday, January 19, 2023 at 2:07:36 AM UTC+9 seb@gmail.com wrote:
Since we can't be sure that all tickets have been converted correctly, I 
prefer to keep the link clickable for as long as possible! Furthermore, I 
think we should not erase the traces of the migration.

As long as trac is running, we can find the ticket by the issue number, 
which is the same with the ticket number.

After migration, we will care less with the welfare of trac. I think the 
links will always be at the risk of getting defunct.
 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d6b9a580-5617-4d49-bd11-c0996b65014an%40googlegroups.com.

Re: [sage-devel] Re: Final call for GitHub user names

[Kwankyu Lee]

On Thursday, January 19, 2023 at 5:40:34 PM UTC+9 john.c...@gmail.com wrote:
What should the policy be about those?  If someone made a trac account 
without registering their full name, I am not sure that it is right for a 
3rd party to later supply that real name.

For a username with *known on Trac: True, *inform us of his/her GitHub name 
if you know, regardless of activity in Sage development. It is up to the 
owner himself/herself to provide the real full name. 

For a username with *known on Trac: False,* inform us of his/her Trac 
username and GitHub name if you know, regardless of activity in Sage 
development. It is up to the owner himself/herself to provide the real full 
name. 

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4136180e-7310-4d57-9b5b-3285fcf95076n%40googlegroups.com.

Re: [sage-devel] Final call for GitHub user names

[Kwankyu Lee]

Thanks, Emmanuel and Justin.

This https://github.com/sagemath/trac-to-github/pull/145/files takes care 
of you.



-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ec2c2a7e-6b41-482b-8d74-5237703d02f8n%40googlegroups.com.

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

[Kwankyu Lee]

There are duplicates of the same comments. See many comments below from

https://34.105.185.241/sagemath/sage-all-2023-01-14-012/issues/34909#issuecomment-4477657

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/04c76fc7-357b-4438-807c-33608df31c8cn%40googlegroups.com.

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

[Kwankyu Lee]

I am not sure if the "/ 1", "/ 2", "/ 3", "/ 4", "/ 5" postfixes are really 
helpful. Note that

(1) As Matthias noticed, the priority labels are sorted in the correct 
order without those prefixes. 
(2) The label text and the label color already indicate the priority.
(3) The numeral postfix is somewhat confusing since "5" may be interpreted 
as the highest priority and "1" lowest.

Matthias pointed out that we can choose the priority label by one key 
stroke (for example, you can type "1" to get "p: blocker / 1"). But why we 
insist to have the convenience that is absent for all other labels? 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5e924913-827a-41c1-934b-7652679e3c92n%40googlegroups.com.

Re: [sage-devel] Final call for GitHub user names

[Kwankyu Lee]

The PR

https://github.com/sagemath/trac-to-github/pull/166

takes care of you, for the migration. Later you also need to update your 
contributor info in the sage website.

On Monday, January 30, 2023 at 10:04:26 PM UTC+9 antoine@gmail.com 
wrote:

> Hi,
>
> I add opened Github Pull Request #357 (
> https://github.com/sagemath/website/pull/357) to add my contributor info. 
> However, my Github account `antoine-leudiere` was deleted because Github 
> terms prevent from having two accounts (typically a personal account and a 
> professional account like I entended to). Therefore, I need replace Github 
> username `antoine-leudiere` with `Kryzar`. Could you help me with that (or 
> tell me if I can just do a new pull request or comment #357)?
>
> Apologies for the extra work.
> Best,
> Antoine Leudière
>
> Le vendredi 20 janvier 2023 à 06:49:15 UTC+1, Kwankyu Lee a écrit :
>
>> Thanks, Emmanuel and Justin.
>>
>> This https://github.com/sagemath/trac-to-github/pull/145/files takes 
>> care of you.
>>
>>
>>
>>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/73c4cf08-10c6-423e-a348-ca6fa10917b9n%40googlegroups.com.

Re: URGENT: Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

[Kwankyu Lee]

For me, Trac is down,

OSError: [Errno 13] Permission denied: 
'/srv/trac/sage_trac/gitolite-admin/conf/gitolite.conf'

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b02155c6-99d6-4c11-83ad-ea53bd2fd26an%40googlegroups.com.

Re: URGENT: Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

[Kwankyu Lee]

On Tuesday, January 31, 2023 at 5:15:24 AM UTC+9 dim...@gmail.com wrote:
that's cause I have to run "trac-admin" - and it breaks www access.

I'll restore it after I am done.

It's restored. Happily I cannot login to trac.
 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/926bbfc9-fa33-4e30-a14c-e53e950146d0n%40googlegroups.com.

Re: URGENT: Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

[Kwankyu Lee]

On Tuesday, January 31, 2023 at 5:41:39 AM UTC+9 dim...@gmail.com wrote:

Did you log out? Or you were basically kicked out?

I didn't log out.  

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e92978b7-54f7-4a18-ad89-30c64ce306d3n%40googlegroups.com.

[sage-devel] Announcement: the migration ship to the GitHub planet launched

[Kwankyu Lee]

Be fastened!

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7e2a54da-7d1a-4964-9069-faf0db3c709en%40googlegroups.com.

[sage-devel] Re: MIgration to GitHub: Heads-up on org invitations

[Kwankyu Lee]

Does the invitation come by email? I didn't receive it yet.

On Thursday, February 2, 2023 at 4:52:10 AM UTC+9 Matthias Koeppe wrote:

> I am sending out invitations to all Sage contributors with known GitHub 
> accounts to join the sagemath organization (unless they are already a 
> Member).
>
> If you accept the invitation, your contributions to Sage (tickets, 
> comments, ...) will be connected to your GitHub account.
>
> Otherwise, we have to create a placeholder account ("mannequin") for your 
> contribution. Our GitHub migration team contact has assured us that it will 
> be possible to link mannequins to real accounts later; but it is an extra 
> step, so it pays off to respond quickly to the invitation.
>
>
>
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1bd928cd-ac0e-44c7-b954-861b918e4ab2n%40googlegroups.com.

[sage-devel] Re: MIgration to GitHub: Heads-up on org invitations

[Kwankyu Lee]

On Thursday, February 2, 2023 at 8:10:01 AM UTC+9 Matthias Koeppe wrote:
It may take a little bit longer because we've hit the rate limit for org 
invitation.

Not yet. 

For those who didn't see this message on sage-devel, how about touching 

https://trac.sagemath.org/ticket/34664

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ad597b91-1759-4f1e-9d05-63dcd28f8b94n%40googlegroups.com.

[sage-devel] Re: MIgration to GitHub: Heads-up on org invitations

[Kwankyu Lee]

I received the invitation an hour ago. It worked great!

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/43a37b9d-1d90-4db7-a94d-83931c7a0bd2n%40googlegroups.com.

[sage-devel] Re: MIgration to GitHub: Heads-up on org invitations

[Kwankyu Lee]

On Thursday, February 2, 2023 at 7:54:41 PM UTC+9 Matthias Koeppe wrote:
333 members and counting!

Homecoming day :-) 

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/555fe68c-f707-4d13-875e-25a8d4ed0af7n%40googlegroups.com.

[sage-devel] Announcement: we are approaching to the GitHub planet

[Kwankyu Lee]

It should be visible, soon!

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ef4c620c-7d62-440c-9548-0779a19edf66n%40googlegroups.com.

Re: [sage-devel] Re: Announcement: we are approaching to the GitHub planet

[Kwankyu Lee]

Perhaps only visible to the owners?

On Friday, February 3, 2023 at 12:18:50 PM UTC+9 François Bissey wrote:

> It 404 for me. I am guessing it is not public yet.
>
> On 3/02/23 16:05, Matthias Koeppe wrote:
> > Only 10% of the final approach (import) are done, but the impatient can 
> > already take a look at https://github.com/sagemath/sage/issues: The 
> > attribution of imported issues to GitHub users and the creation of 
> > mannequins seem to work as we hoped!
> > 
> > On Thursday, February 2, 2023 at 4:56:37 PM UTC-8 Kwankyu Lee wrote:
> > 
> > It should be visible, soon!
> > 
> > -- 
> > 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 
> > an email to sage-devel+...@googlegroups.com 
> > <mailto:sage-devel+...@googlegroups.com>.
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/sage-devel/ad5143d8-df3c-40c6-a90b-2a0dd66ecbbfn%40googlegroups.com
>  
> <
> https://groups.google.com/d/msgid/sage-devel/ad5143d8-df3c-40c6-a90b-2a0dd66ecbbfn%40googlegroups.com?utm_medium=email&utm_source=footer
> >.
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/916ffeb6-2fdf-42d8-9296-6b2faf9af677n%40googlegroups.com.

[sage-devel] Re: wiki access

[Kwankyu Lee]

Perhaps you may borrow Matthias or Dima's login credentials for temporary 
trac logging-in for the event.

On Friday, February 3, 2023 at 6:36:48 PM UTC+9 vdelecroix wrote:
Dear all, 

It seems that it is not possible anymore to log in for editing the 
SageMath wiki at https://wiki.sagemath.org/. This is the tool we were 
planning to use for sage days 117 starting on Monday. Does anyone know 
what happened? 

Best 
Vincent 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4f46288b-5ae8-44bd-a6cb-cd661408b4ccn%40googlegroups.com.

[sage-devel] Re: Colours

[Kwankyu Lee]

On Friday, February 3, 2023 at 7:53:26 PM UTC+9 john.c...@gmail.com wrote:
A few people who post to this list have their email configured so that 
quoted text is in a different colour, instead of having quoted text 
prefixed by > or similar.

Right. It happens to me. I don't know how I can control this. 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0e967e3f-3cfd-4ca1-b1a9-c532fd512068n%40googlegroups.com.

[sage-devel] Re: Colours

[Kwankyu Lee]

Again. Sorry.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/444c48f1-52ac-4d55-bcc9-7e391134a2b6n%40googlegroups.com.

[sage-devel] Re: Migrated repo ready for review on GitHub.com

[Kwankyu Lee]

Thank you!

On Saturday, February 4, 2023 at 7:38:10 PM UTC+9 Matthias Koeppe wrote:

> The first preview is now available at https://github.com/sagemath/sage
> (it is "archived", i.e., read-only).
>
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6cfbb235-24ff-4e1e-81c5-99cd8df4abf0n%40googlegroups.com.

[sage-devel] Re: Migrated repo ready for review on GitHub.com

[Kwankyu Lee]

An issue with many comments folds the comments in middle. For example,

https://github.com/sagemath/sage/issues/34340

It's inconvenient to unfold it again and again. Is there a configuration 
that leave them unfolded by default?

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/75945dad-24c6-4116-9b84-6e62e3bcc1dbn%40googlegroups.com.

Re: [sage-devel] Migrated repo ready for review on GitHub.com

[Kwankyu Lee]

It seems it's still being updated.

On Saturday, February 4, 2023 at 8:44:49 PM UTC+9 dim...@gmail.com wrote:

> 1) there is something funny with search - it it because it's still not 
> done?
>
>
> https://github.com/sagemath/sage/issues?q=is%3Aissue+strongly+regular+is%3Aopen
>
> gives
>
> 5 Open 71 Closed
>
> No results matched your search.
>
> 
> so there are 5 open issues, but they are not shown. (searching for
> closed ones seems to work)
>
> 
>
> 2) GitHub nathanncohen is a real GitHub account, not a mannequin - and
> it corresponds to Trac's ncohen just fine.
>
>
>
>
> On Sat, Feb 4, 2023 at 10:38 AM Matthias Koeppe
>  wrote:
> >
> > The first preview is now available at https://github.com/sagemath/sage
> > (it is "archived", i.e., read-only).
> >
> > --
> > 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 
> an email to sage-devel+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/841273d5-4bca-40a5-afbf-6c4fccde8b4dn%40googlegroups.com
> .
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9d7fc037-799e-4ae5-9d90-36c82f8b01f5n%40googlegroups.com.

Re: [sage-devel] Migrated repo ready for review on GitHub.com

[Kwankyu Lee]

2) GitHub nathanncohen is a real GitHub account, not a mannequin - and 
it corresponds to Trac's ncohen just fine.

Perhaps he didn't respond to the recent invitation. 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a9ae0a4f-a9a7-45d1-9087-5081ad6527d2n%40googlegroups.com.

[sage-devel] Re: Migration to GitHub complete

[Kwankyu Lee]

Great! Thank you!

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a765b34c-f9e1-4a0b-af20-85b3a8c273d3n%40googlegroups.com.

[sage-devel] Re: https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8

[Kwankyu Lee]

It is now in 

https://github.com/sagemath/sage/wiki/ReleaseTours-sage-9.8

But we don't have permissions to edit it yet.

On Monday, February 6, 2023 at 5:38:46 PM UTC+9 Eric Gourgoulhon wrote:

> Hi, 
>
> Since trac logins are now disabled, it seems that we cannot edit the 9.8 
> release tour.
>
> Eric.
>
> Le samedi 7 janvier 2023 à 09:02:07 UTC+1, Matthias Koeppe a écrit :
>
>> It's time to work on the release tour for the upcoming 9.8 release 
>> https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8
>>
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/03eececf-46eb-4a34-8919-b731caf05f21n%40googlegroups.com.

[sage-devel] Re: pull requests for migrated issues

[Kwankyu Lee]

On Monday, February 6, 2023 at 5:47:22 PM UTC+9 Lorenz Panny wrote:
Sorry if this is answered somewhere in the new documentation, I couldn't 
find it: What is the intended procedure for migrated issues which were in 
"needs review" state and already had a branch? Am I to push the branch to 
my own fork and create a fresh pull request for each such issue?

Yes, according to the guide: 

https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md#for-contributing-a-change-that-addresses-an-existing-open-issue-that-has-been-migrated-from-trac

 But the procedure is not smooth yet. I could not add labels to 

https://github.com/sagemath/sage/pull/34960

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d9b49d18-7a3b-41e1-b137-4ecfba429e35n%40googlegroups.com.

[sage-devel] Re: Migration to GitHub complete

[Kwankyu Lee]

On Monday, February 6, 2023 at 11:45:12 PM UTC+9 emanuel.c...@gmail.com 
wrote:
After followong the steps given for an existing tree, my develop branch 
still followed OLD-ORIGIN. Shouldn't that be orign ?

You remove the develop branch, and make a new one (named develop) from the 
remote origin. 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2c6b7b82-6cee-485e-ad91-a323aa37174en%40googlegroups.com.

[sage-devel] Re: Migration to GitHub complete

[Kwankyu Lee]

No. Make it from the remote upstream, so I think the command is 

git branch -D develop; g checkout -b develop upstream/develop 

On Monday, February 6, 2023 at 11:51:43 PM UTC+9 Kwankyu Lee wrote:
On Monday, February 6, 2023 at 11:45:12 PM UTC+9 emanuel.c...@gmail.com 
wrote:
After followong the steps given for an existing tree, my develop branch 
still followed OLD-ORIGIN. Shouldn't that be orign ?

You remove the develop branch, and make a new one (named develop) from the 
remote origin. 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4cdbe8a0-c20b-49a4-9b48-e9b5bfd48af8n%40googlegroups.com.

[sage-devel] Re: Migration to GitHub complete

[Kwankyu Lee]

Or 

git branch -D develop; git branch --track develop upstream/develop 

On Tuesday, February 7, 2023 at 12:03:39 AM UTC+9 Kwankyu Lee wrote:
No. Make it from the remote upstream, so I think the command is 

git branch -D develop; g checkout -b develop upstream/develop 

On Monday, February 6, 2023 at 11:51:43 PM UTC+9 Kwankyu Lee wrote:
On Monday, February 6, 2023 at 11:45:12 PM UTC+9 emanuel.c...@gmail.com 
wrote:
After followong the steps given for an existing tree, my develop branch 
still followed OLD-ORIGIN. Shouldn't that be orign ?

You remove the develop branch, and make a new one (named develop) from the 
remote origin. 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/28540f6d-7a66-46ee-9db9-0df2c6ea3da2n%40googlegroups.com.

[sage-devel] New wiki at sagemath/sage hosted by GitHub

[Kwankyu Lee]

For those who haven't heard the news,

We also migrated the wiki pages from Trac to GitHub. 

The new wiki needs your care and love!

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/51626848-8df0-4a88-8ee5-a8453bf479dfn%40googlegroups.com.

[sage-devel] Re: New wiki at sagemath/sage hosted by GitHub

[Kwankyu Lee]

The url is

https://github.com/sagemath/sage/wiki

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b41e4d56-e77f-4ebe-b469-4d1d3355e23bn%40googlegroups.com.

Re: [sage-devel] Re: New wiki at sagemath/sage hosted by GitHub

[Kwankyu Lee]

On Thursday, February 9, 2023 at 10:10:54 AM UTC+9 David Roe wrote:
Has any content from https://wiki.sagemath.org/ been moved to the github 
wiki, or is that planned?

No.

As far as I know, it's lingering at the state of 
https://github.com/sagemath/sage/issues/33725

 
David

On Thu, Feb 9, 2023 at 2:08 AM Kwankyu Lee  wrote:
The url is

https://github.com/sagemath/sage/wiki

-- 
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 an 
email to sage-devel+...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b41e4d56-e77f-4ebe-b469-4d1d3355e23bn%40googlegroups.com
 
<https://groups.google.com/d/msgid/sage-devel/b41e4d56-e77f-4ebe-b469-4d1d3355e23bn%40googlegroups.com?utm_medium=email&utm_source=footer>
.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3d2a3f52-f8a9-4324-85f0-d2851573f923n%40googlegroups.com.

[sage-devel] Re: GH Notifications

[Kwankyu Lee]

The "Watch" menu at the upper right corner does what you want?

On Thursday, February 9, 2023 at 3:54:07 PM UTC+9 Travis Scrimshaw wrote:

> I liked getting emails from trac when changes to tickets I cared about 
> happened. However, I only want emails from notifications related to 
> SageMath. I see that there is a routing to chose which account it will go 
> to. Yet, I don't see a way to say "only from Sage I want email 
> notifications".
>
> Is there any way to do this or do I have to set up an email filter?
>
> Travis
>
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f1b69a89-5449-475b-91c8-6002c8b2450dn%40googlegroups.com.

[sage-devel] Re: reviewer role on github

[Kwankyu Lee]

I suggest this procedure:

You open an issue: "promote me to a reviewer". Then if you get enough 
hearts from other reviewers,  an admin promotes you.

On Friday, February 10, 2023 at 7:07:04 PM UTC+9 Martin R wrote:
I was unable to find out how I declare myself as reviewer in the new 
workflow.

This question applies to

* pull requests without issue (I'm not sure yet how they work: given a 
number like #35053, how can I see issue and pull request associated to it?

* issues without pull requests.

Martin

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/05e37c45-cd34-4ed2-8d47-8d41fd570db2n%40googlegroups.com.

[sage-devel] Re: reviewer role on github

[Kwankyu Lee]

On Friday, February 10, 2023 at 7:33:51 PM UTC+9 Martin R wrote:
In which repository?

Here: https://github.com/sagemath/sage/issues 

Does this mean that researchers cannot become reviewers immediately anymore?

You first become a member of sage organization, and then be promoted to 
Triage team (of reviewers).

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a42527ef-61bd-499a-a2dd-2c69cd17f1a7n%40googlegroups.com.

[sage-devel] Issues/PRs search reports on the Wiki

[Kwankyu Lee]

Hi,

You may use

https://github.com/sagemath/sage/wiki

as a portal to interesting issues/prs.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cfbbdfb9-c10a-4ca4-9765-f062caca2ba9n%40googlegroups.com.

[sage-devel] Procedure to be a member of sage github organization

[Kwankyu Lee]

Hi,

We are getting PRs from non-member contributors.

What is the procedure or the condition to be invited for membership?

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9eae5420-6b43-440e-b36d-d30c3b23421bn%40googlegroups.com.

[sage-devel] Re: Sync labels with GitHub states by a bot

[Kwankyu Lee]

Thanks a lot!

On Wednesday, March 15, 2023 at 4:31:22 PM UTC+9 seb@gmail.com wrote:

> Hello everyone,
>
>
> More than a month has passed since we migrated to GitHub. As you explored 
> the new workflows, you may have noticed that there are some redundancies 
> regarding a PR's status. On the one hand there are states supported by 
> GitHub to mark a PR as draft or approved... on the other hand there are 
> labels migrated from Trac that show almost the same thing (s: need 
> review, s : positive_review . ..).
>
> The need to have them in parallel was discussed in issues 8 of the 
> trac-to-github repo  
> (see this comment there 
> ).
>  
> To simplify our manual workflows and keep the redundant labels reliable, I 
> implemented a bot to sync these labels with their corresponding GitHub 
> states. Please take a look at PR #35172 
> .
>
> Best
> Sebastian
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/da5279af-b374-4881-9922-7e25f0b8186bn%40googlegroups.com.

Re: [sage-devel] ChatGPT is an expert in SageMath too

[Kwankyu Lee]

Can this specific example be found in the online documentation?


I also guess that the example is from our documentation. I didn't try to 
spot the source.

did you try asking whether it's geometric genus, or not?


No. We understand what it did. It didn't "think" that there are two kinds 
of genus and did not ask your question back to me :-)

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/40517423-2c5c-4b8e-91e8-54725832c509n%40googlegroups.com.

Re: [sage-devel] ChatGPT is an expert in SageMath too

[Kwankyu Lee]

I can't reproduce the AI script.
First, 'y' is not defined.
Second, sage doesn't like this constructor of Curve ...


Ah, I missed that. So its answer is less than perfect. 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0d655a75-3263-4033-b1df-ba4ef1ba337fn%40googlegroups.com.

Re: [sage-devel] ChatGPT is an expert in SageMath too

[Kwankyu Lee]

which doesn't work because C.degree() isn't implemented.  It would probably 
be a reasonable thing to implement though (e.g., magma has 
https://magma.maths.usyd.edu.au/magma/handbook/text/1411#15877)


This

sage: C.projective_closure().degree()

3

does work.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/7c703fa0-2bea-46cd-8f13-e324a4a0ff30n%40googlegroups.com.

Re: [sage-devel] ChatGPT is an expert in SageMath too

[Kwankyu Lee]

... The syntactical correction Curve(x^3+y^3-x-y+1,P) still doesn't work 
because we have an affine equation and are specifying an unrelated 
projective space.


That is the most serious defect in the answer. I missed that.

I think the conclusion should be that ChatGPT pretends to be a SageMath 
expert with great confidence but .. gasp ... isn't!


and also I was not careful enough to claim 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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f49e1b3e-396b-4483-93d1-1af4d721476bn%40googlegroups.com.

Re: [sage-devel] OT: google's chatbot Bard is at https://bard.google.com/

[Kwankyu Lee]

... the goal is not to be "correct" but just to try to satisfy the human 
users.


A nice insight into what ChatGPT does. AI is human in that respect.
 


-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4bec12c5-a199-4fcf-8bcf-a161372dc816n%40googlegroups.com.

[sage-devel] Re: Sage developer's guide

[Kwankyu Lee]

It seems like that banner could be updated a bit, now that it is April. 
I do realize that there's still a lot being hashed out about the exact 
workflow...


It seems that the workflow is still in flux. Some questions: 

(1) Who can be a reviewer? Anyone, organization member or members of triage 
team?

(2) How one can be an organization member?

(3) How one can be a member of triage team?

(4) Currently, for a PR from an outside contributor(not organization 
member), github workflows need an approval to run. Who are supposed to  
approve this? Anyone with maintainer privilege?

(5) How one can be a maintainer?

(6) What to do with automatic labelling vs manual labelling? 
https://github.com/sagemath/sage/pull/35172

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0de426ca-a98a-4ef4-b35a-82fc521339bcn%40googlegroups.com.

[sage-devel] Re: Sage developer's guide

[Kwankyu Lee]

(6) What to do with automatic labelling vs manual labelling? 
https://github.com/sagemath/sage/pull/35172


If any organization member can be a reviewer, automatic labelling should be 
implemented, since only triage team members can add labels. But I think the 
current manual labelling should not be hindered by the automating script. 

 

 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9eedde50-afca-4224-9728-e07ece238a40n%40googlegroups.com.

[sage-devel] Re: Sage developer's guide

[Kwankyu Lee]

I created a PR 

https://github.com/sagemath/sage/pull/35460

to start. Please help if you want to get things done fast.

On Wednesday, April 5, 2023 at 2:33:44 PM UTC+9 William Stein wrote:

> Hi Sage Developers,
>
> Somebody was asking me about doing Sage development, and I pointed
> them to the sage developer's guide [1]. However, looking at it for a
> moment was worrisome, since it starts with a big scary banner saying:
> "Warning: Sage development is scheduled to move to GitHub in February
> 2023. The exact date will be announced in
> https://groups.google.com/g/sage-devel. After the transition, some
> parts of this guide (especially those related with the Sage Trac
> server) will become obsolete and be updated according to the new
> workflow on GitHub. See our transition guide from Trac to GitHub for
> the preliminary version of the workflow."
>
> It seems like that banne could be updated a bit, now that it is April.
> I do realize that there's still a lot being hashed out about the exact
> workflow...
>
> William
>
> [1] https://doc.sagemath.org/html/en/developer/index.html
>
> -- 
>
> Best Regards,
> William Stein
>
> CEO, SageMath, Inc.
> https://cocalc.com
>

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0db99c75-ad1d-42b7-b6d6-18720a4944c0n%40googlegroups.com.

Re: [sage-devel] web site from cocalc but in our domain

[Kwankyu Lee]

+1. It seems a redirect.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b8e47814-fbd1-48e9-b41b-c79b09e439e2n%40googlegroups.com.

[sage-devel] Re: random_element and randtest_element

[Kwankyu Lee]

>
> What do you think? Does the name randtest_element look ok? 


How about "_random_test_element", as this method needs not to be revealed 
to users, unlike "random_element" and "some_elements".

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] ceil or ceiling?

[Kwankyu Lee]

Hi,

I always thought there are "floor" and "ceiling" functions in math. But in 
Sage,

{{{
sage: ceil(pi)
4
sage: floor(pi)
3
sage: ceiling(pi)
---
NameError Traceback (most recent call last)
 in ()
> 1 ceiling(pi)

NameError: name 'ceiling' is not defined
}}}

I guess, one principle in Sage is to use the full name unless an 
abbreviated form is already firmly rooted in our culture. So I propose to 
change the name ceil to ceiling everywhere and allow ceil as an alternative 
short form.

If you agree, then I will make a ticket.

Cheers.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: ceil or ceiling?

[Kwankyu Lee]

On Friday, June 8, 2018 at 6:23:51 PM UTC+9, Samuel Lelievre wrote:
>
>
>
> Fri 2018-06-08 06:21:45 UTC, Dima Pasechnik:
> >
> > ceil() is a standard Python function.
> > Thus, Sagemath has to live with it.
>
> If we look at object methods rather than functions
> in the global namespace, it is already the case that
> both ceil and ceiling are available, with one of them
> an alias to the other.
>
> Try this for example:
>
> sage: a = 0.1
> sage: a.cei
>
> where  denotes hitting the TAB key.
> You will see that autocompletion suggests a.ceil and a.ceiling.
>

Right.
 

>
> Then if you do
>
> sage: a.ceil?
> sage: a.ceiling?
>
> you will see they have the same documentation.
>

Right.
 

>
> The source code reveals that in this case ceil is
> implemented, and ceiling is an alias to ceil:
>
>
> https://github.com/sagemath/sage/blob/master/src/sage/rings/real_mpfr.pyx#L2866
>
> https://github.com/sagemath/sage/blob/master/src/sage/rings/real_mpfr.pyx#L2897
>
> You could likewise explore other types of numbers in Sage.
>
> Regarding the function in the global namespace,
> we could add ceiling as an alias to ceil.
>

As Dima said, python and other programming languages only have ceil(), as 
apparently they prefer short names. Precisely python only has math.ceil()

What I like to see in Sage is that ceiling() is implemented and ceil() is 
an alias, so that we can live with both.

If no one objects to this switch, I will try to make a patch. 

Thanks.

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] ceil or ceiling?

[Kwankyu Lee]

On Friday, June 8, 2018 at 8:50:48 PM UTC+9, vdelecroix wrote:
>
> On 08/06/2018 08:21, Dima Pasechnik wrote: 
> > ceil() is a standard Python function. 
> > Thus, Sagemath has to live with it. 
>
> Not only Python. It is C standard function 
> from math.h. Also GMP, MPFR, etc does use ceil and 
> not ceiling. 
>

Right. Is this an objection to my proposal?

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] ceil or ceiling?

[Kwankyu Lee]

>
> Yes and no. I would rather keep ceil to be the default and ceiling to 
> be an alias. It is more complient with mathematical libraries, 
> programming languages, etc. 
>

In a sense, I like the philosophy of Mathematica, where Ceiling[x] is 
standard. I thought Sage shares the same philosophy... 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Re: ceil or ceiling?

[Kwankyu Lee]

On Saturday, June 9, 2018 at 2:53:56 AM UTC+9, John H Palmieri wrote:
>
>  
> On Friday, June 8, 2018 at 7:59:39 AM UTC-7, Marc Mezzarobba wrote:
>>
>>
>> Personally, I'd vote for keeping ceil(), and not adding any alias. 
>>
>
> I agree with this. Another philosophy (at which Sage should do a better 
> job) is to not have too much in the global namespace. Because of Python, we 
> have 'ceil()', and I don't see a compelling reason to add 'ceiling()'.
>

Ok, I withdraw my suggestion. I think 'ceil()' is a different case from 
'tan()' or 'log()'. I wonder if you write or read it as "ceil" in your 
class...  Anyway the consensus seems not to do anything.

Thank you for you attention.


Kwankyu

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Matplotlib plotting style 'classic' hardcoded to Sage

[Kwankyu Lee]

Hi,

This ticket

https://trac.sagemath.org/ticket/25799

aims to remove matplotlib style 'classic' hardcoded into Sage. This makes 
customization through the matplotlibrc file work, which fails presently.

After the ticket merged, the default matplotlib styles would be applied to 
all Sage graphics, and Sage graphics may look subtly different than what 
you have been used to. If you don't like this, then raise your voice to the 
ticket. 

-- 
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 an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.