[gpodder] Re: Your turn to contribute to gPodder: How to submit a patch ;)
- From: Zachary Lombardo <zacharylombardo@xxxxxxxxx>
- To: gpodder@xxxxxxxxxxxxx
- Date: Thu, 26 Jul 2012 11:50:18 -0400
Ok, I will do that.
Can I share a Google Doc with you? I want to make sure you agree with my
corrections. I also have many comments which are questions to help me
better understand. I think the questions I ask are good hints to where the
manual can be more specific.
On Thu, Jul 26, 2012 at 11:40 AM, Thomas Perl <th.perl@xxxxxxxxx> wrote:
> Hi Zachary,
>
> 2012/7/26 Zachary Lombardo <zacharylombardo@xxxxxxxxx>:
> > I am interested in editing the user manual. Where/how do I submit my
> > changes?
>
> Thanks for wanting to help out! You can start by registering an
> account on wiki.gpodder.org. Then you can simply edit the User manual
> page like a normal Wiki page:
>
> http://wiki.gpodder.org/wiki/User_Manual
>
> Thanks,
> Thomas
>
> > On Thu, Jul 26, 2012 at 7:00 AM, Thomas Perl <th.perl@xxxxxxxxx> wrote:
> >>
> >> Hi,
> >>
> >> Now that 3.2.0 is out, I'll probably not spend too much time on new
> >> things on gPodder for the next few weeks (August mostly, having to
> >> work on some other project). But! This would be a great opportunity
> >> for you guys to get involved a bit more in the project :) We've had
> >> some great contributions in this release, and I hope this trend
> >> continues with the upcoming gPodder release.
> >>
> >> I'm happy to offer mentoring, answering questions about the codebase
> >> or Python itself and reviewing and commenting on patches.
> >>
> >> Here's how to get started contributing code:
> >>
> >> - Search for something you'd like to work on at
> http://bugs.gpodder.org/
> >> - If this is your first patch, pick something small/easy to work on
> >> - Send a mail here and/or comment on the bug report
> >> - Checkout the "master" branch from Git: http://gpodder.org/wiki/Git
> >> - ...hack, hack, hack...
> >> - "Fork" https://github.com/gpodder/gpodder on Github and upload your
> >> changes
> >> - Submit a pull request on Github to gpodder/gpodder's master branch
> >> - Mention the pull request ID / URL in the bug report you're working
> >> on as comment
> >>
> >> Of course, don't forget that you don't need to be a coder to contribute:
> >>
> >> - We need someone to review and clean up the user manual:
> >> http://gpodder.org/wiki/User_Manual
> >> - We need more translations (and updated ones):
> >> https://www.transifex.com/projects/p/gpodder/
> >> - Having a string review over the translation file and figuring out
> >> where we can merge strings and/or have a better wording would also
> >> help
> >>
> >> If you have any questions or need help getting started, feel free to
> >> ask here on the mailing list :)
> >>
> >>
> >> Thanks,
> >> Thomas
> >>
> >
> >
> >
> > --
> > Zachary Lombardo
> > About Me
> > zacharylombardo@xxxxxxxxx
> >
>
>
--
Zachary Lombardo
About Me <http://about.me/zacharylombardo>
zacharylombardo@xxxxxxxxx
Other related posts:
