[gpodder-devel] Co-maintainers, gPodder team and SVN/Git
- From: paul at thegithouse.com (Paul Rudkin)
- Date: Wed, 02 Jan 2008 19:35:42 +0000
Hi Thomas
First of all, Happy New Year to you and your family.
SVN vs Git - I do not have any experience of Git, but the benefits you
highlight seem to suit the distributed development model. I'll be
interested in what others have to say, in the meantime I will do some
reading up on Git and perhaps set it up on my server so that I can
experiment with it!
I am more than willing to help out in any of the areas you have
highlighted. I am not as experienced as some of the others in the list
developing in Python / GTK / Linux so maybe I am not best suited as a
co-maintainer, however I am still learning and am willing to give it a
try if nobody else steps forward!
I have started on some documentation (locally) however with the dynamics
of some of the features right now I may stick with a version just to get
a baseline up on the Wiki.
I don't mind helping with the TODO list etc. Should we even consider a
Bug/Feature reporting system such as Bugzilla? This may help us assign
bugs/features to various developers? Just a thought?
Paul
On Wed, 2008-01-02 at 11:51 +0100, Thomas Perl wrote:
> Hello, gPodder users and developers!
>
> First of all, I wish you all a happy new year 2008. This mail is about
> maybe switching from SVN to Git and about the areas of gPodder in which
> YOUR help is needed :) The first section is about SVN/Git, the second is
> about the help-needing parts - please read at least the second one if
> time permits.
>
> -----
>
> In the last few weeks, we've seen some people on the mailing list start
> providing patches to gPodder that fulfill long-standing feature
> requests. I believe this is partially to the introduction of the wiki,
> which enables us to easily update the project status.
>
> I'm very happy with the tray icon patch that is currently in the works,
> J?r?me Chabod does a great job getting this patch forward.
>
> Some months ago, I started using Git for some projects of mine, and it
> really shines in some aspects compared to Subversion. I would like your
> input and opinion about switching gPodder development from Subversion to
> Git for some reasons:
>
> * Easier branching (would be better for "big" patches like trayicon)
> * Multiple developers (work on your patch, publish the Git repository)
> * Offline development (commits don't need an onlIf this is the general
> consensus then go for it...I must now read up on Git and give it a try on my
> home server! ine connection)
> * No server outages (BerliOS' SVN server is unavailable at times)
>
> What do you think? Should we "go Git"?
>
> ------
>
> Another area in which I need some help is maintaining gPodder, answering
> questions on the mailing list, maintaining/cleaning up the TODO list,
> taking care of the Wiki in general and reviewing/applying patches. There
> are some persons on the mailing list that have been involved
> in/following the gPodder project for some months now. I wonder if you
> want to join in and be more officially involved in gPodder by taking
> over some small areas of responsibility, like:
>
> * Taking care of the Wiki (clean-up, user documentation)
> * Answering questions on
> * Review patches and/or manage the TODO list (specifications)
> * Co-maintainership (code-wise)
>
> For the Co-maintainership, I want to add some remarks: First, the code
> style I used to write until two months ago was not adhering to PEP-8[1],
> which is the style guideline for Python. I've started writing code with
> PEP-8 in mind now, but am only updating the sections of the codebase
> that are changed for a commit. If you write Python code for gPodder,
> please take the three minutes required to read PEP-8. I will try to
> reformat your patches when needed, but reviewing and merging your patch
> will be faster when I don't need to reformat every line :)
>
> Also, for the GTK+ GUI and preferences, please keep it as simple as
> possible. I initially suggested to add six different options for the
> tray icon and notification area, but now I think this is overkill and
> not "usable". As far as the GUI design goes, we should keep the GNOME
> HIG[2] in mind where possible.
>
> Apart from that, there's not much to say about writing "good" code for
> gPodder. I would be really happy if at least one or two would step up
> and help improve gPodder.
>
> Looking at our TODO list, there is not much that is left to do to bring
> the codebase and the GUI in good shape for a 1.0 release. Maybe we
> should draft a 1.0 roadmap - that would also be a good opportunity to
> get involved in the gPodder team :)
>
> Thanks for taking the time to read this (rather long) mail :)
>
> Thomas
>
>
> [1] http://www.python.org/dev/peps/pep-0008/
> [2] http://developer.gnome.org/projects/gup/hig/2.0/
> _______________________________________________
> gpodder-devel mailing list
> gpodder-devel at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/gpodder-devel
Other related posts:
