[kde-community] Official KDE mirror on github

[Patrick von Reth]

So I just started the process of Incubating my project and moving it to the KDE infrastructure, I gained a modest level of visibility on Github and I'm a bit afraid of losing it. So a github mirror sounds like something interesting for me as I currently still provide my own github mirror.
For some projects not for all the issue tracker on github might be a smaller barrier to report issues as it doesn't require a separate login. Would it be possible to allow github logins to phabricator for non kde members?
Cheers,
Patrick 

From: mgraesslin at kde.org
To: kde-community at kde.org
Date: Mon, 17 Aug 2015 10:14:19 +0200
Subject: Re: [kde-community] Official KDE mirror on github

On Monday, August 17, 2015 10:10:17 AM Jos van den Oever wrote:
> On Monday 17 August 2015 09:16:02 Martin Sandsmark wrote:
> > On Mon, Aug 17, 2015 at 12:35:09PM +0530, Bhushan Shah wrote:
> > > In my opinion first two are too wrong arguments to begin with.. If our
> > > repositories can not be found from outside then it requires
> > > improvement from our side. Putting source code on Github is not going
> > > to solve this problem.
> > 
> > I don't think improving discoverability of our own infrastructure and
> > putting mirrors of our code on Github are mutually exclusive. I think both
> > will improve our "visibility" so to speak.
> > 
> > > Even if people will use github to search projects eventually they will
> > > have
> > > to use our infrastructure to contribute.
> > 
> > In my opinion all of our projects should have a short description about
> > how
> > and where to send us their patches, even if we don't push things to
> > Github.
> > If we ensure that our git repositories can be found via search engines
> > people still need to know how to contribute.
> 
> Agree. This is a good idea regardless of mirroring on GitHub.
> 
> A mandatory preamble in the README.md for each KDE project could go
> something like this:
> 
> ==
> $name is a [KDE](https://www.kde.org/) project. The source code for $name
> can be found at [$git.kde.org/$name](https://$git.kde.org/$name). KDE
> welcomes you to [join KDE](https://community.kde.org/Get_Involved) and
> contribute to $name. You can report [issues and wishes]($git.kde.org/$name]
> (https://$git.kde.org/$name).
> <img style="float: right;" src="images/kdelogo.png" alt="KDE logo"/>
> ==
> 
> In this way, even if our repos are not completely indexed, the pagerank will
> increase a lot.
 
and is also something we could actually install with the software.
 
> 
> > And I think lowering the threshold for people to contribute in general is
> > also something that should be done (and is being worked on already), and
> > is
> > a bit separate from this thing about mirroring stuff on Github.
> > 
> > > And about people being surprised that our code is not on Github, it is
> > > really clear that Github is _not_ standard place to get open source
> > > software.
> > 
> > We might think so, but I don't think the rest of the world agrees.
> > 
> > > So, In short IMO there is nothing wrong with having Github mirror but
> > > that should be read-only and we should have real reason to do it.
> > > Currently sysadmins are reworking our git infrastructure. So lets wait
> > > little bit and see how it goes and then think of this.
> > 
> > Yeah, I agree that the reworking of our own infrastructure should be
> > prioritized, and we should disable the pull requests, bug reporting, etc.
> > for everything we put on github.
> 
> _______________________________________________
> kde-community mailing list
> kde-community at kde.org
> https://mail.kde.org/mailman/listinfo/kde-community

_______________________________________________
kde-community mailing list
kde-community at kde.org
https://mail.kde.org/mailman/listinfo/kde-community 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20150817/f43aa68b/attachment.htm>