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 circumstances with the borked CVS
repository, it seemed unfair to leave an impending release hanging.

To that end, I have therefore created an organisation on Github[1] which at
the moment houses what I'm now calling the "official" FVWM repository [2].
This has been converted from the existing FVWM CVS repository (branch-2_6).

The 2.6.6 release now has a tarball uploaded and can be found here[3].

I've not changed fvwm-web, but this will likely be converted as well and put
on [1] in due course.

Note that as an organisation on Github, we have a lot more freedom, in that
more than one person who is a member of the fvwmorg organisation will be able
to do things like handle releases, etc., and that should something happen,
it's not anything in our control that we'd need to worry about.

This has absolutely *no* reflection on Jason at all.  He's spent the last
twenty odd years managing this, and to have all of this go through one person
is not scalable, especially when something goes wrong.  So we should be really
thankful indeed for Jason's efforts, and to note that I hope he continues to
manage the hosting/mailing lists, but the code... that's now better handled by
us.  Moving away from CVS is also long overdue.

So what happens next?  Well, I need existing fvwm-workers who had commit-bit
access to let me know so I can add you to the organisation.

Additionally, I have the following outstanding items:

* Convert fvwm-web, and add to fvwmorg on GH;
* Rip out the existing CVS docs and put something else in place;
* Update the release procedure
* Put our logo on the front of the landing page for fvwmorg on GH

Any questions, do please let me know.

Thomas Adam

[1] https://github.com/fvwmorg
[2] https://github.com/fvwmorg/fvwm
[3] https://github.com/fvwmorg/fvwm/releases/tag/version-2_6_6

Reply via email to