← Back to team overview

gwibber-team team mailing list archive

Re: Coding standards

 

I believe that most of us in the Gwibber team favor two-space
indentation. I personally think that it's much more conducive to
readability. The parts of the code base that use standard four-space
indentation should probably be changed to two-space, but it can be done
incrementally as needed.

Aside from that, we don't really have any official standards. I don't
object to a lack of consistency on other matters and I generally think
it's fine to let individual contributors write code in the manner that
they are most comfortable with.

I'm open to having further discussion on this issue if you or others on
this list have additional feedback or feel differently. If you think
that the lack of consistency is creating a barrier to entry for
potential contributors, then it might be worthwhile to consider more
rigid guidelines.

-- Ryan

On Wed, 2009-05-06 at 22:55 +0100, Graham Binns wrote:
> Hi guys,
> 
> My contributions to Gwibber have so far been limited to bug filing and
> triage, and I've been looking to get more involved with actual coding.
> 
> However, I'm slightly puzzled by the coding standards in the Gwibber
> codebase. Some files (for example bin/gwibber) stick to basic PEP 8 [1]
> guidelines whilst others don't (most obviously by using 2-space
> indents). Which guidelines should I be following? Is there any reason
> for the code not to follow PEP 8 (which is generally a pretty good set
> of guidelines)?
> 
> If it's something that everyone else is interested in, I'm happy to
> create a branch that brings everything into line with a given set of
> coding standards.
> 
> OTOH, if the files should stay as they are then fair enough, and I'll
> just stick to the implied guidelines on a per-file basis.
> 
> Cheers,
> 
> Graham
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~gwibber-team
> Post to     : gwibber-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~gwibber-team
> More help   : https://help.launchpad.net/ListHelp




Follow ups

References