On Sun, Sep 14, 2014 at 12:05 PM, Nick Sauce
wrote:
> I'm fine with trying to keep things working, but I don't have a GitHub
> account and would prefer not to use them.
>
>
I'm not discouraging any contributions, but having everything at one place
ready for discussion has been very helpful.
I do
There's gitlab for that. But in my opinion, anything not being github would
reduce by a great amount the number of contributors.
On Sat, Sep 13, 2014 at 10:07 PM, Vladimír Čunát wrote:
> On 09/13/2014 09:41 PM, Mateusz Kowalczyk wrote:
>
>> Of course there is still the problem of GitHub not bein
I'm fine with trying to keep things working, but I don't have a GitHub
account and would prefer not to use them.
FWIW, GitHub's terms of service might forbid a bot that would open PRs:
https://help.github.com/articles/github-terms-of-service
Thanks for the consideration though (and thanks Vla
It's not that migrating away from Github, if it was ever necessary, is
going to be really hard. It's not that they added proprietary stuff to git,
just a very nice frontend.
Just my 2 cents,
Nathan
On Sat, Sep 13, 2014 at 10:07 PM, Vladimír Čunát wrote:
> On 09/13/2014 09:41 PM, Mateusz Kowal
On 09/13/2014 09:41 PM, Mateusz Kowalczyk wrote:
Of course there is still the problem of GitHub not being responsive to
feature requests (we still can't delete issues and it took YEARS to be
able to lock them) and its service all the way up to its web frontend
being proprietary code.
Yes, the c
On 09/13/2014 06:49 PM, Vladimír Čunát wrote:
> On 09/13/2014 07:48 PM, Mateusz Kowalczyk wrote:
>> GitHub has a pretty shitty terms of service which is why these patches
>> are being sent over e-mail.
which is probably*
> Can you point me to some explanation why they're shitty?
>
> Vladimir
Ap
On 09/13/2014 07:48 PM, Mateusz Kowalczyk wrote:
GitHub has a pretty shitty terms of service which is why these patches
are being sent over e-mail.
Can you point me to some explanation why they're shitty?
Vladimir
smime.p7s
Description: S/MIME Cryptographic Signature
__
On 09/13/2014 12:33 PM, Vladimír Čunát wrote:
>
> Nick: do you want to become a maintainer of all these newly added
> packages? It means that you would be getting e-mail when a package
> changes status (success/failure), and you would be expected to try to
> keep them working.
>
> On 09/13/201
Nick: do you want to become a maintainer of all these newly added
packages? It means that you would be getting e-mail when a package
changes status (success/failure), and you would be expected to try to
keep them working.
On 09/13/2014 11:13 AM, Luca Bruno wrote:
Out of curiosity, is anybod
Out of curiosity, is anybody reviewing your patches in the mailing list? We
usually use github.
On Sat, Sep 13, 2014 at 10:57 AM, Nick Sauce
wrote:
> pyenchant: new package
> ---
>
> diff --git \
> a/pkgs/top-level/python-packages.nix \
> b/pkgs/top-level/python-packages.nix
> index 34ecbff..aec
pyenchant: new package
---
diff --git \
a/pkgs/top-level/python-packages.nix \
b/pkgs/top-level/python-packages.nix
index 34ecbff..aec3a3b 100644
--- a/pkgs/top-level/python-packages.nix
+++ b/pkgs/top-level/python-packages.nix
@@ -839,6 +839,36 @@ rec {
};
};
+ pyenchant = buildPythonP
11 matches
Mail list logo
