Remove Tag?

Do you want to untag yourself from this post?

The Command Ship

Open Session- July 2023

Posted by Captain Katy Darrah (CMM) in Open Session- July 2023

Posted by Captain Nathan Miller (TECH) in Open Session- July 2023

Posted by Vice Admiral Robert Archer (Engineering DIrector) in Open Session- July 2023

I know a lot of this lays on members of TECH who volunteer their time to the club and this isnt a job for them. But if our structure of updating and maintenance of the site is said to need a database migra4tion and software update to XYZ and it goes 1+ years after first being mentioned publicly, same for a library update and such related to this, then how are we members who do other things supposed to do our own tasks? I appreciate this site and everyone past and present who’s done work on the backend. I wish I had more skills for that which I could help with, but TBH I can’t even remember the last time any constant active effort was pushed by TECH or anyone to really get the word out constantly on getting people to try to help and become engaged. It just feels like 2-3/4 people which only has 1 person who I ever see help or talk about anything. So I don’t know what else to say about this end of things for updating the site’s library and such. But it is definitely something which we as a club need to take a major look at....

<snip>

I have been out of town the last few days and haven’t had a chance to look at Command until today. I’m splitting this thread as to not derail the other thread, which is on a different topic.

The answer to this is the same as it has always been, and is twofold:

1) What is in planning is not simply a database migration, or a software update. It is a database migration, a software update, an OS change, a change of service provider, and making sure that we will have as minimal a disruption in service as possible while doing so, and that the new setup will continue to be easily maintainable in the future. This is not a small change. The server move will involve updating the DNS A record, which can take up to 72 hours to propagate across the network. We want all of TECH available, which leads to the next point.

2) Needing all of TECH available for 72 hours requires a three day weekend and coordinating the schedules of multiple people. I just did a similar project at work: it required 6 months of advance work to prepare, and collaboration of 5 full time employees - and it wasn’t successful the first time. We don’t have that luxury, and we unfortunately haven’t been able to align our schedules for various reasons.

Nathan

I can’t speak for everyone, but I can for myself, and I’d like to say one thing: Can we have a bit more communication? To an outsider (of TECH, obviously) it appears as though TECH has done nothing, because all we have are backend updates (if there are any) and other background work that we cannot see as members of the club.

Even if it was merely a line of “Attempted to coordinate schedules for server migration. Couldn’t.” would be fine with me, personally, just so that I’m not sitting here thinking TECH is twiddling their thumbs.

Katy

So as Katy said, more regular communication on things like this would go a long way I think to least keeping the club at large informed. While I was somewhat aware of what you said Nathan the last information on this that I was given was over a year ago.

Robert Archer

Use the full posts index to browse this ship's thread list.

Open Full Posts Index