headers
Jonathan Gordon | 1 Mar 2012 23:56
Picon
Gravatar

Reminder: Use Gerrit to submit patches/translation fixes, not flyspray

Hi all,

Please remember we have mostly switched to gerrit for patch tracking
and would like to only use flyspray for bugs. If your patches
(translations especially) are submitted to gerrit it is much more
likely they will be merged quickly (they can be done wih a single
click from the website instead of requiring a checkout, download and
apply the patch and push.)

Useful links:
http://gerrit.rockbox.org/
http://www.rockbox.org/wiki/UsingGit
http://www.rockbox.org/wiki/UsingGit#Setting_up_Gerrit

Finally, please add your full name to docs/CREDITS on the first patch
you submit.

Thanks
Jonathan
Permalink | Reply | 4 comments |
headers
Paul Louden | 2 Mar 2012 00:03
Picon

Re: Reminder: Use Gerrit to submit patches/translation fixes, not flyspray

Shouldn't we remove the "patches" category on Flyspray then, much like
we did "Feature Requests?"
Permalink | Reply | 2 comments |
headers
Jonathan Gordon | 2 Mar 2012 00:04
Picon
Gravatar

Re: Reminder: Use Gerrit to submit patches/translation fixes, not flyspray

On 2 March 2012 09:56, Jonathan Gordon <jdgordy <at> gmail.com> wrote:
> Hi all,
>
> Please remember we have mostly switched to gerrit for patch tracking
> and would like to only use flyspray for bugs. If your patches
> (translations especially) are submitted to gerrit it is much more
> likely they will be merged quickly (they can be done wih a single
> click from the website instead of requiring a checkout, download and
> apply the patch and push.)
>
> Useful links:
> http://gerrit.rockbox.org/
> http://www.rockbox.org/wiki/UsingGit
> http://www.rockbox.org/wiki/UsingGit#Setting_up_Gerrit
>
>
> Finally, please add your full name to docs/CREDITS on the first patch
> you submit.
>
> Thanks
> Jonathan

I evidently forgot how translate.rockbox.org is used. Ignore this
email (though still if you can, pushing through gerrit is
easier/faster)/

Jonathan
Permalink | Reply | 0 comments |
headers
Dominik Riebeling | 2 Mar 2012 00:10
Picon

Re: Reminder: Use Gerrit to submit patches/translation fixes, not flyspray

On Fri, Mar 2, 2012 at 12:03 AM, Paul Louden <paulthenerd <at> gmail.com> wrote:
> Shouldn't we remove the "patches" category on Flyspray then, much like
> we did "Feature Requests?"

Maybe, but more importantly the "Patches" link in the website menu
should point to Gerrit instead of Flyspray.

 - Dominik
Permalink | Reply | 1 comment |
headers
Torne Wuff | 2 Mar 2012 11:26
Picon
Gravatar

Re: Reminder: Use Gerrit to submit patches/translation fixes, not flyspray

On 1 March 2012 23:10, Dominik Riebeling <dominik.riebeling <at> gmail.com> wrote:
> On Fri, Mar 2, 2012 at 12:03 AM, Paul Louden <paulthenerd <at> gmail.com> wrote:
>> Shouldn't we remove the "patches" category on Flyspray then, much like
>> we did "Feature Requests?"
>
> Maybe, but more importantly the "Patches" link in the website menu
> should point to Gerrit instead of Flyspray.

It might be better for it to point to UsingGit instead, since patches
in Gerrit are not particularly discoverable and there is no way to
actually upload a patch there. :)

--

-- 
Torne Wuff
torne <at> wolfpuppy.org.uk
Permalink | Reply | 0 comments |
headers
Thomas Martitz | 3 Mar 2012 22:36
Favicon
Gravatar

Re: Google Summer of Code 2012 mentors ideas needed!

Am 10.02.2012 21:44, schrieb Frank Gevaerts:
> Hi all,
>
> If we want to apply to participate again to the Google Summer of Code
> 2012, we'll need more project ideas and more mentors.

No replies. I guess the desire to participate in gsoc isn't strong this 
year.

I would throw in an idea or two, if it isn't to late already. I think 
we're in need of a more dynamic skin layout system to support multiple 
screen sizes with a single skin. Multiple approaches are imaginable. 
Another nice item would be working in the playback/buffering engine to 
allow buflib allocations without intercepting playback.

On the other hand, seeing this low enthusiasm, we perhaps shouldn't 
apply at all (which would be sad IMO).

Best regards.
Permalink | Reply | 1 comment |
headers
Jonathan Gordon | 4 Mar 2012 11:17
Picon
Gravatar

Re: librbcodec

On 28 February 2012 15:22, Sean Bartell <wingedtachikoma <at> gmail.com> wrote:
> Hi, everyone,
>
> I realize I all but disappeared last summer when GSoC ended, and I'm sorry for
> leaving my work unfinished. I've spent some more time on it, and completed the
> patches that create librbcodec[0].
>
> I think it's a reasonable way of separating the DSP, metadata, and codec code
> so they can be used by other software, but I haven't gotten much feedback on my
> overall approach. Does my code have the potential to be committed?
>
> Thanks,
> Sean Bartell
>
> [0] http://gerrit.rockbox.org/r/#/q/status:open+project:rockbox+branch:master+topic:rbcodec,n,z

Hey!

As always, the most likely way of getting patches pushed is hanging out in IRC.

Jonathan
Permalink | Reply | 0 comments |
headers
Stayvoid | 4 Mar 2012 19:24
Picon

Non-free fonts

Hello.

I just want to tell you that Rockbox ships non-free fonts with it
(e.g. Helvetica).
Please remove those.

P.S. Are there any other non-free components? For example, themes.

Cheers
Permalink | Reply | 3 comments |
headers
Stayvoid | 4 Mar 2012 19:25
Picon

iPod Nano

Hello.

Do you have a plans to support the 3—5 generations of Nanos?

Cheers
Permalink | Reply | 1 comment |
headers
Paul Louden | 4 Mar 2012 19:36
Picon

Re: iPod Nano

Rockbox doesn't make plans to support any specific device. People
interested in supporting any given device do the work, or they don't.
If you don't find much information shared on a specific device in the
wiki, and not much conversation about it on IRC, it's likely work
isn't being done.
Permalink | Reply | 0 comments |

Gmane