From: "Hans" <hans64@ht-lab.com>
To: linux-8086@vger.kernel.org
Subject: Re: New user wanting to help
Date: Mon, 19 Nov 2007 15:34:57 -0000 [thread overview]
Message-ID: <03a601c82ac1$bffca740$6402a8c0@linux104> (raw)
In-Reply-To: 47419CEC.2050709@nc.rr.com
Jody,
You behave a bit like a little kid stamping its feet, using phrases like
"provides me precisely USD$0.00 in compensation" and "have other things to
worry about ". This is not the attitude of a GNU project site maintainer
which you volunteered for!
If you don't have the time to maintain the website, i.e. as a minimum keep
the "latest news" page up2date (which shouldn't take you more than 10
minutes) than ask somebody else to do it!
Hans
www.ht-lab.com
----- Original Message -----
From: "JBRUCHON" <jbruchon@nc.rr.com>
To: <linux-8086@vger.kernel.org>
Sent: Monday, November 19, 2007 2:25 PM
Subject: Re: New user wanting to help
> Or, as "THE site admin," I could just be human like the other 20 or so
> "site admins" and have other things to worry about beyond following links
> and editing HTML when I have bills to pay. No one here has any right to
> tell me what I "should" do when doing so provides me precisely USD$0.00 in
> compensation. I can convert that amount to Euros or CDN$ or whatever you
> happen to use if you like, but I'm pretty sure that the conversion is
> quite easily done by anyone interested in doing such.
>
> Whatever I happen to do comes from the goodness of my own heart and my
> desire to further such a project. When the priority of ELKS is trumped by
> the priority of Real Life(tm), I'll do "what I should do." Until then,
> you can either have patience and wait for me to get free time to do it
> when life permits such, you can "raise the priority of ELKS" by channeling
> compensation my way, or you can request addition to the developer list
> like I did. I'm not a project admin, so I don't have privileges to add
> new admins or developers, so don't ask.
>
> I'm sure, since they seem to still get this mailing list, that Alan Cox
> and others can back up the fact that other aspects of life can easily take
> precedence over ELKS. That, as I understand it, is what happened to them.
>
> In the meantime, please don't make demands of a free volunteer, even if
> you try to cushion it with the "I don't mean to sound like this, but..."
> preface. You may not want to sound that way, but guess what? You do.
> It's disrespectful and rude. Solutions provided above.
>
>
>
> **** tl;dr: I'll do it when time permits.
>
>
> Jody
>
>
> Hans wrote:
>>
>> ----- Original Message ----- From: "JBRUCHON" <jbruchon@nc.rr.com>
>> To: <linux-8086@vger.kernel.org>
>> Sent: Sunday, November 18, 2007 10:11 PM
>> Subject: Re: New user wanting to help
>>
>>
>>> I'm sort of the current maintainer of the site and the project, but have
>>> no access to the mailing list setup at all.
>>>
>>> I'm a fairly busy person so I don't do much without being asked to do
>>> it, and my web-fu sucks pretty bad.
>>
>> Sorry Jody, I don't want to sound nasty since I have done 0% contribution
>> myself but we shouldn't have to tell you to add a link. When somebody
>> like Bram Lohman emails the list that he has Elks running on an emulator
>> and that is it freely available to download than you as the site admin
>> should, as a bare minimum, add the link without one of us telling you to
>> do so.
>>
>> Since you are very busy (which I fully understand) can I suggest you
>> share the admin details with a few more people or better speak to Mario
>> to get a wiki page added.
>>
>> Back to work :-)
>>
>> Regards,
>> Hans.
>> www.ht-lab.com
>>
>>
>>>
>>> If you want something in particular done, give me the resources and I'll
>>> get it done.
>>>
>>> Ben Weiss wrote:
>>>> --- Hans <hans64@ht-lab.com> wrote:
>>>>
>>>>> I am a bit disappointed that Rask Lambertsen's GCC
>>>>> port and the Dioscuri emulator (which runs ELKS!) are not mentioned on
>>>>> the
>>>>> website, come on guys, it can't be that much work to add some
>>>>> hyperlinks...
>>>>
>>>> This seems like the easiest thing to fix first, and
>>>> makes the project "look" better, so I'd be happy to
>>>> provide some updates to the site. Not too much for
>>>> now, just keeping with static pages- fixing broken
>>>> links, adding some (ie Rasks's port), etc. Does anyone
>>>> know who needs to be contacted to update the archive
>>>> mentioned on vger.kernel.org? Is this list still even
>>>> being archived, or do we have to "sign up" for it? (If
>>>> so, gmane comes to mind...)
>>>>
>>>>> Compiling ELKS under GCC is not going to be
>>>>> easy but IMHO will be very beneficial for the wider embedded user
>>>>> community and
>>>>> hence will/might increase the popularity of ELKS.
>>>>
>>>> Sounds like great minds think alike :)
>>>> Not only is GCC much more popular and continuously
>>>> maintained, but apparently GCC (GAS, rather) uses AT&T
>>>> syntax, and BCC uses Intel syntax. Since Linux uses
>>>> GCC, it follows that modifying/porting to ELKS would
>>>> be easier if we also use GCC. -Ben
>>>>
>>>>
>>>>
>>>> ____________________________________________________________________________________
>>>> Get easy, one-click access to your favorites. Make Yahoo! your
>>>> homepage.
>>>> http://www.yahoo.com/r/hs -
>>>> 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
>>>>
>>> -
>>> 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
>>>
>>
>>
>> -
>> 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
>>
> -
> 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
>
next prev parent reply other threads:[~2007-11-19 15:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 3:46 New user wanting to help Ben Weiss
2007-11-17 11:14 ` Hans
2007-11-17 16:18 ` Sebastian Rosenkiewicz
2007-11-18 22:01 ` Ben Weiss
2007-11-18 22:11 ` JBRUCHON
2007-11-19 9:35 ` Hans
2007-11-19 14:25 ` JBRUCHON
2007-11-19 14:52 ` Mario Frasca
2007-11-19 14:56 ` JBRUCHON
2007-11-19 15:04 ` Mario Frasca
2007-11-19 15:15 ` Mario Frasca
2007-11-19 15:22 ` JBRUCHON
2007-11-19 15:34 ` Hans [this message]
2007-11-19 15:44 ` Mario Frasca
2007-11-19 15:56 ` Hans
2007-11-19 15:53 ` JBRUCHON
2007-11-18 23:02 ` Mario Frasca
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='03a601c82ac1$bffca740$6402a8c0@linux104' \
--to=hans64@ht-lab.com \
--cc=linux-8086@vger.kernel.org \
/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