Hi Jonathan
On Mon, Aug 31, 2020 at 06:21:10PM +0200, Jonathan Carter wrote:
> * Have accounts with the major hosting providers so that
> they can also create new instances whenever there's a
> new request from a developer
I opened an issue for the AWS side of that:
On Tue, Sep 01, 2020 at 09:14:30AM +0200, Lucas Nussbaum wrote:
> > That's it in a nutshell for now. Any thoughts... or volunteers?
>
> I think that this proposal combines two quite different aspects, and
> that it might be better to keep them separate.
>
> 1. Maintaining contacts with
On Wed, Sep 02, 2020 at 05:10:18PM +0200, Lucas Nussbaum wrote:
> On 02/09/20 at 13:49 +0200, Jonathan Carter wrote:
> > Hey Lucas
> >
> > On 2020/09/01 16:05, Lucas Nussbaum wrote:
> > > On 01/09/20 at 15:29 +0200, Jonathan Carter wrote:
> > >> On 2020/09/01 09:14, Lucas Nussbaum wrote:
> > >>>
On 02/09/20 at 13:49 +0200, Jonathan Carter wrote:
> Hey Lucas
>
> On 2020/09/01 16:05, Lucas Nussbaum wrote:
> > On 01/09/20 at 15:29 +0200, Jonathan Carter wrote:
> >> On 2020/09/01 09:14, Lucas Nussbaum wrote:
> >>> 2. Keeping our important services sanely maintained. Your proposal is to
> >>>
I've been thinking about your question about alternate names for the
debian.net team.
Everything I come up with would be confusing with regard to DSA--like
the Debian services team.
Perhaps something like Services Facilitators.
Or just go with debian.net team and be clear in the description
Hey Lucas
On 2020/09/01 16:05, Lucas Nussbaum wrote:
> On 01/09/20 at 15:29 +0200, Jonathan Carter wrote:
>> On 2020/09/01 09:14, Lucas Nussbaum wrote:
>>> 2. Keeping our important services sanely maintained. Your proposal is to
>>> sanitize *.debian.net a bit. I wonder if instead, we should have
Hi
On 01/09/20 at 15:29 +0200, Jonathan Carter wrote:
> On 2020/09/01 09:14, Lucas Nussbaum wrote:
> > 2. Keeping our important services sanely maintained. Your proposal is to
> > sanitize *.debian.net a bit. I wonder if instead, we should have a list
> > of requirements for *.debian.org that
On 2020/09/01 09:14, Lucas Nussbaum wrote:
> 2. Keeping our important services sanely maintained. Your proposal is to
> sanitize *.debian.net a bit. I wonder if instead, we should have a list
> of requirements for *.debian.org that does not include "hosted on a
> machine managed by DSA". People
On 2020/09/01 15:18, Sam Hartman wrote:
> I think it would be fine if the same team handled both aspects of the
> proposal, although I'd prefer that the name be different than debian.net
> team if that's the case.
Sure, the name doesn't matter at all that much to me. Any other
su
ike Lucas's idea
about making it easier to get things under debian.org).
I think Jonathan's idea would be better if it did not conflate contacts
for hosting providers so much with debian.net.
I think it would be fine if the same team handled both aspects of the
proposal, although I'd prefer that th
Hi Jonathan
On Mon, Aug 31, 2020 at 06:21:10PM +0200, Jonathan Carter wrote:
> The services ran under the debian.net domain are typically run by
> individual Debian Developers or small teams, and range from a toy
> service to something that's short lived or even a service that's even
> considered
Hi,
On 31/08/20 at 18:21 +0200, Jonathan Carter wrote:
> 2. Create a new team to organise some aspects of everything under
> debian.net, which would include:
>
> * Keeping the domain list on the above mentioned
> DebianNet page maintained on a regular basis
> * Maintain external
Hi Debianites
I'd like to talk about an idea that needs some more thought, but that
has been floating in my head for a while and I think it could benefit
from some further discussion. Ideally we could've had a BoF about it
during DebConf, but my plate was full already.
We have a bunch of
13 matches
Mail list logo
