Re: Freenet's Hackathon (second edition)
Hello all, Around mid-november sounds great to me. It's a bit close but we can make it. So *November 17* is a tentative date for the Hackathon. I'll prepare a list of tasks to work on (suggested but not required) from [1]. Please do propose any task/project that you know you want to tackle and/or need help with. Ideal tasks for the hackathon are: - Web interface changes (translations, enhancements, bug fixes) - Installers bug fixes - Website translations and visual enhancements - Testing, documentation and code reviews @Arne Do you have a list of tasks you'll like to see included? Best regards, [1]: https://freenet.mantishub.io/view_all_bug_page.php?filter=5bd14e83cc743 On 2018-10-23 12:47, Hunter Poe wrote: > Hi, I haven't contributed to Freenet before but am interested in doing > so and getting an opportunity to do a hackathon would be a great way > to get involved. I could probably do November 17th > > On Tue, Oct 23, 2018 at 7:11 AM Steve Dougherty > wrote: > >> I’d be interested - I’m free the weekend of November 17th, as >> well as weekends in December. >> >> - Steve >> >> Typed on a mobile keyboard >> >> On Sat, Oct 13, 2018 at 4:01 PM, DC* wrote: >> >>> Hello everyone! >>> >>> I've been looking around the issue tracker and found many stalled >>> projects and initiatives. I'm also a bit stuck on some >>> freenet-related >>> projects due to this slow pace. >>> >>> I was wondering if it'll be a good idea to bring back the Weekend >>> Of >>> Code Hackathon[1][2] as it brought good results [3]. >>> >>> If it's OK we'll need to define: >>> >>> - Date and time >>> - Scope (tasks to work on) >>> - Team involved (to ask for advice, help) >>> >>> The idea is to quickstart some projects and get new people >>> involved. >>> >>> What do you think? >>> >>> Best regards! >>> >>> [1]: >>> >> > https://freenetproject.org/weekend-of-code-hackathon-announcement.html >>> >>> [2]: >>> >> > http://127.0.0.1:/Sone/viewPost.html?post=6acc3640-efe6-4ea3-9fec-258d3189d384 >>> >>> [3]: >>> https://freenetproject.org/weekend-of-code-hackathon-results.html
Re: final final test release of 1481
Hey there, I'm gonna test the installers on *nix and windows and report back. Hopefully 1481 can be released soon. Best regards, On 2018-10-24 19:05, Arne Babenhauserheide wrote: > Hi, > > I had to add some more fixes to run.sh to ensure that the classpath > includes jna and jna-platform. I updated the pre-release with the new > files and added a note for those who update by copying in the jar: > >> This also means that you need jna-4.2.2.jar and jna-platform-4.2.2.jar >> in your freenet folder. The auto-updater takes care of that for you. >> If you update manually by copying in new jar-files, you need to adapt >> the classpath in wrapper.conf or in run.sh (if you do not use the wrapper). > > Please give it some now hopefully truly final testing: > > https://github.com/freenet/fred/releases/tag/build01481 > > Installers: > → *nix: > https://github.com/freenet/fred/releases/download/build01481/new_installer_offline_1481.jar > → Windows: > https://github.com/freenet/fred/releases/download/build01481/FreenetInstaller-1481.exe > > (add .sig for the PGP signature, the OSX installer will follow once > mrsteveman1 has time). > > Thanks to jamesaxl from #freenet on Freenode for finding this problem on BSD! > > > I’m sorry that this adds another week to the release date. I’m also > still waiting for confirmation by anonymous@6KMY4DVjZ… on FMS whether > the breakage reported was due to missing the jna files. If that’s > resolved, there are no more release blockers I know of. > > > I plan to upload this true true real final release to a new testing key > the next days so we can do another full update cycle test (install 1480, > change the update key, watch freenet update to 1481 over Freenet, > celebrate). And then get this release truly fully done. > > > Sidenote: the statistics site should soon work again. I switched pyProbe > from enum to enum34 to resolve a dependency conflict with the > cryptography package (that needs enum34, but user-installed enum can > override that and cause undecipherable errors). > > > Best wishes, > Arne > > > Arne Babenhauserheide writes: > >> Steve Dougherty writes: >>> Hooray! I was able to verify this build on my Debian Jessie box: >> Nice! Thank you for checking! >> >>> Thank you for your work, both of you! :) >> >> Thank you for verifying the build, and for your work on preparing the >> new keys! There’s a lot of work which finally gets released in this build. >> >>> - Steve >>> >>> PS: This is my first time trying ProtonMail's "sign message" function; >>> assuming it works my ProtonMail key fingerprint is listed here: >>> https://www.asksteved.com/?page_id=2 >> >> My mu4e tells me that your sig was verified. >> >> Best wishes, >> Arne > > > -- > Unpolitisch sein > heißt politisch sein > ohne es zu merken
final final test release of 1481
Hi, I had to add some more fixes to run.sh to ensure that the classpath includes jna and jna-platform. I updated the pre-release with the new files and added a note for those who update by copying in the jar: > This also means that you need jna-4.2.2.jar and jna-platform-4.2.2.jar > in your freenet folder. The auto-updater takes care of that for you. > If you update manually by copying in new jar-files, you need to adapt > the classpath in wrapper.conf or in run.sh (if you do not use the wrapper). Please give it some now hopefully truly final testing: https://github.com/freenet/fred/releases/tag/build01481 Installers: → *nix: https://github.com/freenet/fred/releases/download/build01481/new_installer_offline_1481.jar → Windows: https://github.com/freenet/fred/releases/download/build01481/FreenetInstaller-1481.exe (add .sig for the PGP signature, the OSX installer will follow once mrsteveman1 has time). Thanks to jamesaxl from #freenet on Freenode for finding this problem on BSD! I’m sorry that this adds another week to the release date. I’m also still waiting for confirmation by anonymous@6KMY4DVjZ… on FMS whether the breakage reported was due to missing the jna files. If that’s resolved, there are no more release blockers I know of. I plan to upload this true true real final release to a new testing key the next days so we can do another full update cycle test (install 1480, change the update key, watch freenet update to 1481 over Freenet, celebrate). And then get this release truly fully done. Sidenote: the statistics site should soon work again. I switched pyProbe from enum to enum34 to resolve a dependency conflict with the cryptography package (that needs enum34, but user-installed enum can override that and cause undecipherable errors). Best wishes, Arne Arne Babenhauserheide writes: > Steve Dougherty writes: >> Hooray! I was able to verify this build on my Debian Jessie box: > Nice! Thank you for checking! > >> Thank you for your work, both of you! :) > > Thank you for verifying the build, and for your work on preparing the > new keys! There’s a lot of work which finally gets released in this build. > >> - Steve >> >> PS: This is my first time trying ProtonMail's "sign message" function; >> assuming it works my ProtonMail key fingerprint is listed here: >> https://www.asksteved.com/?page_id=2 > > My mu4e tells me that your sig was verified. > > Best wishes, > Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken signature.asc Description: PGP signature
