Re: Getting rid of emu: an option

On Sunday 31 May 2009 05:26:33 Juiceman wrote:
> On Sat, May 30, 2009 at 3:24 PM, Matthew Toseland
> <toad@...> wrote:
> > On Saturday 30 May 2009 11:55:17 Matthew Toseland wrote:
> >> We need to get rid of emu. It costs us a significant amount of money and we don't seem able to
cost-effecitvely administer it.
> >>
> >> Basically what we need:
> >> - PHP scripts. The website is built with PHP.
> >
> > But it could easily be all static.
> >
> >> - Database-backed PHP for MANTIS. I don't think we should get rid of MANTIS.
> >
> > The consensus is we should get a whole new bug tracker and dump all the old issues, maybe run a copy on a
developer's machine for checking old bugs. IMHO getting rid of the bug database would be a bad thing and
lead to significant work in migration, but ian, nextgens and sdiz think otherwise.
> >
> >> - SSL. We need to serve checksums and signatures through SSL, although big files will generally be
served through HTTP. It would be nice to serve the installer through SSL if we have a huge traffic limit,
since code signing certs are expensive, on the other hand if we get cheaper hosting we can probably afford
to buy a code signing cert with a fraction of the money saved...
> >> - IMAP accounts ideally, but at least aliases.
> >
> > - Wiki. We need a wiki. There are free wiki providers. Migrating our existing english language wikka wiki
will be some work, migrating the french mediawiki wiki will be less work.
> >
> > - Mailing lists. Berlios does this, there are also free mailman sites such as:
> > http://www.glowhost.com/mailman.php
> >

About the website

Hello all,

about three weeks ago I had a HCI webproject to do. 
The subject was : improve an existant website (well, I'm not 100% sure that it 
was the subject, but that what we've done)

I convinced the three other people who worked with me to work on the freenet 
website. It was a small project though (3 hours with a teacher in the room, + 
3 hours max of personal time), so we didn't go far.

But maybe some of what we've done could be usefull for the project.

Here is the copy/paste of what we've done :

--------------------------------------------------------------------------------------------------
Objective of the new website: 
- To improve the existing navigation controls of freenetproject.org
- To improve it's structural presentation of information on home page

Aim of the web-site:
- to present the software product and provide support
- documentation and tools to users and developers to allow them to use and 
contribute to the software.

Problems:
The problems of current website http://freenetproject.org :
- irrelevant information for homepage: mainly financial status, we don't know 
what freenet is
- too many items in left navigation menu and not really well structured
- documentation section where subsections do not have direct hyperlinks - its 

Re: About the website

Hello!

I wish you get a good grade for your work:)

My first-time thoughts:
- I really like the background, it makes the whole site much more modern.
- The 80% width feels boxed. It should be 90-95%
- When navigating, I more like to see all the submenus, not just when
clicked on a heading. So they should appear when hovering with the
mouse
- I dont like the shadows on the Download Freenet image. It makes it
harder to read slightly
- I agree with the financial status to the main page
- The menu tree is logical

I hope my review helps at some degree

sashee

On Mon, Jun 1, 2009 at 2:24 AM, Clément <cvollet@...> wrote:
> Hello all,
>
> about three weeks ago I had a HCI webproject to do.
> The subject was : improve an existant website (well, I'm not 100% sure that it
> was the subject, but that what we've done)
>
> I convinced the three other people who worked with me to work on the freenet
> website. It was a small project though (3 hours with a teacher in the room, +
> 3 hours max of personal time), so we didn't go far.
>

"cover more codes" : 3932e32b68815e8322d43f351221b368d297f0c0

HUH??? The below is invalid, no?

commit 3932e32b68815e8322d43f351221b368d297f0c0
Author: Daniel Cheng (鄭郁邦) <j16sdiz <at> freenetproject.org>
Date:   Mon Jun 1 16:39:21 2009 +0800

    LongTermPushPullTest: Use filename in test, so we can cover more codes :)

diff --git a/src/freenet/node/simulator/LongTermPushPullTest.java b/src/freenet/node/simulator/LongTermPushPullTest.java
index 084bb1e..ec81a50 100644
--- a/src/freenet/node/simulator/LongTermPushPullTest.java
+++ b/src/freenet/node/simulator/LongTermPushPullTest.java
 <at>  <at>  -120,7 +120,7  <at>  <at>  public class LongTermPushPullTest {
                        for (int i = 0; i <= MAX_N; i++) {
                                Bucket data = randomData(node);
                                HighLevelSimpleClient client = node.clientCore.makeClient((short) 0);
-                               FreenetURI uri = new FreenetURI("KSK <at> " + uid + "-" + dateFormat.format(today.getTime()) +
 "-" + i);
+                               FreenetURI uri = new FreenetURI("KSK <at> " + uid + "-" + dateFormat.format(today.getTime()) +
 "-" + i + "/file");
                                System.out.println("PUSHING " + uri);

                                try {
 <at>  <at>  -167,7 +167,7  <at>  <at>  public class LongTermPushPullTest {
                                Calendar targetDate = (Calendar) today.clone();
                                targetDate.add(Calendar.DAY_OF_MONTH, -((1 << i) - 1));

-                               FreenetURI uri = new FreenetURI("KSK <at> " + uid + "-" + dateFormat.format(targetDate.getTime
()) + "-" + i);
+                               FreenetURI uri = new FreenetURI("KSK <at> " + uid + "-" + dateFormat.format(targetDate.getTime

Re: Getting rid of emu: an option

On Saturday 30 May 2009 16:37:15 Ian Clarke wrote:
>
> I like this idea.  I think it is clear that there is a lot of cruft in
> Mantis, open bugs that are no-longer relevant etc.  Cleaning house
> would be useful.
>
> Ian.

I am strongly against getting rid of the bugtracker contents if that is what 
you guys mean.

If we were supposed to rate our development process in terms of "best 
practices", deleting the bugtracker content would probably be the WORST 
practice which anyone can think of, besides deleting all documentation.

I think we should do the following:
1. (FIRST!) clean up mantis
2. migrate to a different bug tracker.

As for cleaning up: Resolving about 10 obsolete issues per day should be 
enough to get mantis quite empty soon, I've suggested that some days ago on 
devl.

Personally, I use mantis for having a overview of all WoT/Freetalk tasks which 
need to be finished before the next release, it IS very useful to me.

xor

Re: "cover more codes" : 3932e32b68815e8322d43f351221b368d297f0c0

On Mon, Jun 1, 2009 at 6:44 PM, Matthew Toseland
<toad@...> wrote:
> HUH??? The below is invalid, no?

ya, invalid.
reverted before reading this email.

Re: Getting rid of emu: an option

On Mon, Jun 1, 2009 at 7:15 PM, xor <xor@...> wrote:
> On Saturday 30 May 2009 16:37:15 Ian Clarke wrote:
>>
>> I like this idea.  I think it is clear that there is a lot of cruft in
>> Mantis, open bugs that are no-longer relevant etc.  Cleaning house
>> would be useful.
>>
>> Ian.
>
> I am strongly against getting rid of the bugtracker contents if that is what
> you guys mean.
>
> If we were supposed to rate our development process in terms of "best
> practices", deleting the bugtracker content would probably be the WORST
> practice which anyone can think of, besides deleting all documentation.
>
> I think we should do the following:
> 1. (FIRST!) clean up mantis
> 2. migrate to a different bug tracker.
>
> As for cleaning up: Resolving about 10 obsolete issues per day should be
> enough to get mantis quite empty soon, I've suggested that some days ago on
> devl.

I guess you may have awared: Lots of the open bugs are undecidable by you or me.

For example, https://bugs.freenetproject.org/view.php?id=2669#c5091
keep asking if this is fixed, yet no reply.

Closing 10 issues per day is too optimistic.

Re: Getting rid of emu: an option

We had a policy where I worked for some time, that if a bug is
inactive for some time, and cannot be reproduced by the developer,
will be force closed.
This would be applicable to freenet, because if a problem still
exists, users will open a ticket, you cannot expect that users will
search for an open ticket before opening a new one.

sashee

On Mon, Jun 1, 2009 at 1:22 PM, Daniel Cheng
<j16sdiz+freenet@...> wrote:
> On Mon, Jun 1, 2009 at 7:15 PM, xor <xor@...> wrote:
>> On Saturday 30 May 2009 16:37:15 Ian Clarke wrote:
>>>
>>> I like this idea.  I think it is clear that there is a lot of cruft in
>>> Mantis, open bugs that are no-longer relevant etc.  Cleaning house
>>> would be useful.
>>>
>>> Ian.
>>
>> I am strongly against getting rid of the bugtracker contents if that is what
>> you guys mean.
>>
>> If we were supposed to rate our development process in terms of "best
>> practices", deleting the bugtracker content would probably be the WORST
>> practice which anyone can think of, besides deleting all documentation.
>>
>> I think we should do the following:
>> 1. (FIRST!) clean up mantis
>> 2. migrate to a different bug tracker.

French translation

some french translation

BookmarkManager.defaultBookmarks=Marque page par défaut
DarknetAddRefToadlet.explainBox1=Vous pouvez améliorer la sécurité de Freenet en vous
connectant à vos amis. Il s'agit de personnes que vous connaissez qui utilisent également
Freenet. Il peux s'agir de connaissance en ligne, mais n'ajoutez pas de connexions avec un total inconnu,
ceci ne va pas améliorer la sécurité et va causer d'avantage de problèmes au réseau si un
grand nombre de personnes agissent ainsi. Lorsque vous aurez suffisamment d'amis, au moins 5 qui sont en
ligne en même temps, vous pourrez augmenter votre niveau de sécurité réseau au maximum, et
ne vous connecter qu'à des amis, ceci est appelé le "mode Darknet". Ceci rend beaucoup plus
difficile à un attaquant de simplement savoir que vous utilisez Freenet, et rend la plupart des
attaques contre l'anonymat beaucoup plus difficile à réaliser.
DarknetAddRefToadlet.explainBox2=Pour pouvoir vous connecter à un ami vous avez besoin
d'échanger avec lui les références de vos nodes. Une référence de node est un petit
fichier qui contient les informations dont a besoin votre ami pour que sa node se connecte à la votre.
Vous devez ajouter sa référence de node et il doit ajouter la votre, pour que les deux nodes puissent
se connecter entre elles. Voyez ci-dessous pour votre référence de node.
DarknetAddRefToadlet.explainBoxTitle=Pourquoi devriez vous vous connecter à des amis utilisant Freenet
DarknetAddRefToadlet.title=Connexion à un ami
DarknetConnectionsToadlet.numOfResults=Nombre de résultats
DarknetConnectionsToadlet.peersClearAllowLocal=Supprimer l'autorisation de l'adresse locale sur
les peers séléctionnés.
DarknetConnectionsToadlet.peersClearBurstOnly=Désactivé "BurstOnly" sur les peers sélectionnées
DarknetConnectionsToadlet.peersClearDontRoute=Supprimer "ne pas router" sur les peers sélectionnés
DarknetConnectionsToadlet.peersClearIgnoreSourcePort=Supprimer "ignorer le port source" sur les
peers sélectionnés
DarknetConnectionsToadlet.peersClearListenOnly=Supprimer "écouter uniquement" sur les peers sélectionnés

Re: Getting rid of emu: an option

xor skrev:
> On Saturday 30 May 2009 16:37:15 Ian Clarke wrote:
>> I like this idea.  I think it is clear that there is a lot of cruft in
>> Mantis, open bugs that are no-longer relevant etc.  Cleaning house
>> would be useful.
>>
>> Ian.
> 
> I am strongly against getting rid of the bugtracker contents if that is what 
> you guys mean.
> 
> If we were supposed to rate our development process in terms of "best 
> practices", deleting the bugtracker content would probably be the WORST 
> practice which anyone can think of, besides deleting all documentation.
> 
> I think we should do the following:
> 1. (FIRST!) clean up mantis
> 2. migrate to a different bug tracker.
> 
> As for cleaning up: Resolving about 10 obsolete issues per day should be 
> enough to get mantis quite empty soon, I've suggested that some days ago on 
> devl.
> 
> Personally, I use mantis for having a overview of all WoT/Freetalk tasks which 
> need to be finished before the next release, it IS very useful to me.
> 
> xor

I have to more or less completely agree with xor. Removing all the old 
bugs seems like "running away from all the problems" (literally, kind of).