[NCUC-EC] E-Team Engagement

[Benjamin Akinmoyeje]

Dear Andrea,
Good day to you and I hope you are doing well.

Please can you help create a Zoom meeting for us the eTeam and Olga to meet.

Please it would be great if you can invite everyone on this mail trail.

The date and time of the meeting is July 31, 2023, and by 6 pm Kyiv time.

Kind regards,
Benjamin

On Fri, Jul 28, 2023 at 4:07 PM Tapani Tarvainen <ncsg at tapani.tarvainen.info>
wrote:

> I can do July 31 at that time. Probably could arrange the latter
> options as well but would have to look at specific times.
>
> Tapani
>
> On Fri, Jul 28, 2023 at 08:44:21AM +0000, Benjamin Akinmoyeje (
> benakin at gmail.com) wrote:
> >
> > Dear eTeam,
> > Good day to you.
> >
> > Please here is the time availability I got from Olga
> >
> > “So if you want a call, let’s make smth quick for 30 minutes max with EC
> > inviting Tapani who can explain what is the challenge on his side. I can
> > make it for a call on 31 July after 6 pm (Kyiv time, UTC+3), 3 August
> after
> > 4 pm and 5 August any time at the moment.”
> >
> >
> > I will recommend July 31st please
> >
> >
> > Looking forward to hear from you.
> >
> > Kind regards,
> > Benjamin
> >
> > On Thu, 13 Jul 2023 at 2:16 PM, Tapani Tarvainen <
> ncsg at tapani.tarvainen.info>
> > wrote:
> >
> > > So, a brief summary of the situation as I see it:
> > >
> > > Olga and her friend Dusan have designed a new website, which you can
> > > see at www2.ncuc.org. Contentwise it's no more up-to-date than the
> > > old one, but it should be easy to update (the old one isn't as you
> > > presumably know, I won't go into the reasons for that now).
> > >
> > > The first decision would be if the new design is good enough
> > > to move forward with. (I think it is.)
> > >
> > > There are some compatibility issues with the current VPN where
> > > it now is. They are not trivial to solve because the old mailing
> > > list software (lists.ncuc.org) needs different (older) versions
> > > of some stuff, and we don't want to break the mailing lists.
> > >
> > > Easiest solution from my perspective here is getting another VPN and
> > > separate the mailing list and website to their own VPNs. This will
> > > cost something to the order of $10/month.
> > >
> > > So that's the second decision. I can set up a new VPN in
> > > a few minuts once you confirm someone will pay for it.
> > >
> > > Once that's up and the new wordpress setup is there, it's contents
> > > would need to be updated. Not all that much new content is needed,
> > > most important is to make sure that whatever is there is current,
> > > notably EC and other committee memberships. Some subsections are also
> > > completely empty now, but could be populated simply by copying content
> > > from the old site.
> > >
> > > Publication of the new site could be done in two ways:
> > >
> > > (1) keep it in a temporary location (www2 or whatever) until the
> > > contents are more or less up to date and then change the URL to
> > > www.ncuc.org and announce it to the world.
> > >
> > > (2) switch URL immediately, that is make www.ncuc.org point to
> > > the new design even while incomplete and update it there.
> > >
> > > Difference between those is mainly in the optics as it were, how
> > > things look like while it's being worked on. The first would be
> > > prettier, more glamorous so to speak, but if nobody then takes up the
> > > content work it could hang in a limbo for a long time.
> > >
> > > That's the third decision.
> > >
> > > But what that leads to is continued maintenance of the site,
> > > both content (Wordpress) and back end.
> > >
> > > Pretty much everybody should be able to learn what it takes to to edit
> > > WP content in a matter of minutes, although some care (and
> > > documentation!) would be needed to keep the site consistent in what's
> > > where. But you'd need several people doing that enough that they don't
> > > forget how it works.
> > >
> > > So the fourth decision is, who'd be doing that.
> > >
> > > The back end I can manage for now, but at least in the long run it
> > > would be necessary to have a backup sysadmin in case I'm run over
> > > by a bus or die of old age or something, and for that you'd need
> > > someone with Linux sysadmin skills. There are also options for
> > > managed hosting where that'd be somewhat easier, at extra cost
> > > (of course), which might make sense at some point.
> > >
> > > Deciding on that isn't as urgent, but for the record it's one
> > > more question to decide on at some point.
> > >
> > > OK, it wasn't all that brief... but I think I got most of
> > > the issues covered.
> > >
> > > --
> > > Tapani Tarvainen
> > >
>
> --
> Tapani Tarvainen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20230729/eaf6c92a/attachment.htm>