Good to know -- for the foreseeable future, the only thing I'll be updating is the contents of ftp.openefs.org, via the upload/download mechanism.
Just curious, but has ANYONE other than me managed to setup an EFS 3 environment and work with any of the branches newer than 2011 or 2012? On Mon, Nov 24, 2014 at 9:09 AM, Steven Jenkins <[email protected]> wrote: > No worries. The wheels had already been turning to keep it in the > same place for another year. Like I mentioned, we can always link > over to github from the current openefs.org site. > > Steven > > On Sun, Nov 23, 2014 at 12:37 PM, Phillip Moore > <[email protected]> wrote: > > Well, I take back what I said -- I actually do have a use for at least > > ftp.openefs.org, since I'm rebuilding all the binary content for RHEL5 > and > > RHEL6 (not bothering with 7 yet), and uploading it to ftp.openefs.org. > This > > makes bootstrapping a new domain trivial, since you don't have to > recompile > > all this stuff, which takes WEEKS, literally. > > > > So I retract my suggestion that we shut the site down for now. > > > > Of course, it looks like nothing happened after that last email, but > just in > > case you were putting any effort into this, don't bother. > > > > On Sun, Oct 19, 2014 at 11:45 AM, Phillip Moore < > [email protected]> > > wrote: > >> > >> This is the first email to the efs-dev mailing list in almost two years, > >> and in that time, there have been very few commits to the public git > >> repositories as well. > >> > >> After spending the last 2 years working on major improvements to EFS for > >> my current consulting gig, I have once again re-released all of that > work to > >> the OSS world. However, given the complete mess that is openefs.org, > and > >> the lack of a real community, I am no longer going to use that site, and > >> will in fact encourage anyone interested in my code to ignore it. > >> > >> I've published all of my latest work on github.com, and I'm in the > process > >> of moving all of the trac tickets to issues on github's system. I am > doing > >> these because I am almost certainly about to start a new gig where we > will > >> be using EFS as the foundation for a new global filesystem > infrastructure, > >> and I'm not interested in maintaining compatibility with the "official" > (if > >> that even makes any sense) openefs.org code base. > >> > >> I'm pretty sure BAC is still paying for openefs.org support via > OSU-OSL, > >> and as far as I am concerned, that's a waste of money at this point. > It is > >> clear by now that BAC has no interest in the code I've written, and I > long > >> ago ripped out all the EFS 2 compatibility code anyway. I am about to > make > >> major changes to efsdeploy and the EFS::Perl infrastructure as well, and > >> these changes will be made with no commitment to backwards > compatibility, > >> either. In fact, the efs-core code base already has major namespace > >> changes that aren't compatible with the old environment as well. > >> > >> I would like to formally suggest that we decommission that site, and > >> preferably free up the domainname. If I can't get openefs.org back, > I'll > >> just use something else, but right now, there's really no need for a > >> dedicated website for the product, since it has so few users, and no > active > >> community. > >> > >> If there is interest in keeping openefs.org up and running, then > consider > >> this an announcement that I am forking the code and going my own way. > >> > > > > > > _______________________________________________ > > EFS-dev mailing list > > [email protected] > > http://mailman.openefs.org/mailman/listinfo/efs-dev > > > _______________________________________________ > EFS-dev mailing list > [email protected] > http://mailman.openefs.org/mailman/listinfo/efs-dev >
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
