← Back to team overview

quickshotdevs team mailing list archive

Re: Quickshot planning and structure

 

On Wed, Mar 10, 2010 at 12:28 PM, Tommy Brunn <tommy.brunn@xxxxxxxxx> wrote:
> Welcome everybody to the Quickshot mailing list. Since we're all pretty
> much on opposite sides of the earth, I figured this would be a more
> reliable mode of communication than to try to catch each other on IRC.
>
> I wanted to talk about the current structure of the Quickshot
> development team and the plans we have for the future of Quickshot.
>
> The only information that we have written down about what we want
> Quickshot to be and how it should work is horribly out of date and
> frankly just not that relevant anymore. At least the technical
> specification needs to be updated to reflect the current state of
> things. I wouldn't mind doing it personally, but sadly I just don't know
> the specifics of how everything is going to work.
>
> Therefore I would like someone to go ahead and write down the short
> version of how stuff should work, and what things we still need to
> figure out.
>
> Examples that come to my mind are:
> - Server-client communication.
Currently, quickshot can upload screenshots to a server maintained by
Red_Hamsterx (Neil) and can retrieve a list of screenshots already
made (meaning that someone uploaded that screenshot already, not that
it has been approved)

> - Storing screenshot information on the server (things like whether or
> not it should be a full screenshot or just a portion of the screen, what
> applications should be running, etc.)
This is something we still need to discuss.

> - Moderation of submitted screenshots.
I think we went with the following: the screenshots will be first
uploaded and then someone can review them. If they're good, the
reviewer will add them in the ubuntu-manual-screenshots project.

> - Listing needed screenshots.
This is also something that needs to be discussed. This can be taken
together with the screenshot information from above.

> - Level of screenshot automation (should we launch the needed
> applications for the user? Should we change the language automatically?
> Etc.)
Changing the language would only work for running new applications and
not for the whole desktop, so this won't be usable for full screen
screenshots or from gnome-panel or other similar apps.
As for the launching of applications: we could include what app to run
in the screenshot info, although I would focus first on the basic
functionality like retrieving what screenshots still needs to be
taken.

>
> There are more things I would like to touch on, like the structure of
> the development team and the current development schedule, but as this
> message is already getting kind of long, I'll save that for later.
>
> Live long and prosper,
> Tommy Brunn
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~quickshotdevs
> Post to     : quickshotdevs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~quickshotdevs
> More help   : https://help.launchpad.net/ListHelp
>


Also, I only recently joined this project and haven't seen this yet,
but what is the time frame? I think it should be fully usable by the
end of the month?

And if I'm wrong on anything, feel free to correct me :)

-- 
Simon Vermeersch



References