<html> <head> <style></style></head> <body class='hmmessage'><div dir='ltr'>Hi,<div><br></div><div>I thought that request access to a repository was simpler task.</div><div>Exists a lot of activities that the original autor, for time or any reason, gives the access</div><div>to other mantainer with the hope to help.</div><div><br></div><div>I see a lot of activities, originally writes for other people, mantained now for AC people.</div><div>How they can have access to the repos??</div><div><br></div><div>I'm agree to the point 3: "<span style="font-size: 12pt;">but, ASLO does not provide decent ways to sort out its content.."</span></div><div><span style="font-size: 12pt;">For me, not have sense create a fork for a unmantained activity (in general, for no one).</span></div><div><span style="font-size: 12pt;">If it's the same activity with only a few changes, it's better have them in the original repo.</span></div><div><span style="font-size: 12pt;">If not, you will have thousands of "same" activity: gambiarra, gambiarra-alan-patchs-for-sugar-0.96+,</span></div><div><span style="font-size: 12pt;">gambiarra-new-style-toolbars, etc.</span></div><div><span style="font-size: 12pt;"><br></span></div><div>-----------------------------------------------------------------------------------------------------------------------</div><div>Other thing. I only have this answer of original mantainer and I answer that mail without</div><div>answer on November 19 of 2013. I consider it appropriate to add to the discussion (add CC)</div><div><br></div><div><br></div><div>> From: luiz.irber@gmail.com<br>> Date: Tue, 19 Nov 2013 18:12:27 -0200<br>> Subject: Re: Gambiarra game<br>> To: alanjas@hotmail.com; gabrielgeraldo@gmail.com; alexandre@harano.net.br; fabiocpn@gmail.com<br>> CC: luiz.irber@gmail.com<br>> <br>> Hello Alan,<br>> <br>> I'm CCing the other authors.<br>> <br>> On Fri, Nov 15, 2013 at 12:15 AM, Alan Jhonn Aguiar Schwyn<br>> <alanjas@hotmail.com> wrote:<br>> > -add translations for other languages<br>> <br>> That could be a problem. Because we made the game during a Game Jam,<br>> strings are hardcoded inside images. Probably we need to refactor code<br>> and use PyGame to render text.<br>> <br>> > -add compatibility with new sugar versions<br>> <br>> > -replace OLPCGames library for SugarGames (olpcgames was<br>> > no suported).<br>> <br>> I think we used OLPCGames pretty lightly, so this should be easy.<br>> <br>> > For that, I want to continue your project and I want, if it's possible,<br>> > have access to your original GIT:<br>> ><br>> > https://git.sugarlabs.org/gambiarra<br>> <br>> I don't see any problems with that, but I would like to ask something:<br>> do any new development on branches, and then create a merge request.<br>> Gitorious UI isn't very good, but I think a merge request works like a<br>> Pull Request in GitHub, and so it is easy to review and comment<br>> changes.<br>> <br>> What do you think?<br>> <br>> Thanks for the interest!<br>> Luiz<br>> <br>> > Regards!<br>> ><br>> > Alan<br>> ></div><div><span style="font-size: 12pt;"><br></span></div><div><span style="font-size: 12pt;"><br></span></div><div><br><div>> Date: Tue, 24 Dec 2013 21:24:11 +0000<br>> From: alsroot@sugarlabs.org<br>> To: gonzalo@laptop.org<br>> CC: alanjas@hotmail.com; sugar-devel@lists.sugarlabs.org; bernie@codewiz.org; walter.bender@gmail.com<br>> Subject: Re: [Sugar-devel] Gambiarra game<br>> <br>> On Tue, Dec 24, 2013 at 12:22:14PM -0200, Gonzalo Odiard wrote:<br>> > One problem with this idea of multiple developers cloning,<br>> > having multiple versions and so,<br>> > is than we transfer to the user the complexity of deal with what activity<br>> > use.<br>> <br>> In my ming, you are messing here several points:<br>> <br>> (1) publish sources<br>> (2) publish "binaries", ie, applications ready to run<br>> (3) QAed and especially sorted out content which is the most useful<br>> for particular auditory<br>> <br>> Back to the subject activity, here, just an example:<br>> <br>> (1) I don't see any problems to have bunch on source repositories<br>> (2) I don't see any problems that every of these source repositories<br>> will be available in running form from the App Store<br>> (3) I don't see how (1) and (2) might prevent providing most appropriate<br>> content for different kinds of users<br>> <br>> The current status within the SL is that:<br>> <br>> (1) git.sl.o provides all needs, pretty enough for people who know<br>> how to use Git<br>> (2) technically, all git.sl.o repos might be uploaded to the ASLO<br>> for multiple entities, eg, Gambiarra, Gambiarra-ng, It-Is-Not-Gambiarra-You-Knew-Before<br>> (3) but, ASLO does not provide decent ways to sort out its content to<br>> meet the (3), especially for different kinds of<br>> users/usage-scenarios (the Internet is not the same as one particular country/reagion<br>> and not the same as particular school/class).<br>> <br>> Nevertheless, I don't think that current buggy status is an excuse for<br>> messing all three points, e.g., trying to keep one entity with the name<br>> "Gambiarra" on git.sl.o and App Store (ASLO). The better way for me is<br>> keeping crystal-clear picture in mind for one part of people and trying<br>> to fix it for the others.<br>> <br>> -- <br>> Aleksey<br>> _______________________________________________<br>> Sugar-devel mailing list<br>> Sugar-devel@lists.sugarlabs.org<br>> http://lists.sugarlabs.org/listinfo/sugar-devel<br></div></div> </div></body> </html>