Giter Site home page Giter Site logo

cz.pycon.org-2019's People

Contributors

baradrb avatar benabraham avatar dariagrudzien avatar darkless012 avatar doupalovakris avatar encukou avatar frenzymadness avatar giraafje avatar honzajavorek avatar hroncok avatar ivafingerova avatar magwit avatar mcurlej avatar messa avatar mikicz avatar ninabel avatar starenka avatar torsava avatar tuttovka avatar veruu avatar webknjaz avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

cz.pycon.org-2019's Issues

Sync design of main headings

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

image

which is not currently true

image

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

  • update Bootstrap to 4.3.1
  • cleanup current markup
  • simple text pages (CoC, Privacy policy etc.)
  • Homepage: also content change
  • Venue page
  • Ostrava page
  • FinAid pages (forms + overview)
  • Team page

Programme/workshop admin doesn't allow to save 3 hour workshop

Admin shows 2 hours (can't save 3 hours).
Because of this?

 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

Menu snadněji

Menu by se měla definovat snadněji.

Nevím jestli přes admin, ale chtělo by to nějak.

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.

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

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.

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

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

Je potřeba zajistit aby

  1. lístky na workshopy mohli registrovat pouze účastníci
  2. 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

Sponsors’ status

pouze celkový stav (řešeno Phases #85)

  • not_public
  • list_public
  • details_public

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

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ý.

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.

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.

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)

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

FinAid closed

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

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.

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

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.

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.

Tickets page design

We need to create a design we'll use for a page with tickets.

Design deadline: 2019-02-18 (end of CfP)
Implementation deadline: 2019-02-25 (early birds start)

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.

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.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.