Hi,

Ticket #18417 hardcodes the author's own private server (on which the Sage
community has no control nor gave any mandate) as part of the Sage source
code to serve as a download source when the mirrors are not up-to-date. I
consider it as an issue by itself, and made it explicit on the ticket.

In the same ticket (and perhaps #15642 which is closely related), the
author sets himself the ticket into a positive_review in the name of
emergency that some server is not available at UW anymore (if i understand
correctly).

I am fearing that we are breaking an important rule in the reviewing
process (which is a central point of what makes us a community) in order
to avoid some downtime in the installation of some optional packages.

In my opinion, if there is something that does not lead to a clear
consensus, then it should be discussed until better solution is reached.
Emergency is always dubious as it allows power concentration.
Unfortunately, harm to the community habits are less visible (but possibly
deeper) than downtime.

I can understand that there are currently some hosting issues at UW, so:

- it could be nice to make them transparent for the people that do not
  have access to those servers to get the actual picture and start working
  on a sustainable solution.

- there are quite a few universities worldwide represented on this
  mailing-list, so i am pretty sure that some of them could provide a
  connection to host a fallback download server managed by the Sage
  community (e.g. Niles could find a new home for ask.sagemath.org, i had
  no problem in finding a way to host the sageindex prototype at my new
  university, while i am just arriving).

- infrastructure is a part of Sage development, fixing problems together
  and transparently strenghtens the community.

Ciao,
Thierry

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to