Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot, github and nopullrequest.com
Date: Sat, 16 Jul 2016 16:08:54 +0200	[thread overview]
Message-ID: <20160716160854.288eed19@free-electrons.com> (raw)
In-Reply-To: <CA+TH9V=4CSerf01N00NY6GhLxjXEc_ED2Y1JUEWyuMddDhzO5Q@mail.gmail.com>

Hello,

On Sat, 16 Jul 2016 15:58:35 +0200, Angelo Compagnucci wrote:

> > I just created https://github.com/buildroot/buildroot.github.io for
> > this purpose, and then realized that we use SSI includes. I think we
> > should probably move away from SSI includes, to a more modern web-site
> > generation mechanism, like Pelican (http://blog.getpelican.com/) or
> > similar.  
> 
> I'm not too familiar with these systems. Usually they are not too
> flexibles and they tend make difficult to write your own theme for the
> website. Thay are also blog oriented and not too much website
> oriented.

Then you indeed don't know such systems very well, because they tend to
be quite flexible. For example, the https://2016.capitoledulibre.org/
(french) website is generated by Pelican.

> >> 2) We have a github account, we should use it as the main repository.
> >> No other words here.  
> >
> > Well, there is one *big* issue: e-mail notifications. They are not
> > available by default, and the only thing that people have been able to
> > do so far is to have notifications with one e-mail per push (i.e one
> > e-mail covering potentially multiple commits). This is definitely not
> > acceptable, and is a show-stopper to moving to github.  
> 
> I didn't realized github is so limited ...

That's a very strong issue with Github. Until this is resolved, no way
we can switch to Github.

> > I'm not sure I like giving access to https://nopullrequests.com to my
> > Google account.  
> 
> You can jump that step, the important is to give the permission to
> close the PRs (github permission). Obviously is not the most clean
> solution, but the only viable one.

Not sure what you mean, but:

 * The https certificate of nopullrequests.com is invalid.

 * If I say "No thanks" when it asks me to log in with my Google
   account, it just redirects me to the Google homepage. Not very
   useful.

> I had a look at infradead.org and to it seems way less solid than the
> infrastructure we have now. On the homepage
> (http://www.infradead.org/) the author seems to look for a job ...

Well, if you search a bit, the guy in question is David Woodhouse
(https://www.linkedin.com/in/dwmw2). He has worked at RedHat for 8
years, and now is at Intel since 8 years. Not sure he is looking for a
job.

infradead.org is used for the ARM kernel mailing list, which receives
much more traffic than the Buildroot one. The Git infrastructure of
infradead is also widely used by kernel people. Grep "infradead.org" in
the kernel MAINTAINERS file.

> >  2/ Migration of the bug tracker history. How do we move Bugzilla
> >     entries to the Github issue tracker? All references of bug tracker
> >     entries in Buildroot commits would become wrong. Not nice.  
> 
> Right, good catch.
> 
> Very intricate problem ...

Indeed.

So as you can see, moving to another infra is not that simple :-/

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-07-16 14:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-16 12:44 [Buildroot] Buildroot, github and nopullrequest.com Angelo Compagnucci
2016-07-16 13:09 ` Thomas Petazzoni
2016-07-16 13:58   ` Angelo Compagnucci
2016-07-16 14:08     ` Thomas Petazzoni [this message]
2016-07-16 14:27       ` Angelo Compagnucci
2016-07-16 16:46 ` Yann E. MORIN
2016-07-16 16:52   ` Angelo Compagnucci
2016-07-16 16:57     ` Angelo Compagnucci

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=20160716160854.288eed19@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox