Re: developer account set up

[Konstantin Kharlamov]

On Tue, 2023-05-09 at 10:57 +0200, Johnny Jazeix wrote:
> > I remember when we were integrating Gitlab at work, people for some reason
> > were
> > attempting to create branches in the upstream repo rather than on their own
> > fork. Had to do some explanation that this isn't the way to go, because
> > after an
> > year of such workflow upstream will end up with hundreds if not thousands of
> > abandoned branches that serve no purpose, and who's gonna clean that up
> > 路‍♂️
> > Especially given that people may come and go, and so in some cases you
> > wouldn't
> > even find an author of a branch (and in some cases it's hard to even figure
> > out
> > who could be the author in the first place).
> > 
> 
> 
> The issues you mentioned are the same with forks. Instead of having abandoned
> branches in the main repo where maintainers could know if they are active or
> not, we will have abandoned branches in abandoned repositories without MR to
> know they exist and they would need to be cleaned.

A fork belongs to a user account though. That knowledge simplifies cleaning
process as for example one could send to the user a notification saying that
their fork has not seen any activity in months and asking if it's still needed.
And then in absence of answer for some determined amount of time to delete the
fork.

Re: developer account set up

[Johnny Jazeix]

Hi,
Le dim. 7 mai 2023 à 17:54, Konstantin Kharlamov  a
écrit :

> On Sun, 2023-05-07 at 17:21 +0200, Nate Graham wrote:
> > There's also no reason anymore why they need to use a work branch in the
> > main repo; a fork works just fine. I do nearly all of my development
> > using personal forks; it's a 100% supported first-class citizen
> experience.
>
> +1
>
>
Ok for me to go with forks for GSoC but as Ben said, we probably need to
find something about abandoned forks.

I remember when we were integrating Gitlab at work, people for some reason
> were
> attempting to create branches in the upstream repo rather than on their own
> fork. Had to do some explanation that this isn't the way to go, because
> after an
> year of such workflow upstream will end up with hundreds if not thousands
> of
> abandoned branches that serve no purpose, and who's gonna clean that up
> 路‍♂️
> Especially given that people may come and go, and so in some cases you
> wouldn't
> even find an author of a branch (and in some cases it's hard to even
> figure out
> who could be the author in the first place).
>

The issues you mentioned are the same with forks. Instead of having
abandoned branches in the main repo where maintainers could know if they
are active or not, we will have abandoned branches in abandoned
repositories without MR to know they exist and they would need to be
cleaned.

Cheers,
Johnny

Re: developer account set up

[Ben Cooksley]

On Mon, May 8, 2023 at 3:22 AM Nate Graham  wrote:

> There's also no reason anymore why they need to use a work branch in the
> main repo; a fork works just fine. I do nearly all of my development
> using personal forks; it's a 100% supported first-class citizen experience.
>

For those using forks, please make sure you cleanup any fork that you're
not using once you're finished with it.

This is especially relevant if you are only using it for one or two quick
changes, as GitLab only performs something known as "housekeeping" on
repositories that have a certain level of use (I think it is run every 5
pushes)

Over the weekend I executed "housekeeping" on every repository on
invent.kde.org, including the 7,000 or so forks that exist (to put that
number in perspective, we have around 11,000 repositories in total).
It resulted in the better part of 100GB being freed, and around 600,000
inodes being released - mostly due to forks that only got used a small
handful of times.


>
> Nate
>

Thanks,
Ben


>
> On 5/7/23 17:06, Joshua Goins wrote:
> >> We usually recommend contributors to create branches in the main
> repository
> >> (work/gsoc/...). Is it possible without a developer account?
> >>
> >> Johnny
> >
> > It doesn't have to be the GSoc student that creates the branches, only
> that
> > they are the ones putting commits in it. Something I've seen done is the
> > mentor creates the work branch (work/gsoc/student) and the student
> creates MRs
> > to merge their work into the branch instead of targetting master.
> >
> >
>

Re: developer account set up

[Konstantin Kharlamov]

On Sun, 2023-05-07 at 17:21 +0200, Nate Graham wrote:
> There's also no reason anymore why they need to use a work branch in the 
> main repo; a fork works just fine. I do nearly all of my development 
> using personal forks; it's a 100% supported first-class citizen experience.

+1

I remember when we were integrating Gitlab at work, people for some reason were
attempting to create branches in the upstream repo rather than on their own
fork. Had to do some explanation that this isn't the way to go, because after an
year of such workflow upstream will end up with hundreds if not thousands of
abandoned branches that serve no purpose, and who's gonna clean that up 路‍♂️
Especially given that people may come and go, and so in some cases you wouldn't
even find an author of a branch (and in some cases it's hard to even figure out
who could be the author in the first place).

Re: developer account set up

[Nate Graham]

There's also no reason anymore why they need to use a work branch in the 
main repo; a fork works just fine. I do nearly all of my development 
using personal forks; it's a 100% supported first-class citizen experience.


Nate

On 5/7/23 17:06, Joshua Goins wrote:

We usually recommend contributors to create branches in the main repository
(work/gsoc/...). Is it possible without a developer account?

Johnny


It doesn't have to be the GSoc student that creates the branches, only that
they are the ones putting commits in it. Something I've seen done is the
mentor creates the work branch (work/gsoc/student) and the student creates MRs
to merge their work into the branch instead of targetting master.

Re: developer account set up

[Joshua Goins]

> We usually recommend contributors to create branches in the main repository
> (work/gsoc/...). Is it possible without a developer account?
> 
> Johnny

It doesn't have to be the GSoc student that creates the branches, only that 
they are the ones putting commits in it. Something I've seen done is the 
mentor creates the work branch (work/gsoc/student) and the student creates MRs 
to merge their work into the branch instead of targetting master.

Re: developer account set up

[Johnny Jazeix]

Le dim. 7 mai 2023 à 11:22, Nate Graham  a écrit :

> -Utarsh
>
> It might be worth re-thinking this policy now that we use GitLab. People
> don't need a developer account to fully contribute anymore.
>
> Nate
>
>
We usually recommend contributors to create branches in the main repository
(work/gsoc/...). Is it possible without a developer account?

Johnny


>
> On 5/7/23 09:41, Johnny Jazeix wrote:
> >
> >
> > Le sam. 6 mai 2023 à 23:31, Nate Graham  > > a écrit :
> >
> > Hello Utkarsh,
> >
> > You don't need a developer *account* to start contributing, and in
> fact
> > you can't have one until you've made a number of contributions
> > already. :)
> >
> > If you're looking for information about starting the process of
> > contributing with code, we have a bunch of documentation at
> > https://community.kde.org/Get_Involved/development
> > .
> >
> >
> > Best of luck!
> >
> > Nate
> >
> >
> > On 5/6/23 20:42, Utkarsh Kumar wrote:
> >  > Hlw, I am Utkarsh Kumar and I want to need help creating a
> developer
> >  > account setup. so please can someone suggest to me the steps I
> > need to
> >  > follow to create a developer account?
> >
> >
> > Hi Nate,
> > Utkarsh has been selected for GSoC to work on digiKam and it's a
> > prerequisite to create a developer account do in the community bonding
> > period.
> > Cheers,
> >
> > Johnny
>

Re: developer account set up

[Utkarsh Kumar]

So Right now what do I need to do? Can you suggest to me anything that is
beneficial for me?

On Sun, May 7, 2023 at 2:53 PM Nate Graham  wrote:

> -Utarsh
>
> It might be worth re-thinking this policy now that we use GitLab. People
> don't need a developer account to fully contribute anymore.
>
> Nate
>
>
> On 5/7/23 09:41, Johnny Jazeix wrote:
> >
> >
> > Le sam. 6 mai 2023 à 23:31, Nate Graham  > > a écrit :
> >
> > Hello Utkarsh,
> >
> > You don't need a developer *account* to start contributing, and in
> fact
> > you can't have one until you've made a number of contributions
> > already. :)
> >
> > If you're looking for information about starting the process of
> > contributing with code, we have a bunch of documentation at
> > https://community.kde.org/Get_Involved/development
> > .
> >
> >
> > Best of luck!
> >
> > Nate
> >
> >
> > On 5/6/23 20:42, Utkarsh Kumar wrote:
> >  > Hlw, I am Utkarsh Kumar and I want to need help creating a
> developer
> >  > account setup. so please can someone suggest to me the steps I
> > need to
> >  > follow to create a developer account?
> >
> >
> > Hi Nate,
> > Utkarsh has been selected for GSoC to work on digiKam and it's a
> > prerequisite to create a developer account do in the community bonding
> > period.
> > Cheers,
> >
> > Johnny
>

Re: developer account set up

[Nate Graham]

-Utarsh

It might be worth re-thinking this policy now that we use GitLab. People 
don't need a developer account to fully contribute anymore.


Nate


On 5/7/23 09:41, Johnny Jazeix wrote:



Le sam. 6 mai 2023 à 23:31, Nate Graham > a écrit :


Hello Utkarsh,

You don't need a developer *account* to start contributing, and in fact
you can't have one until you've made a number of contributions
already. :)

If you're looking for information about starting the process of
contributing with code, we have a bunch of documentation at
https://community.kde.org/Get_Involved/development
.


Best of luck!

Nate


On 5/6/23 20:42, Utkarsh Kumar wrote:
 > Hlw, I am Utkarsh Kumar and I want to need help creating a developer
 > account setup. so please can someone suggest to me the steps I
need to
 > follow to create a developer account?


Hi Nate,
Utkarsh has been selected for GSoC to work on digiKam and it's a 
prerequisite to create a developer account do in the community bonding 
period.

Cheers,

Johnny

Re: developer account set up

[Johnny Jazeix]

Le sam. 6 mai 2023 à 23:31, Nate Graham  a écrit :

> Hello Utkarsh,
>
> You don't need a developer *account* to start contributing, and in fact
> you can't have one until you've made a number of contributions already. :)
>
> If you're looking for information about starting the process of
> contributing with code, we have a bunch of documentation at
> https://community.kde.org/Get_Involved/development.
>
>
> Best of luck!
>
> Nate
>
>
> On 5/6/23 20:42, Utkarsh Kumar wrote:
> > Hlw, I am Utkarsh Kumar and I want to need help creating a developer
> > account setup. so please can someone suggest to me the steps I need to
> > follow to create a developer account?
>

Hi Nate,
Utkarsh has been selected for GSoC to work on digiKam and it's a
prerequisite to create a developer account do in the community bonding
period.
Cheers,

Johnny

Re: developer account set up

[Nate Graham]

Hello Utkarsh,

You don't need a developer *account* to start contributing, and in fact 
you can't have one until you've made a number of contributions already. :)


If you're looking for information about starting the process of 
contributing with code, we have a bunch of documentation at 
https://community.kde.org/Get_Involved/development.



Best of luck!

Nate


On 5/6/23 20:42, Utkarsh Kumar wrote:
Hlw, I am Utkarsh Kumar and I want to need help creating a developer 
account setup. so please can someone suggest to me the steps I need to 
follow to create a developer account?

developer account set up

[Utkarsh Kumar]

Hlw, I am Utkarsh Kumar and I want to need help creating a developer
account setup. so please can someone suggest to me the steps I need to
follow to create a developer account?