[Xastir-dev] Lots of good info hidden in the pull request discussions

Wed Apr 17 09:13:49 PDT 2019

I guess I'll say "never mind" on my last message. Found this:

https://help.github.com/en/articles/watching-and-unwatching-repositories

Which left me with a question about repo's people _didn't_ have push access
to. Then went to Tom's Xastir fork (one that I don't have push access to)
and saw that the "Watch" tab at the top allowed me to set any of four
options. So... Anyone interested in a repo can "Watch" it if they want...
We don't need a separate mailing list for that.

On Wed, Apr 17, 2019 at 8:16 AM Curt Mills <curt.we7u at gmail.com> wrote:

> Found this:
>
>
> https://help.github.com/en/articles/about-email-notifications-for-pushes-to-your-repository
>
> Step 4 talks about putting up to two email addresses there, one of which
> can be a mailing list. Would then have to authorize reception of Github
> messages on the mailing list side.
>
> This would be a new mailing list for folks that wanted to see all changes
> to the repo, like we used to have with SourceForge. One list for
> xastir/Xastir and perhaps one for xastir/Xastir-Qt after it is split out.
>
> Any interest?
>
>
> On Tue, Apr 16, 2019 at 8:45 AM Curt Mills <curt.we7u at gmail.com> wrote:
>
>> That all makes sense, although to many of us finding things in email is
>> easier, until perhaps we get used to Git and Github tools. I'm not using
>> Git every day like you are.
>>
>> I also think back when we had no central repo, then CVS at Univ. of
>> Virginia, CVS on Sourceforge, SVN on Sourceforge, Git on Github... Our repo
>> keeps moving while email remains standard. I do agree with you that
>> specifics about Pull Requests should be on Github, same for specific Issues.
>>
>> Is there a way though to have a read-only list that's written to by
>> Github but doesn't report back to Github? Like the change list we used to
>> get from Sourceforge.
>>
>>
>> On Tue, Apr 16, 2019 at 8:38 AM Tom Russo <russo at bogodyn.org> wrote:
>>
>>> On Tue, Apr 16, 2019 at 08:15:22AM -0700, we recorded a bogon-computron
>>> collision of the <curt.we7u at gmail.com> flavor, containing:
>>> > For those interested in learning more about Git and how the whole
>>> > fork/pull-request thing works, a lot of good info is hidden away in the
>>> > Xastir pull requests on Github.
>>> >
>>> > I kind'a miss the larger development discussions that used to happen
>>> here
>>> > on this mailing list. Maybe the Github discussions could be piped over
>>> here
>>> > too, even if read-only? I haven't seen a way to do that yet.
>>>
>>> We shouldn't be carrying on tangential discussions in pull requests,
>>> really.
>>> We got carried away with commentary on #61, which would have been better
>>> kept in email.  General discussion of how to do things in Git isn't what
>>> pull request conversations are for.  That would be a good thing for this
>>> list
>>> (or the users' list) instead.
>>>
>>> I have a real problem with discussing specific issues related to a pull
>>> request (which should be focused on the real changes proposed in the
>>> pull
>>> request) anywhere but on Github --- by keeping it there, we encapsulate
>>> the entire thread in one place so that all commentary appears in one web
>>> link,
>>> and by referring to the pull request and issue (if any) by number (#61)
>>> in
>>> commit messages, we maintain a link between commits and tracked issues
>>> in a
>>> clear and searchable way on github.
>>>
>>> It is extraordinarily painful for me to search for discussions about
>>> Xastir changes in old emails (I have Xastir emails dating back
>>> almost 18 years) --- sure, there are email archives on line, but they're
>>> not easily searchable.  It is much, much easier for me to search git
>>> history using git commands.  If git history is linked to github issues
>>> and
>>> pull requests (as it automatically is if we use the issue number and pull
>>> request number), then it becomes a piece of cake.  And I look back in
>>> history
>>> a lot in attempt to figure out why and how certain changes were made.
>>> Trying
>>> to sync those changes with emails from the same period is nearly
>>> impossible.
>>>
>>> So my preference is to keep all discussion of specific proposed changes
>>> (where
>>> the proposal is actually done in a concrete pull request) in the pull
>>> request
>>> system.
>>>
>>> I would also like to see specific bugs opened as tracked issues on github
>>> as well, because you can discuss the issue in an encapsulated manner
>>> right
>>> there and tie those directly to pull requests when a real fix is found.
>>>
>>> I would rather keep emails for general discussion, and not mix up the
>>> two.
>>>
>>> --
>>> Tom Russo    KM5VY
>>> Tijeras, NM
>>>
>>>  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
>>> [n-z][a-m]
>>>
>>> _______________________________________________
>>> Xastir-dev mailing list
>>> Xastir-dev at lists.xastir.org
>>> http://xastir.org/mailman/listinfo/xastir-dev
>>>
>>
>>
>> --
>> Curt, WE7U        http://we7u.wetnet.net
>> http://www.sarguydigital.com
>>
>
>
> --
> Curt, WE7U        http://we7u.wetnet.net
> http://www.sarguydigital.com
>

-- 
Curt, WE7U        http://we7u.wetnet.net        http://www.sarguydigital.com