NetworkInfrastructure » History » Revision 32
h1. NetworkInfrastructure |_. What |_. Where |_. Access type | Who | comments | | "Redmine instance":https://redmine.replicant.us | OSUOSL | Redmine administrator | Several Replicant contributors including: * GNUtoo * Add your name here if you have access and want to be mentioned | | | "Mailing list":https://lists.osuosl.org/mailman/listinfo/replicant | OSLOSL | ? | ? | | | "Wordpress instance":https://blog.replicant.us/ | OSUOSL | Wordpress administator | Several Replicant contributors including: * GNUtoo * Add your name here if you have access and want to be mentioned | This instance is auto-updated automatically with the help of a plugin. | | "Releases":https://ftp-osl.osuosl.org/pub/replicant/ | OSUOSL | SSH? SFTP ? | ? | We should not use too much space | | "Source code":https://git.replicant.us/ | FSF | SSH (in a vm?) | ? | Resources kindly offered by the FSF | | [[PrivateContact|Private contact address]] | ? | ? | ? | The contact address is redirected to several Replicant contributors including: * GNUtoo * Add your name here if you have access and want to be mentioned | | IRC channel | Freenode | ? | ? | | | The replicant.us (mostly-static) front website | ? | ? | ? | * "Source code":https://git.replicant.us/replicant/website/ * Patches are to be sent to the Replicant mailing list | | The replicant.us domain name | ? | ? | ? | ? | | The replicant.us TLS certificate | Let's Encrypt | Access probably Probably by controlling the respective domain name | * https://www.replicant.us: OSUOSL * https://blog.replicant.us: OSUOSL * https://redmine.replicant.us: OSUOSL * https://git.replicant.us: ? | History: CA-cert -> GlobalSign -> LetsEncrypt | h2. OSUOSL The OSUOSL is the Oregon State University Open Source Lab. * Where is it hosted? * What is the backup policy? h2. FSF * It is hosted in their office. * What is the backup policy?