Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mark Constable <markc@renta.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] always_stop_at_dbus_package
Date: Sun, 16 Sep 2012 13:29:17 +1000	[thread overview]
Message-ID: <5055478D.7070407@renta.net> (raw)
In-Reply-To: <CAA93jw5e1rfV+DLSXL0e=M8rW_aygWaJhpOVxtgWXp66uLXPBg@mail.gmail.com>

On 09/16/12 10:37, Dave Taht wrote:
> That said, I think having a scrum/google hangout on getting more
> people up to speed on "how to build openwrt and cerowrt" would be
> helpful for many.

I had to google "scrum", I guess this is it...

http://en.wikipedia.org/wiki/Scrum_(development)

Hopefully a static video of the session could be put on youtube for
those of us not likely to attend on the day (timezone tragics).

I use Archlinux so in a way, fwiw, I'd rather see simpler but expanded
copy n paste instructions at, say...

https://github.com/dtaht/cerowrt/wiki

where the "cerowrt" meta project pulls in everything else as submodules
and contains various shell based build scripts to manage the whole show.
Those sh based build scripts would be far more educational than anything
else I could think of. I know this is what...

https://github.com/dtaht/Cerowrt-3.3

essentially does but the "3.3" concerns me because when a 3.4|5|6|7
comes out then anything in the 3.3 project gets superseded meaning that
any effort on Cerowrt-3.3/wiki becomes kind of redundant. In general,
when I go to...

https://github.com/dtaht/

it's not entirely clear what projects are important or not or where to
start and that slows down adoption (for me) and my point is that there
is a lot that could be done to improve the github project space as the
center of the cerowrt universe rather than a once-off hangout event,
which would be totally cool as well, for those who attend.


      reply	other threads:[~2012-09-16  3:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  8:25 Oliver Niesner
2012-09-16  0:37 ` Dave Taht
2012-09-16  3:29   ` Mark Constable [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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5055478D.7070407@renta.net \
    --to=markc@renta.net \
    --cc=cerowrt-devel@lists.bufferbloat.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