Re: Documentation Updates

[Adam Schreiber <sadam gnome org>]

On Tue, May 12, 2009 at 10:27 AM, Paul Cutler
<pcutler foresightlinux org> wrote:
> I'll make sure bugs in the future go to seahorse-maint gnome org   Other

@gnome.bugs

The maintenance addresses are non-routeable.

Cheers,

Adam

>
> Paul
>
> On Tue, May 12, 2009 at 9:21 AM, Adam Schreiber <sadam gnome org> wrote:
>>
>> On Tue, May 12, 2009 at 10:01 AM, Paul Cutler
>> <pcutler foresightlinux org> wrote:
>> > Hi, I've started updating the docs.  I started with bug 580171, and
>> > fixed
>> > all references to "Key" and changed to "File", as well as some other
>> > minor
>> > fixes:
>> >
>> > http://bugzilla.gnome.org/show_bug.cgi?id=580171
>>
>> Hmmm ... QA contact was set to gnome-user-docs-maint gnome bugs so I
>> didn't get notified a patch was waiting for review.  Could you please
>> CC seahorse-maint gnome bugs on any of these bugs if setting docs as
>> the contact is the documentation team's policy?
>>
>> > When I submitted the patch via Bugzilla last week, I did not have git
>> > access, but now do.  I'm not sure what the etiquette is on submitting
>> > patches now that I do have git access.  Is it ok to apply, or do you
>> > prefer
>> > to review first from the patch in Bugzilla?
>>
>> I think with documentation, you can go ahead and just commit it
>> following the policies outlined in ChangeLog for commit messages.  If
>> you discover bugs in code or something that doesn't work like it
>> should and come up with a patch, at least at first post it in bugzilla
>> so we can get to know you.
>>
>> > I'm going to keep going through the docs for updated behavior and fix as
>> > needed for the 2.28 cycle.
>>
>> Sounds good.  Thanks.
>>
>> Cheers,
>>
>> Adam
>>
>> >
>> > Paul
>> >
>> > On Sun, May 3, 2009 at 5:36 PM, Adam Schreiber <sadam gnome org> wrote:
>> >>
>> >> On Sun, May 3, 2009 at 6:24 PM, Paul Cutler
>> >> <pcutler foresightlinux org>
>> >> wrote:
>> >> > I'm interested in lending the Seahorse team a hand with some
>> >> > documentation
>> >> > updates.
>> >>
>> >> Great!
>> >>
>> >> > As I find errors in the documentation, do you have a preference for
>> >> > how
>> >> > I
>> >> > file bugs?  Would one bug report that lists all of the documentation
>> >> > updates
>> >> > work, or individual bug reports?  (I plan on fixing them).
>> >>
>> >> You should create a tracking bug that depends on a bug for each issue.
>> >>
>> >> > Looking through Seahorse's Bugzilla, it looks like it is a goal to
>> >> > work
>> >> > on
>> >> > the import feature.  Are there any other application changes that
>> >> > might
>> >> > need
>> >> > updated documentation as well?
>> >>
>> >> I'm not sure which bug you're referring to.  I would guess that a
>> >> large amount of the manual is out of date and should probably just be
>> >> gone through entirely.
>> >>
>> >> Cheers,
>> >>
>> >> Adam
>> >
>> >
>
>