Re: Minutes 11 May
On 05/11/2015 03:53 PM, Nic Bernstein wrote:
lirecyrus.{io|com|org} are all available
Opps, typo. I meant to write that librecyrus.{io|com|org} are all
available.
-nic
--
Nic Bernstein n...@onlight.com
Onlight, Inc. www.onlight.com
1442 N Farwell Ave., Suite 600v. 414.272.4477
Milwaukee, Wisconsin 53202
<>
Re: Minutes 11 May
On 05/11/2015 08:52 AM, Bron Gondwana wrote:
Website - the situation with cyrusimap.org and cyrus.foundation is
awfully confusing. Somebody needs to take ownership for uncrapping this.
Nobody put their hand up yet, so we'll see if it happens by Thursday or
I might start appointing people;)
I've already spoken up about trying to do something about this, but to
no avail. I'll volunteer to at the very least uncrap things a bit.
However, the current site has some problems with the authentication
system. I have credentials on the site, but had lost/forgotten the
password. I used the password reset facility, but now when I log in I
am asked to change my password, and that process always results in this
message:
There seems to be a problem with your login session; this action has
been canceled as a precaution against session hijacking. Go back to
the previous page, reload that page and then try again.
So I'm stuck. If someone can fix this, fine; please do so. If not, I
can register again, but then need someone with authority to authorize my
new account, and I'll probably be asked to update my password, and...
(wash, rinse, repeat).
Speaking of naming - cyrusfoundation ==http://www.cyrusfoundation.org/
== not us. We need a new name. Cyrus IMAP Foundation -> two imappy.
Cyrus Mail Foundation -> not enough cal/carddav. "Cyrus Connect" -
doesn't someone already own "* Connect"?
FWIW, both cyrus-connect.com and cyrus-connect.org are available, as are
the unhyphenated versions, cyrusconnect.{com|org}.
But maybe. reCyrus /
recyrus.{io|com|org} are all available
librecyrus
lirecyrus.{io|com|org} are all available
Okay, putting aside simple whois searches and getting back to work now.
-nic
PS - Great to meet folks at OpenSuSE and Kolab conferences last week. :-)
/ "recycle". Hmm... Great names greatly appreciated. Make
your mark here, but don't make it a trademark that somebody else has
already... yeah, that.*sigh*. All the good ones are taken or insane
(or both).
--
Nic Bernstein n...@onlight.com
Onlight, Inc. www.onlight.com
1442 N Farwell Ave., Suite 600v. 414.272.4477
Milwaukee, Wisconsin 53202
<>
Minutes 11 May
So I haven't written up notes for a while, but we've been ticking
along doing our regular meetings every Monday (11am GMT) and Thursday
(midday GMT).
That means the next one is 2015-05-14T12:00:00Z at:
https://plus.google.com/hangouts/_/g4xnqjjb5zvomzeb4kqvja3fz4a
Freenode #cyrus
Today's meeting had: Chris, Conrad, Ellie, Ken, Nicola, Simon and Bron
(in the alphabetical order that the pictures at the bottom of Hangouts
are for me)
Congratulations Ellie for releasing 2.5.2. Man it took a long time.
Next time is going to be heaps faster because we have a process sorted,
so get your small bugfixes in so we can knock out a whole bunch of them
and get the process really smooth.
Speaking of processes - we're still getting assert failures on shutdown
in httpd at FastMail when the kill_user_connections script sends SIGQUIT
to a user's processes (as happens on password change and for a few other
reasons). It's caused by auth_{cal|card}davdb. This database stays
open as an optimisation in case the process handles another request for
the same user, so we can either always close it, or just shut the
database if given a sigquit. Bron and Ken are both going to look into
this one, because there's nothing like doubling up on work ;)
I spoke (mixing third and first persons like this email) about rewriting
the entire cyrus.index and about 5 other custom formats as a single per-
user (well, per nameroot) SQLITE database or similar. Downside might be
worse performance, the killer win for Cyrus has been the fact that an
O(N) algorithm with a really tiny constant can be a lot faster than a
O(log N) algorithm with a heaps higher constant up to quite large N,
particularly once you take cache effects and readahead into account. So
we're going to need to do some benchmarks here.
Sieve: Ken has reached out James Cassell to help get his pending
variables and other sieve patches committed to master. We have been lax
in dealing with these, which is bad - because we love other people doing
good work, and we need to encourage it! Thanks James.
Conrad - has been looking at T80 - compile errors on some Centos with a
compiler which #defines 'const' away because the compiler doesn't
support it. We're just going to ditch that, if your compiler doesn't
support const, get a new compiler. We already agreed to require c99
(well, gnu99) support.
Also, Conrad has OpenIO running locally now, and is waiting to hear more
about how to use the C interface library to talk to it. Hopefully soon.
Has been reading the IMAP spec some more. Heaps of stuff in there. We
chatted about Alexey's new IMAP4rev2 draft, which basically adds all the
extension that everyone agrees is a great idea into IMAP4rev1 and
removes a couple of things that everyone agrees are bad ideas. A big
step back from IMAP5, but achievable and means that people claiming to
support IMAP need to be a little better before being laughed at.
Simon: not much, but suggested we put the release date on release notes.
Website - the situation with cyrusimap.org and cyrus.foundation is
awfully confusing. Somebody needs to take ownership for uncrapping this.
Nobody put their hand up yet, so we'll see if it happens by Thursday or
I might start appointing people ;)
Speaking of naming - cyrusfoundation == http://www.cyrusfoundation.org/
== not us. We need a new name. Cyrus IMAP Foundation -> two imappy.
Cyrus Mail Foundation -> not enough cal/carddav. "Cyrus Connect" -
doesn't someone already own "* Connect"? But maybe. reCyrus /
librecyrus / "recycle". Hmm... Great names greatly appreciated. Make
your mark here, but don't make it a trademark that somebody else has
already... yeah, that. *sigh*. All the good ones are taken or insane
(or both).
Chris - been working on trying to follow the instructions as someone who
doesn't already know how to do things, and getting appropriately
confused at the places that the docs are suboptimal. Yet more of the
"we need to improve documentation even more than we need to improve
code". He will continue to work on this path for the next couple of
days, with Nicola helping improve the docs.
Right now there are various README files of various quality and
usefulness, and a lot of docs in different formats scattered around the
project, with no clear idea of where to go for what problem.
And Bugs... do they go in Bugzilla, or Phabricator? How do users know?
What do we do for existing bugs in Bugzilla? Conclusion was to close
bugzilla for new bugs. Maybe have to get Dave to do this.
Bron.
--
Bron Gondwana
br...@fastmail.fm
Re: Cyrus-devel Digest, Vol 114, Issue 11
Hello, Just a few thoughts from today -There is another project called the 'Cyrus foundation' (www.cyrusfoundation.org). For SEO, should we use 'Cyrus IMAP foundation'? -The about pages from https://cgit.cyrus.foundation/cyrus-imapd/about/, https://cgit.cyrus.foundation/cyrus-sasl/about/ and https://cgit.cyrus.foundation/cyrus-sasl/about/ are blank. Could we add some text here, or a a link to https://cyrusimap.org/ ? - From README.git: > The latest development code is on the branch called 'master', and the > latest code destined for the stable release is on the branch > 'cyrus-imapd-$major-$minor'. So the current stable is called > cyrus-imapd-2.4 Throughout the documentation, there are many references to the 'current' version, it seems like a lot of effort to keep these up to date. Could we dynamically generate these? or not use version numbers in places where we don't need to? -/home/tester/cassandane/doc/setting_up.txt Step 0: > gnb> cd ~/my/cassandane/workarea gnb> make This folder is empty. 'make' works in the parent directory but not here. I think I've missed a step, any suggestions? Step 4: > "Partially installed Cyrus build in a temp directory. This is > what I use." Could we avoid use of first person? Cheers, Chris On Sat, 25 Apr 2015, at 02:00 AM, cyrus-devel-requ...@lists.andrew.cmu.edu wrote: > Send Cyrus-devel mailing list submissions to > cyrus-devel@lists.andrew.cmu.edu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.andrew.cmu.edu/mailman/listinfo/cyrus-devel or, via > email, send a message with subject or body 'help' to > cyrus-devel-requ...@lists.andrew.cmu.edu > > You can reach the person managing the list at > cyrus-devel-ow...@lists.andrew.cmu.edu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Cyrus-devel digest..." > > > Today's Topics: > > 1. Re: Cyrus-devel Digest, Vol 114, Issue 9 (Chris Davies) > > > -- > > Message: 1 Date: Fri, 24 Apr 2015 11:45:24 +1000 From: Chris Davies > Subject: Re: Cyrus-devel Digest, Vol 114, Issue 9 > To: cyrus-devel@lists.andrew.cmu.edu > Cc: nico...@fastmail.com Message-ID: > <1429839924.2747637.257911773.62412...@webmail.messagingengine.com> > Content-Type: text/plain; charset="us-ascii" > > Also, file:///home/tester/Downloads/cyrus-imapd-2.5.0/doc/readme.html > "last modified: **2001**/08/03 21:18:05". Looks like the script that > generates that date is broken. > > > On Wed, 22 Apr 2015, at 08:22 PM, > cyrus-devel-requ...@lists.andrew.cmu.edu wrote: >> Send Cyrus-devel mailing list submissions to >> cyrus-devel@lists.andrew.cmu.edu >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.andrew.cmu.edu/mailman/listinfo/cyrus-devel or, via >> email, send a message with subject or body 'help' to >> cyrus-devel-requ...@lists.andrew.cmu.edu >> >> You can reach the person managing the list at >> cyrus-devel-ow...@lists.andrew.cmu.edu >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Cyrus-devel digest..." >> >> >> Today's Topics: >> >> 1. Cyrus 2.5 documentation (Chris Davies) >> >> >> -- >> >> Message: 1 Date: Wed, 22 Apr 2015 20:22:34 +1000 From: Chris Davies >> Subject: Cyrus 2.5 documentation To: >> Cyrus-devel@lists.andrew.cmu.edu Message-ID: >> <1429698154.1183446.257038437.1a14d...@webmail.messagingengine.com> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Just a few thoughts on the 2.5 documentation and Cyrus websites: >> >> -It isn't obvious what website users should go to >> http://www.cyrus.foundation or http://www.cyrusimap.org? Do we need >> two websites? >> >> -http://www.cyrus.foundation redirects to >> https://cgit.cyrus.foundation/ and doesn't have an obvious link to >> http://docs.cyrus.foundation. Should I be testing against >> docs.cyrus.foundation or the cyrusimap.org documentation? >> >> -http://cyrusimap.org/docs/cyrus-imapd/2.5.0/ The page title for >> 2.5.0 help docs is 'Cyrus IMAP Server, version 2.4'. >> >> -Cyrusimap.org : "*? 1999-2010 Carnegie Mellon University. All Rights >> Reserved.*". Should this be updated to 2015? and mention the Cyrus >> foundation? >> >> -http://www.cyrusimap.org/mediawiki/index.php/Downloads#IMAP_Server >> "*The latest stable/current release of the IMAP server is 2.4.16*". >> Is this now 2.5? >> >> -I've downloaded the latest version from cyrusimap.org (2.5.0). The >> README file inside cyrus-imapd-2.5.0.tar.gz says "*The 2.4 series >> contains numerous features*". Should this say 2.5? >> >> -/home/tester/Downloads/cyrus-imapd-2.5.0/README.andrew : "# This is >> internal documentation for Computing Services at >> # Carnegie Mellon University. >> # >> # Please refer to doc/readme.html for the 'real' README. " >> >> Should this file be placed elsewhere? >> >> -/home/tester/Downloads/cyrus-imap
