Google Summer of Code didn't work out for us, but maybe we can have a
Freenet Summer of Toad? It's not certain yet, but Matthew might be
interested in working 35-hour weeks over the summer for FPI. He says he
wants at least $6k for 8 weeks but preferably $10k for 12 weeks. Paying
this while maintaining current operations will require a fundraiser. Are
people interested in doing this?

If we go through with it we'd put a fundraising bar on the website and
count subsequent donations toward it. It might be good to have a mark
both at $6k as the minimum and $10k as the entire summer.

Last summer purge-db4o coming into review all at once was a formative
experience for the community. We've agreed that development must now be
put up for review and merged in much, much smaller pull requests along
the way.

What would we want to direct this development time toward? My opinion is
that more code / features is not what Fred needs most right now. I'd
like to ask that Matthew document plugin APIs and work on packaging:
things like splitting freenet-ext, making a Debian / Ubuntu package, and
maybe even creating an official distro package repo in Freenet. This is
because for those utilities that already exist, Freenet is pretty
effective, but I have seen many developers give up when they see the
lack of documentation, and the lack of packages makes it harder to
install and harder to depend on. There are unofficial packages for Arch
and Gentoo, and freenet-ext being monolithic makes packaging Freenet harder.

Documenting the API will also make it clear what is considered API, and
reviewing it can then suggest improvements. If documentation is
completed it could get as far as developing improvements to the plugin
API. It is mandatory that any changes be backwards-compatible.

Thoughts?

- Steve

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20150409/4cd6d5f2/attachment.sig>

Reply via email to