From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] Fix check for Python modules for cross-compilation
Date: Sat, 18 Jan 2014 14:18:42 +0100 [thread overview]
Message-ID: <20140118131842.GA3400@free.fr> (raw)
In-Reply-To: <02e001cf13e9$7fd5cee0$0700000a@D400>
Peter, Simon,
On 2014-01-18 01:06 -0000, Peter Newman spake thusly:
> Taking on board what you said, I've put together a small page on our site
> about how to contribute:
> http://www.openlighting.org/ola/developer-documentation/contributing/
>
> As someone a bit external to the project, and a recent contributor, would
> you mind just taking a quick look at it to confirm it gives the sort of
> information you were looking for before?
OK, I was a bit puzzled when browsing the openlightning.org website.
Navigating from the homepage down to the contributing section is not
straightforward.
What is strange here is that he homepage has those shortcuts on the
banner[*] : Overview - People - Supporters - History
Plus a big button to download OLA. But no info on how to contriute to
OLA. I had expected to find something like "contacts" or "Developpers"
right on the frontpage.
OK, so I hover over "Download OLA": it's not an archive, but point to a
page labelled "getting-started". *That* sounds like a good starting
point, indeed. *Click*
From there on, here's the path I followed:
-> Download & Install OLA
-> Install From Git
- section of "Install on Linux"
- no infro on how to contribute
Ok, what was this link Peter sent me, BTW? Ah, there is
"developer-documentation" in the link. But I can't see a page labelled
"developpers" or some such.
Hmm.. Wait! The banner does not contain the same items as the homepage
does! And there *is* a "Developpers" item, now! Yes, it;s a menu!
Yes it has a "Contributing" section. Aha! Good! :-)
So it all boils down to the fact that the homepage and the rest of the
website does not contain the same items in the banner. I think it would
be much more helpful to have the same banner acros the whoel website.
After all, this banner should be a way to quickly go to interesting
sections.
But, hey, the info is there and it took me only a few minutes to find
it. So that's not so bad in the end.
All the required info I needed is there on that page, so that's good.
Thank you for providing this; hopefully, that will make it easier for
people to send their contributions. :-)
Regards,
Yann E. MORIN.
[*] Sorry, I'm French and don't know what this part is called in
english. I roughly tranlstated from the french "bandeau".
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-01-18 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 21:23 [Buildroot] [PATCH 0/2] Fix check for Python modules for cross-compilation Yann E. MORIN
2014-01-14 21:23 ` [Buildroot] [PATCH 1/2] configure: move python sub-check to configure.ac Yann E. MORIN
2014-01-14 21:23 ` [Buildroot] [PATCH 2/2] configure: add option for user to override checks for Python modules Yann E. MORIN
[not found] ` <CAPQm1=O0zZbJR4NWXjop5RH4-KMRTJWM60BiXnw6OHnv5m6T+Q@mail.gmail.com>
[not found] ` <02e001cf13e9$7fd5cee0$0700000a@D400>
2014-01-18 13:18 ` Yann E. MORIN [this message]
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=20140118131842.GA3400@free.fr \
--to=yann.morin.1998@free.fr \
--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