elementary-dev-community team mailing list archive

[Albert Palacios <optimisme@xxxxxxxxx>]

Hi Munchor,

A contribution / bug fixing step by step guide is needed at the developers
site. There was a .pdf before the new site change, but now it is impossible
to find.

The problem with the old guide is that it encouraged to create your own
branch instead of using the ~elementary-dev-community one (this is totally
new for me). Obviously, bazaar guides doesn't teach you on using the
"elementary-dev-community".




On Mon, Aug 19, 2013 at 6:57 PM, David Gomes <david@xxxxxxxxxxxxxxxx> wrote:

> I always tell people if they make their branches owned by
> ~elementary-dev-community I will volunteer to fix the code style myself. I
> have all the free time and the will to do it, just people always make their
> branches owned by themselves.
>
> ~David "Munchor" Gomes
>
>
> On Mon, Aug 19, 2013 at 4:29 PM, Albert Palacios Jimenez <
> optimisme@xxxxxxxxx> wrote:
>
>> Hi,
>>
>> Before talking about testing, and advanced development techniques for
>> teams with resources, there is one easy and simple thing we can do to
>> accelerate development.
>>
>> Sometimes (very often), bugs are stopped due spaces not following the
>> "code style" guidelines. Adding a "code style" validator script before
>> compiling, we can prevent uploads with spaces at the end of the lines ...
>>  and save a lot of time.
>>
>> For example, just executing the next line before compiling:
>>
>> find . -type f -print0 | xargs -0 sed -i 's/[ \t]*$//'
>>
>> We will remove every "white space" at the end of any line, including new
>> lines with tab spaces.
>>
>> This can sound stupid, but it is absurd to block bug fixes during several
>> days due white spaces at the end of lines.
>>
>>
>>
>> --
>> Mailing list: https://launchpad.net/~elementary-dev-community
>> Post to     : elementary-dev-community@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~elementary-dev-community
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>