public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans" <hans64@ht-lab.com>
To: Miguel Bolanos <mike@hsol.net>, linux-8086@vger.kernel.org
Subject: Re: Help Wanted!
Date: Sat, 24 Sep 2005 10:35:48 +0100	[thread overview]
Message-ID: <003301c5c0eb$68f1ece0$6502a8c0@dionysus> (raw)
In-Reply-To: 1127539824.8686.33.camel@selene.hsol.net

Hi Miguel,

I am very happy that you will attempt to do this, I have given up on ELKS 
since even a basic question like why is the mailing list archive link dead 
has remained unanswered.

However, before you start  I think that you need a good set of obtainable 
goals. The reason is simple, you need to get hackers/hobbyist interested in 
the project so that they start contributing. The current target audience(?) 
of old XT/PC type of hardware systems is no longer viable. I might be wrong 
in this respect but I believe you should target embedded and home grown 
hobby systems.  This requires a fundamental change in the development tools 
since BCC is limited to 8086/6809 systems only.

David Given had an idea to use the ACK compiler for ELKS since ACK supports 
a large range of 8 bits microcontrollers, however, I am afraid that by 
adopting ACK we add a huge amount of work and complexity to the project. I 
for one failed to build ELKS on my 64bits system and after a day of hacking 
I gave up since the system was too complex for me (I am a hardware designer 
and not a softie :-).

Why don't you start with a survey, how many people are on this list, what do 
they use ELKS for, what would they like to use ELKS for, who is in charge of 
the website etc..

Regards,
Hans.
http://www.ht-lab.com/


----- Original Message ----- 
From: "Miguel Bolanos" <mike@hsol.net>
To: <linux-8086@vger.kernel.org>
Sent: Saturday, September 24, 2005 6:30 AM
Subject: Help Wanted!


> Greetings to all,
>
> As you may have noticed the project has been stuck for quite a while, i
> am looking forward to bring it back to life, but and would like to ask
> for some help, obviously coders are very welcome, but also people
> willing to help writing docs, and even people looking forward to help us
> create a new look for the project website.
> Looking forward to hear back from you.
>
> regards
>
> Miguel.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html 


  reply	other threads:[~2005-09-24  9:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24  5:30 Help Wanted! Miguel Bolanos
2005-09-24  9:35 ` Hans [this message]
2005-09-24 19:43   ` Rex Walburn
2005-09-27 18:38     ` Hans
2005-09-27 19:10       ` Isaque Galdino
2005-09-27 20:13         ` David Given
2005-09-27 20:30           ` Dan Olson
2005-09-27 21:06           ` Hans
2005-09-27 21:48             ` David Given
2005-09-28  2:32               ` Rex Walburn
2005-09-28 12:45               ` Javier Sedano
2005-09-27 19:30       ` Dan Olson
2005-09-28  9:29       ` jb1
2005-09-28 15:30         ` Gregg C Levine
2005-09-29  9:14           ` jb1
2005-09-28  9:51 ` Alexander van Heukelum
  -- strict thread matches above, loose matches on Subject: below --
2005-09-28 16:33 hansydelm
2005-09-28 16:48 hansydelm

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='003301c5c0eb$68f1ece0$6502a8c0@dionysus' \
    --to=hans64@ht-lab.com \
    --cc=linux-8086@vger.kernel.org \
    --cc=mike@hsol.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