Update to the two top tasks. Arne Babenhauserheide writes: > These are the two top tasks (they came out on top in every evaluation): > > > (1) Title: *Darknet invitation bundles* > Description: Adding a single use node reference to an installer > executable. People could hand out the installer executable to > their friends to allow them to connect by Darknet instantly. See > - https://bugs.freenetproject.org/view.php?id=166#c11290 > (an overview of the requirements and options for invites) and > - https://bugs.freenetproject.org/view.php?id=1342 > ("create a bundle installer") > Estimated cost: 1 to 1.125 weeks (~ 1000$ to 1250$)
toad wrote: > IMHO this is more work because making it work well pulls in a lot of > other stuff, e.g. FOAF connections, using your well-connected peer to > answer your invites, etc. Obviously we should do it but somebody needs > to look carefully at the scope of the problem. We can do it in pieces, > but you've already proposed at least two of the components above. That’s true. Also the cost estimate should at least include essential components. I actually already wrote that in my last evaluation in december, but forgot to add it this time: > - Darknet invitation bundles (a: 1.125, g: 1.0) > - Single use node references (a: 2.4, g: 2.0) (required for implementation) - https://emu.freenetproject.org/pipermail/devl/2016-December/039428.html So the cost estimate for task 1 would rather be 3 to 3.525 weeks ($3000 to $3525). > (2) Title: *Fix the installers* > Description: Fix windows installers first, then add packages for > linux. See > - https://bugs.freenetproject.org/view.php?id=1276 and > - https://bugs.freenetproject.org/view.php?id=1275 and > - https://bugs.freenetproject.org/view.php?id=5892 and > linked issues. > Estimated cost: 0.5 to 2 weeks (~ 500$ to 2000$) After discussion on IRC, the main breakage in the windows installers seems to be 64 bit Java and the wrapper. Therefore the requirement here would be "Freenet installs and runs cleanly with 64 bit and 32 bit Java on Windows while using the wrapper". This will likely require finishing and releasing the work on compiling the wrapper for Windows 64bit. Providing separate installers for 32bit and for 64bit could be acceptable. Linux packages require additional maintenance for which we might not have the resources at the moment. Since java-based installers for Linux work, packages need not be part of the task. > Can we put up offers for these, using the cost estimates as payment? > Are the descriptions here sufficient? > > > As success condition for payment I’d use: > > (1) A pull-request is accepted which adds a single-click option in the > web interface which creates a bundle with installers for Windows, > MacOS and *nix. These installers must be preconfigured to > automatically connect via darknet to the node on which the bundle > was created. This will require single-use connection-tokens with which only the first person who uses the installer can connect to the node which created the installer. > (2) Pull-requests are accepted which identify problems in the > windows-installer and resolve them. This includes porting the > wrapper to a 64bit JVM. > > Did I miss something required to address the tasks? Best wishes, Arne _______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
