[Pypentago-devel] The future of pypentago
Status: Pre-Alpha
Brought to you by:
segfaulthunter
From: Florian M. <flo...@ai...> - 2008-08-06 23:41:07
|
Dear pypentago developers, I just completed refactoring the pypentago code-base to make use of the new actions module I have written. It enables us to exchange the UI of pypentago more easily. As the current user-interface is not the best one, this could give us the opportunity to make a better way. Because I am not that skilled in user-interface design, as you can tell from the current interface, I think we could make use of a seasoned user-interface programmer. Secondly, I have to talk about worse news. You might not have noticed, as I am currently the de-facto only committer to the repository, but it is down pretty often: [ gna/pypentago/trunk ] % svn update ssh_exchange_identification: Connection closed by remote host svn: Connection closed unexpectedly I get this pretty often and I am pretty annoyed by it. It also ruined todays commit I did using git-svn, as I *really* like the branching of DVCS. This all boils down the the question of whether we should switch to a new repository. We could still keep our bug-tracker at Gna! or wherever we want it to be, but I, personally, would really support opening up a Git or Mercurial repository for pypentago. There are good and free locations where you can put up your Git or Mercurial repository, being http://gitorious.org and http://bitbucket.org, respectively. I really ask you to, if you have time, install both Git and Mercurial and play around with them locally. As they are DVCS you do not need a central repository to try out all the stuff. Thirdly I am telling you that I am not going to be available starting from the following Wednesday for about one-and-a-half week. If you don't know what to do, you can always try to improve pypentago.server.rooms if you want, as at the moment it only is a blueprint. Best regards, Florian Mayer PS: If you have time to review the changes I have recently done, please tell me what you think. -- GPG Key ID: BC0FFB31 Blog: http://segfaulthunter.blogspot.com/ |