Re: Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)

2012-08-11 Thread Roland Winkler
On Sat Aug 11 2012 Sriram Karra wrote:
 Further, throwing them away could just be stashing the fields
 into the notes list.

Certainly. But if you then decide to give v3 a second try, you will
not get back what you had before.

 Just for the record, can you tell us about all the changes in the
 file format? I know:
 
 - a new field called affix now appears as the third field of the record
 - organizations is a list instead of a ';' delimited string.

The above is correct.

Also, there is one Notes field in each record which usually holds
the list of note fields, which in turn are cons pairs (KEY . VALUE).
Some pieces of BBDB v2 also allowed the Notes field to be a single
string, instead of the list of cons pairs. I do not know whether
this was just a historical thing left over in the code, or whether
this was still a fully supported feature. V3 definitely relies on
having a list of cons pairs (KEY . VALUE) in the Notes field and
bbdb-migrate converts a single Notes string accordingly. Obviously,
going back to a Notes field with a single string would break pretty
much everything.

For the other things, someone could write a function bbdb-unmigrate
to go back to v2 and post it here.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)

2012-08-10 Thread Sriram Karra
On Mon, Jul 2, 2012 at 2:56 AM, Roland Winkler wink...@gnu.org wrote:


  I would like to capture this question and a summary of your
  answers as a FAQ on the updated project site on sourceforge.

 Thanks a lot, that will be helpful



I have updated site (http://bbdb.sourceforge.net/) with a note pointing to
Savannah.  That done,  I now feel it is best to just leave that site alone.
Any FAQ etc. should reside on the Savannah site. Thoughts?

-Karra
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

Re: Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)

2012-08-10 Thread Roland Winkler
On Fri Aug 10 2012 Sriram Karra wrote:
 I have updated site (http://bbdb.sourceforge.net/) with a note
 pointing to Savannah.  That done,  I now feel it is best to just
 leave that site alone. Any FAQ etc. should reside on the Savannah
 site. Thoughts?

Thanks a lot for doing this. Two things:

- My first name is Roland

- I suggest to replace the 2nd paragraph by something like the
  following

  It is important to note that at the moment v3 can import a BBDB
  database from v2. Also, most concepts of the user interface have
  been preserved (plus many new concepts have been added to make
  BBDB yet more powerful). However, beyond this point v3 is not
  backwards compatible with v2. A database from v3 cannot be used
  with v2. Also, the names of many commands and user variables have
  been changed and v3 currently does not support Xemacs.
  
  Therefore, the rest of the page below will be kept around in
  state at least till support for Xemacs has been addressed
  somehow.

You also mentioned backward compatibility that should / could be
addressed. I do not know what this could mean more specifically.
(I do not expect it will ever be feasible / useful to provide a
compatiblity mode that allows a user of v2 to switch to v3 without
worrying about anything.)

Roland

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)

2012-08-10 Thread Sriram Karra
On Fri, Aug 10, 2012 at 11:15 PM, Roland Winkler wink...@gnu.org wrote:


 Thanks a lot for doing this. Two things:

 - My first name is Roland


Ah, indeed :)


 - I suggest to replace the 2nd paragraph by something like the
   following


I have rewritten along lines you have suggested and pushed it. Please take
a look.


 You also mentioned backward compatibility that should / could be
 addressed. I do not know what this could mean more specifically.
 (I do not expect it will ever be feasible / useful to provide a
 compatiblity mode that allows a user of v2 to switch to v3 without
 worrying about anything.)


Backwards compatibility for me would mean a few distinct things:

1. Will my old customizations work with the new code

2. If I use BBDB v3 and don't like it can I go back to v2

v3 fails the test on both counts.

#1 might never get fixed given the direction we've headed.

#2 can and should get fixed. I find it quite amusing in fact, the
bbdb-migrate stuff has always had the hooks to downgrade to an earlier file
format version - until now, i.e., when it is needed more than ever before
really :) One of these days...

-Karra
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

Re: Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)

2012-08-10 Thread Roland Winkler
On Sat Aug 11 2012 Sriram Karra wrote:
 I have rewritten along lines you have suggested and pushed it. Please take a
 look.

Looks fine to me, thanks,

 Backwards compatibility for me would mean a few distinct things:
 
 1. Will my old customizations work with the new code
 #1 might never get fixed given the direction we've headed.

My intention has been to make the concepts more transparent. So yes,
making old customizations work in an automated would be very
difficult.

 2. If I use BBDB v3 and don't like it can I go back to v2
 #2 can and should get fixed. I find it quite amusing in fact, the
 bbdb-migrate stuff has always had the hooks to downgrade to an
 earlier file format version - until now, i.e., when it is needed
 more than ever before really :) One of these days...

Well, the new format allows you to do things you could not do with
the old format. So going back to v2 is only possible by throwing
away the incompatible extensions in the format of v3. I do not
consider this a satisfactory procedure.

Of course, anyone switching from v2 to v3 should first make a copy
of his or her old database. Then if things do not work out for
whatever reason you can fully go back.

Roland

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)

2012-07-01 Thread Roland Winkler
On Thu Jun 21 2012 Sriram Karra wrote:
 Perhaps now is a good time for me to ask this question that's been
 on my mind for a while: Apart from an extensive code cleanup, are
 there any other things to look forward to with your upcoming
 release? This is particularly important given the level of
 breakage in user customization and general backward compatibility
 (relative to 2.x).

Of course, once BBDB v3 is released, users need to be able to rely
on the new design. For me, this has been a major reason that delayed
an earlier release: Turning BBDB around once must be enough. So I
wanted to do this carefully.

By now, unless someone on this list brings up problems with BBDB v3
that remained unnoticed so far, I do not have plans to further
modify the code of BBDB (except for fixing docstrings that could
still be buggy / incomplete). In particular, I do not want to
introduce any additional incompatible changes beyond the ones
present in the current code.

 I would like to capture this question and a summary of your
 answers as a FAQ on the updated project site on sourceforge.

Thanks a lot, that will be helpful!

Roland

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: Fwd: BBDB development shifted from sourceforge to savannah

2012-07-01 Thread Roland Winkler
On Thu Jun 21 2012 Sriram Karra wrote:
 I now have ownership of the BBDB project on sourceforge; I will bring the
 content up to date over the next few weeks as I figure out how to manage that
 site.

Thanks a lot for working on this.

Roland

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Why V3 (Was: Re: Fwd: BBDB development shifted from sourceforge to savannah)

2012-06-20 Thread Sriram Karra
On Wed, Jun 20, 2012 at 1:17 AM, Roland Winkler wink...@gnu.org wrote:


 PS: I hope that in a few days I can submit my recent work on BBDB. I
 just need to summarize things in the ChangeLog.


Great! Perhaps now is a good time for me to ask this question that's been
on my mind for a while: Apart from an extensive code cleanup, are there any
other things to look forward to with your upcoming release? This is
particularly important given the level of breakage in user customization
and general backward compatibility (relative to 2.x).

I would like to capture this question and a summary of your answers as a
FAQ on the updated project site on sourceforge.

-Karra
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

Re: Fwd: BBDB development shifted from sourceforge to savannah

2012-06-19 Thread Roland Winkler
On Mon Jun 18 2012 Sriram Karra wrote:
 This is the response of the SF team. Would you like to take
 ownership of the page at bbdb.sourceforge.net? If yes, send me
 your sourceforge user name. Otherwise I can take temporary
 ownership of that page and bring it 'up to date' to the extent I
 understand the situation.

For me that's too much to worry about. If you and/or someone else
could handle this, I'd much appreciate it.

Roland


PS: I hope that in a few days I can submit my recent work on BBDB. I
just need to summarize things in the ChangeLog.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: Fwd: BBDB development shifted from sourceforge to savannah

2012-06-19 Thread Sam Steingold
 * Roland Winkler jvax...@tah.bet [2012-06-19 14:47:41 -0500]:

 PS: I hope that in a few days I can submit my recent work on BBDB. I
 just need to summarize things in the ChangeLog.

how about my patches of a few months back?

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000
http://www.childpsy.net/ http://americancensorship.org http://memri.org
http://www.memritv.org http://thereligionofpeace.com http://iris.org.il
Professionalism is being dispassionate about your work.


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/