Le jeudi 18 février 2016 à 21:20 +, Allan Day a écrit :
>
> > On Thu, Feb 18, 2016 at 11:08 AM Jeff F. T.
> > wrote:
> > > I have to say wow, Allan, that version of yours looks really
> > > good. Other than the bottom part (specifically the "}", the
> > > arrows and the background of some of
Hi Allan!
The concept of the release cycle infographic is really really good. For someone
like me, who is very new to GNOME and very minimally technically-versed, just
by glancing at the graphic already gives me a clear idea what happens within a
release cycle vis-a-vis the timeline and the rel
On Thu, Feb 18, 2016 at 7:30 PM Sriram Ramkrishna wrote:
> On Thu, Feb 18, 2016 at 11:08 AM Jeff F. T. wrote:
>
>> I have to say wow, Allan, that version of yours looks really good. Other
>> than the bottom part (specifically the "}", the arrows and the background
>> of some of the distributors'
On Thu, Feb 18, 2016 at 11:08 AM Jeff F. T. wrote:
> Le lundi 08 février 2016 à 18:33 +, Allan Day a écrit :
>
> […]
>
> I've had a rough go at sketching out an infographic that communicates some
> of this information. Some things are missing, and some parts are quite
> rough:
> https://dl.dr
Le lundi 08 février 2016 à 18:33 +, Allan Day a écrit :
[…]
> I've had a rough go at sketching out an infographic that communicates
> some of this information. Some things are missing, and some parts are
> quite rough: https://dl.dropboxusercontent.com/u/5031519/gnome-year-i
> nfographic.png
So
On Thu, Feb 18, 2016 at 4:20 AM Allan Day wrote:
> I think that there's more that needs adding to it. I also think that the
> graphics need updating by an actual visual designer. :)
>
>
I think we should probably try to see if we can attract one who can polish
it up to the point that it looks rea
Oliver Propst wrote:
...
> I've had a rough go at sketching out an infographic that communicates some
>>> of this information. Some things are missing, and some parts are quite
>>> rough:
>>>
>>> https://dl.dropboxusercontent.com/u/5031519/gnome-year-infographic.png
>>>
>>
> Nice done! its a (ver
On Mon, Feb 8, 2016 at 7:14 PM, Allan Day wrote:
> To be clear - I do think that a nice graphic of the release schedule would
> be useful, but it might be better to target that at coding contributors.
>
Yeah would be great to have booth resources available.
>
>
>> It might be a good exercise t
Sriram Ramkrishna wrote:
>
> That's totally acceptable as a direction. The reason I asked is that your
>> original draft looks rather engineering-focused. The release cycle is
>> interesting to engagement contributors, but I'm not sure the specifics of
>> the release schedule are the main pieces o
On Mon, Feb 8, 2016 at 10:33 AM Allan Day wrote:
> Sriram Ramkrishna wrote:
>>
>> I get that the infographic is intended for new contributors. The
>>> question was which contributors: are we talking about new engagement
>>> team recruits, or any new contributor? This will affect the kind of
>>>
Sriram Ramkrishna wrote:
>
> I get that the infographic is intended for new contributors. The
>> question was which contributors: are we talking about new engagement
>> team recruits, or any new contributor? This will affect the kind of
>> information we include.
>>
>>
> Ah, well for now I think w
On Thu, Feb 4, 2016 at 2:51 AM Allan Day wrote:
>
> I get that the infographic is intended for new contributors. The
> question was which contributors: are we talking about new engagement
> team recruits, or any new contributor? This will affect the kind of
> information we include.
>
>
Ah, well
Sriram Ramkrishna wrote:
...
>> The content seems like the most interesting thing at this stage - the
>> visuals and layout can be changed later. With that in mind, who is this for?
>> (And how will they find it?)
>
> I think this is really part of on boarding, when deciding what team does in
> th
On Tue, Feb 2, 2016, 3:29 AM Allan Day wrote:
> Jeff F. T. wrote:
>
>> Beyond the execution, details and visual polish, what do you folks think
>> of the concept in general?
>>
>> And the contents?
>>
>> FWIW, there are also alternative ways to represent a timeline generally
>> (with a circle, s
Jeff F. T. wrote:
> Beyond the execution, details and visual polish, what do you folks think
> of the concept in general?
>
> And the contents?
>
> FWIW, there are also alternative ways to represent a timeline generally
> (with a circle, spiral, serpent, or some other object metaphor). Open to
>
On Mon, Feb 1, 2016 at 11:12 AM Jeff F. T. wrote:
> Beyond the execution, details and visual polish, what do you folks think
> of the concept in general?
>
> And the contents?
>
> FWIW, there are also alternative ways to represent a timeline generally
> (with a circle, spiral, serpent, or some ot
Beyond the execution, details and visual polish, what do you folks
think of the concept in general?
And the contents?
FWIW, there are also alternative ways to represent a timeline generally
(with a circle, spiral, serpent, or some other object metaphor). Open
to any ideas.
17 matches
Mail list logo