Skip to Content.
Sympa Menu

emacspeak - Re: [Emacspeak] Github Issue Threads and Mailing List

Subject: Emacspeak discussion list

List archive

Re: [Emacspeak] Github Issue Threads and Mailing List


Chronological Thread 
  • From: Robert Melton <lists AT robertmelton.com>
  • To: John Covici <covici AT ccs.covici.com>
  • Cc: "T.V Raman" <raman AT google.com>, Tim Cross <theophilusx AT gmail.com>, Emacspeaks <emacspeak AT emacspeak.net>
  • Subject: Re: [Emacspeak] Github Issue Threads and Mailing List
  • Date: Thu, 7 Mar 2024 07:09:35 -0500

https://sr.ht -- SourceHut is a place to manage code, like Github.

gh is a terminal tool for working with Github.

> On Mar 7, 2024, at 01:00, John Covici <covici AT ccs.covici.com> wrote:
>
> What is sr.ht? Also, how to use github from the command line -- never
> heard of how to do that.
>
> On Wed, 06 Mar 2024 22:34:49 -0500,
> Robert Melton (via emacspeak Mailing List) wrote:
>>
>> [1 <text/plain; us-ascii (7bit)>]
>> Not pushing for it in anyway, but just as an FYI for those interested.
>>
>> sr.ht actually is completely accessible from the command line hut
>> tool, they actually go beyond gh, as I believe every last feature of
>> the website is supported.
>>
>> Additionally, the entire website and all features work 100% without
>> javascript so the experience is eww is actually pleasant.
>>
>>
>>> On Mar 6, 2024, at 20:59, T.V Raman <raman AT google.com> wrote:
>>>
>>> 1+ on both points.
>>>
>>> A good thing about Github is that the commandline gh lets you do
>>> everything you can on the Web, and by limiting ourselves to using
>>> email for most things and using gh to close issues, we get to be
>>> relatively free of getting too tangled into the Github Web mess.
>>>
>>>
>>> Tim Cross writes:
>>>>
>>>>> For now, I'll recommend the lazy solution: do nothing, just remember to
>>>>> CC the list. Let's see how that scales.
>>>>
>>>> Always like the lazy approach!
>>>>
>>>> More seriously, I do feel this needs some carful thought. We want to get
>>>> the right balance here. I think the point about early issue discussions
>>>> often not being of much value to the list generally is quite
>>>> relevant. We don't want too much 'noise' on the list.
>>>>
>>>> Ideally, we probably want the ability to send interersting threads from
>>>> issues to the list - those which show how to solve a common problem or
>>>> those which show how people can investigate, tweak or otherwise improve
>>>> their emacspeak configuration.
>>>>
>>>> As a trial and to see how useful the list finds it, I'd agree that what
>>>> we should do is just CC the list when an issue seems worthwhile to share
>>>> with everyone.
>>>>
>>>> BTW the point Robert mentioned regarding sourcehut mayu be worth
>>>> consideration. One of the main aims of sourcehut was to have workflow
>>>> driven primarily via email instead of JS based web interfaces. Any
>>>> workflow which does not include JS dependencies is likely going to be
>>>> better from an emacs and emacspeak perspective.
>>>
>>> --
>>
>> --
>> Robert "robertmeta" Melton
>> lists AT robertmelton.com
>>
>> [2 <text/plain; UTF-8 (8bit)>]
>> Emacspeak discussion list -- emacspeak AT emacspeak.net
>> To unsubscribe send email to:
>> emacspeak-request AT emacspeak.net with a subject of: unsubscribe
>
> --
> Your life is like a penny. You're going to lose it. The question is:
> How do
> you spend it?
>
> John Covici wb2una
> covici AT ccs.covici.com

--
Robert "robertmeta" Melton
lists AT robertmelton.com




Archive powered by MHonArc 2.6.19+.

Top of Page