github hygiene

github hygiene

[Henning Schild]

Hi,

this morning i had a look at the isar github site again, and it seems
to be in a pretty outdated state.
It has a ton of dead branches that should better be kept in clones of
the authors. And the issues seem like they have not been looked at for
quite some time.

I would suggest to revisit those issues and close them, and to get rid
of some of those branches. We might hardly ever look on github, but
others will. And the first impression often counts.

Henning

Re: github hygiene

[Maxim Yu. Osipov]

Hi all,

At the moment we have 4 active branches on isar github:

'next'
'mosipov-next'
'asmirnov/devel'
'ibr/devel'

We have a number of stale branches (see list below).
I'm going to archive them on our local server and after that
remove them on github. If you have any objections  please let me know.


Kind regards,
Maxim.

List of stale branches:

'develop' Updated 2 years ago by flenorm
'custom_kernel' Updated a year ago by flenorm
'custom_uboot' Updated a year ago by flenorm
'i386' Updated a year ago by flenorm
'lenormf/bincache-20170331' Updated a year ago by lenormf
'lenormf/uefi_wic_amd64-20170428' Updated a year ago by ismagulb
'lenormf/develop-l20170602-dpkg-cross' Updated a year ago by ismagulb
'asmirnov/tmp' Updated 10 months ago by alexbluesman
'asmirnov/proot' Updated 9 months ago by alexbluesman
'asmirnov/build_rep' Updated 8 months ago by alexbluesman
'build_rep' Updated 7 months ago by alexbluesman
'ibr/20171231-3-avocado' Updated 7 months ago by ismagulb
'asmirnov/next' Updated 5 months ago by jan-kiszka


On 06/28/2018 06:45 PM, Henning Schild wrote:
> Hi,
> 
> this morning i had a look at the isar github site again, and it seems
> to be in a pretty outdated state.
> It has a ton of dead branches that should better be kept in clones of
> the authors. And the issues seem like they have not been looked at for
> quite some time.
> 
> I would suggest to revisit those issues and close them, and to get rid
> of some of those branches. We might hardly ever look on github, but
> others will. And the first impression often counts.
> 
> Henning
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

Re: github hygiene

[Henning Schild]

Am Wed, 18 Jul 2018 13:00:22 +0300
schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:

> Hi all,
> 
> At the moment we have 4 active branches on isar github:
> 
> 'next'
> 'mosipov-next'
> 'asmirnov/devel'
> 'ibr/devel'
> 
> We have a number of stale branches (see list below).
> I'm going to archive them on our local server and after that
> remove them on github. If you have any objections  please let me know.

Looks good to me. I would even suggest to call mosipov-next
mosipov/devel to be consistent with the other two dev-branches.

> Kind regards,
> Maxim.
> 
> List of stale branches:
> 
> 'develop' Updated 2 years ago by flenorm
> 'custom_kernel' Updated a year ago by flenorm
> 'custom_uboot' Updated a year ago by flenorm
> 'i386' Updated a year ago by flenorm
> 'lenormf/bincache-20170331' Updated a year ago by lenormf
> 'lenormf/uefi_wic_amd64-20170428' Updated a year ago by ismagulb
> 'lenormf/develop-l20170602-dpkg-cross' Updated a year ago by ismagulb
> 'asmirnov/tmp' Updated 10 months ago by alexbluesman
> 'asmirnov/proot' Updated 9 months ago by alexbluesman
> 'asmirnov/build_rep' Updated 8 months ago by alexbluesman
> 'build_rep' Updated 7 months ago by alexbluesman
> 'ibr/20171231-3-avocado' Updated 7 months ago by ismagulb
> 'asmirnov/next' Updated 5 months ago by jan-kiszka

You could also leave tags on them, to archive them on github. Given
that will not make them show up as a "release". There might still be
value in them, maybe the people that created them should give their OK.

Henning

> 
> On 06/28/2018 06:45 PM, Henning Schild wrote:
> > Hi,
> > 
> > this morning i had a look at the isar github site again, and it
> > seems to be in a pretty outdated state.
> > It has a ton of dead branches that should better be kept in clones
> > of the authors. And the issues seem like they have not been looked
> > at for quite some time.
> > 
> > I would suggest to revisit those issues and close them, and to get
> > rid of some of those branches. We might hardly ever look on github,
> > but others will. And the first impression often counts.
> > 
> > Henning
> >   
> 
>