<div dir="ltr">I agree, a pull request is the simplest way to do this, if available.<br><div>As well, Github's pull request system is actually really simple to newbies, so I think it would also be the easiest to learn.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 21, 2015 at 11:44 PM, Sérgio Basto <span dir="ltr"><<a href="mailto:sergio@serjux.com" target="_blank">sergio@serjux.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Sáb, 2015-12-12 at 12:56 +0100, Nicolas Chauvet wrote:<br>
> 2015-12-11 23:34 GMT+01:00 Sérgio Basto <<a href="mailto:sergio@serjux.com">sergio@serjux.com</a>>:<br>
> > On Seg, 2015-12-07 at 14:36 +0000, Sérgio Basto wrote:<br>
> > > Hi, <br>
> > ><br>
> > > On Qui, 2015-12-03 at 21:41 +0100, Nicolas Chauvet wrote:<br>
> ><br>
> ... <br>
> > > > Current priority is:<br>
> > > > 1/ setup the new infra to push git content using rfpkg-<br>
> > free/rfpkg-<br>
> > > > nonfree. (gitolite)<br>
> > > > Recently has an issue with fasClient that should be fixed now.<br>
> > Need<br>
> > > > time to work on it.<br>
> > > > 2/ Close the f23 repository for release and move to updates.<br>
> > > > 3/ Introduce new packages from the review queue. (so if you<br>
> > don't<br>
> > > > know how to help, please have a look on the review request<br>
> > queue<br>
> > > > http<br>
> > > > s://<a href="http://bugzilla.rpmfusion.org/2" rel="noreferrer" target="_blank">bugzilla.rpmfusion.org/2</a>).<br>
> > ><br>
> > > IMO also branching f23, rawhide and epel7 <br>
> ><br>
> > kwizart: people still trying fix things that can't , and the main<br>
> > thing<br>
> > for them is got git sources correct , why we don't do branch f23 ,<br>
> > do<br>
> > the mass rebuild, see <a href="http://github.com/rpmfusion" rel="noreferrer" target="_blank">github.com/rpmfusion</a> correctly and "Close the<br>
> > f23<br>
> > repository for release and move to updates." , internals things<br>
> > don't<br>
> > matter to the people , this ones makes many questions and people<br>
> > try to<br>
> > fix it (without success) Martin ask for rebuilds now Jeremy made<br>
> > f23<br>
> > branch in is own account and I don't know what to answer.<br>
> ><br>
> I don't have any issue wih people using local branch as f23 to<br>
> separate content targetted for f24 using their master branch.<br>
> But you only need to fetch the content for f23 as the current master<br>
> branch in the git preview. git checkout master && git pull remote<br>
> f23.<br>
> people will need to rebase later when the f23 branch will be created<br>
> from git preview master.<br>
<br>
</div></div>OK , someone have branched f23 in his fork, I also don't see any<br>
problem. <br>
I think, add one branch (f23) or two (f24) in git preview, seems to me<br>
a very ship operation, a rpmfusion much better organized for all, even<br>
if we don't build anything and more simplify communication to<br>
contributors, also I think I can do this branching because is just git<br>
commands . <br>
<br>
I'm thinking do one wiki page with all instructions , we already got<br>
some examples how update things ... <br>
<br>
Today and thinking in a more simpler communication, someone send a pull<br>
request to <a href="https://github.com/rpmfusion" rel="noreferrer" target="_blank">https://github.com/rpmfusion</a> . With my updating method, of<br>
fetch git remote and merge it into preview , it makes that pull request<br>
was closed !, it looks like the pull request was made, when I just<br>
update git preview. So if I could receive the notifications of the pull<br>
requests for rpmfusion, it will be much more simpler communication,<br>
contributor doesn't have to do more , I can update git and block<br>
tracker to request builds , contributor when see his pull request<br>
closed , can consult the tracker of the builds, it easy . <br>
<span class=""><br>
<br>
> I'm still having limited bandwidth, so anything else is deferred. <br>
><br>
><br>
--<br>
</span>Sérgio M. B.<br>
</blockquote></div><br></div>