Mailman 3 January 2024 - Twisted

magic-folder 24.1.0
by meejah 05 Feb '24

05 Feb '24

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Greetings, We are pleased to announce version 23.6.0 of magic-folder. Magic Folder synchronizes local data to and from a Tahoe-LAFS Grid, keeping data private with the end-to-end encrypted "Capabilities" of Tahoe-LAFS. One or more magic-folder clients can join the same Folder, adding and synchronizing data across multiple devices. Written in Python, Magic Folder supports Linux, MacOS and Windows. Python3 and PyPy are supported. By itself, this project requires familiarity with the command-line and long-running processes. The Gridsync project provides a cross- platform GUI experience using the localhost HTTP API. Changes in this release include: - - security: Bump dependencies, including security-relevant cryptography library (#716) - - feature: Added a description of the datamodel to the documentation (#702) - - feature: Conflict files now named after the Participant (not Author) (#711) - - bugfix: "magic-folder status" properly parses scan/poll events (#717) - - bugfix: Handle updates to conflicted files more robustly (#719) You may download the release from PyPI: https://pypi.org/project/magic-folder/23.6.0/#files Currently the localhost HTTP API used for integration is not 100% stable, although we do not expect large changes. thanks, meejah on behalf of all contributors -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEnVor1WiOy4id680/wmAoAxKAaacFAmSZNRIACgkQwmAoAxKA aaeMBggAhijgTKRlYSBbIO+Y/mms4drY2ArEptF+Q5secHo9of68xlL1tQoTGgeF et/xxgrjmn7WmnQYrC6k0f+xH+6mlW6sNb6wCafUmP/oh3p5bjAGv2tJDmfs81e+ iW7IUWBklx2mLdquwU4nWouJKZjeidqOyBvaBxx30hqOQe3yMwL5mxcliZg9ueZ6 M2HnQZmhA0yKblZrQ8H26dGTSvDLSOOCuHJKab04XYrmOJSJRqYK0DFXogjpNZbB Ep5wiMpxyEsfPc1bHpxdIJmgJZq1iIgx6dFnHiMNe7yQLykLc9kjPJcxvWRLVsk4 OzN5lHzsiYKsS0g3NVSj+2PKxY3d3w== =abqD -----END PGP SIGNATURE-----

2 1

Contribution policy change for pull requests without associated GitHub Issues.
by Adi Roiban 29 Jan '24

29 Jan '24

Hi I would like to propose a change to the contribution policy. The current policy is Authors: How to get your change reviewed There must be an issue in the Twisted Github Issue tracker describing the desired outcome. This is found in our docs at https://docs.twisted.org/en/latest/development/review-process.html#authors-… I would like to have this rule to allow pull requests without a Github issue for the following cases: * typo fixes in docstrings * changes to documentation * changes that only affect the automated tests, and which don't change the production code. In my opinion, asking for a separate GitHub each time you find a typo, is just red tape, and discourages small contributions. With GitHub web UI, you can browse the current code, observe a type, fix the typo in the web and then send the changes as a PR. I feel that this is as frictionless as possible. A PR with a GitHub issue would still need a release note, but the release notes will have the PR ID, instead of the ticket ID. ------------- Here is an example of a PR https://github.com/twisted/twisted/pull/12088 that I consider a redtape. The PR description is just a placeholder `Fixes #12087` and then on Issue 12087 we have: Title: BufferingTLSTransport has docstring formatting errors. #12087 Description: see https://docs.twisted.org/en/stable/api/twisted.protocols.tls.BufferingTLSTr… I think that it would help to have all this information just in the PR, instead of navigating between PR and Issue. --------- Here is an example of a PR that was merged without an associated GitHub Issue https://github.com/twisted/twisted/pull/12095 Do you see any disadvantages of merging such a PR? ---------- What do you think? Thanks for the feedback. -- Adi Roiban

2 1

Tahoe-LAFS release 1.19.0
by meejah 19 Jan '24

19 Jan '24

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ANNOUNCING Tahoe, the Least-Authority File Store, v1.19.0 The Tahoe-LAFS team is pleased to announce version 1.19.0 of Tahoe-LAFS, an extremely reliable decentralized storage system. Get it with "pip install tahoe-lafs", or download a tarball here: https://tahoe-lafs.org/downloads Tahoe-LAFS is the first distributed storage system to offer "provider-independent security" — meaning that not even the operators of your storage servers can read or alter your data without your consent. Here is the one-page explanation of its unique security and fault-tolerance properties: https://tahoe-lafs.readthedocs.org/en/latest/about.html The previous stable release of Tahoe-LAFS was v1.18.0, released on October 2, 2022. Major new features and changes in this release: A new "Grid Manager" feature allows clients to specify any number of parties whom they will use to limit which storage-server that client talks to. See docs/managed-grid.rst for more. The new HTTP-based "Great Black Swamp" protocol is now enabled (replacing Foolscap). This allows integrators to start with their favourite HTTP library (instead of implementing Foolscap first). Both storage-servers and clients support this new protocol. `tahoe run` will now exit if its stdin is closed (but accepts --allow-stdin-close now). Mutables may be created with a pre-determined signature key; care must be taken! This release drops Python 3.7 support and adds Python 3.11 and 3.12 support. Several performance improvements have been made. Introducer correctly listens on Tor or I2P. Debian 10 and Ubuntu 20.04 are no longer tested. Besides all this there have been dozens of other bug-fixes and improvements. Enjoy! Please see ``NEWS.rst`` [1] for a complete list of changes. WHAT IS IT GOOD FOR? With Tahoe-LAFS, you distribute your data across multiple servers. Even if some of the servers fail or are taken over by an attacker, the entire file store continues to function correctly, preserving your privacy and security. You can easily share specific files and directories with other people. In addition to the core storage system itself, volunteers have built other projects on top of Tahoe-LAFS and have integrated Tahoe-LAFS with existing systems, including Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django, Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and more. See the Related Projects page on the wiki [3]. We believe that strong cryptography, Free and Open Source Software, erasure coding, and principled engineering practices make Tahoe-LAFS safer than RAID, removable drive, tape, on-line backup or cloud storage. This software is developed under test-driven development, and there are no known bugs or security flaws which would compromise confidentiality or data integrity under recommended use. (For all important issues that we are currently aware of please see the known_issues.rst file [2].) COMPATIBILITY This release should be compatible with the version 1 series of Tahoe-LAFS. Clients from this release can write files and directories in the format used by clients of all versions back to v1.0 (which was released March 25, 2008). Clients from this release can read files and directories produced by clients of all versions since v1.0. Network connections are limited by the Introducer protocol in use. If the Introducer is running v1.10 or v1.11, then servers from this release can serve clients of all versions back to v1.0 . If it is running v1.12 or higher, then they can only serve clients back to v1.10. Clients from this release can use servers back to v1.10, but not older servers. Except for the new optional MDMF format, we have not made any intentional compatibility changes. However we do not yet have the test infrastructure to continuously verify that all new versions are interoperable with previous versions. We intend to build such an infrastructure in the future. This is the twenty-second release in the version 1 series. This series of Tahoe-LAFS will be actively supported and maintained for the foreseeable future, and future versions of Tahoe-LAFS will retain the ability to read and write files compatible with this series. LICENCE You may use this package under the GNU General Public License, version 2 or, at your option, any later version. See the file "COPYING.GPL" [4] for the terms of the GNU General Public License, version 2. You may use this package under the Transitive Grace Period Public Licence, version 1 or, at your option, any later version. (The Transitive Grace Period Public Licence has requirements similar to the GPL except that it allows you to delay for up to twelve months after you redistribute a derived work before releasing the source code of your derived work.) See the file "COPYING.TGPPL.rst" [5] for the terms of the Transitive Grace Period Public Licence, version 1. (You may choose to use this package under the terms of either licence, at your option.) INSTALLATION Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD, and probably most other systems. Start with "docs/INSTALL.rst" [6]. HACKING AND COMMUNITY Please join us on the mailing list [7]. Patches are gratefully accepted -- the Roadmap page [8] shows the next improvements that we plan to make and CREDITS [9] lists the names of people who've contributed to the project. The Dev page [10] contains resources for hackers. SPONSORSHIP A special thanks goes out to Least Authority Enterprises [12], which employs several Tahoe-LAFS developers, for their continued support. HACK TAHOE-LAFS! If you can find a security flaw in Tahoe-LAFS which is serious enough that we feel compelled to warn our users and issue a fix, then we will award you with a customized t-shirt with your exploit printed on it and add you to the "Hack Tahoe-LAFS Hall Of Fame" [13]. ACKNOWLEDGEMENTS This is the twentieth release of Tahoe-LAFS to be created solely as a labor of love by volunteers. Thank you very much to the team of "hackers in the public interest" who make Tahoe-LAFS possible. meejah on behalf of the Tahoe-LAFS team October 1, 2022 Planet Earth [1] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.19.0/NEWS.rst [2] https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/known_issues.rst [3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects [4] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.19.0/COPYING.GPL [5] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.19.0/COPYING.TGP… [6] https://tahoe-lafs.readthedocs.org/en/tahoe-lafs-1.19.0/INSTALL.html [7] https://lists.tahoe-lafs.org/mailman/listinfo/tahoe-dev [8] https://tahoe-lafs.org/trac/tahoe-lafs/roadmap [9] https://github.com/tahoe-lafs/tahoe-lafs/blob/master/CREDITS [10] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Dev [12] https://leastauthority.com/ [13] https://tahoe-lafs.org/hacktahoelafs/ [14] https://github.com/warner/magic-wormhole -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEnVor1WiOy4id680/wmAoAxKAaacFAmWpwIUACgkQwmAoAxKA aac6agf/RtC1yV4Sv6DzMMLd4ZpYNBy4m6Cm1cq8gTPeyv25q3vrFrJx0OQ8/mdv C7ooEsgMndEEnTTmfTto4xWUBnClq6dlFaX340M/RbWxAuH41YcItJdlNxdAcm3R +BABeNIO+LCKxpBKB6svhgxer7n/2TiU81zpRUSFlBmxPy8URpjJOkGGzuGE75d5 0w6ZOHhgFqMJadQpd+VS4zApTj0FKjwCGdIjCGZBL3Hj0Q0UOow52ejNAzJ+Zx8K W1+pTOQgCpHqzFJjIc9hwrS0cesv6q+BQMUB8Wbs8waDKgBbbHaKG+AFCx31R9AW zTyeyP1vHJ2gz6m167WJC0mDrlgVig== =uDDO -----END PGP SIGNATURE-----

1 0