Cory Nelson wrote:
> I've created a list here, it should be active within the next 24hr.
Thanks, I´ve suscribed. Until we have all subscribed, we should keep the
current CC list at BCC (I don´t know which eMails are private and
should not appear in the list archive. If anyone is concerned about
his privacy he should tell us!!!
> On Sun, Jul 12, 2009 at 6:29 AM, Enrico<ebutera@...> wrote:
>> Since we have the "blessing" from peerguardian (Cory) i think the name
>> should be one of the "pgld, pglgui..." or "peerguardiand....".
Although we have no full consensus about that, I agree to go with
"PeerGuardian Linux" and
and probably pgl as wrapper with options for the others.
I would have loved it, if we were all behind the naming, but IMHO it´s
not worth to spend weeks on finding a full consensus. If anyone
opposes this, please say it NOW. Remember, I contacted you, because I
saw all of you doing great work, and I´d really would like to have
all of you in! And for working on this project, it is essential to
have fun, not being obliged to do anything.
As forum and for user support we can use the Peerguardian Linux forum:
>> Right now i wouldn't try to make a single cross platform app, imho it
>> would be more work that we can handle right now. We should just decide
>> the name, choose the daemon to use (it seems nfblock is the first
>> candidate) and then decide about more technical stuff (dbus, splitting
>> the parser...), a better place place to discuss all of this should be
>> a mailing list, something like peerguardian-linux-devel on
So let´s go!
Everybody sign up at sourceforge and send your user name to phrosty,
so that he can give you commit access for the svn repository.
I´d suggest the following procedure:
1. ) Every author checks his project in (Jindrich nfblock, I do
blockcontrol and João his nfblock GUI)
2.) Others commit their changes they have already done. Especially
João his dbus work on nfblock
3.) We patch the source to use PeerGuardian Linux and pgl... naming
4.) Real development can start. We have to talk about (or just do):
general layout (see the blocker&parser discussion), documentation of
interfaces, common installer, dbus, logger, GUI, ...). When
discussions are needed, I´d sugggest separate threads in the new
However I´m not sure how we really continue with the GUI. Although
João told us that he has just started his own pet project, I am quite
sure that he made some really good progress with dbus for nfblock. So
I think it would be really good to have this code! For the further
development (AFAIK João uses python/gtk, and Jim used C++/Qt for
mobloquer) all interested persons should raise their voices.
Command line interface: I will check in blockcontrol this week, after
making a final release with my current work. When the project is
running I will drop moblock and nfblock support.
>> Since 90% of what we need is already developed we will soon have a
>> release 1.0 feature complete (daemon, gui, scripts, packages...).
>> After that we can start thinking about THE single app Peerguardian.
We should start with "PeerGuardian Linux 2.0", bacause there´s already the old
Then "PeerGuardian 3.0" would be reserved for the all-platform PeerGuardian.