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

On Mon, Apr 04, 2016 at 11:56:47AM -0600, Jaimos Skriletz wrote: > https://help.github.com/articles/using-a-custom-domain-with-github-pages/ > https://help.github.com/articles/setting-up-your-pages-site-repository/ I say we trial this, as it's the simplest change, without additional overhead, and

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

On Mon, Apr 4, 2016 at 11:31 AM, Jason L Tibbitts III wrote: > > "JS" == Jaimos Skriletz writes: > > JS> So to complete the switch the fvwm.org domain needs to be pointed > JS> at/redirected to github.io. > > That's easy for me to do, but

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

> "JS" == Jaimos Skriletz writes: JS> So to complete the switch the fvwm.org domain needs to be pointed JS> at/redirected to github.io. That's easy for me to do, but before I make any changes. JS> I think pointing fvwm.org at github would be preferable as

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

On Sat, Apr 02, 2016 at 02:45:22PM -0400, Dan Espen wrote: > Jaimos Skriletz writes: > > > Also I am unsure if these various markdown files, FAQ.md, AUTHORS.md, > > DEVELOPERS.md, etc should be located and maintained on the webpage or > > in $FVWM.GIT source. I

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

On Sat, Apr 02, 2016 at 11:58:41AM -0600, Jaimos Skriletz wrote: > On Fri, Apr 1, 2016 at 5:43 PM, Thomas Adam wrote: > > > On Fri, Apr 01, 2016 at 02:47:24PM -0600, Jaimos Skriletz wrote: > > > ​​ > > > > Thanks! It looks really good. We can remove the Changelog section;

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

Jaimos Skriletz writes: > Also I am unsure if these various markdown files, FAQ.md, AUTHORS.md, > DEVELOPERS.md, etc should be located and maintained on the webpage or > in $FVWM.GIT source. I think either can work with git.io so it is > probably a matter of

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

On Fri, Apr 1, 2016 at 5:43 PM, Thomas Adam wrote: > On Fri, Apr 01, 2016 at 02:47:24PM -0600, Jaimos Skriletz wrote: > > ​​ > > Thanks! It looks really good. We can remove the Changelog section; people > can look at the release descriptions and/or Git history from now on. >

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

On Fri, Apr 01, 2016 at 02:47:24PM -0600, Jaimos Skriletz wrote: > ​​ > > On Sat, Mar 26, 2016 at 2:09 PM, Jaimos Skriletz < > jaimosskril...@boisestate.edu> wrote: > > > Here is what I have created so far > > > > http://fvwmforums.org/fvwm.org/ > > > > The sources are available on github > > >

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

​​ On Sat, Mar 26, 2016 at 2:09 PM, Jaimos Skriletz < jaimosskril...@boisestate.edu> wrote: > Here is what I have created so far > > http://fvwmforums.org/fvwm.org/ > > The sources are available on github > > https://github.com/somiaj/fvwmorg.github.io > > ​Update: ​The site is mostly complete

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

Here is what I have created so far http://fvwmforums.org/fvwm.org/ ​Jekyll seems to be fairly straight forward for the basics. Once the framework is setup, you can just add/remove files as either .html or .markdown (.md) with a small YAML header. This will then cause the software to generate the

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

On 26 March 2016 at 01:11, Dan Espen wrote: > My account is named "danespen". I've added you, along with Jaimos as well. My last official act before I move onto a few more important things for a bit. >> Note that I'm getting married this weekend and will then be away on >>

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

Thomas Adam writes: R> On 23 March 2016 at 22:21, Dan Espen wrote: > 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. My account

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

On Fri, Mar 25, 2016 at 05:37:50PM -0500, Jason L Tibbitts III wrote: > > "TA" == Thomas Adam writes: > > TA> I note that it's possible to set up webhooks on repositories on > TA> Github. We could use that mechanism to notify you of changes which > TA> need pulling (and

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

> "DE" == Dan Espen writes: DE> Not sure why, maybe I paid, but paid for you? Yes, the last time it came up for renewal, you paid for it. We didn't actually transfer the ownership or the registrar. If you want to do that, though, then just let me know what I need to

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

> "TA" == Thomas Adam writes: TA> I note that it's possible to set up webhooks on repositories on TA> Github. We could use that mechanism to notify you of changes which TA> need pulling (and hence, enact some script to do a git-pull), rather TA> than polling for them. It's

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

On Fri, Mar 25, 2016 at 04:43:53PM -0500, Jason L Tibbitts III wrote: > OK, a manual pull worked. Turns out that the update script is in my > home directory, which isn't accessible without a kerberos ticket. > That's fixed up. TGTs. Nice! > It's a trivial matter to have this do a git pull

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

Jason L Tibbitts III writes: >> "JS" == Jaimos Skriletz writes: > > JS> who controls the domain name fvwm.org, > > A whois query shows that it's me. Not sure why, maybe I paid, but paid for you? From: Gandi

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

On Fri, Mar 25, 2016 at 04:00:19PM -0600, Jaimos Skriletz wrote: > Hello, I have offered to help migrate the fvwm.org to something more > maintainable as this is something Thomas was wanting help with in #fvwm. Hi Jaimos, > I am unsure on a lot of the details about how the current site is >

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

> "JS" == Jaimos Skriletz writes: JS> who controls the domain name fvwm.org, A whois query shows that it's me. - J<

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

> > Jaimos Skriletz has also expressed an interest in this (I'ev Cced him), and > he'll post here soon about what his thoughts are, etc. Hopefully you and > he > can work together on this. > ​Hello, I have offered to help migrate the fvwm.org to something more maintainable as this is something

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

OK, a manual pull worked. Turns out that the update script is in my home directory, which isn't accessible without a kerberos ticket. That's fixed up. It's a trivial matter to have this do a git pull instead, so if the fvwm-web repository on github is up to date, then just let me know and I'll

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

> "DE" == Dan Espen writes: DE> Meanwhile, I committed fvwm-web changes yesterday, but those changes DE> have not shown up at fvwm.org. Where did you commit them? I'm surprised you could commit at all, given the fact that the CVS server isn't really happy. I'll try to

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

On Fri, Mar 25, 2016 at 05:21:27PM -0400, Dan Espen wrote: Hi Dan, > My first impression, it's Github only. No, not at all. It's a way of generating HTML from static templates, which can be augmented with CSS and extra HTML where necessary. It just so happens that what Github hosting offers,

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

Thomas Adam writes: > On Wed, Mar 23, 2016 at 09:19:18PM -0400, Dan Espen wrote: >> 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

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

On Wed, Mar 23, 2016 at 09:19:18PM -0400, Dan Espen wrote: > 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. Have a

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

On 24 March 2016 at 01:19, Dan Espen wrote: >> Thomas Adam writes: >> 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

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

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

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

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

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

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

Re: FVWM code moved to Github

Hi Jason, On 21 Mar 2016 17:04, "Jason L Tibbitts III" wrote: > I can continue to provide mailing lists in case people still find them > useful. Please. We really need those as they're a core part of our infrastructure. Is there some means by which you'd be able to delegate

Re: FVWM code moved to Github

Hi Jason, On 21 Mar 2016 17:18, "Jason L Tibbitts III" wrote: > > > "TA" == Thomas Adam writes: > > TA> Yes, and he's not always around, alas. > > I'm _almost_ always around. But I was in New Orleans with crappy > Internet, and got home to no Internet at

Re: FVWM code moved to Github

> "TA" == Thomas Adam writes: TA> Yes, and he's not always around, alas. I'm _almost_ always around. But I was in New Orleans with crappy Internet, and got home to no Internet at all. (Thanks, Comcast.) And I will be jaunting around Europe for most of July and some of

Re: FVWM code moved to Github

> "TA" == Thomas Adam writes: TA> I appreciate I've swooped in here, and just done this, but the TA> discussion[0] happened once before, and given the recent TA> circumstances with the borked CVS repository, it seemed unfair to TA> leave an impending release hanging. Just

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

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

Re: FVWM code moved to Github

On 21 March 2016 at 00:16, Dan Espen wrote: Hi Dan, > I'm not clear on what we can do with Github. > You mention leaving the web pages and mailing lists on fvwm.org. > > For that we need Jason. Yes, and he's not always around, alas. > Is it possible to move the whole

Re: FVWM code moved to Github

Thomas Adam writes: > Hi all, > > I know we've had these discussions in the past, but I think now is the time we > actually do something about them. > > I appreciate I've swooped in here, and just done this, but the discussion[0] > happened once before, and given the recent