testers and reviewers for Github

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

testers and reviewers for Github

Peter Kovacs-3
Hallo all,


We have some pull request (patches) signed in on Github.

We need people to test them and sign them off.

Matthias should not sign everything on his own. I am volunteering here,
but the question is:

Who else can I count into?


All the Best

Peter



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: testers and reviewers for Github

Carl Marcum


On 4/26/20 7:05 AM, Peter Kovacs wrote:

> Hallo all,
>
>
> We have some pull request (patches) signed in on Github.
>
> We need people to test them and sign them off.
>
> Matthias should not sign everything on his own. I am volunteering
> here, but the question is:
>
> Who else can I count into?
>
>
> All the Best
>
> Peter

Hi All,

Do we have new procedures for the workflow in Github ?

For instance, do we create a branch, pull the patch, call for testers,
etc. and then if nobody objects, pull it into trunk?

I can build the office in 2 hours now if I don't run rat scan so I can
try to help out.

Best regards,
Carl


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: testers and reviewers for Github

Peter Kovacs-3
We have no process what soever. The created pull requests are stuck. I
talked with Matthias today, and we both agree that most of the pull
request should not be merged without more feedback from testers.


I would say participation is key, and we figure a workflow out on the
way. And we can also figure tests out on the way.

The minimum feedback I would like to see is that a volunteer has managed
to build the

pull request and did not find anything in the error log. And with time
we improve from that skill level.


All Ideas and input are welcome! If you hve specific Ideas please throw
them in the Ring here.


All the best

Peter


Am 26.04.20 um 14:37 schrieb Carl Marcum:

>
>
> On 4/26/20 7:05 AM, Peter Kovacs wrote:
>> Hallo all,
>>
>>
>> We have some pull request (patches) signed in on Github.
>>
>> We need people to test them and sign them off.
>>
>> Matthias should not sign everything on his own. I am volunteering
>> here, but the question is:
>>
>> Who else can I count into?
>>
>>
>> All the Best
>>
>> Peter
>
> Hi All,
>
> Do we have new procedures for the workflow in Github ?
>
> For instance, do we create a branch, pull the patch, call for testers,
> etc. and then if nobody objects, pull it into trunk?
>
> I can build the office in 2 hours now if I don't run rat scan so I can
> try to help out.
>
> Best regards,
> Carl
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: testers and reviewers for Github

Jörg Schmidt-2
Hello,

> -----Original Message-----
> From: Peter Kovacs [mailto:[hidden email]]
> Sent: Sunday, April 26, 2020 5:11 PM
> To: [hidden email]
> Subject: Re: testers and reviewers for Github
>
> We have no process what soever. The created pull requests are
> stuck. I
> talked with Matthias today, and we both agree that most of the pull
> request should not be merged without more feedback from testers.
>
>
> I would say participation is key, and we figure a workflow out on the
> way. And we can also figure tests out on the way.
>
> The minimum feedback I would like to see is that a volunteer
> has managed
> to build the
>
> pull request and did not find anything in the error log. And
> with time
> we improve from that skill level.
>
>
> All Ideas and input are welcome! If you hve specific Ideas
> please throw
> them in the Ring here.

Raphael was once an expert on these things in the project. I don't know why Raphael left the PMC, but I suppose Raphael would still be willing to help us with his experience.
Maybe it would be useful to ask him by email?



Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: testers and reviewers for Github

Patricia Shanahan
In reply to this post by Peter Kovacs-3


On 4/26/2020 4:05 AM, Peter Kovacs wrote:

> Hallo all,
>
>
> We have some pull request (patches) signed in on Github.
>
> We need people to test them and sign them off.
>
> Matthias should not sign everything on his own. I am volunteering here,
> but the question is:
>
> Who else can I count into?

Do you need me to be able to build?

I have started using Ubuntu on VirtualBox, so I can dodge the
difficulties of building on Windows.

>
>
> All the Best
>
> Peter
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

--
This email has been checked for viruses by AVG.
https://www.avg.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: testers and reviewers for Github

Carl Marcum
In reply to this post by Jörg Schmidt-2
Hi Jörg


On 4/26/20 12:45 PM, Jörg Schmidt wrote:

> Hello,
>
>> -----Original Message-----
>> From: Peter Kovacs [mailto:[hidden email]]
>> Sent: Sunday, April 26, 2020 5:11 PM
>> To: [hidden email]
>> Subject: Re: testers and reviewers for Github
>>
>> We have no process what soever. The created pull requests are
>> stuck. I
>> talked with Matthias today, and we both agree that most of the pull
>> request should not be merged without more feedback from testers.
>>
>>
>> I would say participation is key, and we figure a workflow out on the
>> way. And we can also figure tests out on the way.
>>
>> The minimum feedback I would like to see is that a volunteer
>> has managed
>> to build the
>>
>> pull request and did not find anything in the error log. And
>> with time
>> we improve from that skill level.
>>
>>
>> All Ideas and input are welcome! If you hve specific Ideas
>> please throw
>> them in the Ring here.
> Raphael was once an expert on these things in the project. I don't know why Raphael left the PMC, but I suppose Raphael would still be willing to help us with his experience.
> Maybe it would be useful to ask him by email?
>
>
>
> Jörg

Good advice is always welcome.

As the use of Git is fairly new to the project I just wanted to make
sure I hadn't missed some email or documentation on the subject.

I think as we go along a workflow process for forks, patches, pull
requests, etc. will develop organically and at some point get documented
for volunteers.

Best regards,
Carl

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: testers and reviewers for Github

Peter Kovacs-3
In reply to this post by Patricia Shanahan
Hi Patricia,


In case of any programmer that has merit, I am fine with comments.

If you can afford the time to build, it would be cool.


All the Best

Peter

Am 26.04.20 um 19:57 schrieb Patricia Shanahan:

>
>
> On 4/26/2020 4:05 AM, Peter Kovacs wrote:
>> Hallo all,
>>
>>
>> We have some pull request (patches) signed in on Github.
>>
>> We need people to test them and sign them off.
>>
>> Matthias should not sign everything on his own. I am volunteering
>> here, but the question is:
>>
>> Who else can I count into?
>
> Do you need me to be able to build?
>
> I have started using Ubuntu on VirtualBox, so I can dodge the
> difficulties of building on Windows.
>
>>
>>
>> All the Best
>>
>> Peter
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: testers and reviewers for Github

Jörg Schmidt-2
In reply to this post by Carl Marcum
Hello Carl,

> -----Original Message-----
> From: Carl Marcum [mailto:[hidden email]]
> Sent: Sunday, April 26, 2020 7:58 PM
> To: [hidden email]
> Subject: Re: testers and reviewers for Github
> Good advice is always welcome.
>
> As the use of Git is fairly new to the project

yes
 
> I think as we go along a workflow process for forks, patches, pull
> requests, etc. will develop organically

My thought was that experience in processes is also valuable, because Git is only one (interchangeable) tool



Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: testers and reviewers for Github

Peter Kovacs-3

Lets look at the "Bug fixing live cycle". Whereas everything that causes
code change I define as a bug.

My view is, broken down on a singular incident:

1) There is a unfixed Bug

2) Analysis of the Bug

3) Proposed Solution (pre Git as patch / post git as pull request / or
at all times we had branch commits)

4) Initial developer test

5) developer group sign off

6) Integration into the Code tree

7) Community Test

8) Community Sign off

9) Release

Note: After 6) we do not look at individual Bugs, more like of a group
of bugs.


Currently, we have a special Case at Situation 4. Currently we see
little to none participation in points 3 & 4.

I do not want to speculate on the reasons, I think they do not matter.
The current situation is at this low participation

the live cycle chain becomes broken. Our active times by the way are
more in the second half of a year.

Now we have 2 choices. We skip Point 4 and 5 and move the test and hope
a later stage will identify any flaws in the proposed solution.

Or we enforce 4 and 5 and risking the development halts. In order to
fight a halt I started this discussion, asking for participation.

I ask everyone who can code, but since I know there are a lot of people
whop can not code, I am open for their participation, too.

The worse thing that can happen is that they learn something. So I think
all steps are open to all at default. Everyone can describe a bug.

Everyone can propose solutions, and everyone can test the bug at
different stages.


I hesitate to criticize the Idea to contact Raphael, but for me it makes
sense if we have specific questions. If you look at his Blog, you will
see he

has changed his live substantially, and moved on. I respect that, and he
has communicated that in a open way and in my case in a clear way.

If he returns he is most welcome to participate.


And participation is all what the discussion is about. With as low entry
point as possible.


Am 27.04.20 um 06:25 schrieb Jörg Schmidt:

> Hello Carl,
>
>> -----Original Message-----
>> From: Carl Marcum [mailto:[hidden email]]
>> Sent: Sunday, April 26, 2020 7:58 PM
>> To: [hidden email]
>> Subject: Re: testers and reviewers for Github
>> Good advice is always welcome.
>>
>> As the use of Git is fairly new to the project
> yes
>  
>> I think as we go along a workflow process for forks, patches, pull
>> requests, etc. will develop organically
> My thought was that experience in processes is also valuable, because Git is only one (interchangeable) tool
>
>
>
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: testers and reviewers for Github

Keith N. McKenna
In reply to this post by Jörg Schmidt-2
On 4/27/2020 12:25 AM, Jörg Schmidt wrote:

> Hello Carl,
>
>> -----Original Message-----
>> From: Carl Marcum [mailto:[hidden email]]
>> Sent: Sunday, April 26, 2020 7:58 PM
>> To: [hidden email]
>> Subject: Re: testers and reviewers for Github
>> Good advice is always welcome.
>>
>> As the use of Git is fairly new to the project
>
> yes
>  
>> I think as we go along a workflow process for forks, patches, pull
>> requests, etc. will develop organically
>
> My thought was that experience in processes is also valuable, because Git is only one (interchangeable) tool
>
>
>
> Jörg
>
In my professional life I was a process engineer I would be more than
willing to help with that end.

Regards
Keith



signature.asc (499 bytes) Download Attachment