Re: [Trion-kernel-dev] Is the project still active?

[Stephen M. W. <ste...@br...>]

Daniel Raffler wrote:
> 
>> Stephen M. Webb wrote:
>> I think the next major task in the kernel is to work the scheduler and  
>> dispatcher.
> 
> Before we can tackle that some more work on the kernel memory manager will  
> be needed. I've already finished most of the paper-work for the kernel  
> memory system, so that it shouldn't take too long until I can present some  
> more details.

That's great.  Any idea when you'll have something for us?  Is there 
anything we can do to help?

>> Sergey Kuznetsov wrote:
>> What if we will make some brain storm here ( I love brainstorming ) what
>> do we need on the web-site, and later make the voting on the topics and
>> will assign priorities on each feature.

> b) The site should describe the goals of the kernel in much greater  
> detail. Right now there're only a couple of rather generic sentences about  
> our design on the page. Developers however want to know much more about a  
> project before they might consider to join: Why should I join Trion and  
> not some other sourceforge  project ?

Anyone willing to have a go at a first (or, um, maybe second) draft?

> c) A project history and a roadmap for the next 6-12 months should give  
> the visitors an impression of the current state of the project. It can  
> also help us to keep track of the development as we plan in the long term.  
> This section should get updated regularly as the development proceeds. It  
> could even be an alternative to the not-so-exiting news sections that most  
> other projects have.

Okay, a roadmap/project plan and a news section.  The roadmap should 
have a estimated percent complete and estimated time-to-complete.

> d) The "What Can I Do?" section should in my opinion be more specific. We  
> don't need somebody to do anything, but a developer that know language X  
> and has experience with Y to write module Z. The more specific the given  
> information, the easier it is for a potential developer to imagine his  
> tasks. Visitores interested in the project would no longer have to  
> register to the mailing list in order to find out what exactly they could  
> contribute.

Yes.  A 'choose a project' list.  Daniel, you seem to have the best idea 
about what needs to be done still, could you start such a list circulating?

> e) A member page with some private information about the regulars might  
> give the project a personal touch. After having leart a bit about the  
> other team-members, one might be less hesitant to get into contact with  
> the team.

That's one of the things the wiki is good for.

> If he's really new to OS develpment chances are that he doesn't know about  
> the toolchain or has no experience with installing bochs. It would  
> probably also be a good idea to add a number of such beginner tutorials to  
> the wiki.

Yes.  Hmmm, perhaps I'll work on that.

--
smw