ubuntu-developer-manual team mailing list archive

[Belinda Lopez <belinda.lopez@xxxxxxxxxxxxx>]

On 01/26/2011 09:58 AM, Kyle Nitzsche wrote:
> Some quick thoughts on Screenshots.
>
> One issue is visual consistency.
>  * Authors may have different themes and take shots at different DPI. 
> So they don't look consistent.
>  * As I understand it, ubuntu manual team developed quick shots which 
> does this: creates a user with standard theme, sets DPI. Person then 
> takes shots that are needed for the given locale.
We can also accomplish this by publishing standard guidelines:
Create a VM with the default theme, 800*600 resolution, username: 
ubuntu-developer, desktop named: ubuntu-dev, etc.
>  * the list of missing screenshots in ub-manual is auto generated 
> based on different source 'tags'.
That is a really nice thing to have.  But I don't think we're going to 
have as many overall screenshots.
> In my option, this sounds great but it should not remove from authors 
> the requirement of taking initial screenshots: they should NOT leave 
> them blank since this creates a broken book right off the bat with 
> missing images. Also, there should never be any missing screenshots 
> and authors shouldn't need to modify source tags.
>
> It may be reasonable to work towards a dual approaches later. leverage 
> quick shots for visually consistent screenshots. But for now, authors 
> should add their own screen shots. We should have simple and clear 
> instructions; Set your system to XYZ theme. Screenshots at XYZ DPI.
>
> Another issue is where do the actual images live.
>  * in the same branch as the content? All locales? this makes the 
> content branch unnecessary large and slow to download.
>  * one option is separate author images branches: draft-images that 
> authors must put shots into. It is next to the project branch on the 
> system. the build system looks there for images, but in a fall-back: 
> first look in images-<locale> sibling branch, if not found, fall back 
> to images-en, if not found, fall back to author branch: images-draft. 
> I can implement this in doctemplate easily as needed.
In the same branch as the content.  Yes it is large to d/l the first 
time but it's only the team who will be actively downloading source - 
I'd imagine.  It's the same for any of the doc projects; d/l-ing the doc 
branch initially takes hours (or so it seems).

thanks,

Belinda

> Cheers,
> Kyle
>
>
>
>
>
>
> On 01/26/2011 10:42 AM, Rick Spencer wrote:
> > On Wed, 2011-01-26 at 09:33 -0600, Belinda Lopez wrote:
> > > Speaking of screenshots and images I think it's worth having the
> > > images/screenshots locally instead of using the process used by the
> > > manual team.  Any other thoughts on screenshots?
> > Could someone explain our options for screenshots? Thanks.
> >
> > Cheers, Rick
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~ubuntu-developer-manual
> > Post to     : ubuntu-developer-manual@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~ubuntu-developer-manual
> > More help   : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ubuntu-developer-manual
> Post to     : ubuntu-developer-manual@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-developer-manual
> More help   : https://help.launchpad.net/ListHelp

Education
Canonical
belinda.lopez@xxxxxxxxxxxxx
dinda@xxxxxxxxxx
IRC: dinda
Office: Galveston, Texas
--
Ubuntu - Linux for Human Beings
http://www.ubuntu.com
http://www.edubuntu.org	
http://www.canonical.com
---------------------------