On Mon, Sep 23, 2013 at 09:57:25PM -0400, Dan Espen wrote: > Thomas Adam <[email protected]> writes: > > * Consider using DBus as the API which is used to communicate to/from > > FVWM, INCLUDING MODULES; > > Is it available on all X Windows platforms?
Yes. Even compiles for Solaris, AFAIK. > Is it faster than the pipes we use? I haven't profiled it, but it'll be no slower, that's for sure. > > That's more blue-sky thinking. The immediate goals should be for you to > > switch to Git and shove the thing on Github. Per-project hosted sites are > > not going to cut it in 2013, chaps and chapettes. Really. Get yourselves > > noticed, and go hang with the cool kids. Sure, you could make git.fvwm.org > > authoritative, but at least have an official mirror on something like > > GitHub. It's where projects are noticed nowadays. You can create > > organisations therein and list members; might make the CVS permissioning > > scheme in use obsolete, thank God. > > If we move our source, we would still need Jason for accepting release > binaries, and we'd need to update CVS to get our web pages updated. > So, I think a Git transition would necessitate moving the entire > project, web pages and all. > > I'm not sure what all the steps are but I've been thinking of buying > some web space. Any comments? I started this a while ago; I think you'll find this all on the mailing list archives. I've got a conversion of both fvwm.git and fvwm-web.git on my GitHub page. As for hosting, not sure. I mean, we've been very lucky to have had Jason all these years, and I'd like to think we'll continue to do so. -- Thomas Adam
