Hi, 

> Le 3 octobre 2017 à 20:22, Medical Wei <[email protected]> a écrit :
> 
> 
> Hi,
> 
> It sounds nitpicking but I feel unsure if DebConf 2018 is also a valid
> title.

Fair enough.  How about DebConf18 ("DebConf18 will take place in Hsinchu, 
...")?  I'm just a little uncomfortable with the phrasing of "In 2018,..." It 
feels a tiny bit awkward.  

But it is not incorrect, so I won't insist if you want to keep it as is.  

It also will be outdated in January.  Might we be sending out sponsorship 
requests in January, or will that all be done before hand?  If not, will we 
remember to change "In 2018,..." to "This year, ..."?

--
znoteer
[email protected]


> 
> Yao Wei
> On Wed, 4 Oct 2017 at 02:31 <[email protected]> wrote:
> 
> > Hi Yao Wei,
> >
> > Why are you trying to avoid saying DebConf 2018?
> >
> > --
> > znoteer
> > [email protected]
> >
> >
> >
> > > Le 2 octobre 2017 à 23:37, Yao Wei <[email protected]> a écrit :
> > >
> > >
> > > Hi,
> > >
> > > I am trying to prevent saying DebConf 2018 but use DebConf18 or In 2018,
> > > DebConf...
> > >
> > > For now if you visit https://medicalwei.github.io/debconf18-landing/
> > > this is my updated results.  Also before migrating the website to Alioth
> > > (or Salsa, if it set up quick and can serve static pages), you can send
> > > pull requests in GitHub as long as you have the account:
> > >
> > >   https://github.com/medicalwei/debconf18-landing
> > >
> > > Ciao,
> > > Yao Wei
> > >
> > > On Sun, Oct 01, 2017 at 08:17:54PM -0400, [email protected] wrote:
> > > > Hi, I had a look at the static page.  I'd like to suggest a change to
> > > > the opening sentence to make it more closely match the language used
> > > > in the flyer and brochure.  The diff is attached.  Comments are
> > > > welcome.
> > > >
> > > > The rest of the static page seems to conform to the language of the
> > > > other two docs.
> >
_______________________________________________
Debconf-team mailing list
[email protected]
http://lists.debconf.org/mailman/listinfo/debconf-team

Reply via email to