unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Peter Šurda" <surda@economicsofbitcoin.com>
To: guix-devel@gnu.org, chicks@getbackinthe.kitchen,
	ng0 <contact.ng0@cryptolab.net>
Subject: Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PAT
Date: Fri, 17 Feb 2017 18:19:24 +0100	[thread overview]
Message-ID: <20170217171924.GE8688@mutt.economicsofbitcoin.com> (raw)
In-Reply-To: <20170217164131.qqcv5mzvmihg6agi@wasp>

Hello,

On Fri, Feb 17, 2017 at 04:41:31PM +0000, ng0 wrote:
>I don't really feel part of this conversation, but since you keep CC'ing
>me I have to reply.
I keep CCing you because I don't know if my messages will make it into
the list, and I don't know who is doing what.

>> https://bitmessage.org/wiki/Compiling_instructions#Resolve_dependencies
>This is not accesible from behind restrictive proxies and networks like
>tor, so I have to pass on this.
There is at the moment a snapshot mirror available for testing new web
infrastructure with the goal to improve the experience. I manually
copied over the Guix instructions so that you can view those too:

https://test.bitmessage.org/wiki/Compiling_instructions#Resolve_dependencies

>I did the initial packaging of PyBitmessage on GuixSD but there is no
>maintainer per package, whoever wants to update can update it.
Ok.

>Since all my questions, improvements, and attempts to contribute have
>been blocked and/or forgotten by the PyBitmessage project I don't want
>to have this discussion in my inbox longer than necessary.
I'm sorry you feel that way. I'm now doing most of the work and have to
balance between the various aspects of the whole project of which coding
is just one part. I cannot reprioritise based on or even track the
communication of a single user. I need to think about the bigger picture
and whole community. I just bought a 3400 EUR server for VMs so that I
can test the PyBitmessage on the zillions of OS variants around there. I
monitor the web so that I can react to bug reports no matter when they
appear.

The project now has clear(er) contribution guidelines:

https://bitmessage.org/wiki/Contribute

or on the test mirror:

https://test.bitmessage.org/wiki/Contribute

and you can get paid in Bitcoin for providing commits that get merged.

Translations have been integrated with transifex and a webhook will
automatically create a pull request when a language is complete. All
commits are PGP signed.

The current cycle focused on bugfixes and refactoring of some horrible
parts. There are also some minor but nice usability improvements that
are particularly important for beginners.

Extended encoding is available for experimenting and is written in a
developer-friendly way. The project registered #bitmessage on freenode
and the website will be migrated to better infrastructuer after 0.6.2
comes out.

>LibreSSL support is at least one improvement I welcome.  Any news on
>the use of setuptools, and the move to PyQt5?
PyQt5 is not a priority. It may be better to have separate projects for
a library written in C, and a GUI written in, perhaps, PyQt5. But I
don't have time for it, maybe if I can raise funds and pay someone to do
that while I focus on the bugfixes and protocol.

I'll look at setuptools in the current cycle (i.e. in the next week or
two).

>ng0 -- https://www.inventati.org/patternsinthechaos/

-- 
Peter Šurda
Bitmessage core developer

  reply	other threads:[~2017-02-17 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 16:38 [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PAT Peter Šurda
     [not found] ` <20170217110502.GC8688@mutt.economicsofbitcoin.com>
2017-02-17 16:25   ` Peter Šurda
2017-02-17 16:41     ` ng0
2017-02-17 17:19       ` Peter Šurda [this message]
2017-02-17 17:53         ` ng0
2017-02-17 19:33           ` Peter Šurda
2017-02-17 19:40             ` ng0
2017-02-17 20:06               ` Peter Šurda
2017-02-17 20:14                 ` ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170217171924.GE8688@mutt.economicsofbitcoin.com \
    --to=surda@economicsofbitcoin.com \
    --cc=chicks@getbackinthe.kitchen \
    --cc=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).