Re: [PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests

2023-09-04 Thread Christian Heusel
On 23/09/02 01:24AM, Christian Heusel wrote: > On 8/28/23 21:01, Christian Heusel wrote: > > On 8/24/23 13:08, Christian Heusel wrote: > > > On 23/08/24 01:33AM, Christian Heusel wrote: > > > > Most of our worflows have moved from mailing lists and patches to merge > > > > requests on gitlab. Until

Re: [PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests

2023-09-01 Thread Christian Heusel
On 8/28/23 21:01, Christian Heusel wrote: On 8/24/23 13:08, Christian Heusel wrote: On 23/08/24 01:33AM, Christian Heusel wrote: Most of our worflows have moved from mailing lists and patches to merge requests on gitlab. Until now amending the TU Bylaws formally requires sending patches via mai

Re: [PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests

2023-08-28 Thread Christian Heusel
On 8/24/23 13:08, Christian Heusel wrote: On 23/08/24 01:33AM, Christian Heusel wrote: Most of our worflows have moved from mailing lists and patches to merge requests on gitlab. Until now amending the TU Bylaws formally requires sending patches via mail which this amendment intends to replace w

Re: [PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests

2023-08-24 Thread Johannes Löthberg
On 24/08/2023 22.17, Polarian wrote: Because in order for the bylaws to be valid, the functionality must be supported. It is pointless allowing MR within the bylaws if you currently can't make MR isn't it? All people who have the right to propose TU bylaw amendments are currently already able

Re: [PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests

2023-08-24 Thread Johannes Löthberg
On 24/08/2023 21.58, Polarian wrote: This amendment is proposing the change from patches sent through the mailing list () to merge requests, which is possible for the endpoint to be spammed, and is very user friendly allowing anyone to do For TU bylaw amendments.  In what way do you figure that

Re: [PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests

2023-08-24 Thread Leonidas Spyropoulos
Hi Polarian On 24/08/2023 22:48, Polarian wrote: > Hello, > > Sorry I am not a TU, and shouldn't really respond to said thread, but > I have a question/problem I would like to bring up. > > If you enable the merge request functionality of Gitlab, what will > stop the hundreds (potential thousands)

Re: [PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests

2023-08-24 Thread Johannes Löthberg
(Sorry for double-sending, I fucked up the reply recipients.) On 24/08/2023 21.48, Polarian wrote: If you enable the merge request functionality of Gitlab, what will stop the hundreds (potential thousands) of people who want to contribute to the official repositories? That is entirely unrelated

Re: [PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests

2023-08-24 Thread Christian Heusel
On 23/08/24 01:33AM, Christian Heusel wrote: > Most of our worflows have moved from mailing lists and patches to merge > requests on gitlab. Until now amending the TU Bylaws formally requires > sending patches via mail which this amendment intends to replace with > merge requests on the gitlab repo

[PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests

2023-08-23 Thread Christian Heusel
Most of our worflows have moved from mailing lists and patches to merge requests on gitlab. Until now amending the TU Bylaws formally requires sending patches via mail which this amendment intends to replace with merge requests on the gitlab repository. Signed-off-by: Christian Heusel --- tu-byl