Proposal forms tweaks

this issue was moved from 2018

Better order of fields + divide them into 2 sections (their names are TBD)

[Public information]
What’s your name?
What is the title of your talk?
Tell the audience about your talk in 1–3 paragraphs (90–200 words)
Language
Difficulty
Why are you the right person to talk about the topic you chose?
Your photo (not an illustration nor avatar)
Twitter handle
GitHub username

[Non-public information]
Got a video?
Your email address
I need financial aid to make this talk possible
Details about required financial aid
Anything else you want to tell us?

Better microcopy

What is the title of your talk? and Tell the audience about your talk in 1–3 paragraphs (90–200 words):
English (preffered) => English (preffered by PyCon CZ)
If you already have a recording of you giving a talk, you can paste the link here. => If you have a link to a publicly available recording of you giving a talk. Will be used in the decision process.
It will be published on the website. Ideal photo is: a head shot, shows only you, has no “filters” applied and is as large and uncompressed as possible. We might crop it and change contrast, brightness etc. to fit PyCon CZ visual style. => Ideal photo is as large (really there's no limit, please no 128 × 128 px, even 1000 × 1000 px isn’t too much) and as uncompressed as possible, is a head shot, doesn’t show other people and has no “filters” applied. We might crop it and change contrast, brightness etc. to fit PyCon CZ visual style.
Try better to explain what is required for bio.

@hroncok commented on the original issue

Why are you the right person to talk about the topic you chose?
Who are you, tel us something about you.

We could add both questions and than combine the bio used on the website ourselves. We edit all the bios anyway, so this would just give us more material.

Collect feedback on talks & workshops

Speakers/WS leaders want to know how they did & what can be improved

PyCon API

Is there any way to get any data about PyCon, like number of people etc.? It would be great for us to have these data to use them as demo in our project.

Registrace na workshopy (stavy)

možné stavy

not launched
opened
sold out
waiting list
opened for ppl on waiting list
offered
accepted
timed out

Inform speakers about accessibility considerations

Vojta, a blind Pythonista that attended last year's PyCon, shared a few notes on how to make the talks more accessible. They should be made available to speakers (maybe as part CfP, perhaps as part of some instructions on how to do a talk).

The text went to info@pyvec via @kejbaly2, don't know yet if I can share it here.

Program by měl umět speciální položky

Položky jako Snídaně apod. by měly být snadno přidatelné do programu.

Schedule design

We need to create a design we'll use for the final schedule inc workshops.

Design deadline: 2019-05-19 (a week before schedule deadline)
Implementation deadlines: 2019-05-25 (schedule going public)

Cc: @encukou

Footer is not according to design

The Do you have any questions? Contact us! text is not in mono font and my OCD finds it disturbing. Is it on purpose?

Override phase directly

Because I was so time focused I missed the obvious feature: force a phase for preview purposes by just using it’s name and value.

something like
…?phase_sponsorship=not_public&phase_ticket_sale=launched

it should set the override to that value

Prepare Fin Aid form

We need to prepare a form for Financial Aids.

It's very important to mention in the form that the form is also a good (preferred) way how to ask for a free ticket.

Deadline for PR: 31st of January
Financial Aid launch date: 4th of February

Rozběhat betu webu 2019

Ať je někde vidět, jak se to rodí.

Stav lístků zobrazovat na základě informací z API ti.to

Keynotes on homepage

We need to create a design we'll use for keynotes announcements as a part of main page (keynotes)
Design deadline: 2019-02-18 (end of CfP)
Implementation deadlines:

2019-02-25 (early birds start, keynoters going public)
2019-03-18 (talks going public)

Cc: @encukou

Preview of different phase for staff

Ad an option for previewing the website on different date for Phases app.

Should be limited for logged in users who have is_staff on production.

It should have a setting that allows this for anyone on localhost and even more on beta as we don't want to create account for everybody on the team.

I vote for get parameter with date time but there might be other solution to preview easily multiple dates even on beta without changing configuration in admin or config.

Talks’ + Workshops’ statuses

pro každý zvlášť (přidat třetí stav, měl by být jen jeden)

not public
published list (fotka, titulek ok)
published detail (abstrakt + python level ok)

celkový stav, zvlášť pro workshopy a talky, nemusí být venku zároveň (řešeno přes Phases #85)

not public
list public
details public

gzip everything

currently server doesn't gzip *.{svg,js,etc.} 😢

Udělat fixture s dummy datama

Talky, workshopy atd.

Consider secret early bird tickets as sold out

We need to have tickets available for companies paying by invoice but no more available publicly.

We can switch them to secret tickets so they should be considered the same as soldout.

Workshop: extra info pro účastníky

Sice lze napsat do popisu, ale extra pole to umožní zviditelnit.

Soubory ať si publikují na GitHubu, dáme link do extra info.

Add description to Phase

There should be an option to leave comment about meaning of each phase.

Proposal forms improvements

The issue to gather ideas about improvements of proposal forms. Basically a nice to have things which might or might not be implemented for this year.

It would be nice to have a limit of minimal words count for important parts of proposal forms (abstract, bio)

FinAid closed

remove from top menu
change copy on related pages
remove from tickets page (if present)

Proposals / Fin Aid results mass replies

Do we want to use this system to send e-mails with CfP and Finaid results?

These templates need to be updated (and make it work actually?)

accepted_aid.tpl
accepted_sprint.tpl
accepted_talk.tpl
accepted_workshop.tpl

Also there are no templates (and probably no functionality) for refused talks which would be a common courtesy to send.

Talks by měl být stejný objekt jako workshops

Nedává smysl to oddělovat, protože je skoro vše stejné a pak to jen komplikuje šablony.

Zobrazování informací na frontendu ovládáné z adminu

ručně: true/false/hodnota
automaticky: různé hodnoty dle aktuálního času (možnost override dle 1)

Připravit výchozí „prázdnou“ verzi webu

A prosím o plný práva v adminu pro mě.

Administrace obsahových stránek

Stránky jako CoC apod. by měly mít možnost snadných úprav bez nutnosti nasazování.

Ideálně to mít ne jako flatpages jako jeden text pro url, ale prostě jako nějaký snippets, terý můžem umístit na různý místa dle potřeby, mít tak snadno víc variant podle phases (řeší šablona) .

Vedlejší efekt bude i to, že ne všechny texty by měly být veřejné hned (díky GitHubu) a v db budou skryté. U něčeho je verzování asi plus, ale to přežijeme.

Možnost publikovat sponzora bez loga

Mitigate vulnerabilities

See https://github.com/pyvec/cz.pycon.org-2019/network/alerts

Team photos too large in second row

https://cz.pycon.org/2019/about/team/

The second row is always bigger. If you refresh, you get different people, but still bigger.

Sync design of main headings

IMHO every page main heading should use the same design as on Code of Conduct page:

which is not currently true

I think that the design with the brown stripe is better so I'd apply the same to other pages. Anyone against?

New design implemented

Branch facelift

Definovat jasně úroveň začátečník vs. pokročilý pro přednášky a workshopy

Jde o textovou záležitost na webu.

Lístky na workshopy: párování s účastníky

Je potřeba zajistit aby

lístky na workshopy mohli registrovat pouze účastníci
nešlo registrovat více workshopů pro jednoho účastníka na stejnou dobu

Ti.to to přímo nezvládá.

Máme řešení bez API založené na slevových kupónech.

(nutno přidat ID workshopu z Ti.to ke každému workshopu v naší db) (@benabraham)
Budeme chtít mít na detailu workshopu input pro kód lístku + tlačítko pro registraci daného workshopu (@benabraham)
Extra: Tlačítko vylepšit o to, že se místo něj zobrazí vyprodáno, pokud je vyprodáno (@mcurlej)
Extra extra: v přehledu workshopů zobrazit vyprodáno

Nekompletní talky/workshopy

Možnost uložit nekompletní talk/workshop, aby se mohl například zobrazit speaker, ale bez názvu talku a bez detailu.

Náhledová verze webu

Nevím jak přesně řešit, ale bylo by fajn mít web, kde jsou publikované nové věci ke schválení sponzory, speakery, ostatními orgy atd.

Ideálně ze stejné DB, prostě jen status, který se po schválení přepne na veřejný.

Generovat responzivní velikosti obrázků vkládaných přes admin

FinAid: stavy

Do šablon stavy: (řešeno přes Phases #85)

not launched
launched
closed
awarded

To je informace extra, aby se dalo zobrazovat v menu atd.
Je to sice duplicita s nastavením formulářů, ale ty mohou žít svým nezávislým životem.

proposals/emails/*.tpl

Not sure what to do with them: pyvec/cz.pycon.org-2018#31

Email after talk proposal submission

People do not get any acknowledgement by email when they post a CfP proposal, but according to feedback, that's something they expect. See https://pyvec.slack.com/archives/C4PPZNPDK/p1519223809000450

For 2018 we decided to send a bulk email with the closure of CfP. This is a sprint idea to make PyCon CZ great for future generations.

Supersedes pyvec/cz.pycon.org-2018#23

Položka programu by měla mít začátek i konec

jako datetime
validovat aby se ve stejné místnosti nepřekrývaly

not_public
list_public
details_public

Pokud něco není k publikaci určeno, nebudeme to do administrace dávat.

 LENGTH = (
        ('1h', '1 hour'),
        ('2h', '2 hours'),
        ('2h', '3 hours'),
        ('1d', 'Full day (most sprints go here!)'),
        ('xx', 'Something else! (Please leave a note in the abstract)')
 )

Everybody in accepted proposals has 3 hour workshop (except Caletka)

FYI @frenzymadness