[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-community
Subject: Re: [kde-community] Official KDE mirror on github
From: Patrick von Reth <vonreth () kde ! org>
Date: 2015-08-17 9:14:39
Message-ID: DUB109-W60D38D812D4A8E91126110F8790 () phx ! gbl
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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@kde.org
To: kde-community@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@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
[Attachment #5 (text/html)]
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div>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.</div><div><br></div><div>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?</div><div><br></div><div>Cheers,</div><div><br></div><div>Patrick <br><br></div><div>From: \
mgraesslin@kde.org<br>To: kde-community@kde.org<br>Date: Mon, 17 Aug 2015 10:14:19 \
+0200<br>Subject: Re: [kde-community] Official KDE mirror on github<br><br><pre>On \
Monday, August 17, 2015 10:10:17 AM Jos van den Oever wrote:<br>> On Monday 17 \
August 2015 09:16:02 Martin Sandsmark wrote:<br>> > On Mon, Aug 17, 2015 at \
12:35:09PM +0530, Bhushan Shah wrote:<br>> > > In my opinion first two are \
too wrong arguments to begin with.. If our<br>> > > repositories can not be \
found from outside then it requires<br>> > > improvement from our side. \
Putting source code on Github is not going<br>> > > to solve this \
problem.<br>> > <br>> > I don't think improving discoverability of our \
own infrastructure and<br>> > putting mirrors of our code on Github are \
mutually exclusive. I think both<br>> > will improve our "visibility" so to \
speak.<br>> > <br>> > > Even if people will use github to search \
projects eventually they will<br>> > > have<br>> > > to use our \
infrastructure to contribute.<br>> > <br>> > In my opinion all of our \
projects should have a short description about<br>> > how<br>> > and \
where to send us their patches, even if we don't push things to<br>> > \
Github.<br>> > If we ensure that our git repositories can be found via search \
engines<br>> > people still need to know how to contribute.<br>> <br>> \
Agree. This is a good idea regardless of mirroring on GitHub.<br>> <br>> A \
mandatory preamble in the README.md for each KDE project could go<br>> something \
like this:<br>> <br>> ==<br>> $name is a [KDE](<a \
href="https://www.kde.org/" target="_blank">https://www.kde.org/</a>) project. The \
source code for $name<br>> can be found at \
[$git.kde.org/$name](https://$git.kde.org/$name). KDE<br>> welcomes you to [join \
KDE](<a href="https://community.kde.org/Get_Involved" \
target="_blank">https://community.kde.org/Get_Involved</a>) and<br>> contribute to \
$name. You can report [issues and wishes]($git.kde.org/$name]<br>> \
(https://$git.kde.org/$name).<br>> <img style="float: right;" \
src="images/kdelogo.png" alt="KDE logo"/><br>> ==<br>> <br>> In this way, \
even if our repos are not completely indexed, the pagerank will<br>> increase a \
lot.<br> <br>and is also something we could actually install with the software.<br> \
<br>> <br>> > And I think lowering the threshold for people to contribute in \
general is<br>> > also something that should be done (and is being worked on \
already), and<br>> > is<br>> > a bit separate from this thing about \
mirroring stuff on Github.<br>> > <br>> > > And about people being \
surprised that our code is not on Github, it is<br>> > > really clear that \
Github is _not_ standard place to get open source<br>> > > software.<br>> \
> <br>> > We might think so, but I don't think the rest of the world \
agrees.<br>> > <br>> > > So, In short IMO there is nothing wrong with \
having Github mirror but<br>> > > that should be read-only and we should \
have real reason to do it.<br>> > > Currently sysadmins are reworking our \
git infrastructure. So lets wait<br>> > > little bit and see how it goes and \
then think of this.<br>> > <br>> > Yeah, I agree that the reworking of \
our own infrastructure should be<br>> > prioritized, and we should disable the \
pull requests, bug reporting, etc.<br>> > for everything we put on \
github.<br>> <br>> _______________________________________________<br>> \
kde-community mailing list<br>> kde-community@kde.org<br>> <a \
href="https://mail.kde.org/mailman/listinfo/kde-community" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-community</a><br></pre><br>_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community</div> </div></body>
</html>
[Attachment #6 (text/plain)]
_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic