Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Ketan Kulkarni <ketkulka@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Getting basics in place..
Date: Thu, 23 Feb 2012 12:53:06 +0000	[thread overview]
Message-ID: <CAA93jw5Z1miKcC4MhP+X1qUPmfPPW9nC-RxeSRcD+jRucFFfRg@mail.gmail.com> (raw)
In-Reply-To: <CAD6NSj4JKvZBDx6rm2J2Vt=mqmOYfU8hL3emws8JKfiOkVomYw@mail.gmail.com>

I regret that we are not at the point where cerowrt is independently
buildable, as the build process from the previous release has changed
significantly and is still in flux.

I HAVE finally got to where all the repositories are online on github
(cerowrt-3.3, cerowrt-luci, ceropackages, cerofiles-3.3), but it's not
obvious how to get the right packages overridden as I write, and
there are no doubt other problems.

The second url you pointed to is only a draft, and only works if the
build is directly on the build server, and was the questions that
another developer (each - evan hunt) had asked about it, and it's not
an actual howto...

I hope to get it independently buildable by the middle of feburary.

I wouldn't mind working one-on-one to debug that process with you, (or
anyone else that is interested)
in irc at around that time. It would be a goodness for more people to
be able to fully customize their build...

As for coping with bugs, etc, well, let me know a few you are
interested in working on and I'll try to help nudge you along.
On Tue, Feb 21, 2012 at 5:06 PM, Ketan Kulkarni <ketkulka@gmail.com> wrote:
> Hi Team,
> I am very new to cerowrt and trying to get hands on the code and other
> activities in the project.
> I have been following bufferbloat blogs, mailing lists and the bug lists for
> a while.
>
> I tried building cerowrt using instructions on this -
> http://www.bufferbloat.net/projects/cerowrt/wiki/Building_CeroWrt_on_your_own_machine
> and
> http://www.bufferbloat.net/projects/cerowrt/wiki/Cerowrt_33_Build
>
> However, I am not yet confident whether I built it right.
> Moreover not sure of the next step I should be doing to get involved in any
> sort of developments.
>
> I may also not be aware of the development methodology, what to test, how to
> test, where the code is and where to start looking for the code.
> Just looking at the bug list as well, I couldn't figure out how to recreate
> the issues and where to look for those :-(. (May be I am too naive??)
>
> Would really appreciate your help in getting my basics in place.
>
> Thanks,
> Ketan
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

      reply	other threads:[~2012-02-23 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-21 17:06 Ketan Kulkarni
2012-02-23 12:53 ` Dave Taht [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=CAA93jw5Z1miKcC4MhP+X1qUPmfPPW9nC-RxeSRcD+jRucFFfRg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=ketkulka@gmail.com \
    /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