On 4/23/19 4:59 AM, Pierre Labastie wrote:
Hi all,
There is a private repository on github, created by Bryan Gonzalez
(thanks to him), containing jhalfs. It has the whole history of jhalfs
(not ALFS), up to svn rev 4100. Bryan has given me (not sure he has
given others) write privileges to this repository. I've already added a
.gitignore file.
I've received an answer from five out of seven contributors to jhalfs.
They all agree to change the license to MIT. The remaining ones are
Gerard Bekmans, who actually is not a contributor to the present code (4
commits, 2 for putting test files, 2 for removing them), and Manuel
Canales Esparcia, who has been very active on jhalfs and other LFS
projects until September 2007, and then suddenly disappeared (hope
nothing bad happened). So here are the plans (feel free to comment):
- Change the license file to MIT on SVN and github. Note that the "menu"
part of the code will still be GPLv2, since it comes from another
project. Adapt the "jhalfs -v" output to reflect that.
- Remove all the $Id$, $date$, etc, which are specific to subversion,
from files on github
- Add a mechanism to replace that, at least so that the date and most
recent commit appear in the ouptut of "jhalfs -v". Actually the
subversion mechanism was not very satisfactory, since it reflected the
date of the last change to the jhalfs file, not to the jhalfs repository.
- Write a small howto for the commands needed to use jhalfs (not for
contributing, this may be another howto, but github has already well
written howtos), to be put somewhere on the linuxfromscratch site, so
that users can switch smoothly from subversion to git.
- discuss a workflow for when the github repository will be made public:
should we keep this mailing list, keep trac on linuxfromscratch, or move
everything to github, using their "comments", "issues", and "pull
request" areas? Discuss also governance (who has write access to the
repo when it is public, who makes decisions, etc. See
https://opensource.guide/leadership-and-governance/ for some thoughts
about that. I can see me as "BDFL", but I'm open to anything else).
- once all (the above + something we may discover or think of) is set
up, make the repository public...
Is there a way that issue conversations can be mirrored on the mailing
list? The same for commits to master. Right now I see every commit,
including branches and tags, made to svn.
I don't make commits to jhalfs, but I follow the development because
everything is automatically reflected in the mailing list. I'd hate to
have to make following jhalfs development a manual operation.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
