Re: DIP 1024---Shared Atomics---Accepted
On 1/7/2020 6:31 PM, Manu wrote: It will still do that, either now... or later. So, why wait? Because customers have their own schedules.
Re: DConf 2020: Double Decker Edition
On Saturday, 4 January 2020 at 12:23:40 UTC, Mike Parker wrote: The announcement is on the blog and dconf.org is up to date. Read all about it! https://dlang.org/blog/2020/01/04/dconf-2020-double-decker-edition/ https://dconf.org/2020/index.html Once I submit a proposal for a talk, how long will it take to be reviewed and replied to?
Re: code.dlang.org downtime
On 12/17/19 12:34 PM, H. S. Teoh wrote: This looks like something the D Foundation ought to fund. Buy one of the many VPS's out there to be used as the "official", Foundation-backed dub server, preferably with a hosting provider that has multiple redundant network connections and automatic backup service. Depending on availability of funds, add a hot failover server as backup in case things go wrong with the primary server. This ought to alleviate any concerns about downtime. ... I am sorry to post on an older (but < 30 days!) thread that I've just seen. While it would be very reasonable for the Foundation to be running this infra, Sebastiaan's proposal is quite right -- eliminate the need for a server entirely. I would add one thing to his proposal: The metadata are already stored in github/bitbucket/gitlab/etc. -- in the form of the dubfile. All we need is a K:V lookup mapping package name to canonical git repository. This K:V store could be served perhaps more cheaply , and more reliably, than the current infra which must serve all metadata (presumably). If dub could be retooled to only query for the git repo, it could then clone and work entirely with metadata stored in the repo, minimizing dependence on a hosted server, whether 6 nines reliable or not. If, though, the foundation takes over the current infra and hosting, please put out a call for donations -- I will donate.
Re: code.dlang.org downtime
On Friday, 10 January 2020 at 02:36:51 UTC, James Blachly wrote: I am sorry to post on an older (but < 30 days!) thread that I've just seen. While it would be very reasonable for the Foundation to be running this infra, Sebastiaan's proposal is quite right -- eliminate the need for a server entirely. I would add one thing to his proposal: The metadata are already stored in github/bitbucket/gitlab/etc. -- in the form of the dubfile. All we need is a K:V lookup mapping package name to canonical git repository. This K:V store could be served perhaps more cheaply , and more reliably, than the current infra which must serve all metadata (presumably). If dub could be retooled to only query for the git repo, it could then clone and work entirely with metadata stored in the repo, minimizing dependence on a hosted server, whether 6 nines reliable or not. If, though, the foundation takes over the current infra and hosting, please put out a call for donations -- I will donate. I can't say I like the idea of requiring users to use the aforementioned or similar services and necessitating the use of git over other VCS solutions.
Re: code.dlang.org downtime
On 1/9/20 10:03 PM, suncarpet wrote: I can't say I like the idea of requiring users to use the aforementioned or similar services and necessitating the use of git over other VCS solutions. How is it that dub works today?
Re: code.dlang.org downtime
On Friday, 10 January 2020 at 03:14:29 UTC, James Blachly wrote: On 1/9/20 10:03 PM, suncarpet wrote: I can't say I like the idea of requiring users to use the aforementioned or similar services and necessitating the use of git over other VCS solutions. How is it that dub works today? It works such that I don't post anything to code.dlang.org, lol. (Not that I would because all my stuff is very niche.) If things were to change, I'd like for restrictions on where code is hosted and the VCS to be loosened. I may be looking at this very naively, however.
Re: code.dlang.org downtime
On 10/01/2020 4:37 PM, suncarpet wrote: If things were to change, I'd like for restrictions on where code is hosted and the VCS to be loosened. I may be looking at this very naively, however. You are. It is an implementation detail, not policy. To do it 100% generically dub repository will have to understand each VCS system, check it out and then archive it before shipping it off on request. Instead of just downloading an archive from the provider. You may not know this, but in the past the repository has had problems crashing from doing these updates and then performing downloads (its been resolved, but it really doesn't have the infrastructure to do it properly I think).
Re: code.dlang.org downtime
On Friday, 10 January 2020 at 04:06:28 UTC, rikki cattermole wrote: You are. It is an implementation detail, not policy. To do it 100% generically dub repository will have to understand each VCS system, check it out and then archive it before shipping it off on request. Instead of just downloading an archive from the provider. You may not know this, but in the past the repository has had problems crashing from doing these updates and then performing downloads (its been resolved, but it really doesn't have the infrastructure to do it properly I think). And this is why I dig ditches for a living. Thank you for the (what should've been obvious) explanation.
Re: DConf 2020: Double Decker Edition
On Friday, 10 January 2020 at 01:11:44 UTC, Murilo wrote: On Saturday, 4 January 2020 at 12:23:40 UTC, Mike Parker wrote: The announcement is on the blog and dconf.org is up to date. Read all about it! https://dlang.org/blog/2020/01/04/dconf-2020-double-decker-edition/ https://dconf.org/2020/index.html Once I submit a proposal for a talk, how long will it take to be reviewed and replied to? Soon, I'll update the website with all of the deadline dates. There will be a submission deadline and a deadline for the announcement of selections. Typically, the announcement takes place one week after the submission deadline and the submission authors are notified by email the day before. I anticipate the submission deadline will be some time in March.
