Hello.
On Fri, 2007-06-08 at 10:24, Jeff Andros wrote:
>
> Are we really suggesting that we manually maintain one set of information
> about all the tasks on the wiki, and another on the bugtracker?
No, we put the different information in different, proper, locations.
> What it seems you're sayi
On 6/8/07, Stefan Schmidt <[EMAIL PROTECTED]> wrote:
Hello.
So the wiki page should have the following for every single task:
Description, needed skills, links to reference code...
If nobody beat me, *hint*, I'll add these tasks and perhaps some more
to the wiki tonight.
regards
Stefan Schm
Stefan Schmidt wrote:
> Should be both in the wiki already, no?
Yup, so the walk-through should just explain the easiest approach,
and link to the more detailed background material for the rest.
E.g., the QEMU part doesn't need all the background information
from the QEMU page. Trimming the MokoMa
Hello.
On Fri, 2007-06-08 at 07:01, Werner Almesberger wrote:
> Stefan Schmidt wrote:
> > We already had some thoughts about such 'junior tasks'. I really like
> > the idea to give interested people small tasks for a quick start.
>
> Regarding quick starts, perhaps some sort of tutorial could be
Stefan Schmidt wrote:
> We already had some thoughts about such 'junior tasks'. I really like
> the idea to give interested people small tasks for a quick start.
Regarding quick starts, perhaps some sort of tutorial could be useful,
e.g.
- how to get the basic development/run-time environment
- h
Hello.
On Fri, 2007-06-08 at 02:41, Philippe De Swert wrote:
>
> So I would like to propose a todo list on the wiki. This should list a
> number of tasks which people can take up with a short explanation of
> what has to be done and what is expected.
We already had some thoughts about such 'juni
On Fri, 2007-06-08 at 02:41 +0300, Philippe De Swert wrote:
> Hi all,
>
> Lately I have been wondering how to be able to contribute to the actual
> development of the OpenMoko software. I have been looking at the
> bugzilla but it is often hard to contribute to certain parts. Some
> things are tri
Hi all,
Lately I have been wondering how to be able to contribute to the actual
development of the OpenMoko software. I have been looking at the
bugzilla but it is often hard to contribute to certain parts. Some
things are trivial but troublesome to do due to having to modify a lot
of seperate pro
8 matches
Mail list logo
