From: ng0 <contact.ng0@cryptolab.net>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix package incubator (later a channel)
Date: Tue, 7 Feb 2017 20:37:16 +0000 [thread overview]
Message-ID: <20170207203716.lwvijzs4ckn4alzu@wasp> (raw)
In-Reply-To: <8760klzv1x.fsf@dustycloud.org>
On 17-02-07 12:59:22, Christopher Allan Webber wrote:
> Pjotr Prins writes:
>
> > On Mon, Feb 06, 2017 at 09:44:48PM +0000, ng0 wrote:
> >> Just a reply on the notabug question (I don't have much time otherwise):
> >> Notabug will eventually move to an instance of pagure.io, you can read
> >> about this in their own issues where I asked about some question back
> >> then (no link, sorry .. my name was 'ng0' back on there). Developing
> >> with pagure might be easier (fedora and surrounding communities)
> >> compared to the situation they describe in the issue.
> >> I started packaging pagure for this reason, which is about ~85% done
> >> (services + pagure itself left to wrap it up ... pagure itself is more
> >> or less done, just the service are needed. I'm more than happy to pass
> >> this on (could rebase the pagure patch), as I know I have taken on some
> >> tasks which would be better handled by different people :)
> >> That is in case you want to use a GuixSD as a host, otherwise you should
> >> not have many problems.
> >
> > That would be a great result :). Also pagure looks very interesting -
> > simpler than gitlab. I like simple.
>
> It does look good:
>
> Open data: Sources, doc, ticket and pull-requests meta-data are
> available in the web interface but also in git repos which can thus be
> cloned and changed locally.
>
> That's really appealing.
>
The only thing we found (not answered, but I didn't check so far with
pagure development team) is that issues and pull requests are read-only
git repositories. Maybe our short trip into pagure was too short to
answer this, but it looked like read-only, no push. One reason why I
want an local instance to play with so I can check wether my
feature-issues are really issues or just pagure.io instance
configuration settings.
Also no trace of the "pull requests" across different hosted
instance of it, but that can be solved aswell later.
I agree with Pjotr, doesn't matter for now, might matter later.
--
ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-02-07 20:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 19:09 Guix package incubator (later a channel) Pjotr Prins
2017-02-06 21:44 ` ng0
2017-02-07 5:42 ` Pjotr Prins
2017-02-07 18:59 ` Christopher Allan Webber
2017-02-07 20:37 ` ng0 [this message]
2017-02-07 19:38 ` Ricardo Wurmus
2017-02-07 20:59 ` ng0
2017-02-08 6:58 ` Pjotr Prins
2017-02-08 13:46 ` Debbugs handling of packages Ludovic Courtès
2017-02-08 14:29 ` Ricardo Wurmus
2017-02-08 19:15 ` Andreas Enge
2017-02-12 11:05 ` ng0
2017-02-09 23:12 ` Debbugs handling of Guix patches Ludovic Courtès
2017-02-10 0:40 ` Glenn Morris
2017-02-10 12:41 ` Ludovic Courtès
2017-02-10 17:41 ` Glenn Morris
2017-02-10 22:46 ` Ludovic Courtès
2017-02-11 1:43 ` Christopher Allan Webber
2017-02-11 14:37 ` New guix-patches mailing list not showing up on Mailman Ludovic Courtès
2017-02-11 22:11 ` [Savannah-hackers-public] " Assaf Gordon
2017-02-11 22:51 ` Karl Berry
2017-02-12 13:54 ` Ludovic Courtès
2017-02-12 1:51 ` Debbugs handling of Guix patches Glenn Morris
2017-02-12 14:01 ` Ludovic Courtès
2017-02-26 8:42 ` Pjotr Prins
2017-02-12 14:11 ` New guix-patches mailing list hooked to Debbugs! Ludovic Courtès
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=20170207203716.lwvijzs4ckn4alzu@wasp \
--to=contact.ng0@cryptolab.net \
--cc=cwebber@dustycloud.org \
--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).