Re: [opennic-discuss] [PROPOSAL] TLD Reliability Policies (Git mirrors)

Jonah Aragon <[email protected]>
Newsgroups gmane.network.opennic.general
Message-ID <CAMcWD6yxdPSxdzUpyxL1_ByA08e3kh=UDODbA6hPZ=fpnKFmWw@mail.gmail.com>
That being said... if community members set up their own publicly
accessible automatic Git mirrors of our entire GitHub organization at
https://github.com/opennic, and send me links, I can throw together a
list and put them on the homepage. I'm planning an entire "community
showcase/projects" section anyways.

Jonah
On Sun, Jul 15, 2018 at 6:58 PM Jonah Aragon <[email protected]> wrote:
>
> I've already discussed this with some people, I even offered to host a
> Git host myself, and nobody is really interested in moving to another
> Git host or creating multiple places for us to manage. GitHub is
> working fine for us, and the nature of Git means that if GitHub ever
> fails we can easily migrate to another host without their help. It's
> really not an issue that we don't have multiple hosts setup
> simultaneously. People are welcome to clone all our repositories and
> store them on their own computers for safekeeping if they so choose.
>
> Also, the zone backups are now online, I just put them up at
> https://github.com/opennic/zone-backup
>
> Jonah
> On Sat, Jul 14, 2018 at 4:06 PM Jacob Bachmeyer <[email protected]> wrote:
> >
> > Jonah Aragon wrote:
> > > The reason I said GitHub specifically in the proposal is because we as
> > > an organization have an official GitHub account
> > > at https://github.com/opennic where things like the homepage and wiki
> > > backups are currently hosted. That is the location we will be hosting
> > > the automatic backups if this proposal is passed, and that repository
> > > (yet to be created) will be recognized as officially operated by the
> > > OpenNIC organization.
> > >
> > > Of course people are free to clone it or create their own backups,
> > > it’s all public data, just “AXFR" the zone. But community mirrors
> > > won’t be recognized as “official” within the scope of this proposal.
> >
> > Git was designed to avoid a single point of failure, and having multiple
> > *official* mirrors, with a list on the OpenNIC website, allow us to take
> > advantage of that.
> >
> > In other words, I argue that the OpenNIC organization should officially
> > operate more than just one Git repository.  The same commits can be
> > pushed to all of the official repositories.
> >
> > -- Jacob
> >
> > >> On Jul 13, 2018, at 11:31 PM, Daniel Quintiliani <[email protected]
> > >> <mailto:[email protected]>> wrote:
> > >>
> > >> Even better.
> > >>
> > >> --
> > >>
> > >> -Dan Q
> > >>
> > >>
> > >> On Fri, 13 Jul 2018 23:21:52 -0500, Jacob Bachmeyer
> > >> <[email protected] <mailto:[email protected]>> wrote:
> > >>
> > >>> Daniel Quintiliani wrote:
> > >>>> While I can't say anything about the specifics of this, as I don't
> > >>>> run any TLDs, you might want to take into account the current
> > >>>> volatile nature of Github, by specifically stating that members can
> > >>>> vote to move things to other sites in the event of a problem. We
> > >>>> shouldn't try and predict the finances and (mis)management of
> > >>>> Github, but instead change these proposals to specifically state
> > >>>> that members can vote to move hosting to other places.
> > >>>>
> > >>>
> > >>> Git was designed for repositories to be widely mirrored, so I suggest
> > >>> replacing "GitHub" with "public Git hosting services" and keeping a
> > >>> list
> > >>> of multiple official OpenNIC Git mirrors.
> > >>>
> > >>> Also, there should be a procedure for returning archived TLDs to active
> > >>> status if an operator steps forward.
> > >>>
> > >>> -- Jacob <mailto:[email protected]>
> >
> >
> >
> > --------
> > You are a member of the OpenNIC Discuss list.
> > You may unsubscribe by emailing [email protected]



--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.