Re: Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

"Thomas Adam" wrote: > On Fri, Mar 25, 2016 at 03:30:03AM +0100, Thomas Funk wrote: > > One point: > > Should we use for development branches a special nomination like > > feature_xy, fix_abc? > > Or only a README which describes the feature/fix? > > I don't think that's

Re: Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

"Thomas Adam" wrote: > On Fri, Mar 25, 2016 at 12:25:09PM +0100, Thomas Funk wrote: > > I think we should. It's better to have such in the documentation so no > > questions appears anymore ;) > > > > I can add it to the document, no prob. > > I've added a few words about this,

Re: Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

On Fri, Mar 25, 2016 at 12:25:09PM +0100, Thomas Funk wrote: > I think we should. It's better to have such in the documentation so no > questions appears anymore ;) > > I can add it to the document, no prob. I've added a few words about this, without making this a rule, which hopefully people

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: [fvwmorg/fvwm] c6de88: distcheck2: remove bzip2 archive generation

Hi, On 25 March 2016 at 22:57, GitHub wrote: > Branch: refs/heads/ta/makedist-no-bzip2 > Home: https://github.com/fvwmorg/fvwm > Commit: c6de883d85466cdc4c3ee4fc6b8ee3f5c87b8af0 > > https://github.com/fvwmorg/fvwm/commit/c6de883d85466cdc4c3ee4fc6b8ee3f5c87b8af0

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]

> > 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]

> "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]

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]

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]

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]

> "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 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]

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]

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]

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