[freenet-dev] Freenet Summer of Code wrap-up
Matthew Toseland wrote: > Apologies for being the absolute last wrap-up! This year went really well, we > had 5 students, and they all (more or less) deserved their passes. We had a > much stronger selection process than in the first 2 years, requiring some > demonstration in the form of code: a new feature or a bugfix. So even though > most of the students were completely new to us, mostly they did pretty well. > One of our students had a work conflict, but this was resolved satisfactorily. > > For the Googlers reading this, Freenet is an anonymous peer to peer system > with support for forums, browsing the internal web, filesharing etc, with a > focus on security and the option of running in "darknet" or friend-to-friend > mode. It is intended (at least by me) for people in hostile environments > (China, Iran etc) to express themselves freely, but it is currently mostly > used in the West by geeks, filesharers, etc. > > infinity0 and mikeb worked together on a new searching plugin, which we have > now deployed. infinity0's work was primarily on a new index format (which > works, but the spider needs more work), and on distributed indexing (which > doesn't yet), and mikeb mainly worked on improving the user interface and > adding essential features (simple non-infringing page ranking algorithm, > booleans, phrase matches etc). kurmi worked on new filtering code for various > formats, particularly a vastly improved CSS filter, which needed considerable > work to sort out all the parsing perversities but is now merged (Freenet has > to be very careful not to send anything to the browser that might give the > user's IP away via a web-bug). ljb worked on more friend-to-friend > functionality, his work is included in current builds. sashee worked on > making the web interface more dynamic, including solving a long-running > problem with image loading blocking the browser (freenet has quite high > latency!), using Google Web Toolkit; this branch has not yet been merged, but hopefully will be inside the next 6 months or so, it needs some tuning and debugging for slow browsers. > > Some of our students achieved less than expected IMHO but in more cases there > was a lot more work involved in the project than I expected, and the students > did really well. I have talked to most of them in the last month, well after > the programme was finished, and hopefully some of them will continue to > contribute at least occasionally. Best year yet, many thanks to Google! /me *claps* - Zero3
[freenet-dev] Update on getting rid of emu
bo-le wrote: > Am Samstag, 31. Oktober 2009 17:28:38 schrieb Zero3: >> Matthew Toseland wrote: >>> On Friday 30 October 2009 17:10:02 Zero3 wrote: Matthew Toseland wrote: > If this line of reasoning is correct, we need to choose an > end-user-oriented issue tracker or forums system (either way ideally > gratis and hosted) to complement Uservoice. Suggestions? It would make sense to find a tracker that both users and devs can use. Saves the overhead of moving things from e.g. a forums system to a bug tracker. >>> Is it possible? Is Trac something that end users can use? >> I don't think Trac is the perfect solution (not as it is right now, at >> least), but it seems much better than our current solution (Mantis + >> Wikka Wakka). >> >> Pidgin (see http://developer.pidgin.im/) has an interesting >> implementation directly into their website. The bar at the top contains >> easy access to some of the most used features: Wiki (starts here), >> Timeline (aka "what's new?"), Roadmap and Search. It is possible to >> create other things like "New ticket" and "Browse source" it seems, if >> you look at the official trac site (http://trac.edgewall.org/). >> >> I don't have any personal experience with Trac though. Perhaps someone >> else around here has, and can give us some recommendations? >> > this may fit our needs better then trac: http://basieproject.org/ A third option is Google Project Hosting (we are already using some Google-thingy for downloads I think?). Example here: http://code.google.com/p/support/issues/list The interface seems quite simple, and has both bug tracker and wiki. I'm quite fond of the "starring" of bugs. It's basically the possibility for users to mark the bugs they are specially interested in, which also gives the developers the possibility to focus on the most popular bugs. This might be able to supercede uservoice too (which is quite prone to spam as no user verification of votes are done). - Zero3
Re: [freenet-dev] Update on getting rid of emu
bo-le wrote: Am Samstag, 31. Oktober 2009 17:28:38 schrieb Zero3: Matthew Toseland wrote: On Friday 30 October 2009 17:10:02 Zero3 wrote: Matthew Toseland wrote: If this line of reasoning is correct, we need to choose an end-user-oriented issue tracker or forums system (either way ideally gratis and hosted) to complement Uservoice. Suggestions? It would make sense to find a tracker that both users and devs can use. Saves the overhead of moving things from e.g. a forums system to a bug tracker. Is it possible? Is Trac something that end users can use? I don't think Trac is the perfect solution (not as it is right now, at least), but it seems much better than our current solution (Mantis + Wikka Wakka). Pidgin (see http://developer.pidgin.im/) has an interesting implementation directly into their website. The bar at the top contains easy access to some of the most used features: Wiki (starts here), Timeline (aka what's new?), Roadmap and Search. It is possible to create other things like New ticket and Browse source it seems, if you look at the official trac site (http://trac.edgewall.org/). I don't have any personal experience with Trac though. Perhaps someone else around here has, and can give us some recommendations? this may fit our needs better then trac: http://basieproject.org/ A third option is Google Project Hosting (we are already using some Google-thingy for downloads I think?). Example here: http://code.google.com/p/support/issues/list The interface seems quite simple, and has both bug tracker and wiki. I'm quite fond of the starring of bugs. It's basically the possibility for users to mark the bugs they are specially interested in, which also gives the developers the possibility to focus on the most popular bugs. This might be able to supercede uservoice too (which is quite prone to spam as no user verification of votes are done). - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
Re: [freenet-dev] Freenet Summer of Code wrap-up
Matthew Toseland wrote: Apologies for being the absolute last wrap-up! This year went really well, we had 5 students, and they all (more or less) deserved their passes. We had a much stronger selection process than in the first 2 years, requiring some demonstration in the form of code: a new feature or a bugfix. So even though most of the students were completely new to us, mostly they did pretty well. One of our students had a work conflict, but this was resolved satisfactorily. For the Googlers reading this, Freenet is an anonymous peer to peer system with support for forums, browsing the internal web, filesharing etc, with a focus on security and the option of running in darknet or friend-to-friend mode. It is intended (at least by me) for people in hostile environments (China, Iran etc) to express themselves freely, but it is currently mostly used in the West by geeks, filesharers, etc. infinity0 and mikeb worked together on a new searching plugin, which we have now deployed. infinity0's work was primarily on a new index format (which works, but the spider needs more work), and on distributed indexing (which doesn't yet), and mikeb mainly worked on improving the user interface and adding essential features (simple non-infringing page ranking algorithm, booleans, phrase matches etc). kurmi worked on new filtering code for various formats, particularly a vastly improved CSS filter, which needed considerable work to sort out all the parsing perversities but is now merged (Freenet has to be very careful not to send anything to the browser that might give the user's IP away via a web-bug). ljb worked on more friend-to-friend functionality, his work is included in current builds. sashee worked on making the web interface more dynamic, including solving a long-running problem with image loading blocking the browser (freenet has quite high latency!), using Google Web Toolkit; this branch has not yet been merged, but hopefully will be inside the next 6 months or so, it needs some tuning and debugging for slow browsers. Some of our students achieved less than expected IMHO but in more cases there was a lot more work involved in the project than I expected, and the students did really well. I have talked to most of them in the last month, well after the programme was finished, and hopefully some of them will continue to contribute at least occasionally. Best year yet, many thanks to Google! /me *claps* - Zero3 ___ Devl mailing list Devl@freenetproject.org http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
