View Full Version : Aeon Stark on github. (All in for the orientation lecture)
Just an idea. It'd be nice to track and test changes and bugfixes live. Nice for downloading and very useful also for translators, documentation, etc.
Some people asked for online docs. Some others posted patches or temporal solutions (till Auriga comes out), I'm sure Duncan already corrected some bugs, or added some features (Russian lang. for example).
Should we copy from here and there, following all the threads and so on?
Wouldn't it be better to take advantage of github, bitbucket, etc, for innumerable reasons?
I'm sure I sound like a complete Neanderthal saying this, but I actually prefer doing things purely through the forum. Means I only have to keep my eye on one place.
I'm just talking about the code, Ducan, not the requests or discussions, etc.
Now, you use mediafire or whatever, and you'll update that somewhen. But the code could be in a versioned public repository, available with the patches already submitted, ready for download or update by us, users.
For translators, we can make a diff and see what strings have changed or been added since last strings.xml. For commiters (Aeon Group ?), an easy and friendly environment to track everything. For users, better testing, since the beginning (maybe a patch to solve some problem isn't working the way it should, etc).
But ok, you should use svn, git, mercurial or whatever (quite useful and not that hard).
Anyway, I won't insist further. But it's just the code, for everything else, this forum is nice.
PMKnecht
2009-04-01, 16:15
+1 for putting the Skin/Code to SVN. Makes it a lot easier to update/maintain get fixes faster for testing
For Bugs&Feature Request:
Habe a look at vBulleting Project Tools Addon. It would integrate directly into the Forums (XBMC is using vBulletin) and would make handling of all this stuff a lot easier.
Link:
http://www.vbulletin.com/forum/project.php?projectid=1
Peter
Batemann
2009-04-01, 17:10
I think that a developer doesn't want to learn new tooling or a "new way of working", especially in this stage of the development. SVN is commonly used around here, DJH chose not to use that. I think DJH is focused om getting this beast finished. ;-)
as far as i remember, aeon was initially intended to be updated through svn in the 'original' readme, at least after the alpha stage and once in beta, or am i wrong?? so, +1 for a svn repository, now or at least after auriga (which should be the real 1.0) :)
Yes, I'm proposing a new way of working, a better one, I guess. I know it could sound counterproductive, right now, half the way. But I think it could speed things up.
I was proposing github cause it's free for opensource projects and cause it rocks :) , but svn is ok.
You know, I've done the Spanish translation. I found the new strings.xml (Stark release) on a post by Duncan linking to a dropbox file on page 8 of one thread here.
If Duncan or the Aeon Group says this is the way to do things, that's ok. You've done this amazing work and I'll agree. I feel grateful, after all.
I'm only pointing out there are better ways to do this kind of things, that the tools are out there (for free) and that this tools aren't hard to use.
msaspence
2009-04-03, 18:21
I vote svn too
I'ld love to (and having started) making some patches
Would be great to be able to create and merge different branches
so people with mods don't have to worry as much about updates
we can use the forum as a dialog on which make it into the trunk
it might be a bit more work initially but it makes submitting and integrating patches much easier, so more people can contribute and therefore more gets done
I actually spent about three hours last night getting my head around gtihub, only for it to crash repeatedly when trying to pull from the remote repository, and throw up an error when trying to push. I'm sure this is a problem with my setup as much as anything, but the point is that those were three hours wasted. So unless someone can explain what went wrong in precise terms, without need for a lengthy back-and-forth period of diagnosis and resolution, then I won't be returning to it for a while yet.
As has been rightly pointed out already, I don't have the time to work on designing and coding the remaining parts of Aeon while simultaneously getting to grips with entirely new ways of hosting and maintaining it. So yes, I appreciate the usefulness of SVN and git, but right now the transition would be an impediment.
Well, following an eloquent and useful PM from dedaluz I gave it another try, and it's just finished its first successful commit. I still don't have a f'ing clue what I'm supposed to do next but it seems logical enough.
Here it is:
http://github.com/djh/aeon/tree/master
I don't know if that's of any use to anyone or if I need to do anything more. I'm sure someone will tell me, though. :rofl:
pletopia
2009-04-03, 21:21
okay .. so you guys got what you wanted .. now can someone explain to djh (and me) how to frackin' use git :)
I think I've sussed it, actually. Come on - catch up! :nerd: