CVS dane fvwm-web: * download/index.php:

2016-03-23 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm
Module name:fvwm-web
Changes by: dane16/03/23 17:16:57

Modified files:
.  : ChangeLog 
download   : index.php 

Log message:
* download/index.php:
Correctly remove reference to snapshots.
Remove "which package should you use comments about even/odd releases".
We don't do that now.
Remove daily snapshots reference.
Remove reference to being able to FTP source tree, that's not current either.
Direct users to new Github repository.
More work needs to be done to get the CVS stuff replaced with Git stuff.




Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-03-23 Thread Dan Espen
Thomas Adam  writes:

> On Sun, Mar 20, 2016 at 08:16:13PM -0400, Dan Espen wrote:
>> Moving the Fvwm-web source to Github won't help if we still need to
>> publish using Jason's services.
>
> So I've taken a look at this, and have noted the following:
>
> * PHP is used to regenerate the theming components of the site;
> * PHP is used to render in from the fvwm repo, the contents of files from:
>   
>   NEWS
>   FAQ
>
> * PHP is used to ensure the theme is applied consistently for the borders for
>   "window" (the default theme).
>
> What happens via github.io pages is that static content can be used for this.
>
> I'm starting to think that we have no desire or need for PHP at all for the
> website.  Before the use of static HTML generators, etc., it made a lot of
> sense.  Additionally, there's a lot one can do with CSS which mitigates the
> need for PHP as we're currently using it for the website.
>
> As for the linking in NEWS/FAQ -- the NEWS file in particular is obsoleted,
> given that git commit logs can be used to gather the same information.  That
> said, if we do retain NEWS for releases, we can just upload a separate set of
> notes for that against each release in the releases area of Github [1].  It's
> a part of the process.
>
> The FAQ therfore, is part of the website and it should be moved into that
> repository.
>
> I've since renamed the fvwm-web repository [2] to match the expectations of
> what github.io expects.
>
> I'd really (REALLY!) be interested in someone coming up with a proof of
> concept on what a FVWM website might look like using a static HTML generator
> that github.io accepts, just to prove my points above.  I won't be doing that
> work, however, but if someone does want to give this a go, do please let us
> know!
>
> Kindly,
> Thomas Adam
>
> [1]  https://github.com/fvwmorg/fvwm/releases
> [2]  https://github.com/fvwmorg/fvwmorg.github.io

I think we're embarking on a lot of work.
As a start I've updated the download instructions to send users to GIT.
I know you have the web stuff on GIT but if I make changes there they
won't get to fvwm.org.

Jason, let us know if/when you start pulling the web pages from GIT.

I'm pretty good with HTML/CSS.  PHP gives us some nice stuff, but I
guess we can live without it.

-- 
Dan Espen



Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-03-23 Thread Thomas Adam
On 23 March 2016 at 22:21, Dan Espen  wrote:
> I think we're embarking on a lot of work.

Which aspect, specifically?  Note that if you're referring just to the
website, then you might be right---I don't know enough about HTML/CSS
to make that call.  However, it requires someone with enough
understanding to put in place something static which can be hosted on:

https://github.com/fvwmorg/fvwmorg.github.io

Note that this repository as-named, assumes hosting under github.io,
which as I understand it makes thing a lot easier.  Certainly,
removing PHP at this point is definitely a good idea, as we're not
gaining anything from its use any more that CSS can't provide.  I
consider this a good thing.

> As a start I've updated the download instructions to send users to GIT.

OK.

> I know you have the web stuff on GIT but if I make changes there they
> won't get to fvwm.org.

That's OK -- because we can leave what's hosted on fvwm.org
as-is---and start to do something proper with fvwmorg.github.io --
that's your play area.  Go forth and have a blast.  Note that I'm
envisaging something which is self-hosting.  That is to say, something
we can redirect to from fvwm.org -- I see that as a positive thing
indeed.

> Jason, let us know if/when you start pulling the web pages from GIT.

See previous paragraph, I do not think this is the right approach at all.

> I'm pretty good with HTML/CSS.  PHP gives us some nice stuff, but I
> guess we can live without it.

Excellent.  Then set yourself up with a Github account, and let me
know your username, and I'll add you to the fvwmorg and you can do
something with the website repository.

Note that I'm getting married this weekend and will then be away on
honey moon for two weeks.

Kindly,
Thomas Adam



Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-03-23 Thread Dan Espen
Thomas Adam  writes:

> On 23 March 2016 at 22:21, Dan Espen  wrote:
>> I think we're embarking on a lot of work.
>
> Which aspect, specifically?  Note that if you're referring just to the
> website, then you might be right---I don't know enough about HTML/CSS
> to make that call.  However, it requires someone with enough
> understanding to put in place something static which can be hosted on:
>
> https://github.com/fvwmorg/fvwmorg.github.io
>
> Note that this repository as-named, assumes hosting under github.io,
> which as I understand it makes thing a lot easier.  Certainly,
> removing PHP at this point is definitely a good idea, as we're not
> gaining anything from its use any more that CSS can't provide.  I
> consider this a good thing.

Yep, I'm referring to the web pages.
I have some CSS based pages at work using themes.
The themes aren't really important to me, but since
I doubt GIT is going to give us PHP I think we'll be better off without
the PHP.

>> As a start I've updated the download instructions to send users to GIT.
>
> OK.
>
>> I know you have the web stuff on GIT but if I make changes there they
>> won't get to fvwm.org.
>
> That's OK -- because we can leave what's hosted on fvwm.org
> as-is---and start to do something proper with fvwmorg.github.io --
> that's your play area.  Go forth and have a blast.  Note that I'm
> envisaging something which is self-hosting.  That is to say, something
> we can redirect to from fvwm.org -- I see that as a positive thing
> indeed.

We own the domain name, I'm not clear on the details but I think once
we move the pages we can just make Fvwm.org be the git pages.

>> Jason, let us know if/when you start pulling the web pages from GIT.
>
> See previous paragraph, I do not think this is the right approach at all.

I don't see the difference.
Right now Jason pulls from CVS to build the pages at fvwm.org.
He said he's willing to pull from Git instead.
So, the fvwm-web can be in CVS or GIT, it doesn't matter,
we just need Jason to decide where he wants to pull from.

>> I'm pretty good with HTML/CSS.  PHP gives us some nice stuff, but I
>> guess we can live without it.
>
> Excellent.  Then set yourself up with a Github account, and let me
> know your username, and I'll add you to the fvwmorg and you can do
> something with the website repository.

Okay, will get to that sometime.

> Note that I'm getting married this weekend and will then be away on
> honey moon for two weeks.

Well, CONGRATULATIONS.
That's just great.
I was married in 1964.
I'm retiring as of March 31.

-- 
Dan Espen