I think if we are using what winter has started using (Jekyll), the only
thing that you'll need to know is markdown. There will be the HTML and CSS
templates in there as well, but most of the time you will not need to edit
those. Regardless when or if you do need to edit them, they are in the code
base and I don't imagine that we would have anything outside the code base.
This means that you edit the website in the code, commit to Git, and then
simply upload it if we are going to continue using source forge.

If we switch to using GitHub for the website, the only thing that you would
need to do is edit the documents and commit them to Git. They would be
immediately visible on the website. we could even put some controls around
it like pull requests to make them go live.

David

On Fri, Jan 3, 2020, 1:04 AM D Blakeley via Freecol-developers <
freecol-developers@lists.sourceforge.net> wrote:

> Jon, I think we both lost the Wordpress debate buddy, time to capitulate
> haha.
>
> Hmm well if Stian's not to be contacted unless there's an emergency I'd
> say that's a no haha!
>
> I think Mike came later after other dudes worked on it for years and
> burned out.
>
> BTW Don't worry Mike I got your latest msg via dev list and your
> previously missing message decided to arrive (from dev list) today a day
> late too.. and into my spam folder lmao. Well played yahoo well played..
>
> I'm thinking about switching to Internode.. iinet are driving me nuts..
>
> If you guys are doing all this website work on SF I guess I better figure
> out how to edit webpages on SF lol.. took me long enough to figure out how
> to do the website changes on the github copy but if that's missing out on
> the latest stuff then I better figure out SF lol. Do I need any special
> programs installed on my comp? Or does SF have a built in HTML/text file
> editor like github has?
>
>
> Regards
>
> Blake
>
>
>
> On Friday, 3 January 2020, 07:21:59 pm ACDT, Jonathan Aquilina <
> eagles051...@gmail.com> wrote:
>
>
> My concern is this. Is said person holding the domain still interested in
> the project and being involved. If not its best to easily have the domain
> transferred to someone who is more active like Michael for example.
>
> @Michael is freecol your baby that you have developed from the ground up?
>
> Jonathan Aquilina
>
>
> On Fri, Jan 3, 2020 at 9:40 AM <win...@genial.ms> wrote:
>
> This was all before I joined the project. My assumption had always been he
> is only to be contacted in case of emergency.
> We should only disturb them after everything is decided, and then it would
> fall on Mike, as he is the one who knows them.
>
>
> *Gesendet:* Freitag, 03. Januar 2020 um 09:30 Uhr
> *Von:* "Jonathan Aquilina" <eagles051...@gmail.com>
> *An:* win...@genial.ms
> *Cc:* "FreeCol Developers" <freecol-developers@lists.sourceforge.net>
> *Betreff:* Re: [Freecol-developers] Website fixes
> Has anyone tried to contact him?
>
> Jonathan Aquilina
>
> On Fri, Jan 3, 2020 at 9:29 AM <win...@genial.ms> wrote:
>
> As I tried to say, Stian or another inactive project member is controlling
> the domain records, which means it is not that easy.
>
>
> *Gesendet:* Freitag, 03. Januar 2020 um 09:20 Uhr
> *Von:* "Jonathan Aquilina" <eagles051...@gmail.com>
> *An:* win...@genial.ms
> *Cc:* "David Lewis" <highwayofl...@gmail.com>, "FreeCol Developers" <
> freecol-developers@lists.sourceforge.net>
> *Betreff:* Re: [Freecol-developers] Website fixes
> Hi Winter,
>
> You are worried about breaking the domain, there is an easy solution to
> that you would need to add a CNAME (Alias) record on DNS which will point
> to the .io site so if i go to the .org it would redirect me to the alias .io
>
> Jonathan Aquilina
>
> On Fri, Jan 3, 2020 at 9:18 AM <win...@genial.ms> wrote:
>
> Hi,
>
> a few days ago when reading SF webserver documentation, I saw that you
> could switch over from PHP5 to PHP7.
> It's just that we are completely HTML only without a single .php file
> remaining -- that's why I saw no use in doing it.
> If you switch over the domain would change from .net to .io, possibly
> breaking our .org domain, depending on how it is configured. This might
> also break some direct links to the .net subdomain somewhere.
> We would get https on the .io domain, but certificates are bound to the
> domain not ip, thats why I doubt it would work correctly on our .org domain.
> There is still some old files on the ftp for the webserver in the
> directory above the htdocs directory for the website -- these will need a
> backup before a switchover!
> I would not click the switch over button, without Stian and/or whoever
> controls the .org domain giving his ok.
>
> Greetings
>
> wintertime
>
>
> *Gesendet:* Freitag, 03. Januar 2020 um 06:31 Uhr
> *Von:* "David Lewis" <highwayofl...@gmail.com>
> *An:* "Michael T. Pope" <mp...@computer.org>
> *Cc:* "FreeCol Developers" <freecol-developers@lists.sourceforge.net>
> *Betreff:* Re: [Freecol-developers] Website fixes
> Lol, bizarre.
>
> Yay for Yahoo filtering.
>
> I don't know that the forums would be moved.
> I think we may just leave those as is on SF. overall I really don't see a
> need to transition absolutely everything over to github from source forge,
> just primarily the code base and the website. And also probably the ticket
> tracker to GitHub issues.
>
> I don't really see a need to abandon SF entirely.
>
> David
>
> On Thu, Jan 2, 2020, 9:26 PM Michael T. Pope <mp...@computer.org> wrote:
>
> On Thu, 2 Jan 2020 23:19:14 +0100
> win...@genial.ms wrote:
> > I was anticipating of moving the website over to GitHub someday, but
> it's kinda surprising you'd like to move over the domain so fast when the
> other stuff is still on SF?
>
> Quite so.  I wish people who want to move stuff around would
> at the very least come up with a plan that includes the hard
> problems, like how to move the forums.  The website is easy.
>
> > Would it be easier to get https support for the freecol.org domain on
> GitHub?
>
> That is a timely remark.  Yesterday while I was trying to work out who has
> permission to update the SF website I came across something new[1]:
>
>                 Your website is currently hosted at
>                 http://freecol.sourceforge.net with PHP 5.4
>
>                 To update to https://freecol.sourceforge.io and PHP 7.x,
> click the button below.
>                 There will be a small delay for it to take effect. You may
> switch back if needed.
>
> I propose to click the button.  There is also some interesting stuff about
> github connections which I have yet to read.  More soon.
>
>
> And in the special D Blakeley section:-):  Blake, yahoo is not
> accepting mail from my ISP, who are sending me messages like:
>
>         This is an automatically generated Delivery Status Notification.
>
>         THIS IS A WARNING MESSAGE ONLY.
>
>         YOU DO NOT NEED TO RESEND YOUR MESSAGE.
>
>         Delivery to the following recipients has been delayed.
>
>               <d_blake...@yahoo.com>
>
>         The reason for the problem:
>         4.3.2 - Not accepting messages at this time 421-'4.7.0 [TSS04]
> Messages from 150.101.137.19 temporarily deferred due to user complaints -
> 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html'
>
> Given that I am with internode who have won a bunch of customer service
> awards, and you are with yahoo, who... hasn't, I am guessing the problem
> is at your end.  Now we just need someone to quote this email so Blake
> sees it.
>
> Cheers,
> Mike Pope
>
> [1] "New" as in "added since I last looked around about a year ago"
>
>
>
>
> _______________________________________________
> Freecol-developers mailing list
> Freecol-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freecol-developers
> _______________________________________________
> Freecol-developers mailing list
> Freecol-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freecol-developers
>
_______________________________________________
Freecol-developers mailing list
Freecol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freecol-developers

Reply via email to