[Dev] Request-4-Opinion: marking deactivated git repos

MyungJoo Ham myungjoo.ham at samsung.com
Thu Dec 29 04:51:03 GMT 2016


> On Thu, 29 Dec 2016 04:29:28 +0000
> MyungJoo Ham <myungjoo.ham at samsung.com> wrote:
> 
> what we do in enlightenment upstream is we literally rename "dead"
> repositories. we also mark them clearly in description:
> 
> https://git.enlightenment.org/
> 
> look at "Legacy". we do this so code is available if someone wants to
> dig through it, but it:
> 
> 1. is clear by description and/or PATH to git repo that its legacy
> (old/dead).
> 2. it will force good old build scripts to break - thus informing
> whoever runs such tools by way of their build breaking that things have
> moved/changed.
> 
> so i agree that it'd be good to rename and change descriptions when a
> repository is abandoned. we should reduce the number of repos perhaps
> in the process.

Renaming may incur problems with build processes targetting old Tizen versions.

I wish we've never renamed any active git repositories; but we've already
committed such sins. Therefore, there are a lot of git repos that are
used by some build projects while not supposed to get any attention from
code writers.

Thus, renaming (or moving) git repos might need some aliasing (e.g., symbolic
links) so that developers might be able to distinguish them quickly
while obsolete build systems (for obsolete projects) may keep access them.


> 
> > Dear All Tizen Developers,
> > 
> >  
> > 
> > When we access a git repo (via gitweb with review.tizen.org or
> > git-clone), it is hard to know whether
> > 
> > the git is used or not.
> > 
> >  
> > 
> > Determining the activation based on the recent commit date doesn't
> > work because some repositories
> > 
> > are actively used by build system while not getting new commits.
> > 
> >  
> > 
> > It is possible to determine by carefully looking at the data in
> > build.tizen.org or download.tizen.org.
> > 
> > However, it is not that effective and it is easy to make a mistake.
> > 
> > (Taking several minutes to (unreliably) find out that the git is
> > there but not used? It's seriously wrong.)
> > 
> >  
> > 
> > So, wouldn't there be a nice mechanism to let developers (especially
> > new to that git repo or that part of Tizen)
> > 
> > know that a specific git getting their attention is no more used?
> > (I'm occasionally getting comments on my commits
> > 
> > from maintainers that those git are not used anymore...)
> > 
> 


More information about the Dev mailing list