From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GNU GRUB maintenance
Date: Thu, 8 Oct 2015 21:28:25 -0400 [thread overview]
Message-ID: <20151009012825.GC4190@x230.dumpdata.com> (raw)
In-Reply-To: <CAG1y0scFse4kRbmiWLRQN3hzphe04GK4ukD_dL30c1z==kzs=Q@mail.gmail.com>
On Thu, Oct 08, 2015 at 01:24:50PM +0700, Fajar A. Nugraha wrote:
> On Thu, Oct 8, 2015 at 6:02 AM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com> wrote:
> > On 07.10.2015 23:36, SevenBits wrote:
>
> >> What other systems would be ok? It
> >> obviously has to be a free software and hosted on free software-friendly
> >> hosting. It also has to have an efficient 1-click merge (so that someone
> >> with privileges can get any patch submitted to the system merged in
> >> couple of clicks).
> >>
> >>
> >>
> >> I know that git is pretty popular...
> >>
> > Git integration is a plus. Like gerrit: git based with a review system
> > on top of it.
>
> Is "has to be a free software" an absolute requirement?
Also an kernel.org git account could be requested. It is there for
syslinux, dracut, bluetooth, etc. GRUB2 could be hosted there as well?
>
> Github, the web, is not open source. However it uses git, adds
> features (like the "1-click merge" and organization), and free (to
> use) for open source projects.
>
> Some open source projects hosted on github (and use the organization feature):
> https://github.com/zfsonlinux
> https://github.com/freeradius
>
> Some open source projects using github as mirror:
> https://help.github.com/articles/about-github-mirrors/
>
> Github help on web-based pull request:
> https://help.github.com/articles/using-pull-requests/
> https://help.github.com/articles/merging-a-pull-request/
>
> The downside with github that I can think of, is that for efficient
> use of the "1-click merge" web interface, the pull request must be
> created from the github interface (and the discussion will happen
> there as well), as opposed to in the mailing list like what currently
> happen. Then again, if the intention is simply to provide
> "notification to the mailing list" (and no need to allow discussion
> participation FROM the mailing list on the pull requests), you could
> probably work around that by having a normal git account with
> mailing-list address "watching" your repository.
>
> --
> Fajar
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2015-10-09 1:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 21:14 GNU GRUB maintenance Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-07 21:36 ` SevenBits
2015-10-07 23:02 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-08 6:24 ` Fajar A. Nugraha
2015-10-09 1:28 ` Konrad Rzeszutek Wilk [this message]
2015-10-10 18:49 ` Felix Zielcke
2015-10-08 18:21 ` Konrad Rzeszutek Wilk
2015-10-08 14:52 ` Andrei Borzenkov
2015-10-08 19:34 ` Konrad Rzeszutek Wilk
2015-10-09 12:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-09 12:18 ` Andrei Borzenkov
2015-10-10 0:30 ` Konrad Rzeszutek Wilk
2015-10-10 1:24 ` Konrad Rzeszutek Wilk
2015-10-09 4:41 ` Fajar A. Nugraha
2015-10-09 12:10 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-10-08 18:02 ` Josef Bacik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151009012825.GC4190@x230.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=grub-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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.