Only backporting documentation + build/test system fixes, but I'll probably apply and push the TeeInput patch in: http://bogomips.org/unicorn-public/m/20150422183808.GA5277@dcvr.yhbt.net.txt The following changes since commit 7087bb7ed5a1b9d9f24069cb92707d086668b6dc: unicorn 4.8.3 - the end of an era (2014-05-07 07:49:19 +0000) are available in the git repository at: git://bogomips.org/unicorn 4.8.x-stable for you to fetch changes up to 548e1e67d314f6ebd17df37ece0ee20632462f6f: doc: document UNICORN_FD in manpage (2015-04-22 18:57:39 +0000) ---------------------------------------------------------------- Eric Wong (19): ISSUES: update with mailing list subscription FAQ: add entry for Rails autoflush_log dev: remove isolate dependency unicorn.gemspec: depend on test-unit 3.0 remove RubyForge and Freecode references remove mongrel.rubyforge.org references examples: add run_once to before_fork hook example t/t0002-parser-error.sh: relax test for rack 1.6.0 switch docs + website to olddoc README: clarify/reduce references to unicorn_rails gemspec: fixup olddoc migration GNUmakefile: fix clean gem build + reduce build cruft doc: update support status for Ruby versions fix uninstalled testing and reduce require paths test_socket_helper: do not depend on SO_REUSEPORT ISSUES: add section for bugs in other projects explain 11 byte magic number for self-pipe Links: mark Rainbows! as historical, reference yahns doc: document UNICORN_FD in manpage .document | 1 - .gitignore | 4 +- .wrongdoc.yml => .olddoc.yml | 6 ++- Documentation/unicorn.1.txt | 7 ++++ FAQ | 10 ++++- GNUmakefile | 71 +++++++++++++---------------------- HACKING | 31 ++++----------- ISSUES | 46 +++++++++++++++++++++-- KNOWN_ISSUES | 20 +++++----- Links | 5 ++- README | 10 ++--- Rakefile | 44 ---------------------- Sandbox | 2 +- examples/unicorn.conf.rb | 11 ++++++ lib/unicorn/configurator.rb | 2 - lib/unicorn/http_server.rb | 6 ++- local.mk.sample | 59 ----------------------------- script/isolate_for_tests | 31 --------------- t/GNUmakefile | 6 +-- t/README | 2 +- t/t0002-parser-error.sh | 6 +-- test/exec/test_exec.rb | 2 +- test/test_helper.rb | 4 +- test/unit/test_http_parser.rb | 6 +-- test/unit/test_http_parser_ng.rb | 2 +- test/unit/test_http_parser_xftrust.rb | 2 +- test/unit/test_request.rb | 2 +- test/unit/test_response.rb | 6 +-- test/unit/test_server.rb | 6 +-- test/unit/test_signals.rb | 2 +- test/unit/test_socket_helper.rb | 8 ++-- test/unit/test_upload.rb | 2 +- test/unit/test_util.rb | 2 +- unicorn.gemspec | 13 +++---- 34 files changed, 167 insertions(+), 270 deletions(-) rename .wrongdoc.yml => .olddoc.yml (85%) delete mode 100644 local.mk.sample delete mode 100755 script/isolate_for_tests
Michael Fischer <mfischer@zendesk.com> wrote: > Is there some compelling reason why the mailing list simply cannot be > moved to another provider? IMHO your users and fellow developers > shouldn't have to do anything other than change the submission > address. We would need to migrate again if/when that provider goes dead or service starts deteriorating. Ease-of-migration and being forkable again in the future was the top priority. If I'm hit by a bus or start allowing too much spam, it should be trivially easy to migrate the project[1] and all its archives and infrastructure. > I respect your desire to power the communication platform with free > software (and I'm sure this can still be done with Mailman or > whatever), but keep in mind the practical reality of our time, where > most of us these days are now comfortably using Webmail or or POP/IMAP > against a remote server that's not under the user's control and have > no desire to implement yet another communication conduit. I will probably take the addresses of active subscribers who've posted here[2] imported into the new delivery system, even. It would be great to be able to make the list of ML subscribers public, too, to ensure forkability. I'm not sure how the lurkers will react to that, though... [1] of course, whoever takes over may not be a Free Software zealot like myself. [2] those addresses are already public, but lurkers will probably have to resubscribe (or use ssoma or the Atom feed).
On Wed, May 7, 2014 at 10:34 PM, Eric Wong <normalperson@yhbt.net> wrote:
Xavier Noria <fxn@hashref.com> wrote:
> > What's the summary for current subscribers that use Gmail in their
> browser?
> > I have no local email these days.
>
> Yeah, webmail users seem to have this problem :<
> As I wrote here, I'll get SMTP delivery added:
>
> http://bogomips.org/unicorn-public/m/20140507195444.GA12686@dcvr.yhbt.net.html
> That was the fallback plan anyways; but the whole thing is still designed
> for ease-of-migration/forking.
>
Awesome, thanks Eric.
Xavier Noria <fxn@hashref.com> wrote: > What's the summary for current subscribers that use Gmail in their browser? > I have no local email these days. Yeah, webmail users seem to have this problem :< As I wrote here, I'll get SMTP delivery added: http://bogomips.org/unicorn-public/m/20140507195444.GA12686@dcvr.yhbt.net.html That was the fallback plan anyways; but the whole thing is still designed for ease-of-migration/forking.
On Wed, May 7, 2014 at 2:46 AM, Eric Wong <e@80x24.org> wrote:
> Jérémy Lecour <jeremy.lecour@gmail.com> wrote:
> > Would you mind explaining what a regular subscriber has to do to keep
> > receiving those emails in their inbox?
>
> You use ssoma[1] to to import mail into your inbox. This is like how
> slrnpull works with NNTP or getmail/fetchmail works with POP. It's
> only a one-way sync, but you can import it into an IMAP folder.
>
> Currently there's no SMTP delivery component, but I could probably set
> one up this week if there's enough demand for one. The subscriber list
> will be public, though.
Is there some compelling reason why the mailing list simply cannot be
moved to another provider? IMHO your users and fellow developers
shouldn't have to do anything other than change the submission
address.
I respect your desire to power the communication platform with free
software (and I'm sure this can still be done with Mailman or
whatever), but keep in mind the practical reality of our time, where
most of us these days are now comfortably using Webmail or or POP/IMAP
against a remote server that's not under the user's control and have
no desire to implement yet another communication conduit.
Thanks,
--Michael
What's the summary for current subscribers that use Gmail in their browser? I have no local email these days.
+1, pushing to ssoma when emails standards empire is very strong is way too much... Another mailing list in another server should be created... regards, bráulio On Wed, May 7, 2014 at 5:05 AM, Eric Wong <e@80x24.org> wrote: > Changes: > > This release updates documentation to reflect the migration of the > mailing list to a new public-inbox[1] instance. This is necessary > due to the impending RubyForge shutdown on May 15, 2014. > > The public-inbox address is: unicorn-public@bogomips.org > (no subscription required, plain text only) > ssoma[2] git archives: git://bogomips.org/unicorn-public > browser-friendly archives: http://bogomips.org/unicorn-public/ > > Using, getting help for, and contributing to unicorn will never > require any of the following: > > 1) non-Free software (including SaaS) > 2) registration or sign-in of any kind > 3) a real identity (we accept mail from Mixmaster) > 4) a graphical user interface > > Nowadays, plain-text email is the only ubiquitous platform which > meets all our requirements for communication. > > There is also one small bugfix to handle premature grandparent death > upon initial startup. Most users are unaffected. > > [1] policy: http://public-inbox.org/ - git://80x24.org/public-inbox > an "archives first" approach to mailing lists > [2] mechanism: http://ssoma.public-inbox.org/ - git://80x24.org/ssoma > some sort of mail archiver (using git) > > * http://unicorn.bogomips.org/ > * unicorn-public@bogomips.org > * git://bogomips.org/unicorn.git > * http://unicorn.bogomips.org/NEWS.atom.xml > > -- > Eric Wong > __ > http://bogomips.org/unicorn-public/ - unicorn-public@bogomips.org > please quote as little as necessary when replying -- "Lute pela sua ideologia. Seja um com sua ideologia. Viva pela sua ideologia. Morra por sua ideologia" P.R. Sarkar EITA - Educação, Informação e Tecnologias para Autogestão http://cirandas.net/brauliobo http://eita.org.br "Paramapurusha é meu pai e Parama Prakriti é minha mãe. O universo é meu lar e todos nós somos cidadãos deste cosmo. Este universo é a imaginação da Mente Macrocósmica, e todas as entidades estão sendo criadas, preservadas e destruídas nas fases de extroversão e introversão do fluxo imaginativo cósmico. No âmbito pessoal, quando uma pessoa imagina algo em sua mente, naquele momento, essa pessoa é a única proprietária daquilo que ela imagina, e ninguém mais. Quando um ser humano criado mentalmente caminha por um milharal também imaginado, a pessoa imaginada não é a propriedade desse milharal, pois ele pertence ao indivíduo que o está imaginando. Este universo foi criado na imaginação de Brahma, a Entidade Suprema, por isso a propriedade deste universo é de Brahma, e não dos microcosmos que também foram criados pela imaginação de Brahma. Nenhuma propriedade deste mundo, mutável ou imutável, pertence a um indivíduo em particular; tudo é o patrimônio comum de todos." Restante do texto em http://cirandas.net/brauliobo/blog/a-problematica-de-hoje-em-dia
> I guess I am too lazy/busy to dig into this, so an SMTP would be great
> for me. I am also ok to be listed as a public subscriber.
Same here, SMTP sounds great :)
On Wed, May 7, 2014 at 5:46 PM, Eric Wong <e@80x24.org> wrote:
> Jérémy Lecour <jeremy.lecour@gmail.com> wrote:
>> Hi Eric and all,
>>
>> I'm sorry if I'm the dumbest guy in the room, but I absolutely don't
>> understand what I have to do to stay in the mailing list.
>
> Sorry about the confusion, I'll try to clarify...
>
>> Would you mind explaining what a regular subscriber has to do to keep
>> receiving those emails in their inbox?
>
> You use ssoma[1] to to import mail into your inbox. This is like how
> slrnpull works with NNTP or getmail/fetchmail works with POP. It's
> only a one-way sync, but you can import it into an IMAP folder.
>
> Currently there's no SMTP delivery component, but I could probably set
> one up this week if there's enough demand for one. The subscriber list
> will be public, though.
>
> [1] http://ssoma.public-inbox.org/
I guess I am too lazy/busy to dig into this, so an SMTP would be great
for me. I am also ok to be listed as a public subscriber.
Jérémy Lecour <jeremy.lecour@gmail.com> wrote: > Hi Eric and all, > > I'm sorry if I'm the dumbest guy in the room, but I absolutely don't > understand what I have to do to stay in the mailing list. Sorry about the confusion, I'll try to clarify... > Would you mind explaining what a regular subscriber has to do to keep > receiving those emails in their inbox? You use ssoma[1] to to import mail into your inbox. This is like how slrnpull works with NNTP or getmail/fetchmail works with POP. It's only a one-way sync, but you can import it into an IMAP folder. Currently there's no SMTP delivery component, but I could probably set one up this week if there's enough demand for one. The subscriber list will be public, though. [1] http://ssoma.public-inbox.org/ Taken from http://unicorn.bogomips.org/ISSUES based on what I wrote in: http://bogomips.org/unicorn-public/m/20140421183728.GA27047@dcvr.yhbt.net.html URL=git://bogomips.org/unicorn-public LISTNAME=unicorn # to initialize a maildir (this may be a new or existing maildir, # ssoma will not touch existing messages) # If you prefer mbox, use mbox:/path/to/mbox as the last argument # You may also use imap://$MAILSERVER/INBOX for an IMAP account # or imaps:// for an IMAPS account, as well. ssoma add $LISTNAME $URL maildir:/path/to/maildir # read with your favorite MUA (only using mutt as an example) mutt -f /path/to/maildir # (or /path/to/mbox) # to keep your mbox or maildir up-to-date, periodically run the following: ssoma sync $LISTNAME # your MUA may modify and delete messages from the maildir or mbox, # this does not affect ssoma functionality at all # to sync all your ssoma subscriptions ssoma sync # You may wish to sync in your cronjob ssoma sync --cron
Hi Eric and all, I'm sorry if I'm the dumbest guy in the room, but I absolutely don't understand what I have to do to stay in the mailing list. Would you mind explaining what a regular subscriber has to do to keep receiving those emails in their inbox? Thanks -- Jérémy Lecour : http://jeremy.wordpress.com - http://twitter.com/jlecour
Changes: This release updates documentation to reflect the migration of the mailing list to a new public-inbox[1] instance. This is necessary due to the impending RubyForge shutdown on May 15, 2014. The public-inbox address is: unicorn-public@bogomips.org (no subscription required, plain text only) ssoma[2] git archives: git://bogomips.org/unicorn-public browser-friendly archives: http://bogomips.org/unicorn-public/ Using, getting help for, and contributing to unicorn will never require any of the following: 1) non-Free software (including SaaS) 2) registration or sign-in of any kind 3) a real identity (we accept mail from Mixmaster) 4) a graphical user interface Nowadays, plain-text email is the only ubiquitous platform which meets all our requirements for communication. There is also one small bugfix to handle premature grandparent death upon initial startup. Most users are unaffected. [1] policy: http://public-inbox.org/ - git://80x24.org/public-inbox an "archives first" approach to mailing lists [2] mechanism: http://ssoma.public-inbox.org/ - git://80x24.org/ssoma some sort of mail archiver (using git) * http://unicorn.bogomips.org/ * unicorn-public@bogomips.org * git://bogomips.org/unicorn.git * http://unicorn.bogomips.org/NEWS.atom.xml -- Eric Wong